Menu

Post image 1
Post image 2
1 / 2
0

Stop hand-syncing Claude Code and Codex configs

DEV Community·MAXX·25 days ago
#k4O1Drnq
#claude#openai#cli#productivity#sync#config
Reading 0:00
15s threshold

If you've spent any time in Claude Code or Codex, your config tree is probably substantial: ~/.claude/{settings.json, agents/, skills/, .mcp.json, CLAUDE.md} ~/.codex/{config.toml, AGENTS.md} plus ~/.agents/skills/ Two situations get painful fast. Switching tools. You curated skills, agents, MCP servers, and permissions in one. Now you want to try the other. Migrating by hand is slow and easy to get wrong, and the two hosts don't share shapes. Permissions are allow/deny/ask lists in Claude, but sandbox_mode plus web_search plus prefix_rule in Codex. Agents are YAML frontmatter in Claude, TOML fields in Codex. Using both. Same skills, same agents, same MCP. Two trees. They drift. Adding anything means two edits, and you forget which side is canonical. ai-config-sync-manager bridges the two. It diffs both sides, plans changes, applies them with a backup.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More