I broke Roo by using Footgun mode

[mariusursache]

Problem (one or two sentences)

Whenever I overwrite the system prompt for code mode (via a .roo/system-prompt-code file), I start getting read_file tool errors when using the Roocloud/code-supernova model: Roo tried to use read_file without value for required parameter 'path'. Retrying...

Context (who is affected and when)

Anytime footgun (system prompt override) is used, even if used with the EXACT system prompt that the original Roo Code code mode uses. Happens only with code-supernova on Roocloud, not with claude-sonnet-4 and other models

Reproduction steps

1. VSCode + RooCode 3.28.7 on MacOS
2. Attaching the two prompts (original system one and the footgun one - they are identical).
3. If you create a .roo/system-prompt-code file and paste any of these files in
4. And you try to read any file via the Roo Code chat (not even using @ references)

system-prompt.txt
footgun-prompt.txt

Expected result

RooCode reads the file via read_file tool

Actual result

Roo tried to use read_file without value for required parameter 'path'. Retrying...

Variations tried (optional)

Tried different prompts, different projects
Always happens on roocloud/code-supernova - which otherwise works greatly

App Version

3.28.7

API Provider (optional)

Not Applicable / Other

Model Used (optional)

code-supernova

Roo Code Task Links (optional)

https://app.roocode.com/share/a07791ca-654d-431d-9078-570b9307eff5

Relevant logs or errors (optional)

[roomote]

I'm exploring a potential fix for this issue where custom system prompts break the read_file tool for code-supernova. I'll investigate the prompt handling and tool parameter parsing to identify the root cause.

[daniel-lxs]

Hey @mariusursache, We include a warning when you use this that it might break functionality:

So this is expected. The system prompt is dynamic and might change if certain models are selected. Refrain from using it if it's breaking functionality.

[roomote]

I've opened PR #8308 to address this issue: #8308

The fix ensures that tool descriptions are always included in the system prompt, even when using custom system prompt files. This resolves the issue where code-supernova would fail to parse the read_file tool parameters.

The implementation:

• Modifies system prompt generation to include tool descriptions with custom prompts
• Ensures code-supernova gets the simplified read_file format it requires
• Adds comprehensive test coverage for the fix
• All existing tests pass

CI checks are currently running on the PR. Feedback welcome!

[mariusursache]

Thank you @daniel-lxs for the very prompt reply.

Let me give you some thoughts on the solution:

1. It beats the purpose of the footgun approach, which provides a clean slate for experimentation (at the risk of shooting myself in the foot 😉 as the yellow banner says). Some power users prefer to also hack the tool behavior (e.g. format output differently) or reduce/extend verbosity.
2. I do not think it will solve the problem, because I tried with the exact system prompt (so the official tools instructions were included) and I got the same error. The problem might be related to NON-prompt data that is sent differently in footgun mode.

Questions:

1. Is there any documentation here on how footgun mode acts differently (except different prompt text)? What other parameters/flags are sent or not? Or processed differently?
2. Is there a way to check the model response before being processed by RooCode (e.g. the raw tool call)? This would help me better debug the issue.

Thanks!
M

[hannesrudolph]

Thank you @daniel-lxs for the very prompt reply.

Let me give you some thoughts on the solution:

1. It beats the purpose of the footgun approach, which provides a clean slate for experimentation (at the risk of shooting myself in the foot 😉 as the yellow banner says). Some power users prefer to also hack the tool behavior (e.g. format output differently) or reduce/extend verbosity.
2. I do not think it will solve the problem, because I tried with the exact system prompt (so the official tools instructions were included) and I got the same error. The problem might be related to NON-prompt data that is sent differently in footgun mode.

Questions:

1. Is there any documentation here on how footgun mode acts differently (except different prompt text)? What other parameters/flags are sent or not? Or processed differently?
2. Is there a way to check the model response before being processed by RooCode (e.g. the raw tool call)? This would help me better debug the issue.

Thanks! M

Can you please upload the exact system prompt copy you used that broke the flow?