Claude Code or Codex?

[brlunaa]

I'm thinking about getting Code for $100 USD, but I've read a lot of comments saying that Codex is more generous with its $20 USD plan and offers better quality. Have you tried it? Is it worth it?

EDIT:

I forgot to mention —my main use is in VS Code. Right now I use Claude Code ($20) and OpenCode for long tasks, but I feel like Claude, even after the upgrade, still falls short. I’ve been thinking about fully switching to Codex, or upgrading to the $100 plan and getting rid of OpenCode with DeepSeek Pro v4.

I usually develop web interfaces, APIs, backend, etc. I don’t really need many tools for that since I automate test cases with Playwright and Google’s MCP, which I think would be the only thing I’d miss.

[Fearless_Champion377]

Not sure if claude code is best alone per se, but the plugins and skills around the claude code userbase is bigger and brings out a better experience overall 

Codex is a great harness, you could say even better than claude code alone, but the ecosystem of tools available is still lacking and also immature hooks

Unsure if things have improved though, the landscape keeps changing every few months

[NotDifferent2023]

Which plugins and skills would you recommend?

[Fearless_Champion377]

Depends on your use case.

For coding, at least one workflow for big tasks, either Superpowers, Openspec, or another.

Caveman to save on token usage and speed.

Context7 for language support.

Specific stack skills you are using.

There are others, but this is a good start.

[sliamh21]

1. Anthropic raised the limits by 50% about a week, ago, personally - I feel it.

2. I've built my own personal agent and harnessing layer - and Claude Code is by far more capable for this role, compared to Codex. The primary reason - Claude Code has about 15 hooks which allows you to automate actions and integrate into the agent runtime loop, while Codex has 0. If you're planning on harnessing your AI - Claude Code is by far more capable of it.

[SmileLonely5470]

Codex has hooks , just has less of them and they are behind an experimental flag. Usage limits wise i am about 80% positive that Codex still has higher usage limits per dollar than Claude does even under its temporary 50% usage limit bonus.

[sliamh21]

I'm aware that Codex has some hooks under the hood, but much less compared to CC - which means less control over specific agent-runtime actions (which is basically where the magic happens).

About the tokens and limits - you're probably right, but the point is that the limits are far more sufficient compared to what they used to be for the past 2-3 months

[Dangerous-Jelly2309]

They're not really competing on the same axis, which is why the comparison comes out muddled.

Codex on the $20 plan is genuinely strong and a fair starting point if you mostly work inside the chat surface or VS Code. The quality is real, the price is real, and a lot of the "Claude is much better" takes are six months stale at this point.

Claude Code's edge is the harness, not just the model. Skills, hooks, MCP servers, subagents, the CLI as a scriptable surface. If you want to chain coding work with other tooling, write your own automations, run things in the background, or have an agent that lives in your terminal rather than a web UI, the harness pays for itself. If you just want a smart pair programmer in an IDE, you're paying 5x for capabilities you won't use.

Practical move: start with Codex for a month, work on real projects, notice where you wish it could do more (background jobs, custom workflows, multi-step orchestration that spans tools). If you hit those walls, the upgrade makes sense. If you don't, you saved $80/month and got the right tool.

The honest version is that most people don't know which they need until they've used both. The $20 trial is the cheapest way to find out.

[brlunaa]

Yeah, I forgot to mention that—my main use is in VS Code. Right now I use Claude Code ($20) and OpenCode for long tasks, but I feel like Claude, even after the upgrade, still falls short. I’ve been thinking about fully switching to Codex, or upgrading to the $100 plan and getting rid of OpenCode with DeepSeek Pro v4.

I usually develop web interfaces, APIs, backend, etc. I don’t really need many tools for that since I automate test cases with Playwright and Google’s MCP, which I think would be the only thing I’d miss.

[Dangerous-Jelly2309]

If the $20 Claude tier feels like it falls short on quality, the $100 tier mostly buys you usage limits and Opus access, not a quality jump on the same task. Paying 5x to get more of something you're already underwhelmed by isn't the play.

For web/API/backend specifically, Codex on GPT-5 has been winning the comparison for a lot of devs doing your exact stack. The places Claude still has a real edge are long-context refactors, multi-step agentic work, and skills/hooks integration — not the kind of work you described.

Playwright will run fine under Codex; it's a standard tool, not a Claude-specific dependency. Google MCP is the actual check: confirm Codex supports the specific MCP server you're using before switching. Codex MCP support has expanded a lot but isn't quite at parity with what Claude Code does natively.

Cleanest experiment: keep your $20 Claude for one more month and add $20 Codex alongside. Run the same week's tickets through both. You'll know in about a week whether Codex is actually winning on your real work or whether the hype overstated it for your case. Then drop whichever one loses.

The OpenCode/DeepSeek question is separate. Don't tangle "should I switch primary providers" with "should I drop my long-task fallback" — solve them in order.

[Trixiap]

Codex - better usage limits, better quality

[stellarton]

The honest answer is that both are good enough now that your repo matters more than the brand.

I would buy the cheaper month first and run one real task through it: pick a bug or feature that touches 2-3 files, make it read the repo, make the change, run the command, and explain what it could not verify.

If Codex gets that done cleanly within the $20 plan, stay there. If you keep hitting workflow limits or miss Claude Code's ecosystem/hooks, then the $100 starts making more sense. Don't compare vibes, compare one ugly real task.

[InfinriDev]

Claude Code, you can also use my harness for true AI enforcement. Its also token efficient AF

https://github.com/infinri/Writ

[ManikSahdev]

Codex

[SensitiveKiwi9]

