Oompa / Sessions & accounts
Sessions and accounts
Inspect account status and usage, continue a conversation, switch providers, and handle interrupted work without duplicating it.
Checked · Read as Markdown ↗
Read a session’s conversation and recent activity, then compose the next turn in the same workspace.
Loading the example interface…
Screen controls need JavaScript. The written guides cover each workflow.
Check the account before starting work
Use these commands on an existing, initialized machine whose rollout prerequisites are satisfied. Each named profile isolates its managed provider configuration. Select the provider explicitly when checking sign-in state.
oompa account list
oompa account show personal --provider codex
oompa account usage personal --refreshCodex usage reports observed limits and resets; oompa account usage-history personal --limit 50 --json reads its retained local history. Claude exposes sign-in status, not account quotas or usage history. Oompa does not pool subscription limits or automatically move a failed turn to another account.
A pending Codex login can be checked with oompa account show personal --provider codex and canceled with oompa account login-cancel personal --provider codex. A lost one-time URL cannot be recovered by starting another login over the pending attempt. Claude recovery instead requires the exact acknowledged command reported by status, after you have confirmed the original login child exited.
Continue the same conversation
oompa session list
oompa session status <session-id> --json
oompa session send <session-id> -- "Review the latest changes."
oompa session stop <session-id>Use the returned session ID in scripts. A session name is convenient for people, but can change. For live observation, read data.eventStream.cursor from status and pass that exact cursor to oompa session watch <session-id> --cursor <status-cursor> --jsonl so the status snapshot and subsequent events join without a gap.
Queue a message for later with oompa session queue <session-id> -- <message>. Use oompa session steer <session-id> -- <message> for the current turn. The attachment contract lists accepted files and limits.
Change the provider for the next turn
When the session is idle and the target provider is signed in, switch it explicitly. Claude Code requires a Linux execution machine.
oompa session switch <session-id> --provider claude --preset fable-max
oompa session export <session-id> --format jsonThe new provider receives the retained tail of Oompa's conversation record. Its native thread, hidden state, and cached context do not transfer. Oompa states a retention gap when older recorded history was pruned; it does not invent history from before a session was adopted.
Switching providers within the same account profile preserves the session's working-memory binding. An eligible manual switch to another account can transfer custody only after outstanding memory submissions settle. That transfer purges the old working lane and starts a fresh empty epoch; it does not carry working-memory contents across accounts. A failed transfer remains recoverable before the session is rebound. Shared project memory stays project-scoped. Presets control future turns and do not reinterpret an already-bound historical model until you select a preset.
Inspect an interrupted operation before retrying
A lost connection is not proof that a command failed before taking effect. Keep the command ID and reuse the exact recovery command or idempotency key Oompa reports. An ambiguous result needs inspection, not a new send.
oompa status --json
oompa session status <session-id> --json
oompa remote command <uuidv7>
oompa sync statusA recovery-required session stays fenced while Oompa cannot prove who owns the provider process. Do not delete state or launch a second writer to clear it. oompa session abandon <session-id> ends Oompa's local session with provider state still unknown; use it only when you accept that consequence.
Detailed reference
Exact commands, recovery steps, and compatibility details for this guide.
Presets and permissions
Oompa reviews the bound provider's exact runtime profile immediately before each new provider-native session or turn. For Codex, that refresh includes model, reasoning effort, Fast service tier, permission profile, computer-use capability, and accessible apps. For Claude, Oompa admits only the pinned Fable profile and reviewed host-tool boundary. An unavailable requirement fails before the provider effect. Every successful start records that exact account generation and effective profile; oompa session show displays the bound provider's history and recorded public profile. Read the provider-neutral Oompa record with oompa session export or the transcript endpoint. Codex profiles include the requested model, reasoning effort, service tier, permission profile, computer-use capability, and accessible apps; an empty enabled-app list is reported as empty. Claude Code public profiles include the pinned CLI, model, reasoning effort, default permission mode, and stream formats. Oompa privately reviews the exact config-home authority for every Claude effect but omits that custody identity and legacy isolation marker from session show; managed and adopted personal-home sessions therefore share one non-identifying public shape. Each provider remains authoritative for its native permissions, tools, and hidden runtime state.
low: Codex Luna Max, currentlygpt-5.6-lunawithmaxreasoning.high: Codex Astra Max, currentlygpt-6-astrawithmaxreasoning.ultra: Codex Astra Ultra, currentlygpt-6-astrawithultrareasoning.fable-max: Claude Code Fable, currentlyclaude-fable-5-1withmaxreasoning.fast on|off: a Codex-only, explicit per-turn Fast or Standard overlay. Claude Code refuses Fast instead of ignoring it. A prior Fast value cannot leak into the next turn.
New Oompa-created Codex sessions that use high or ultra, and explicit selections of either preset, use the Astra mapping above (contract 2). The low and fable-max bindings are unchanged. Codex sessions already bound to contract 1 keep their exact Sol model and effort until a preset is explicitly selected; unrelated metadata edits, restart recovery, and queued work do not reinterpret an established session.
oompa init reports the required confirmation without changing local state; oompa init --yes creates your Documents directory when it is absent, verifies that it is a readable, writable, and traversable canonical directory, and accepts it as the default project. Initialization is a one-shot maintenance command: run it before opening the persistent shell. The shell rejects /init because its running daemon already owns local state. Codex turns use Codex's auto_review path, the exact advertised :workspace permission profile, and the selected project as the runtime workspace root. Codex remains authoritative for the profile's effective sandbox, network policy, computer use, plugins, and protected turn inspection. Claude Code runs in its default interactive permission mode under the selected project and maps supported tool-use requests into Oompa interactions; it does not expose Codex's permission-profile, app, plugin, or protected turn-inspection surfaces.