syncing-claude-codex

To keep Claude and Codex skill directories synchronized, you can use a bidirectional sync process that propagates updates from either the .claude/ or .codex/ directories to maintain cross-repo parity. It handles path substitution and YAML frontmatter formatting.

Bidirectional sync for Claude and Codex agent definitions ensures consistent definitions across both providers by applying per-item transformation rules and handling provider-specific path conventions during updates. This parity prevents configuration drift.

Yes, you can sync YAML frontmatter between Claude and Codex directories. The sync process handles YAML frontmatter formatting natively, ensuring metadata is correctly transformed and maintained across both provider directories during synchronization.

When syncing content to the Codex directory, path substitution is handled automatically by applying per-item transformation rules, which adjusts internal references to match the target provider's directory structure and conventions.

Yes, the Claude and Codex directory sync supports optional references, scripts, and assets subdirectories, ensuring these additional resources are included when synchronizing skills, agents, or system docs across providers.

The best way to maintain cross-repo parity for system docs is to execute a bidirectional sync after creating or updating documents in either provider, ensuring structured workflows and verification steps confirm completeness across both repositories.