Hi All,
This might be common knowledge but it will be still useful to newbies.
Most months i barely cross the cursor limit as i am not into vibe coding or heavily dependent on cursor.
But recently I was heavily using Claude 3.5/3.7 for developing a new UI component and used nearly 430 fast responses in just 2 days,
with plenty of time still left on the project. So i came up with the below flow to mange my credits
The Workflow:
To make my remaining responses last, I started using a two-step process involving Gemini:
Leverage Gemini for Iteration (Free/API Based):
Add your Gemini API key to Cursor settings.
Use the “Ask” mode extensively with Gemini (I used 2.5).
Iterate on requirements, discuss changes, brainstorm features, etc.
Finalize a clear, actionable list of code changes.
This planning phase does not consume Cursor fast responses.
Use Claude for Precise Edits:
Switch back to Claude 3.5/3.7 or any paid model you prefer
Use the “Edit/Manual” mode.
once the change list is ready i switch over to claude 3.5 and this time choose the edit feature and tell it to make changes as per the change list we have created. this way get things done that cost me 4-5 fast response normally
Tell claude to apply changes as per the change list we have created.
This targeted approach often helps me one shot the changes compared to the 4-5+ I would use up to make claude fully understand my requirements.
For this to work always enable large context window in settings as the chat window can get too long and claude might miss on important contxt otherwise
By using this workflow i have noticed that i am prety much able to continue using a single long chat window,
instead of spawning new ones as claude used to get retarded beyond a certain point unlike gemini which seems to maintain sanity over large chats.
By providng claude with an actionable list it largely manages to stay on the rails and one shot the changes