OMNI-AGENT
Omni-present harness for agents
A from-scratch terminal coding agent for Windows. It talks to any
OpenAI-compatible provider (NVIDIA NIM, xKiro, MiniMax, Agnes, Atria,
Reflection, OpenRouter, local llama.cpp, Ollama, …) and runs a tool-calling agent loop with
per-tool permissions, sub-agents, self-review, layered memory, goal mode and a
live neural view. It has zero npm dependencies: pure Node ≥ 20 and the
built-in fetch.
██████╗ ███╗ ███╗███╗ ██╗██╗ █████╗ ██████╗ ███████╗███╗ ██╗████████╗
██╔═══██╗████╗ ████║████╗ ██║██║ ██╔══██╗██╔════╝ ██╔════╝████╗ ██║╚══██╔══╝
██║ ██║██╔████╔██║██╔██╗ ██║██║████╗███████║██║ ███╗█████╗ ██╔██╗ ██║ ██║
██║ ██║██║╚██╔╝██║██║╚██╗██║██║╚═══╝██╔══██║██║ ██║██╔══╝ ██║╚██╗██║ ██║
╚██████╔╝██║ ╚═╝ ██║██║ ╚████║██║ ██║ ██║╚██████╔╝███████╗██║ ╚████║ ██║
╚═════╝ ╚═╝ ╚═╝╚═╝ ╚═══╝╚═╝ ╚═╝ ╚═╝ ╚═════╝ ╚══════╝╚═╝ ╚═══╝ ╚═╝
Omni-present harness for agents
omni.globalwarningnetworks.com
What's new
The full record of every release is in CHANGELOG.md.
omni --version tells you which one you have.
3.6.3
- Connected services:
/connections, /connect [service] and
/disconnect [service] add MCP servers as services with a saved sign-in
(browser OAuth or a pasted token). Provider setup moved to /login and
/logout.
3.5.46
- Ready to share: the bundled skills that came from other projects are
credited in THIRD_PARTY_NOTICES.md, and a skill
written for Hermes Agent now tells the model which Omni tool replaces each
Hermes tool it names. Three skills that didn't belong in a public install
are gone, and the shipped config no longer runs a startup hook from a fixed
folder on
C:\.
3.5.42 – 3.5.45
- Queued prompts you can edit: what you send while Omni works shows above
the prompt box. ↑/↓ picks one to edit, send right away or delete.
- Several /commands and /skills in one prompt:
/brainstorming /python make a game loads both skills.
- Updating just works:
/update-omni runs from any PowerShell, and an
update that stopped partway finishes on the next run.
3.5.38 – 3.5.41
- Provider card:
/addprovider and /connect open one small window to
pick a provider, paste a key and choose a model by number. Omni checks that
the model answers before switching. New preset: TokenLab.
- Vision fallback: images sent to a model that can't see them go to one
that can, for that step.
- Built-in sub-agents (
explorer, reviewer, tester) ship, and the
model you picked is kept after you quit.
3.5.34 – 3.5.37
- Local AI is an install choice: none, CPU, auto or CUDA, with Spark X2.6
4B as the default local model (
/llama start).
- Security fixes: a command injection through
git_clone, API keys
reaching the model in tool results, and an XSS in the neural view.
3.5.32
- Safer with repos you just cloned: a project's
OMNI.md, AGENTS.md or
CLAUDE.md loads only once you trust its folder, its @ imports can't
reach outside the project or pull in a secrets file like .env, and the
agent treats file contents, web pages and tool output as data, never as
instructions.
Earlier releases (plan mode and /rewind, headless omni -p, hooks,
prompt templates, named sub-agents on their own git branch, scheduled runs,
/update-omni, the installer that never moves a dirty checkout, local
llama.cpp, video understanding) are in CHANGELOG.md.
Install
One line, straight from here. It checks the latest version, downloads it, and
wires up the omni command:
irm https://omni.globalwarningnetworks.com/install.ps1 | iex
Or clone it yourself:
# Requires Git and Node.js 20+
# Clone straight into ~/.omni so it matches the one-liner's default install dir
git clone https://github.com/tattooinmtl/omni.git $HOME\.omni
cd $HOME\.omni
.\install\install.ps1
omni
Both routes run the same script, install/install.ps1.
The public URL serves a small shim that fetches that file from this repo, so the
installer is always whatever is on main. The install dir is ~/.omni; pass
-InstallDir <path> for a development checkout. A git checkout updates with a
fast-forward, anything else resyncs from the branch zip. Re-running is always
safe: your .env and agent/settings.json are never overwritten.
.\install\install.ps1 # update in place (the default)
.\install\install.ps1 -NoUpdate # only report whether an update exists
.\install\install.ps1 -Force # resync every file from GitHub
The installer refuses to move a checkout with uncommitted changes, or one with
commits that exist nowhere on the remote. It names them and stops rather than
losing work.
From inside Omni, /update-omni does the same thing: it asks GitHub for the
latest version right away and, if main is newer, runs this installer and
streams its output. /update-omni check only reports. Restart Omni afterwards
to load the new code. Omni also checks once a day by itself and says so at
startup when an update is waiting.
Stuck on 3.5.41 with "Get-FileHash is not recognized"? That version's
updater fails when Omni was started from a PowerShell 7 (pwsh) terminal, and
since it is the copy you have, /update-omni can't fix itself. Update once by
hand, from any terminal:
irm https://omni.globalwarningnetworks.com/install.ps1 | iex
or start Omni from Windows PowerShell or cmd and run /update-omni there.
From 3.5.43 on, updating works from every PowerShell. If an update from
3.5.43 or older says the files moved but the installer then failed, restart
Omni and run /update-omni again: from 3.5.45 on it notices a setup that
didn't finish and runs the installer to finish it.
以上为 README 的开头部分。其余内容请阅读原文。 查看完整 README ↗
