I usually juggle multiple projects at once. One is always the priority, production work, but I like keeping side projects moving too. My typical flow for those back burner projects was something like this. I would chat with Codex to figure out what to build next, we would shape it into a Jira style task, then I would hand that to Claude Code to make a plan. Then I would ask Codex to review the plan, go back and forth until we were both happy, then Claude Code would implement it, Codex would review the code, and we would repeat until it felt solid. I genuinely find Codex useful for debugging and code review. Claude Code feels better to me for the actual coding. So I wanted to keep both in the loop, just without me being the one passing things between them manually. My first instinct was to get the two tools talking to each other directly. I looked into using Codex as an MCP server inside Claude Code but it didn't work the way I hoped. I also tried Claude Code hooks but that didn't pan out either. So I ended up going with chained CLI calls. Both tools support sessions so this turned out to be the cleanest option. The result is spec2commit. You chat with Codex to define what you want to build, type /go, and the rest runs on its own. Claude plans and codes, Codex reviews, they loop until things are solid or you step in. This was what I needed on side projects that don't need my full attention. Sharing in case anyone else is working with a similar setup. |