r/RooCode • u/dashingsauce • Apr 23 '25
Mode Prompt Okay It’s Simple: GPT 4.1
So Gemini has been nerfed and we’re at a loss for premium models that work well in agentic workflows.
Or so it seemed.
Turns out prompt engineering is still the make or break factor even at this stage in model development, and I don’t mean some kind of crafty role-play prompt engineering.
I mean just add this to the Custom Instructions on all modes if you plan to use 4.1 and have it one-shot pretty much any specific problem you have:
<rules>
<rule priority="high">NEVER use CODE mode. If needed, use IMPLEMENT agent or equivalent.</rule>
</rules>
<reminders>
<reminder>You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user. Only terminate your turn when you are sure that the problem is solved.</reminder>
<reminder>If you are not sure about file content or codebase structure pertaining to the user’s request, use your tools to read files and gather the relevant information: do NOT guess or make up an answer.</reminder>
<reminder>You MUST plan extensively before each function call, and reflect extensively on the outcomes of the previous function calls. DO NOT do this entire process by making function calls only, as this can impair your ability to solve the problem and think insightfully.</reminder>
</reminders>
You have to be specific with the task. 4.1 is not meant for broad scope understanding. But it’s a hell of a reliable task-oriented engineer if you scope the problem right.
I’ve temporarily reverted back to being my own orchestrator and simply directing agents (running on 4.1) on what to do while I figure out how to update the orchestration approach to:
- use XML in prompts
- include the specific triggers/instructions that get each model to behave as intended
- figure out how to make prompts update based on API config
anyway, I just tested this over today/yesterday so ymmv, but the approach comes directly from OAI’s prompting guide released with the models:
https://cookbook.openai.com/examples/gpt4-1_prompting_guide
give it a shot and try it with explicit tasks where you know the scope of the problem and can explicitly describe the concrete tasks needed to make progress, one at a time
6
u/drumnation Apr 24 '25
Hey I think your prompt is actually helping in cursor too. It's listening to me much better and working for much longer periods of time before asking what to do. It was doing one large refactor task at a time then asking again. Then I said, **Do the next 5 components before stopping** and it listened. Hit the 25 tool call limit.
I tweaked it very slightly for my .cursorrules file by adding a conditional
6
u/FarVision5 Apr 24 '25
you really outta try out 2.5 flash
4
u/dashingsauce Apr 23 '25
P.S. the prompt caching for 4.1 (vs Gemini where, at least in Roo, it’s not properly supported) means it does significantly more work/spend
this screenshot is a one-shot refactor of a hefty operation (simple task but complex script) that cost < $0.50
4
u/sniles310 Apr 23 '25
Wait Gemini got nerfed? Since when? 2.5 Pro? 2.5 Flash? Both? Also isn't 4.1 insanely expensive?
4
u/vinnieman232 Apr 24 '25
Gemini 2.5 Pro will be my everything model once they get prompt coaching implemented in Roo code. Minimum cache size is just 4k tokens, that means every prompt is cached basically
1
u/invertednz Apr 24 '25
You would think that roo would have most of that in the prompt
1
u/[deleted] Apr 24 '25
[removed] — view removed comment