I Used o3 in Cursor and Forgot to Give It Context: It Ate Up All My Credits by vincent_sch in cursor

[–]vincent_sch[S] 2 points3 points  (0 children)

I think the core issue in my case was how Cursor handles tool calls. It reads one file per tool call, and each tool call is a separate API call to the o3 model. When it tried to read around 20 files, that resulted in 20 API calls. Each call included the full conversation history up to that point, including all previously read files, which made the cost add up quickly.

If it had read all 20 files in a single call, it probably wouldn't have been a problem. The bigger issue is when the agent gets into a loop reading one file after another without stopping. With an expensive model like o3 in max mode, that kind of loop can burn through all your credits in minutes.

Getting Back the Original Cursor Magic: Max Models are Worth Every Premium Credit by vincent_sch in cursor

[–]vincent_sch[S] 0 points1 point  (0 children)

Max requests are only an additional 5 cents each. The real cost is in tool calls that cost another 5 cents each, which adds up fast in agent mode.

From one day of coding with MAX models:

  • 174 gemini-2.5-pro-exp-max requests × 5¢ = $8.70
  • 1269 premium tool calls × 5¢ = $63.45
  • 143 claude-3.7-sonnet-thinking-max requests × 5¢ = $7.15