Omniscio

CLI Session Recovery — Get Stuck Sessions Going Again

Three targeted CLI calls let an AI agent diagnose and fix a wedged Claude session with no approval round-trip: moving a session off an account that hit a rate limit or auth error, restarting a process that died, and nudging a session that is alive but idle. Covers finding a healthy account and what each call returns when it goes wrong.

On this page

What it is

An AI agent holding the Omniscio bearer token can diagnose and fix a wedged Claude session directly over HTTP — no user approval round-trip. Three targeted endpoints cover the three failure modes: account bad, process dead, session idle.

The problem

A Claude session in Omniscio can get stuck in several ways:

  • The Anthropic account it was on hit a rate limit or got frozen (auth error, quota exhausted).
  • An account switch failed mid-recovery and the session is pointing at a bad account.
  • The Claude Code process died (crash, OOM, signal) and needs to be restarted with full history.
  • The session is technically alive but has gone idle and just needs a push to continue.

All three are fixable over the CLI control server at 127.0.0.1:19519 with the Omniscio bearer token (auto-delivered to ~/.amc/cli-token for the omniscio-control skill; see omniscio-control.md and cli-control.md for connection details). No approval queue — the three mutating routes (plus the read-only GET /accounts discovery helper) apply immediately.

Where to find it

There is no screen for this. CLI Session Recovery exists only for an AI agent, which reaches it over the same local control server the rest of Omniscio's automation is driven from; nothing appears in the app for a person to click. The fixing calls apply the moment they return rather than waiting in an approval queue, so a wedged session can be put right without stopping to ask. What follows is therefore what the agent needs: the token it authenticates with, the read-only call that finds a healthy account to target, and the three calls that fix a session.

Authenticate with the helper

Every example below calls the amc-api.mjs helper, which reads the bearer token in its own process and sends it for you; the route is written without its leading slash.

node "$HOME/.claude/skill-content/omniscio-control/amc-api.mjs" <METHOD> <route> [json-body]

How it behaves

Recovery is immediate by design: there is no approval card, so a fix takes effect as soon as the call comes back, and every call is deliberate about which single problem it addresses. The read-only account list is there to help you choose a target, and the three fixing calls each cover exactly one failure mode — a bad account, a dead process, or a session that is merely idle. One call can outlast its own answer: restarting or moving a session has to spawn a Claude process, and when the machine is busy that work is accepted and continues in the background, which the response says plainly rather than reporting a failure.

The approval queue these three calls deliberately skip is described on the CLI pending actions page. How Omniscio spreads sessions across accounts by itself — so that a stuck session is rarer in the first place — is on Distribute sessions across accounts, and messaging another session rather than reviving it uses the endpoint covered by Cross-session messaging.

See also

Last verified 2026-09-28