Oompa documentation

What do you want to do?

• Set up Oompa: install the CLI, connect a provider account, and open your first session.
• Use the web app: pair a browser, follow the session grid, and send the next instruction.
• Manage sessions and accounts: continue a conversation, switch providers, inspect usage, or recover a stopped flow.
• Find a command: look up CLI families, machine-readable output, memory, and automation.
• Check availability: distinguish the released CLI from runtime rollout and provider support.

Your machine runs the work. You choose the interface.

Oompa keeps Codex and Claude Code sessions on the machine that runs them. The web app shows their synchronized state; the terminal and CLI address the same local accounts and conversations. Other devices can send commands, but do not take over execution.

• Provider account: your Codex or Claude Code sign-in, owned by that provider and used on the execution machine.
• Oompa identity: an email sign-in for optional encrypted sync and paired devices. It does not sign you into a provider.
• Session: one Oompa conversation with an account, project, and execution machine. Changing its provider does not move a provider-native thread.

Local use does not require an Oompa cloud identity. The web app does require sync, an approved machine, and a paired browser. Current setup limits apply to either route.