Part III: Practical Codex Guide in the GPT-5.5 Era

Chapter 8: After GPT-5.5 — Patterns the Community Discovered

Written: 2026-04-28 Last updated: 2026-06-11

8.1 The Arc: April 16 → April 23 → First Month

Chapter 7 ended at April 23 with GPT-5.5 landing in Codex. But to understand why the community reacted the way it did, you have to start at April 16 — not April 23.

When Opus 4.7 shipped on April 16 with its "fewer subagents by default" change, it didn't just change a capability — it created the ambiguity tax. Seven days of developers discovering that prompts that worked on 4.6 now required explicit instructions. Seven days of frustration piling up in r/ClaudeAI, HN threads, and X posts [14].

Then April 23 arrives, GPT-5.5 ships in Codex, and the headline from the 500+ Reddit comment synthesis [1] reads: "Claude Code is higher quality but unusable. Codex is slightly lower quality but actually usable."

That word "unusable" wasn't born on April 23. It was seeded on April 16.

As far back as September 2025, when Codex adoption first accelerated, Sam Altman had expressed the same concern [2]: "The Codex-favorable Reddit sentiment feels very fake."

Both observations can be simultaneously true. The ambiguity tax frustration was real and organic; some of the Codex enthusiasm may have been amplified. This chapter holds both views and focuses on practical patterns with independent corroboration — not Reddit votes.

A note on sources. This chapter draws on Reddit threads, HN discussions, and X posts from the April–May 2026 window. These sources are used with eyes open. Sam Altman flagged in September 2025 that Codex-favorable Reddit sentiment "feels very fake" [2] — and that concern did not disappear with the GPT-5.5 launch. Organizationally amplified voices may be present in the corpus. Every recipe below is backed by at least one independent experiment or multi-source convergence, not by Reddit vote counts alone. Where a source is community sentiment only, it is labeled as such.

One-Week Update Since 2026-04-28

The most important update after this book's first draft on 2026-04-28 was Codex CLI 0.128.0 on 2026-04-30. The official changelog highlights five relevant changes [19]:

  • persisted /goal workflows: create, pause, resume, clear, and runtime continuation
  • permission profiles: built-in defaults, sandbox CLI profile selection, cwd controls
  • plugin workflows: marketplace install, remote caching, plugin-bundled hooks
  • external agent session import: background import and imported-session title handling
  • more explicit MultiAgentV2 configuration: thread caps, wait times, root/subagent hints, depth handling

Simon Willison interpreted /goal as Codex's built-in version of the Ralph loop [10]. Community experiments point in the same direction: a May 1 Tecton & Tide run reported that /goal preserved objective state and resumed after a long pause [17]. This is not a reason to hand over arbitrary long work. It is useful when the done condition is explicit: tests pass, a checklist is exhausted, or a documentation batch is complete.

8.2 Recipe 1: Hybrid Use — Claude (Design + Harness) + Codex (Implementation + Verification)

The most common pattern isn't "switching" — it's role separation.

  • Claude Code: design, harness authoring (CLAUDE.md / AGENTS.md drafts), architecture review
  • Codex: implementation, refactoring, test generation, autonomous long-running tasks

Mejba Ahmed's experiment [4] is the extreme version: Codex as a subagent inside Claude Code. Addy Osmani's "Code Orchestra" [5] extends this to multi-model routing — cheap models for planning, frontier for implementation, dedicated model for security review.

How to apply:

  1. Use Claude Code to summarize the existing harness intent and constraints into HANDOFF.md
  2. Move only tool-neutral rules into AGENTS.md; do not delete .claude/ or CLAUDE.md
  3. Start Codex CLI in Read Only and ask for a plan first
  4. Run one small implementation task
  5. Inspect /diff, run /review, and run tests
  6. Optionally review again in Claude Code
Figure 8.1: Hybrid workflow — Claude (design) into AGENTS.md, then Codex (implementation), then Claude (review). Different agents review different layers — shared blind spots shrink. illustration by author Gemini assisted

8.3 Recipe 2: Cost-Aware Multi-Model

Using frontier models for everything is wasteful. The 3-tier strategy the community converged on:

Tier 1 (planning, design): cheaper/faster model or lower effort

Tier 2 (implementation): frontier model (GPT-5.5, Opus 4.7)

Tier 3 (security, review): subagent with dedicated task instructions

Luong's "Local LLMs with Frontier" guide [6] takes the more aggressive version: local LLMs (llama, deepseek-coder) for Tier 1, API only for Tier 2. Reports of 70-80% cost reduction.

Osmani's approach [5]: route the same task through three models, merge only when confidence is high.

Figure 8.2: Cost-aware 3-tier strategy — cheap or local for planning, frontier for implementation, a dedicated subagent for review. 70 to 80 percent cost reduction reported. illustration by author Gemini assisted

8.4 Recipe 3: Sandbox-First Defaults

The most-shared configuration in the first month after launch [7]:


sandbox_mode = "workspace-write"
approval_policy = "on-request"

Branch-per-task is the default safety net. Each task runs on an independent branch, so bad changes don't touch main.

Real failure case: Codex GitHub issue #11354 [8]. A subagent entered an infinite loop under specific conditions. Two things this tells you: (1) Codex's subagent system is still early-stage; (2) approval_policy = "on-request" is a real lifeline in these cases.

