Terminal command (omniscio chat, -q and acp)
Switch on Terminal command in Settings → Lab (the same switch also sits on the Terminal command card in Settings → CLI Control), and open a new terminal. You can now type omniscio -q "what does this repo do?" for a one-off answer, omniscio chat to talk with an agent in the terminal, or point an editor such as Zed at omniscio acp. The command only works while the Omniscio app is open, and every session it starts shows up in the app like any other.
On this page
What it is
Some work is quicker from a terminal or an editor than from the app window: a quick question, a
script that wants an answer it can read, or an editor that can host an agent panel. The omniscio
command gives all three a door into the same projects, sessions and safety rules you already use in
the app, rather than a second tool to set up.
It has no state of its own. It reads the app's sign-in key for this computer, talks to the running app, and prints what the app sends back.
Where to find it
- Switch it on: Settings → Lab → Terminal command. The Terminal command card in Settings → CLI Control is the same switch; it also shows whether the command is really on your PATH, any failure, and three examples to copy. When the app cannot read the command's status, the card says so and shows no switch, so it never shows the command as on or off without knowing.
- Open a new terminal afterwards. Terminals that were already open keep the old PATH and will not find the command.
- Windows: the command's folder is added to your own user PATH (never the system-wide one). Turning it off removes exactly that entry and leaves every other entry as it was.
- macOS and Linux: the command is linked into
~/.local/bin. If that folder is not on your PATH yet, the card says so; add it to your shell profile (for exampleexport PATH="$HOME/.local/bin:$PATH"in~/.zshrcor~/.bashrc) and open a new terminal. - Desktop only. Only the desktop app can switch the command on or off. A paired phone cannot change your PATH. An agent can ask, which raises a card you answer in the desktop app.
How it behaves
Three ways to use it:
omniscio -q "<prompt>"— asks once, waits for the agent's answer, prints it and exits. Add--project <name>to choose the project, or--engine <id>to choose the engine.omniscio chat— talks with an agent in the terminal. Type a message and press Enter./stopstops the current answer and/exitleaves. When the chat starts it prints the session id; resume later withomniscio chat --resume <session id>.omniscio acp— serves the Agent Client Protocol on its input and output, for an editor to host. It takes no options; the editor chooses the folder.
Which project. Without --project, the project is the one that contains the current folder. A
folder that is inside no Omniscio project is refused with a plain message asking you to run the
command from a project folder or pass --project.
Ordinary sessions. Every session the command starts is a normal Omniscio session in that project. You can watch it, continue it or archive it from the app.
Permission questions. When the agent asks to use a tool, the terminal asks you
Allow <tool>? [y/N] (no is the default). In an editor, the editor shows its own Allow / Deny
choice. Either way the answer counts for that one request only — it is never a standing "always
allow" — and it is recorded as your own answer.
If the connection drops, the command picks the output up again where it left off, and the final answer is always checked against what the session saved. In the terminal the saved answer is what gets printed. In an editor, before the turn ends: when part of the stream was lost or nothing streamed at all, the saved answer is sent as one more piece of the reply; when part was lost and no answer was saved, the editor is told the answer may be incomplete. Either way, if part of an answer could not be shown, the command says so and the full answer is in the app.
Connecting Zed. Add an agent server to Zed's settings.json:
{
"agent_servers": {
"Omniscio": {
"command": "omniscio",
"args": ["acp"]
}
}
}
Open a folder that belongs to an Omniscio project, then pick Omniscio in Zed's agent panel. A folder that belongs to no project is refused.
The limits worth knowing:
- The app must be running. If it is not, the command says so and exits.
- Inside an agent session the command uses that session's own limited key, never your own, so an agent gains nothing by running it, and it cannot start new sessions from there.
- Two Omniscio installs both with the command switched on: on Windows, whichever folder comes
first on your PATH wins. On macOS and Linux, a
~/.local/bin/omnisciothat belongs to another install is never removed or replaced: switching the command on here stops, the card says the command in~/.local/binbelongs to another Omniscio install, and an inbox card says the same. Turn Terminal command off in that install first, then turn it on here. - The switch off in the app: if you run the command after turning Terminal command off, it prints "The terminal command is switched off in Omniscio. Turn on Terminal command in the Omniscio app, then run this command again." rather than claiming the folder is in no project. A folder whose link leads out of its project gets the app's own explanation instead.
- App updates are handled: the small launcher is rewritten every time the app starts, so it never points at a moved file.
- If the PATH change fails — for example a Windows PATH already close to its length limit — the card says so and you get an inbox card with one click to the setting. The command is never reported as installed when it is not.
Related
- CLI control — the control server the command talks to, and where its switch lives.
- Inbuilt terminal — the terminal inside the app, for running shell commands without leaving it.
- Agents as an API — the separate OpenAI-style door for programs; the terminal command never uses it.
- Agent permission level — what an agent may do without asking, which the terminal command never raises.
Last verified 2026-11-01