cxbridge
AGENTS.md1 starsChanged 6 months agoMITView on GitHub
cxbridge is a Rust CLI that bidirectionally converts configuration files between Claude Code (.claude/, JSON) and OpenAI Codex CLI (.codex/, TOML). Conversion rules live in mappings/*.yaml; the CLI is an engine that interprets them. - Design & spec: docs/spec.md — single authoritative document for the CLI design, IR model, transform registry, domain handler contracts, degrade engine, CLI flags, exit codes, and implementation phases. Supersedes any older per-file docs. - Conversion table: mappings/*.yaml + mappings/SCHEMA.md — canonical field-level mapping data (332…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 33,315 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository3 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- run-checksSkill
- validate-mappingsSkill
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 48
Read the relevant rule file before touching files in that area.
- Very specific: line 52
Dropped fields are never silent: Every dropped entry must appear in the conversion report.
- Distinctive: line 53
Degrade scope must be recorded: When a field moves to a broader scope (skill → session/project), the report must name the target scope.
- Very specific: line 55
Codex spec is fluid: Check mappings/*.yaml notes fields and docs/spec.md §17 for known issues and awaiting-codex annotations before …
≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
cxbridge — Contributor & Agent Guide
cxbridge is a Rust CLI that bidirectionally converts configuration files between
Claude Code (.claude/, JSON) and OpenAI Codex CLI (.codex/, TOML).
Conversion rules live in mappings/*.yaml; the CLI is an engine that interprets them.
Repo Layout
src/ Rust implementation
mappings/ Conversion table YAML (332 entries) — canonical data
docs/ Design & specification documents
tests/ Integration tests and fixturesSource of Truth
- Design & spec:
docs/spec.md— single authoritative document for the CLI design, IR model, transform registry, domain handler contracts, degrade engine, CLI flags, exit codes, and implementation phases. Supersedes any older per-file docs. - Conversion table:
mappings/*.yaml+mappings/SCHEMA.md— canonical field-level mapping data (332 entries). When code and spec diverge, followdocs/spec.md.
Dev Commands
cargo build
cargo test
cargo clippy --all-targets -- -D warnings
cargo fmt
cargo run -- check <path>
cargo run -- c2x <path>
cargo run -- x2c <path>
uv run scripts/validate-mappings.py # validate mappings invariantsPer-Area Work Rules
Fine-grained rules are under .claude/rules/ and are auto-loaded by context:
| Area | Rule file |
src/**, tests/** | .claude/rules/rust.md, .claude/rules/code-style.md, .claude/rules/effective-rust.md |
src/handlers/** | .claude/rules/handler-modules.md (directory-module layout) |
mappings/** | .claude/rules/mappings.md |
docs/** | .claude/rules/docs.md |
Read the relevant rule file before touching files in that area.
Key Principles
- Dropped fields are never silent. Every
droppedentry must appear in the conversion report. - Degrade scope must be recorded. When a field moves to a broader scope (skill → session/project), the report must name the target scope.
- Codex spec is fluid. Check
mappings/*.yamlnotesfields anddocs/spec.md §17for known issues and awaiting-codex annotations before assuming behavior.
Language
Project content (code, docs, comments, commit messages, issues, PRs, README) is written in English. The assistant replies to the maintainer in Japanese during chat.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