Figure 8.3: Sandbox-first defaults — workspace-write plus on-request creates a four-shield safety net: workspace boundary, branch isolation, failure-only gate, and a clean revert path. illustration by author Gemini assisted

8.5 Recipe 4: Don't Trust Your Own Benchmarks

MorphLLM's results [3]:

  • Terminal-Bench: Codex 77.3 > Claude Code 65.4
  • Blind review preference: Claude Code 67% > Codex 25%

The tool that wins the benchmark doesn't necessarily produce the output people prefer. Benchmarks you haven't run on your own workload are for reference only.

Practical method: pick 3-5 tasks you actually do, run them through both tools, compare the outputs yourself. Your own-context preference is more accurate than any published benchmark for your use case.

8.6 Choosing CLI/App/Cloud

As of 2026-05-04, the most practical split is CLI/App/Cloud [19]. The CLI is the most natural entry point for taking over an existing local repo. The app's Local and Worktree modes separate foreground local work from isolated worktree threads on the same machine. Cloud is the fit for unattended work that should continue after the laptop closes.

Goal Recommended surface
First read a Claude Code repo and make one small diff Codex CLI
Run independent experiments side by side in one repo Codex app Worktree
Validate in your usual IDE/dev server Codex app Local or CLI
Keep working after the laptop closes Codex Cloud
Connect work to GitHub/Slack/Linear operations Codex Cloud + integrations
Ask Codex to inspect web-app state in browser context Codex Chrome extension
Exercise Windows-only UI or desktop workflows Codex Computer Use
Turn a branch into a quick inspectable web surface Codex Sites
Continue or branch work away from the laptop Remote/mobile Codex

Do not expect Codex CLI alone to reproduce Claude Code's /remote-control experience; that use case belongs closer to Codex Cloud and GitHub/Slack/Linear integrations.

2026-06-11 update: usage moved toward surface choice. The lived Codex question is now "where should this task run?" Local CLI is still the safest first step for a Claude Code repository. Worktree is the practical place for parallel branches. Chrome and Computer Use are inspection surfaces. Sites and Cloud are sharing/remote surfaces. Goal mode and automations belong only after the repository has clear tests, task files, and handoff rules [19].

One research signal points in the same direction. The Einstein Telescope comparison reported that Codex-style workflows can be slower than direct expert work but easier to audit because the intermediate state is explicit [20]. Treat that as a limited case study, not a universal benchmark. For migration, the useful point is the audit trail: when a tool is slower but leaves clearer state, it may still be better for risky repository transitions.

8.7 Methodological Honesty: Taking Altman's Warning Seriously

Sam Altman's "feels very fake" comment [2] isn't just competitive jab. It's a methodological warning about using community sentiment as a source.

The "community reactions" cited in this book from Reddit / HN / Medium are selective samples. Organizationally amplified voices may be present. The recipes in this chapter include only those backed by independent experiments ([4]) or convergence across multiple independent sources ([5], [6]) — not just "the community said so."

References

  1. Dev.to, "Claude Code Reddit 500+ comments synthesis," 2026. [contributor, 2026]
  2. Altman, Sam, "Fake bots on Reddit," X, 2025-09-08. [News, 2025]
  3. MorphLLM, "Codex vs Claude Code Benchmark," 2026. [MorphLLM, 2026]
  4. Mejba Ahmed, "I ran Codex inside Claude Code," 2026. [Ahmed, 2026]
  5. Osmani, Addy, "Code orchestra — multi-model routing," 2026. [Osmani, 2026]
  6. Luong, "Local LLMs with frontier models — 3-tier setup," 2026. [NGUYEN, 2026]
  7. Zack Proser, "Codex daily-use review," 2026. [Proser, 2026]
  8. GitHub, "Codex subagents issue #11354," 2026. [contributors, 2026]
  9. OpenAI, "Codex app features — Local, Worktree, Cloud," 2026. [OpenAI, 2026]
  10. Willison, Simon, "Codex CLI 0.128.0 adds /goal," 2026-04-30. [Willison, 2026]
  11. Matthew Berman, "GPT-5.5 two-week prerelease review," 2026. [Berman, 2026]
  12. LLM Stats, "GPT-5.5 vs Opus 4.7," 2026. [Stats, 2026]
  13. Intuition, "Codex as superapp," 2026. [IntuitionLabs, 2026]
  14. MerchMind, "Claude Opus 4.7 Backlash Explained," 2026. [AI, 2026]
  15. Xlork, "Why Developers Are Frustrated with Opus 4.7," 2026. [Blog, 2026]
  16. OpenAI, "Codex CLI changelog — 0.128.0," 2026-04-30. [OpenAI, 2026]
  17. Tecton & Tide, "/goal: The Six-Hour Codex Run That Survived a Five-Hour Pause," 2026-05-01. [Tecton & Tide, 2026]
  18. OpenAI, "Codex changelog," 2026. [OpenAI, 2026]
  19. OpenAI, "Codex Chrome extension," 2026. [OpenAI, 2026]
  20. Dallago et al., "Einstein Telescope Codex comparison," 2026. [Dallago et al., 2026]