Ask Oracle
The Ask Oracle button above the sidebar’s usage blocks starts a new session with Oracle. It is a split button: its main part starts the session in the chosen harness, and the narrow segment at its right chooses Claude or Codex. In the collapsed rail it is an icon button. Oracle’s sessions are ordinary Claude and Codex sessions. They show in Sessions with Oracle’s golden orb and the name Oracle, and Oracle heads the agent filter, set apart from your agents.What Oracle does
- Runs every session not tied to one of your agents: a dialogue with you, and setup sessions that need judgment, such as Create instance in Settings > Coolify, or bringing your server nodes up to date after a database upgrade.
- Administers the Mac’s connections for every capability. It checks them and reads their state freely, and it adds, relinks or removes a connection, or changes a capability’s machine setup, only after you confirm that change in its session.
- Works with AgentKit’s own Coolify connection in the sessions AgentKit starts for it. It gets any other grant only with your confirmation.
- Records the problems it meets. AgentKit keeps them on the Mac and shows them in Settings > Problems; you decide what to pass on.
What Oracle is not
- It is not one of your agents. It never appears in the agents list, the Tasks or Rooms filters, or an agent picker, and it has no page of its own.
- It has no memory, and its instructions are fixed by AgentKit, so nothing retrains it to act otherwise. What it learns reaches it through a new AgentKit release.
- Its name, identity, instructions and routines cannot be changed from the app or by an agent.