---
title: Omniscio awareness prompt — sessions know they're in Omniscio
---

# Omniscio awareness prompt — sessions know they're in Omniscio

## 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-control` is the hub (auth, the approval
  model, every endpoint), and seven category skills route by intent — `omniscio-sessions`,
  `omniscio-scheduling`, `omniscio-automation`, `omniscio-content`, `omniscio-settings`, `omniscio-inbox`,
  `omniscio-observe`. Failing those, Omniscio's local REST API at `http://127.0.0.1:19519` with
  the bearer token from `~/.amc/cli-token`.
- It should identify itself (its `$AMC_SESSION_ID` as the
  `X-AMC-Source-Session-Id` header) so anything it does in Omniscio traces back to that
  session in your inbox.

## 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.

## For agents

### How it works (for agents with repo access)

The fragment is the `AMC_AWARENESS_SYSTEM_PROMPT` constant in
[src/main/process/spawn-build.ts](/src/main/process/spawn-build.ts), emitted by the
pure `resolveAmcAwarenessPrompt()` helper there (gated on the setting + the
SSH/Ask-Omniscio/Ask-Page checks). It is folded into the single
`--append-system-prompt` value at the spawn fold-in site in
[src/main/process/spawn-cluster-manager.ts](/src/main/process/spawn-cluster-manager.ts)
via `appendToSystemPrompt()`, so it never clobbers the other fragments. The toggle
is the `amcAwarenessPromptEnabled` AppSettings boolean (default `true`).

## Related

- [ask-amc.md](ask-amc.md) — the separate in-app help agent
- [cli-control.md](cli-control.md) — the local REST API the note points at
- [session-provenance.md](session-provenance.md) — the `X-AMC-Source-Session-Id` trace