Omniscio awareness prompt — sessions know they're in Omniscio
An on-by-default note Omniscio adds to every session's system prompt so the agent knows it is running inside Omniscio, which everyday requests are really Omniscio actions, and how to reach Omniscio's own controls to do them — what the note tells the agent, when it is skipped, and how to turn it off.
On this page
What it is
A short, on-by-default note Omniscio adds to every session's system prompt telling the agent that it is running inside Omniscio (the desktop app you use to manage your Claude Code sessions), which everyday requests are really Omniscio actions (reminders and schedules, controlling or messaging other sessions, automations, tasks and notes, settings, the inbox, and search), and how to reach Omniscio's own controls to do them. It is encouraging but judicious — the agent is told to route a request through Omniscio when it fits, not to reach for Omniscio on every turn — so a normal coding session is unaffected and the change shows up exactly when you ask for something Omniscio does. (Before 2026-06-23 the note ended with a suppressive "entirely optional … never just because the capability exists" line that measurably held the agent back; that was dropped for the lighter steer.)
It is the general-session sibling of the always-on note that makes the agent ask questions as clickable widgets. It is not Ask Omniscio (that is a separate in-app help-agent sidebar project).
What the note tells the agent
- It is running inside Omniscio, which you watch from a dashboard.
- Many everyday requests are really Omniscio actions — and it should do them through Omniscio rather than answering in chat: reminders/schedules, controlling or messaging other sessions, automations, tasks/notes, settings, the inbox and approvals, and session search.
- There is a skill family for this:
omniscio-controlis the hub (auth, the approval model, every endpoint), and seven category skills route by intent —omniscio-sessions(which also holds the one table of general agent tools every session shares: tasks, messages, groups, owner cards, documents, reviews, wake-ups, staying alive and missions),omniscio-scheduling,omniscio-automation,omniscio-content,omniscio-settings,omniscio-inbox,omniscio-observe. Failing those, Omniscio's local REST API athttp://127.0.0.1:19519. - It should identify itself (its
$AMC_SESSION_IDas theX-AMC-Source-Session-Idheader) so anything it does in Omniscio traces back to that session in your inbox.
Which parts reach which engines
The note above is Claude-only, and it is worth knowing why: some of its sentences name Claude Code and the Claude Skill tool, so Omniscio's engine prompt bundle hands it to a Claude session and to nothing else. Three rules that are not about Claude at all used to be trapped inside it, and every other engine — Codex, Gemini, OpenCode, Cursor — silently never received them:
- Where to write scratch files — the per-session
$AMC_SESSION_TMPdirectory, never a shared path another session could pick too. - How to message another agent — the peer-message route, and the footer that tells the recipient how to reply.
- Which credential to present, and where the fallback is — your session's own scoped
$AMC_CLI_TOKENby default, and the machine-wide token file only for a route that refuses it with a 401.
All three are their own engine-neutral fragments now, so every engine receives them, on the same settings toggle the note uses. The third matters most in practice: some routes — creating a worktree, for one — refuse a session's own scoped token by design, so an agent that was never told the fallback exists simply 401s and asks you what to do. That is exactly what happened to a Codex session on 2026-10-06, which is what prompted the fix. See engine-prompt-bundle-contract.md for the rule, and the harness-gated-block postmortem for the four times it happened.
Where to find it
Turning it off
Settings → Features → "Make sessions Omniscio-aware." On by default. Turning it off takes effect on the next spawn or resume of each session; nothing else changes. The note is fixed text — there is no per-session or per-project override.
How it behaves
When it is skipped
- Remote SSH sessions — on a remote host the local API and token are not your Omniscio, so the note (which would be misleading) is omitted entirely.
- Ask Omniscio and Ask about this page — these built-in helpers already carry their own Omniscio-aware instructions, so the note would be redundant.
Related
- ask-amc.md — the separate in-app help agent
- cli-control.md — the local REST API the note points at
- session-provenance.md — the
X-AMC-Source-Session-Idtrace
Last verified 2026-10-06