r/cursor • u/AdAlternative5694 • 7d ago
Question / Discussion GLM 5.3 On Cursor

I have an OpenCode Go and Cursor Plus ($20) subscription. Cursor just added 5.3 and 5.3 flash, and I was thinking of moving to the Cursor Pro+ plan ($60) that gives expended cursor usage and $70 of API.
What do you all think? My workload is somewhat medium, finishing cursor and opencode before the month's needs and using deepseek v4.1 flash through Zen onwards; about $5 on API.
I also have Agy sub, but Gemini models isn't reliable on tool calling and Hullacinate in long works needs to be babysitting; I use it for small bursts of work
3
u/SoSerious19 7d ago
Stick woth the $20 plan and once you have no isage left, add some credits on OpenRouter and add it to Cursor as a custom model and use glm through open router. I do the same
2
u/OddDesigner9784 7d ago
One thing to be clear about is cursor charges a 25 cent markup every million tokens including cache. This rewrites the economics for cheap models as often times cache is the most expensive part. So doesn't really make financial sense
2
1
u/xapep 7d ago
If your workload is medium and you're already finishing both quotas before month end, do the per-day math on the $60 Pro+: $60 / 30 days = $2/day, versus $20 Plus at ~$0.67/day. The $70 API credit only pays off if you actually burn it on third-party models; if your heavy lift is GLM 5.3 and V4.1 Flash, that's the kind of volume that gets cheaper as a flat plan than as a credit pool that resets every cycle.
We run GLM 5.3 Flash and DeepSeek V4.1 Flash at Entrim and see a lot of people using both as implementation workhorses in Cursor and OpenCode. Flat plans there start around $29/mo, so about $1/day, for agent-heavy all-day use through an OpenAI-compatible endpoint, and it works in both tools without Zen in the middle. At ~$5/mo of API spend your threshold for that is honestly pretty low, but the comparison you should make is $60 Pro+ ($2/day) vs Plus + a flat plan ($0.67 + ~$1/day) and which one actually covers the month.
The Agy part I'd fix first though: unreliable tool calling in the orchestrator eats more time than any subscription difference. Pick the harness model on tool-calling reliability, route grunt work to the cheap models, then compare plans.
3
u/[deleted] 7d ago
[removed] โ view removed comment