Skip to content

Add slash9494/ai-config-sync-manager to Cross-Agent Tools#29

Open
slash9494 wants to merge 1 commit into
RoggeOhta:mainfrom
slash9494:add-ai-config-sync-manager
Open

Add slash9494/ai-config-sync-manager to Cross-Agent Tools#29
slash9494 wants to merge 1 commit into
RoggeOhta:mainfrom
slash9494:add-ai-config-sync-manager

Conversation

@slash9494
Copy link
Copy Markdown

Resource

slash9494/ai-config-sync-manager

Category

Cross-Agent Tools — bridges Codex CLI with Claude Code.

What it does

Bidirectional sync between Claude Code (~/.claude) and Codex (~/.codex) configurations. Unlike one-way sync tools, it diffs both sides, then converts and merges:

  • Rules (CLAUDE.mdAGENTS.md)
  • Agents / subagents
  • MCP server configs
  • Hooks
  • Permissions / settings

Designed around a YAML round-trip guarantee — frontmatter survives a pass through both the lenient Claude parser and the strict Codex (YAML 1.2) parser without field loss.

How it differs from existing entries

  • vs lbb00/ai-rules-sync: covers full config space (agents, MCP, hooks, settings), not just rules files. Bidirectional, not single-source.
  • vs Leoyang183/sync-agents-settings: covers more than just MCP — full config diff/merge across both directions.
  • vs general orchestrators (josstei/maestro-orchestrate, etc.): not an orchestration platform; a focused config sync utility.

Maintenance

  • Released 0.1.0 stable (npm + GitHub).
  • Active development (recent commits within the past week).
  • MIT licensed.
  • Zero runtime dependencies (Node ESM, single-file CLI).

Why it fits

The list already includes config-sync tools under Cross-Agent Tools. This one targets the Claude ↔ Codex direction specifically and handles a wider config surface than existing entries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant