Bidirectional sync for Claude Code and Codex — instructions, skills, agents, MCP servers, hooks, permissions.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Still active enough to matter. Good candidate for a fast stack test instead of a long evaluation loop.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health 42/100. no security policy. 3 open issues make this testable, but not something to trust blind.
AI Agent
Multiple
Model
Claude
Fastest way to find out if ai-config-sync-manager belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
claude mcp add ai-config-sync-manager -- npx ai-config-sync-managerRun this first. You will know quickly if the workflow earns a permanent slot.
claude mcp remove ai-config-sync-managerNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude.json └─ mcp_servers/ └─ ai-config-sync-manager ← registers here
Bidirectional sync for Claude Code and Codex — instructions, skills, agents, MCP servers, hooks, permissions.
Source: GitHub repository
Source check: July 18, 2026
Upstream commit: July 17, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.