AI Config Sync Manager

AI Config Sync Manager

  Continuous bidirectional sync between Claude Code and Codex — round-trip lossless, not a one-shot migrator.

Highlights

- Continuous bidirectional sync — claude → codex and codex → claude, run as often as the two hosts drift; not a one-shot migration.
- Strict YAML round-trip — Claude lenient YAML and Codex YAML 1.2 strict frontmatter both preserved across repeated syncs without loss or oscillation.
- Diff-first workflow — status to compare → sync --dry-run to preview → --apply to write.
- Risk-tagged operations — permissions, hooks, custom commands labeled safe / partial / manual.
- Backup-on-write — every overwrite snapshotted under .backups/, FIFO retention (30).
- Apply ledger — every --apply writes a per-item sha256 attestation (before/after hash, backup path) to ~/.ai-config-sync-manager/ledgers/.
- Selector syntax — --include skills:code-writer,instructions --exclude mcp style filtering.
- Native semantic mapping — Claude Write → Codex sandbox_mode = "workspace-write", etc.
- Prose-level token rewriting — Claude-only tokens (Read, Bash, TaskCreate, headless claude -p) and Codex-only tokens (spawn_agent, codex exec) auto-translate across hosts and round-trip back.
- Zero runtime dependencies — single ESM file, Node built-ins only.
- Thin host plugins — /config-manager:* for Claude, config-manager-* for Codex.
- Visual inventory board — board renders a self-contained HTML page of every skill, agent, hook, and MCP server on both hosts, colored by sync status (in-sync / conflict / one-host-only) and grouped into per-area tabs and by agent harness. Jump to the board →

Why this exists

Claude Code and Codex use the same concepts (instructions / skills / mcp / permissions / hooks) but in different files, formats, and names:

Hand-rolling the…