2 posts tagged with "Codex"

I often reach the same point in Codex Desktop: most of a task is done, only a few small edits remain, and I would rather finish with a faster, less expensive model.

DeepSeek V4 Flash can now connect directly to Codex through the Responses API. But when I previously changed providers, I ran into a different problem: the conversation still existed, but the original thread no longer appeared in the same place. I eventually used opencodex to manage model routing, which let me switch models and keep working in the current task. This post covers that setup and a few startup messages that are easy to misread.

Once your docs fully live in GitHub and follow a Docs-as-Code workflow, review starts to look a lot more like software collaboration. That is mostly a good thing: we get history, branches, pull requests, and a cleaner workflow. But it also means the quality bar rises fast.

Over the past few months, I ended up building a layered review workflow for technical content. I started with a lightweight local validation step for typos and surface-level issues, then added Codex for deeper local and cloud review, and finally used AGENTS.md to turn a lot of tacit review judgment into reusable rules.

This post is not just a tool recap. It is really about why this workflow is worth building, where each layer helps, and where AI review still needs a human in the loop.