Back to Community
How I bypassed Claude 3.7's context window limitations in Cursor without paying for Max mode
Confident_Chest5567 March 25, 2025
309 likes
https://preview.redd.it/1gchm8y3iqqe1.png?width=179&format=png&auto=webp&s=efaae42fd9740cf08cfb6305c4b5e26d23150901
Hey r/cursor
I've been using Claude 3.7 in Cursor for my development work, but kept hitting that annoying context window limitation. The Max variant gets the full 200K context window, but costs $0.05 per request PLUS $0.05 per tool call (which can add up quickly with 200 possible tool calls).After some digging through the application code, I found a way to modify Cursor to give regular Claude 3.7 the same 200K context window as the Max variant. Here's how I did it:
# The modification
1. Located the main JavaScript file at resources/app/out/vs/workbench/workbench.desktop.main.js
2. Found the getEffectiveTokenLimit function (around line 612) which determines how many tokens each model can use
3. Added this one-line hack to override the limit specifically for Claude 3.7
`async getEffectiveTokenLimit(e) { const n = e.modelName; // Add this condition to override for Claude 3.7 if (n === "claude-3.7-sonnet") return 200000; // Rest of the original function... }`
# Results
* Regular Claude 3.7 now uses the full 200K context window
* I can feed it massive codebases and documentation without hitting limits
* It still has the 25 tool call limit (vs 200 for Max), but that's rarely an issue for me
* No extra charges on my account
# Why this works
The context window limit isn't hardcoded in the client but comes from the API server. However, the client caches these limits locally, and by modifying the getEffectiveTokenLimit function, we intercept the process and return our own value before the client even asks the server.
NOTE: This might break with Cursor updates, and I'm not sure if it violates any terms of service, so use at your own risk.
HERE IS THE GITHUB WITH ALL THE INSTRUCTIONS:
[https://github.com/rinadelph/CursorPlus](https://github.com/rinadelph/CursorPlus)
Has anyone else found cool hacks for Cursor? I'm curious what else can be tweaked to improve the experience.
Comments
More Community
View allSomeone did a deep dive into Cursor Agent and discovered that it was literally just Claude Code with a process that does search and replace to brand it as Cursor Agent
[https://gist.github.com/jasonkneen/4c065df2d7a95610e4fd30c3e3398b17](https://gist.github.com/jasonkneen/4c065df2d7a95610e4fd30c3e3398b17)
D
DrySalamander9728 178
How I use Cursor 10+ hours a day without torching my Claude Opus 4.6 limits
Anyone else here doing full-stack Next.js in Cursor and watching the Claude quota evaporate before lunch? I used to be in the same boat — massive context windows from all the components, pages, and DB logic would smoke the default limits fast. Not anymore. I’ve been on this setup for weeks and basically never hit a wall while still getting top-tier answers. Here’s exactly what I do: **1. .cursorrules is non-negotiable** I keep one in the root of every project. The key line I added: “Never explain the code to me. Just output the code blocks.” That single rule saves me thousands of output tokens a day. No more walls of “here’s what I changed and why” — just the goods. **2. Stopped using Cursor’s built-in Claude quota** I killed the default Cursor Pro subscription for the heavy stuff. Instead I use my own API keys and point Cursor’s “OpenAI Compatible” base URL at LLM Router Gateway. Inside [llmrouter](https://llmrouter.app/) routing settings I set up simple tags routing like this: * **UI & CSS tweaks**: gemini-3.1-flash → gpt-5.4-mini * **Deep backend / complex logic**: claude-opus-4.6 → deepseek-v3.2 * **General / quick questions**: llama-4-scout I sorted the fallback chains by speed vs intelligence. The router auto-detects the query type, so 90% of my UI polish and small fixes go to Gemini (basically free + huge context). I only actually hit Claude Opus 4.6 when I’m doing nasty database refactors or tricky architecture stuff. My Anthropic bill dropped \~70% overnight. **3. Cmd+K for everything small** Don’t open the full chat sidebar just to rename a variable or extract a component. Highlight the code, hit Cmd+K, let a fast model handle the inline edit. Saves a ton of tokens and feels way snappier. That’s it. Super simple but it completely changed how much I can actually use Cursor in a day. How are you all managing the limits? Using a Cursor Team? Or did you build your own router hacks too? Drop your setups — always looking to steal better ideas.
Y
Youssef_Wardi 310
Cursor V3 is a significant regression
So I used to be a big cursor fan - striked the right balance between trusting the AI and being able to check the work. The new version however, sucks. Worktrees are now essentially AI initiated magic git commands that require manual approval, which is slow and annoying, and means I have to read through a bunch of git guff, and I have to wait like a minute before it does any real work for it to essentially do something that can be duplicated with a script, and it doesn't work well half the time - it had to retry twice to apply worktree changes! The new agent screen is pretty useless, because now you need to go and select a bunch of information that previously would be entirely obvious from context i.e. alt-tabbing into a specific repo's IDE. I don't like this direction and if they continue, I might start looking at competitors. Cursor is clearly aimed at and used by developers who can read code and want to read the code produced by AI. I use Claude Code if I want to just trust the AI.
E
ExaminationNo8522 212
Introducing Cursor 3
We’re introducing Cursor 3. It is simpler, more powerful, and built for a world where all code is written by agents, while keeping the depth of a development environment. With the new Cursor, you can run as many agents as you want, everywhere you want: locally, in a worktree, on remote ssh, and in the cloud. And it has the best parts of the editor available when you need them. The new interface is available as a separate window that complements the IDE. Update Cursor to try it. We recently launched Composer 2, a frontier model with high limits. Then, with cloud, we gave agents their own computers so they can work truly autonomously. And now with Cursor 3, we’re releasing a new interface to collaborate with agents on software.
L
lrobinson2011 184
Cursor 3 out now
Cursor 3 out now
G
Graniteman 125
They kinda cute
They kinda cute
S
sugandalai 828