Read & Status (the read-only "what's going on" surface)

What it is

Everything Omniscio can be asked from outside the app goes through one local HTTP server on 127.0.0.1:19519. That server has a read side and a write side, and this page is the read side: liveness, app / project / account state, cross-session search, and the navigation links that only move the user interface.

The point of it is preflight and lookup. Before an agent spends anything, before it moves a session, before it claims something does not exist, this is the surface that answers the question — so a caller can see the current state instead of guessing at it or restarting the app to find out. The same surface is what the bundled omniscio-control skill reads through when an agent checks on the install rather than changing it.

Where to find it

• For a person: there is no screen to open. This surface is driven from a terminal or by an AI agent through the control server, and the in-app equivalents of its answers live on the panels it reads from — the Accounts panel, Settings → Diagnostics, Session Search.
• For an agent: the bundled omniscio-control skill, which teaches an agent how to read and change a running install; read the Omniscio Control hub for the layout and the approval model.
• For a script: the same HTTP routes, with the bearer token from the vault.

How it behaves

Is it up?

• A cheap liveness ping answers "is the app running" and needs no token at all, so it is the right first call before spending one on anything else.
• The authenticated status call is the one that returns the substance: the projects and sessions that exist, what account the app is on, and the project names a caller can resolve a fuzzy name against before making a project-scoped call.

What state is everything in?

• Accounts — every configured account is listed with its health (ok, auth, rate_limit, degraded), its usage percentage, its reset time, how many live sessions it holds, which one is active, and whether it is the spawn fallback. Credentials are never returned, so this is safe to read from anywhere. The account switchers and the wider account story are on Account pool.
• Credentials — an inventory of what is stored, names only, never values.
• Cloud — one call returns the sticky verdict on whether cloud test offload is healthy and, when it is not, why — a recorded verdict rather than a fresh probe, so asking twice is cheap. See Cloud control.
• The app itself — resource and diagnostic readouts have their own panel; see Resources & diagnostic panel.

Finding things

• In your sessions — keyword search and meaning search are two different calls over the same corpus. See Session Search (sidebar virtual project).
• Across the app — the Ctrl+K surface blends session hits into its results. See Global Search (Ctrl+K across everything).
• A capability, from a question — the intent search ranks what Omniscio can do against a plain-English phrasing, which is the tool to reach for when the route you want cannot be found by name.

Moving the interface

• Two navigation links open the inbox and bring the Omniscio window to the front. These are the only calls in the family that touch the interface, and all they do is move it.

The account actions that sit beside it

The same family also carries the non-credential account actions: switching which account is active, and flagging a login account as billing-shut-down so it stops being picked. They change which account gets used — never a credential, never your data. Anything that does change data, sends something, or spends, is on the write side of the server and goes through the approval model described in the Omniscio Control hub.

Related

• CLI Control (control Omniscio from scripts and hotkeys) — the control server itself, the token, and the write side
• Omniscio Control (how an AI agent changes the app live) — the bundled skill and its approval model
• Account pool — the accounts these status calls report on
• Session Search (sidebar virtual project) — keyword and meaning search over your sessions
• Global Search (Ctrl+K across everything) — the in-app surface that blends those hits
• Cloud control — the cloud panels behind the cloud health verdict
• Resources & diagnostic panel — the in-app readout of what the app is using