Omnigent: Open-source AI agent framework and meta-harness Plenty of developers now keep several coding agents close at hand, reaching for Claude Code on one task and Codex or Cursor on the next. Each tool arrives with its own command line, its own handling of credentials, and its own way of running shell commands against a working directory. That spread leaves teams with a governance gap around where agent actions land and how much they cost. Omnigent, an open-source project, sits one level above those tools as a meta-harness. The common layer drives Claude Code, Codex, Cursor, OpenCode, Hermes, Pi, and agents a team writes in YAML, and a user swaps or combines them with one-line changes. Omnigent draws on a first-party API key, a Claude or ChatGPT subscription, or any compatible gateway such as OpenRouter, with a per-agent default a user can switch mid-session. A single session follows the user from a terminal to a browser to a phone, with messages, sub-agents, terminals, and files in sync. Guardrails set at the harness layer The security design centers on policies. A policy governs what an agent may do across shell commands, file edits, and token spend, and it checks every action to allow it, block it, or pause for a person’s approval. Spend caps and access limits ship as builtins, so a session can carry a hard dollar ceiling with a softer warning along the way. These checks run at the meta-harness layer as stateful, data-centric rules that track agent actions, which keeps enforcement out of the prompt where an agent might drift past it. Policies stack across three levels. An administrator sets server-wide rules, a developer sets per-agent rules, and the person in a session sets per-session rules, with the stricter session rules checked first. A team can write a