| This text initially appeared on Medium. Tim O’Brien has given us permission to repost right here on Radar. |
Whenever you’re working with AI instruments like Cursor or GitHub Copilot, the true energy isn’t simply accessing totally different fashions—it’s figuring out when to make use of them. Some jobs are OK with Auto. Others want a stronger mannequin. And generally it’s best to bail and change for those who proceed spending cash on a posh drawback with a lower-quality mannequin. If you happen to don’t, you’ll waste each money and time.
And that is the lacking dialogue in code technology. There are just a few “camps” right here; the vast majority of individuals writing about this seem to view this as a fantastical and enjoyable “vibe coding” expertise, and some individuals on the market are attempting to make use of this know-how to ship actual merchandise. If you’re in that final class, you’ve most likely began to appreciate which you can spend a improbable amount of cash for those who don’t have a technique for mannequin choice.
Let’s make it very particular—for those who join Cursor and drop $20/month on a subscription utilizing Auto and you might be proud of the output, there’s not a lot to fret about. However in case you are beginning to run brokers in parallel and are paying for token consumption atop a month-to-month subscription, this put up will make sense. In my very own expertise, a single developer working alone can simply spend $200–$300/day (or 4 instances that determine) if they’re making an attempt to sort out a challenge and have opted for the costliest mannequin.
And—in case you are an organization and also you give your builders limitless entry to those instruments—prepare for some surprises.
My Escalation Ladder for Fashions…
- Begin right here: Auto. Let Cursor path to a robust mannequin with good capability. If output high quality degrades or the loop happens, escalate the difficulty. (Cursor explicitly says Auto selects amongst premium fashions and can change when output is degraded.)
- Medium-complexity duties: Sonnet 4/GPT‑5/Gemini. Use for targeted duties on a handful of information: sturdy unit checks, focused refactors, API remodels.
- Heavy raise: Sonnet 4 – 1 million. If I must do one thing that requires extra context, however I nonetheless don’t need to pay high greenback, I’ve been beginning to transfer up fashions that don’t shortly max out on context.
- Ultraheavy raise: Opus 4/4.1. Use this when the duty spans a number of tasks or requires lengthy context and cautious reasoning, then change again as soon as the large transfer is finished. (Anthropic positions Opus 4 as a deep‑reasoning, lengthy‑horizon mannequin for coding and agent workflows.)
Auto works high quality, however there are occasions when you’ll be able to sense that it’s chosen the flawed mannequin, and for those who use these fashions sufficient, you understand if you find yourself taking a look at Gemini Professional output by the verbosity or the ChatGPT fashions by the way in which they go about fixing an issue.
I’ll admit that my heavy and ultraheavy decisions listed below are biased in the direction of the fashions I’ve had extra expertise with—your individual expertise may range. Nonetheless, you also needs to have an analogous escalation listing. Begin with Auto and solely improve if that you must; in any other case, you’ll be taught some classes about how a lot this prices.
Watch Out for “Considering” Mannequin Prices
Some fashions help specific “considering” (longer reasoning). Helpful, however costlier. Cursor’s docs notice that enabling considering on particular Sonnet variations can rely as two requests beneath group request accounting, and within the particular person plans, the identical concept interprets to extra tokens burned. In brief, considering mode is great—use it whenever you want it.
And when do you want it? My rule of thumb right here is that once I perceive what must be accomplished already, once I’m asking for a unit check to be polished or a technique to be executed within the sample of one other… I normally don’t want a considering mannequin. Alternatively, if I’m asking it to investigate an issue and suggest numerous choices for me to select from, or (one thing I do typically) once I’m asking it to problem my choices and play satan’s advocate, I’ll pay the premium for the perfect mannequin.
Max Mode and When to Use It
If you happen to want large context home windows or prolonged reasoning (e.g., sweeping adjustments throughout 20+ information), Max Mode may help—however it can eat extra utilization. Make Max Mode a non permanent device, not your default. If you end up continuously requiring Max Mode to be turned on, there’s a superb probability you might be “overapplying” this know-how.
If it must eat one million tokens for hours on finish? That’s normally a touch that you simply want one other programmer. Extra on that later, however what I’ve seen too typically are managers who assume that is just like the “vibe coding” they’re witnessing. Spoiler alert: Vibe coding is that factor that folks do in shows as a result of it takes 5 minutes to make a foolish online game. It’s 100% not programming, and to make use of codegen, right here’s the key: It’s a must to perceive how you can program.
Max Mode and considering fashions should not a shortcut, and neither are they a alternative for good programmers. If you happen to assume they’re, you’ll be paying high greenback for code that may someday should be rewritten by a superb programmer utilizing these identical instruments.
Most Vital Tip: Watch Your Invoice as It Occurs
An important tip is to commonly monitor your utilization and utilization charges in Cursor, since they seem inside a minute or two of operating one thing. You may see utilization by the minute, the variety of tokens consumed, and in some circumstances, how a lot you’re being charged past your subscription. Make a behavior of checking a few instances a day, particularly throughout heavy periods, and ideally each half hour. This helps you catch runaway prices—like spending $100 an hour—earlier than they get out of hand, which is fully attainable for those who’re operating many parallel brokers or doing resource-intensive work. Paying consideration ensures you keep in command of each your utilization and your invoice.
Hold Observe and Keep away from Loops
The opposite factor that you must do is maintain observe of what works and what doesn’t. Over time, you’ll discover it’s very simple to make errors, and the fashions themselves can generally fall into loops. You may give an instruction, and as an alternative of resolving it, the system retains operating the identical course of many times. If you happen to’re not paying consideration, you’ll be able to burn via a variety of tokens—and some huge cash—with out truly getting sound output. That’s why it’s important to observe your periods carefully and be able to interrupt if one thing appears prefer it’s caught.
One other pitfall is pushing the fashions past their limits. There are duties they will’t deal with nicely, and when that occurs, it’s tempting to maintain rephrasing the request and asking once more, hoping for a greater outcome. In observe, that usually results in the identical cycle of failure, besides you’re footing the invoice for each try. Figuring out the place the boundaries are and when to cease is vital.
A sensible method to keep on high of that is to keep up a operating diary of what labored and what didn’t. Document prompts, outcomes, and notes about effectivity so you’ll be able to be taught from expertise as an alternative of repeating costly errors. Mixed with maintaining a tally of your stay utilization metrics, this behavior will provide help to refine your method and keep away from losing each money and time.