Announcing Dome Managed Agents.

Try it now

Codex MCP and Dome

Codex gets your tools while you keep the rules. Two commands put your Gateway in Codex. codex mcp add writes the URL to config.toml, and codex mcp login signs the developer in with their own Dome account. Turn interactive access off and every Codex session loses the Gateway within minutes.

Dome provides governed MCP accessfor Codex.

Sign-in, not a key

Each developer runs codex mcp login and signs in with their own Dome account. No agent key lands in config.toml.

Merges for one person

Rules see which developer ran the login. Give priya merges and everyone else the rest of GitHub.

Short-lived by design

Interactive tokens expire within 10 minutes and reach one Gateway only. Dome rechecks the developer at every renewal.

Codex on a Gatewayin three steps.

Allow your developers, permit the tools, then two codex commands add the Gateway and sign in.
  1. Turn on interactive access

    The allow-list takes exact emails or identity provider subjects. Turning access on creates the managed agent Codex sessions run as.

    shell
    dome gateways interactive enable eng-gateway \  --email priya@example.com \  --email tom@example.com
  2. Permit what it may call

    Attach the rule below to that agent with --agent. dome gateways get prints the name.

    shell
    dome rules apply interactive-access.cedar \  --agent gateway-interactive-<gateway-id> \  --name interactive-access
  3. Add the Gateway to Codex

    This writes the server to ~/.codex/config.toml with no token. The login opens a browser to sign in.

    shell
    codex mcp add dome \  --url https://<gateway-host>/gateways/<gateway-id>/mcpcodex mcp login dome

A rulefor the managed agent.

Discovery and GitHub calls are open to every developer who logged in. A merge from Codex goes through only for priya.
cedar
permit (  principal is Dome::Agent,  action == Dome::Action::"mcp:discover",  resource);
permit (  principal is Dome::Agent,  action == Dome::Action::"mcp:call",  resource is Dome::MCPTool) when { resource.connection_name == "github" };
forbid (principal, action == Dome::Action::"mcp:call", resource is Dome::MCPTool)when {  resource.connection_name == "github" &&  resource.tool_name == "merge_pull_request"}unless {  principal has act_as &&  principal.act_as.email == "priya@example.com"};

One call,two outcomes.

Switch the caller or the argument and watch the same call decide differently, with every decision landing in audit.

Signed in as

agent gateway-interactive-1d85 · acting as priya@example.com
github/merge_pull_request(owner: "acme", repo: "api", pullNumber: 311)
  1. Sign-inpriya@example.com is on the allow-list
  2. TokenInteractive token for eng-gateway, still valid
  3. RuleMerges are open to priya
DecisionAllowed

Bringing it alltogether.

Connecting Codex to registered tools and models in Dome completes a governed agent application.
Dome

Agent

Control point

GatewayEvery call decided and audited
RulesGuardsQuotas

Common questionsabout Codex.

How do I add a remote MCP server to Codex?
Run codex mcp add with the server's --url, then codex mcp login if it uses OAuth. For a Dome Gateway, that login is your Dome account.
Does Codex need an API key for the Gateway?
No. codex mcp login opens a browser once. After that Codex holds a token that expires within 10 minutes and renews.
Can different developers reach different tools?
Yes. A rule can name developers by email. Two teams can share one Gateway and call different tools.
What happens when I turn interactive access off?
Tokens stop renewing and expire within minutes. The allow-list and managed agent stay for when you turn it back on.

More of whatDome works with.

Model

Claude Fable

Fable 5.1 from Anthropic and Amazon Bedrock in one failover pool, open to one group and capped by quota.
Provider

Anthropic

The Claude API behind the Model Broker: the key held in Dome, every call authorized, metered and audited.
MCP server

Atlassian

The Atlassian Rovo MCP server behind the Tool Gateway, with rules that decide each Jira and Confluence call on its tool and site.
Identity

Okta

Okta tokens verified on every agent call, so rules and audit name the person each agent acted for.
Runtime

LangGraph

LangGraph agents with their model calls on the Model Broker and their MCP tools on the Tool Gateway.
Agent service

TinyFish

TinyFish's web agents behind the Tool Gateway, with rules that decide each run on the site it targets.

Talk with ourFDE team.

Or start free, and register your first agent in minutes. Connect it through a gateway, give it rules, and see every call it makes in one audit trail.

Talk with our FDE team

Our engineers design, build and run governed agents for the part of your business you want to change. You see what they deliver.

Claude Code, Cursor and Codex: governed MCP access for your people

People connect Claude Code, Cursor or Codex to a Gateway and sign in with their own Dome account. Nobody holds a shared key, and every call is audited under the person who made it.

Every agent you run, under one system of control.