The problem of overly long bash description #3634

Open
opened 2026-02-16 17:40:57 -05:00 by yindo · 5 comments
Owner

Originally created by @doitcan-oiu on GitHub (Dec 17, 2025).

Originally assigned to: @rekram1-node on GitHub.

Question

I encountered a very strange set of questions in opencode.json

"tools ":{ "bash" : true }

It will prompt: "Error handling response: Request failed, status code 400", and I saw the bash prompt on "toolSpecification". Is it because my model provider doesn't support such long descriptions that these descriptions shouldn't be placed in the userContext? I set bash to false and can make the request

Originally created by @doitcan-oiu on GitHub (Dec 17, 2025). Originally assigned to: @rekram1-node on GitHub. ### Question I encountered a very strange set of questions in opencode.json ` "tools ":{ "bash" : true } ` It will prompt: "Error handling response: Request failed, status code 400", and I saw the bash prompt on "toolSpecification". Is it because my model provider doesn't support such long descriptions that these descriptions shouldn't be placed in the userContext? I set bash to false and can make the request
Author
Owner

@github-actions[bot] commented on GitHub (Dec 17, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #5360: prompt is too long - Similar token/length limit issues
  • #4845: prompt is too long unrecoverable - Same 400 error pattern with long specifications
  • #4866: [FEATURE] Inform the model what shell it's running inside of in Bash tool's description - Related to bash tool description length
  • #4357: Tool argument descriptions lost in schema conversion - Related to tool description handling
  • #3523: [BUG] tools[21].function.name string too long - Related to tool specification validation errors

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Dec 17, 2025): This issue might be a duplicate of existing issues. Please check: - #5360: prompt is too long - Similar token/length limit issues - #4845: prompt is too long unrecoverable - Same 400 error pattern with long specifications - #4866: [FEATURE] Inform the model what shell it's running inside of in Bash tool's description - Related to bash tool description length - #4357: Tool argument descriptions lost in schema conversion - Related to tool description handling - #3523: [BUG] tools[21].function.name string too long - Related to tool specification validation errors Feel free to ignore if none of these address your specific case.
Author
Owner

@rekram1-node commented on GitHub (Dec 17, 2025):

what context size do u have

@rekram1-node commented on GitHub (Dec 17, 2025): what context size do u have
Author
Owner

@doitcan-oiu commented on GitHub (Dec 17, 2025):

what context size do u have

200k

@doitcan-oiu commented on GitHub (Dec 17, 2025): > what context size do u have 200k
Author
Owner

@rekram1-node commented on GitHub (Dec 17, 2025):

hm what provider are u using? Ig we can prolly condense the prompt potentially but i hadnt heard of this

@rekram1-node commented on GitHub (Dec 17, 2025): hm what provider are u using? Ig we can prolly condense the prompt potentially but i hadnt heard of this
Author
Owner

@sowar1987 commented on GitHub (Jan 20, 2026):

Same issue here with Gemini 3 Pro via openai-compatible proxy.
Any tool call fails with 400 "Request contains an invalid argument".
Tested with both Sisyphus and Build agents - same result.

@sowar1987 commented on GitHub (Jan 20, 2026): Same issue here with Gemini 3 Pro via openai-compatible proxy. Any tool call fails with 400 "Request contains an invalid argument". Tested with both Sisyphus and Build agents - same result.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#3634