Claude, Codex, and Pi walk into a shared session

What it does

Omnigent acts as a control plane over existing agent runtimes like Claude Code, Codex, and Pi. It multiplexes them into a single live session that syncs across your terminal, browser, and phone, adding governance policies and shared collaboration on top. You define custom agents in YAML, delegate tasks across vendor boundaries, and let one agent review another’s work while policies cap spend or pause before risky shell commands.

The interesting bit

Instead of replacing your tools, Omnigent treats them as swappable harnesses. The included Polly orchestrator, for example, delegates coding tasks to sub-agents in parallel git worktrees, then routes each diff to a reviewer from a different vendor than the one that wrote it. That turns the usual lone chatbot into a multi-player, cross-model dev environment.

Key highlights

• Swap or combine Claude Code, Codex, Pi, and custom YAML-defined agents in the same session without reimplementing them
• Built-in governance: policies can pause for approval before shell commands, cap token spend, or restrict tool access per server, agent, or chat
• Real-time collaboration: share live sessions, co-drive a teammate’s agent on their machine, or fork conversations to continue independently
• Runs locally, on LAN, or deployed to a server; sessions can offload to disposable cloud sandboxes via Modal or Daytona
• Supports first-party API keys, consumer subscriptions, and gateway endpoints like OpenRouter or Ollama, with mid-session model switching via the /model command

Caveats

• The repo carries an alpha badge, so expect shifting APIs and rough edges
• Full off-device and mobile access requires self-hosting a server or provisioning a cloud sandbox; out-of-the-box use is tied to your local machine
• Running the wrapped agents requires external dependencies like Node.js, npm, and tmux to be present on the host

Verdict

Worth a look if your team already lives in Claude Code or Codex and wants cross-vendor orchestration with shared sessions. Skip it if you need a fully managed service—this is a bring-your-own-keys, self-hosted harness that demands some infrastructure patience.