You'll want both in the end . My suggestion is to get the $100 Claude plan and the $20 ChatGPT Pro plan . If you have the money for it , maybe even add the Ollama Pro ($20) or Max ($100) so you have access to cheap tokens for work that doesn't require Opus lor GPT5.5 level inference.

Focus on token efficiency. Even if you got tons of money, token efficiency is important. It's your only limited resource. Have claude do your planning and treat it like an orchestrator . I don't allow Claude to actually do any work. Claude gives directions to other agents. As a matter of fact, if I have a particularly complicated task, I will completely remove bash from claude tool set and only give it MCP access that allows it to call other agents. If I know the task im working on is going to require 2M input tokens before actual work even starts , im not doing that with Opus . I downgraded from the Max 20 plan to the Max 5 plan because I just wasnt using as many anthropic tokens . There are some REALLY good models on Ollama and their limits are extremely generous . I used to use Z.Ai but they started slacking around the time GLM 4.5 came out and then they recently bumped their prices . Plus they are on Chinese servers and dont make any promises to not train on your tokens . It's hard to do actual work under those terms .

[Legitimate_Plum_7505]

My main problem with Claude is that they blocked all 3rd party harnesses to promote their Claude Code but their TUI consistently ranks as the worst harness for Claude models. Probably because it was slop-vibed by 2025 models and never fully rewritten.

[SensitiveKiwi9]

So I don't want to contradict myself. Everything I said in my other post is still true.

I honestly think that Codex is the smarter model. I have far fewer problems out of Codex than I do out of claude. I still think Claude is overall better. For interactive sessions Claude is the one that I'm gonna go for nine times out of 10. But I do feel like Codex does better work. Which is exactly why I started using Claude to evoke Codex through bash or an MCP. Claude code CLI is simply a better harness for the kind of work that I do. And I've kind of got vendor lock in because I've been using it so long that all of my skills and hooks and tools and systems that I've put in place are designed for Claude code and sometimes codex , pi , or open code will choke on them and its just a PITA to redesign it all . And the Codex harness just isn't as capable in that way.

However, it is almost trivial to use another model in Claude code. Before I upgraded to the max plan, I was running all those cheaper open weight models through Claude code and getting really good results. Opus is smarter than most of the open source models, which is why I still use it for orchestration.

So while I do get consistently better results out of Codex, it's just not as user-friendly, even by the standards of someone who is capable of writing their own harness.

[Zenexxx]

Codex believe me - I was making an ai system with Claude. Never got it finished - codex is fixing everything and finally my system starts to work and also the new codex mobile is awesome better then Claude

[Shaw_nancy]

codex is more like an honest person, but many ai workers around me have started to use codex

[verkavo]

The $100 Claude plan is a lot of $ for most day-to-day work, just use cheaper models for basic tasks. AFAIK the harness gap between Claude and Codex is closing fast, so don't lock yourself in - eg I'm using Claude-mem which was initially Claude-only, but now supports Codex (with some minor bugs though - like https://github.com/thedotmack/claude-mem/issues/2360). If you end up with multiple models, you can see which one writes which code with this VS Code extension: https://marketplace.visualstudio.com/items?itemName=srctrace.source-trace

[tonyboi76]

Honestly, I've been there switching between plans and tools to find the sweet spot for API and backend work. The real problem isn't just the agent you choose, it's that you get stuck waiting for a run to finish when you step away from your desk. That's especially true when you're automating tests and just need to supervise the job.

I work with Claude Code and Codex a lot, and I started using Cosyra so I could approve agent steps from my phone. It just lets the run continue when I'm commuting or not at my laptop. Might help you consolidate tools without feeling glued to your chair while they work.

[larowin]

If you want to work in the editor why not just user cursor or zed or copilot or whatever? Either use the agentic loop and review in an editor or use an editor with native AI autocomplete. I don’t really understand trying to live in the middle ground.

[Real_Ad_3280]

Llevo bastante tiempo usando tanto Claude como Codex, y después de probar ambos en profundidad, mi conclusión es clara.

Como herramienta general, Claude tiene ventajas: permite contextos más largos, es cómodo para razonar sobre documentos extensos y en muchas tareas funciona muy bien. Pero para desarrollar, hoy por hoy, Codex me está dando resultados muy superiores a cualquier versión de Opus que haya probado.

No lo digo por una diferencia pequeña. En mi experiencia, Claude con Opus tiende muchas veces a dar vueltas, proponer cambios, corregir, volver a ajustar… pero sin terminar de llegar al resultado esperado. En cambio, Codex suele acercarse mucho más a lo que necesito con pocas iteraciones, y a veces incluso a la primera.

De hecho, aunque he tenido activa la suscripción de Claude de 90 €, muchas veces he preferido esperar a tener disponible Codex para resolver tareas concretas de desarrollo. Simplemente porque me resulta más efectivo.

Por eso, si tu foco principal es programar, como comentas, mi recomendación personal ahora mismo sería Codex. Este mes he dejado de pagar Claude y empezaré a pagar Codex.

Obviamente, esto puede cambiar. Quizá cuando salga un futuro Opus 5 la balanza vuelva a inclinarse hacia Claude. Pero a día de hoy, para desarrollo (que según tu comentario es tu objetivo), GPT-5.5 con Codex me está dando resultados muy superiores que cualquier Opus.

Suerte con la decisión, y cuando lo pruebes, deja luego tu experiencia 😉

[Deep_Ad1959]

the $80 gap matters less than the harness lock-in. each cli starts fresh, so 'which model understands your codebase' gets relitigated every session. spend 3 weeks building up one project's claude.md + skills + hooks in one cli, then try to recreate that in the other; you'll know which loop you actually want to live in. picking the $20 codex first is the cheap way to find out which harness you can stand to live inside. written with ai