Omnigent is a meta-harness: a common layer over existing agent harnesses (Claude Code, Codex, Cursor, OpenCode, Hermes, Pi, Antigravity, GitHub Copilot, Grok Build, Devin) and agents defined in YAML. Harnesses can be swapped or combined with one-line changes, so one session can mix agents from different vendors, have one agent review another's work, or split a task across them.
A runner wraps any agent in a sandboxed, uniform session. A server adds policies and shared history, and exposes every session over the terminal, a web UI, a desktop app, mobile apps, and a REST API. Sessions follow the user across devices with messages, sub-agents, terminals, and files kept in sync. Teammates can watch a shared session live, co-drive it so their messages run on the owner's machine, or fork it to continue independently.
Policies check every agent action and allow it, block it, or pause for approval. They cover shell commands, file edits, tool-call caps, and spend budgets, and they stack at server, agent, and session level with the session rules checked first. Agent terminals run in an OS sandbox (bubblewrap on Linux, seatbelt on macOS) that restricts filesystem and network access and brokers credentials instead of exposing them. Sessions can also run in disposable cloud sandboxes such as Modal, Daytona, E2B, OpenShell, Kubernetes, or Databricks, provisioned per session by the server.
Models come from first-party API keys, Claude or ChatGPT subscriptions through the official CLIs, any OpenAI- or Anthropic-compatible gateway (OpenRouter, LiteLLM, Ollama, vLLM, Azure), or a Databricks workspace. Example agents include Polly, a coding orchestrator that delegates to Claude Code, Codex, or Pi sub-agents in parallel git worktrees and routes each diff to a reviewer from a different vendor, and Debby, which sends each question to a Claude head and a GPT head and can make them debate.
Features
- Harness switching: run Claude Code, Codex, Cursor, OpenCode, Hermes, Pi, Antigravity, Copilot, Grok Build, Devin, or custom agents behind one interface
- YAML agents: an agent is a prompt plus tools (Python functions, MCP servers, sub-agents), and agents can write these files themselves
- Policies: allow, block, or ask before shell commands and file writes, with tool-call caps and spend budgets at three levels
- OS sandbox: filesystem and network restrictions plus credential brokering for agent terminals
- Cloud sandboxes: per-session runs on Modal, Daytona, Blaxel, E2B, CoreWeave, Kubernetes, OpenShell, microsandbox, Databricks, and others
- Any device: the same live session in terminal, browser, desktop app, and iOS or Android apps
- Collaboration: invite-only multi-user accounts, live session sharing, co-driving, and forking, with optional OIDC sign-in
- Model credentials: API keys, Claude or ChatGPT subscriptions, OpenAI- or Anthropic-compatible gateways, and Databricks, with mid-session model switching
- Example agents: Polly for cross-vendor coding orchestration, Debby for two-model debate, and a cited deep-research agent
- Automations: runs an agent on a recurring schedule
- Deployment targets: Docker Compose, Render, Railway, Fly.io, Hugging Face Spaces, Modal, Cloudflare, and Databricks Apps