Compass is coming to Codex
If your team writes code in Codex, you'll be able to run every change through Compass, the way Claude Code teams do today.
Compass has only ever run in Claude Code. That's been fine if that's where you work. If your team is in Codex, or split between the two, it has meant Compass wasn't for you.
That's changing. Compass now installs into a Codex project, and once it's there you work the way a Claude Code team does. Describe the change in one line, and Compass reads it for risk, familiarity, size and goal, picks an approach, and tells you what it will write and what it will check before anything ships.
The problem
Choose a coding agent and you've chosen your process. While Compass only ran in Claude Code, a team in Codex couldn't have it, and a company using both ended up with two ways of shipping on one codebase. We don't think your choice of agent should decide how carefully you ship.
What's new
We didn't write a second Compass. The commands, the agents, the skills and the Python CLI are shared. Codex gets a small adapter on top: one entry skill, and a translation that turns Codex's hook events into the ones Compass already understands.
In practice:
$compass:compass assess "Add rate limiting to the public API"starts the same assess stage that/compass:assessstarts in Claude Code. The other stages, fromdefinetoship, follow the same way.- A change leaves the same documents behind, in the same place, with the same statuses. The records are the same files whichever runtime wrote them.
compass checkandcompass cirun unchanged, so a pull request is judged the same way.
The hooks are where the two runtimes differ. Codex runs them only once you've trusted them, and we haven't yet measured how they behave through a full native session. Rather than claim parity, we publish a support table that says, control by control, what Codex enforces, what it advises on, and what it doesn't have.
Getting started
Pin a Compass checkout at 7.0.0 or later and point the installer at your project:
python3 adapters/codex/install.py --project /absolute/path/to/your/project
Restart Codex, trust the project, then review and trust the hooks it installed with /hooks. The Codex guide explains what the installer adds, how to take it out again, and exactly what we have and haven't tested.
Frequently asked questions
Who is this for?
Teams that work in Codex. Also teams where some people use Codex and some use Claude Code on the same repository, and want one way of working.
Is it really the same Compass?
Yes, apart from the hooks. Same commands, same agents, same CLI, same records on disk. The support table lists where the hooks differ.
Can I use it today?
You can. It installs from a source checkout of Compass 7.0.0 or later, on macOS or Linux. It isn't in a plugin marketplace yet, and Windows isn't supported.
How far along is it?
The install, the uninstall and the hook translation are tested. What we haven't done is watch a real change go from assess to ship in a native Codex session, resume a cold session, or test on Linux or a clean machine. Approval in Codex is terminal-only for now. Until we've measured those, treat the hooks as advice and run compass check yourself before you merge.
When will you call it done?
When someone who doesn't work at ayeo has shipped a change through Compass on Codex, and we can show it behaved as it would have in Claude Code.
Does this change anything in Claude Code?
No. Claude Code uses the same shared sources it always has.