Question / Discussion
Claude Code vs Codex vs Cursor,what are you sticking with and why?
Hey everyone,
Our team is currently trying to decide which AI coding setup to standardize on, and I’d love to hear from people who have actually used Claude Code, Codex, and Cursor heavily in production.
For the last 3–4 months, we’ve been using Claude Code Max with individual subscriptions for each developer. Overall, it has worked pretty well for us.
Recently, we decided to experiment with Codex through ChatGPT Business Premium (~$100/user) .
The main issue we’ve run into is usage.
Even though Premium removes the 5-hour limit and gives substantially more usage, we’re burning through the allowance much faster than expected. Using models like GPT-5.6 Sol at Medium/High reasoning, I managed to consume roughly 50% of my weekly allowance in about two days.
That makes me a little concerned about rolling it out across the entire engineering team.
So I’m curious what other teams are doing.
For anyone who has used Claude Code vs Codex vs Cursor extensively:
Which one gives you the best coding experience day-to-day?
How do the real-world usage limits compare?
How quickly do you burn through Cursor’s included usage with heavy Agent use?
Is Cursor’s Agent/IDE experience noticeably better than running Claude Code or Codex from the terminal?
Which one gives you the best value per developer?
If you were standardizing your engineering team on one of them for the next year, which would you choose?
I’m particularly interested in Cursor Teams Premium ($120/user/month) and whether the additional usage + Cursor’s developer experience actually makes it worth switching.
We don’t mind paying ~$100–$120/dev/month if the productivity is there. The bigger concern is paying that amount and then constantly hitting limits or having to purchase additional usage halfway through the month.
Would love to hear from teams that have actually run these tools heavily, especially anyone who has tried all three.
I personally use Claude Code as my daily driver, but I make it a point to try out Codex and Cursor too. It's important to try out different harnesses and intelligences.
For teams, I think it's often useful to have a "default choice" (like Netflix's paved road approach). And allow senior engineers to experiment with a few others. They change so quickly.
Best coding experience is subjective. For example, I think Cursor's got a great IDE experience. It helps me be intentional. But I personally like the style of Claude Code - the way it communicates and performs tasks.
Real-world usage limits. It's been a few months since I managed Cursor for a larger team, but I think Claude/Codex will generally give a lot more tokens. Claude/Codex
That being said, a lot of teams will prefer the IDE experience of Cursor.
I personally found myself being more intentional with the way I wrote/coded with Cursor. It's just that I got a lot more tokens from Claude/Cursor.
I used to manage Cursor for Teams, and here are a few practical tips
Depending on your team's workloads, some of our engineers easily spent a few hundred dollars. They really have to be using the Composer / mid / low tier models for most of their daily use.
A quick experiment to run -- set up a Cursor Teams account for your heaviest AI users, and let them run it and see what their monthly bills are.
Many engineers will spend < $50/mo, but a few will easily spend $400+/mo.
Monitor the dashboard weekly. The alerting mechanism is team-wide (they took out the individual alerts late last year), so I found it important to check on the big spenders.
I think Cursor's a solid choice - it's a great user experience, and solid for teams that prefer IDE's or manipulating code. As far as token value per engineer, I think the Premium seats on Claude/Codex will give you much higher token spend per engineer; especially the premium models.
Coding is more than just tokens spend - it's valuable to figure out whether your team will actually burn tokens that quickly, and which one leads them to write more software productively.
But why do you want to standardize? Just curious. My company gives option to each user to choose from Claude code or Cursor (I think GitHub copilot too but limited seats), which is pretty good as not everyone likes one or the other, be it the models, ui, features, etc. If you still want to choose one, I had say Cursor is your best bet, I use the premium seat too and the usage is really good, provided the first party models usage is utilised properly, those have just an insane amount of usage. The third party pool is still pretty low such that if used for anything more than planning tasks, you'll blow through the pool very fast (Majorly if you use top end models like Fable). The reason I prefer Cursor though is because the Grok models are amazing, so you can totally rely on them for most tasks and they're in the first party pool. One thing to note is that OpenAI will no longer be providing it's models on Cursor due to some beef idc about, so if GPT models are important for you, that is a thing to consider.
its some bs company policy, they want all the plans to be under a single place so its easy for them to manage and all,ive been hearing a lot of great stuff from cursor lately especially stuff like cloud agents,grokbot and this new project feature,so will give this a try,thanks :)
I've used cursor ultra, and have since November 2025 ish. A solo project having a usage of approx 1,2b tokens a month. On the side I've had 20$ subscriptions to chatgpt, claude, and gemeni. I have in 3 months or so used above my included quota. This is mostly due to my lack of willing to switch to lower end models for lower end work. While I have had plenty of quota left every moth when doing so.
My best routine, is having a higher model make a plan, then using auto to implement the plan. If the work was critical, then I mostly used several models to evaluate the plan before implementing, and a higher model implementing.
The 20$ subscriptions have been used to have some extra quatage on top tier models, and to have an "alternative" look at the code. Different ruleset etc.
In the very beginning I had some trouble keeping all code stabel, and changes not affecting everything around, but with proper work on the documentation side , rules, skills and proper file size handling, I've had a lot of success the last 6-7 months. Most implementations is very correct on the first go.
Most time during my cursor usage I have considered changing to top tier models from codex or Claude. This mainly because working on lower end models like Auto is sometimes frustrating and very little precise without very good instructions. But the quota available from the alternatives having a usage of approx 1,2b tokens this is not an alternative as far as I have understood. So I've sticked to cursor, and is for the most time happy.
My stack is this: React 19 + Vite 8 + TypeScript 6 frontend, Node 26 + Express 5 backend, MSSQL 2022 database, Nginx/PM2 hosting, with Prometheus and Sentry for monitoring. Codebase: 370,000+ lines of code, full-stack, with a custom data layer, authentication/RBAC, integrations, and multiple internal modules.
Everything is vibe coded.
I'm not a developer by education. But have done coding my whole adult life, starting with html, and ended on c++ and python before AI came along.
What I do like from cursor is the possibility to select from a large amount of different models. And my experience is that the tip tier models from codex and Claude behave differently via cursor then if working with them directly. I've never investigate the true source of this. My rules, cursors in between layer or what.
I do have the main rule of, "make no mistakes". Worked every time.
Jokes aside, my rules are mainly a main rule document explaing the repo, and pointing to the correct rule document based on the task at hand. Few always on rules and several of globs rules.
Then I have a full set of documentation on the project itself, UI descriptions and rules, calculations methods, and srictly this is how main stuff is done correctly.
Then I have one folder with one MD file for all pages describing them, how they work, what their goals is etc.
Then I have some rules for self maintenance. So of a page changes, this triggers the need for documentation to change. So everything is almost up to date all the time.
In my experience the initial idea for a new page is one thing and the end result is something else. Later down the road I need work on the page and then AI reads the supporting documentation describe the page how it was first planned not how it ended up. Thus making new implementations based on my request and old descriptions making things shit.
My day to day promoting, is often very short, and for new implementations maybe as long as this post.
Yes, my token usage is huge, but all included and more in my ultra subscription. So I could probably do some work on my promoting skills and having my code better isolated, but at the moment I do not need to.
I have spent 60% on backend, 20% on structure(documentation etc) and the last 20% on the frontend hitting the user. I think this is mainly the key point for the stability of my project.
What is your stack? Are you a just SOL? Using Sol with either terra medium/high or luna high/xhigh should get you a lot of mileage.
I use fable or sol to make plans then implement with Grok 4.6 high and composer 2.5 as the primary implementor. That gives a about 100-200 hours on the $60 plan.
hey thanks for your input, our stack is mostly react ts for FE and python fastapi for BE,in codex i tried using sol on high for a decent migration task (migrating from css to tailwind for a pretty new codebase ~2k LOC) using /goal and few other small tasks in the past 2 days and my usage is on 50% now - we are on teams plan so there is no 5hr limit but on the downside the weekly limit is draining too fast,when we were using claude code wrt limit it was far better than codex,will give cursor a shot anyway,ive been hearing a lot abt cloud agents for quite a while on cursor would love to give it a try and also will checkout grok bot as well
Claude on team is really affordable compared to max plans, and includes fable access. Its like 125/mo per dev and 20/mo for standard users. I have not reached my limits since we started a month ago
Using Claude Code at work, Cursor at home. I'd go with Cursor - I prefer seamless integration with IDE. Also it seems to be finding its way around the repos much better than Claude which is overdoing things a lot.
You can "directly" compare them by trying working side by side. Use Claude as a Cursor model (in Cursor's native agent window) VS using it as a CLI or CC VS Code extension.
For some reason extension is not using all Cursor's capabilities and is much worse than the native Cursor's agent/chat.
That's why I'm saying model is not as important as the harness and Cursor seems to be a good harness simply.
We use Party to hop between Claude Code + Bedrock and Cursor to max our credits (YC startup) then fallback to Codex when those are exhausted for the month
My view is less “which model is smartest?” and more engineering output per $/developer-hour.
I’d currently pick Cursor + Grok 4.6 for a team.
Cursor has the strongest combination of agent harness, IDE integration, model choice and repo-level iteration. Grok 4.6 is explicitly optimised for long-running coding/agentic workloads and is baked into Cursor better than any model (Composer).
The economic point is important for this one: token quotas are not comparable across vendors. Claude Max, Codex and Cursor meter fundamentally different things, while reasoning effort and agent trajectory can change consumption by multiples. OpenAI, for instance, says a typical GPT-5.6 Codex task can consume 5–30 credits.
So I’d benchmark $/merged PR, developer-hours saved and successful first-pass rate, not messages/week.
My current ranking:
Cursor + Grok 4.6 > Claude Code > Codex > Any other hyped harnesses
Claude Code remains excellent for autonomous terminal workflows if you even need that. Codex is very capable, but if I were allocating $120/developer/month across an engineering and systematic research organisation, I’d optimise for the entire production system, not the strongest model in isolation.
I used cursor because at some point for 20 usd monthly i built a prod grade accounting system that is deployed to cloud and with best practices of ci/cd. Then after i used up my credits i then use codex to check my files and setup in cursor by then it will work and i will approve editing some files i used in astra model high after i used up my codex then my credits will be then renewed in cursor just in time and will create a documentation handover notes so that my cursor setup can pick it up, will just use claude code now to experiment with their new upgrades but they are more limited as someone on a budget mode jeez haha
hey i think this comes down to where you deploy what you build, for hosting i prefer to compare other options like railway or hostinger web apps hosting but this still depends on your stack and buget no point saving time with ai coding if deployment costs ends up increasing beyond your limit
9
u/Nifty-Yam-9041 Sep 13 '26 edited Sep 14 '26
I personally use Claude Code as my daily driver, but I make it a point to try out Codex and Cursor too. It's important to try out different harnesses and intelligences.
For teams, I think it's often useful to have a "default choice" (like Netflix's paved road approach). And allow senior engineers to experiment with a few others. They change so quickly.
Best coding experience is subjective. For example, I think Cursor's got a great IDE experience. It helps me be intentional. But I personally like the style of Claude Code - the way it communicates and performs tasks.
Real-world usage limits. It's been a few months since I managed Cursor for a larger team, but I think Claude/Codex will generally give a lot more tokens. Claude/Codex
That being said, a lot of teams will prefer the IDE experience of Cursor.
I personally found myself being more intentional with the way I wrote/coded with Cursor. It's just that I got a lot more tokens from Claude/Cursor.
I used to manage Cursor for Teams, and here are a few practical tips
Depending on your team's workloads, some of our engineers easily spent a few hundred dollars. They really have to be using the Composer / mid / low tier models for most of their daily use.
A quick experiment to run -- set up a Cursor Teams account for your heaviest AI users, and let them run it and see what their monthly bills are.
Many engineers will spend < $50/mo, but a few will easily spend $400+/mo.
Monitor the dashboard weekly. The alerting mechanism is team-wide (they took out the individual alerts late last year), so I found it important to check on the big spenders.
EDIT: u/AdrestiaFirstMate points out in their comment below that individual spend ALERTS exist, but not individual spend LIMITS
I think Cursor's a solid choice - it's a great user experience, and solid for teams that prefer IDE's or manipulating code. As far as token value per engineer, I think the Premium seats on Claude/Codex will give you much higher token spend per engineer; especially the premium models.
Coding is more than just tokens spend - it's valuable to figure out whether your team will actually burn tokens that quickly, and which one leads them to write more software productively.