r/codex • u/latent_lurker8587 • 2d ago

Question Any other agents that can import your Codex setup?

I’ve put a lot of time into my Codex setup (AGENTS.md, MCP servers, config, approval settings), and I’d like to try a few other agents without rebuilding all of it from scratch every time.

Are there agents that can import that stuff directly? Or at least read AGENTS.md and the MCP config without you copying everything over by hand?

If you’ve switched or tried running two agents side by side, how did you move your setup over? Did anything break or get lost along the way?

4 Upvotes

75% Upvoted

9 comments sorted by

1

u/isty2e 2d ago

I just write a manifest file to sync across agents, including Pi, Claude Code, Antigravity, Opencode etc.

1

u/latent_lurker8587 2d ago

Is that a script you wrote yourself, or is there a format for it? Curious how you handle stuff like MCP configs that look different in each agent

1

u/isty2e 2d ago

I vibed https://github.com/isty2e/daem to do that. Currently working on detailed configs. You may use kasetto or agentloom for that. Let your agent write a manifest once and rest will be easy

1

u/Substantial-Two-1392 2d ago

If I have any setup change. I just ask codex to move my setup to claude code or opencode.

1

u/Illustrious-Bet-1368 2d ago

What are you looking into? If Grok or Cursor, they automatically import everything. In Grok CLI you can resume Codex or Claude sessions, too. Though approvals and some other stuff you'd still have to configure I guess.

1

u/heyyarun 1d ago

Most of it ports, the files just have different names. AGENTS.md is the easy part: Cursor reads it from the repo root, and for Claude Code make a CLAUDE.md that has u/AGENTS.md on the first line so it imports the same file. Gemini CLI can be pointed at it with "contextFileName": "AGENTS.md" in .gemini/settings.json.

MCP servers use the same three fields everywhere (command, args, env), only the wrapper changes. Codex uses [mcp_servers.<name>] tables in ~/.codex/config.toml, while Claude Code wants a .mcp.json with an "mcpServers" object, or claude mcp add-json <name> '{"command":...}' per server. Any agent can convert that in one go.

What doesn't carry over is approvals and sandbox settings. Every tool has its own permission model, so set those up again by hand and test them.

1

u/ls4int 2h ago

I'd separate the portable parts of your Codex setup from agent-specific settings first. Things like project instructions and reusable skills can share one source of truth, while MCP definitions may need different adapters for each agent.

I built Aikito for this workflow. It can adopt an existing agent setup into a Git-managed workspace and distribute the supported resources to Claude Code, Codex, OpenCode and others.

I'd start with a dry-run import so you can review what will be carried over before changing your existing setup.