Skip to content

Conversation

@cc-bjojac
Copy link
Contributor

The motivation behind this is that when opencode executes my tests in a large project, it truncates the output at some point. I was not able to see what test actually failed in the console.

I made the parameter overridable by an env variable with fallback to the original hard-coded value if it is not present or could not be parsed.

@rekram1-node
Copy link
Collaborator

I feel like a variable with this name would apply to other tools as well, (even tho in your pr it isn't) is that your intention or should we make it bash tool specific?

@cc-bjojac
Copy link
Contributor Author

My intention was to do it only for the bash tool to be honest. I can make the env parameter name more specific like OPENCODE_BASH_MAX_OUTPUT_LENGTH

@rekram1-node
Copy link
Collaborator

/oc adjust the env var to be prefixed by OPENCODE_EXPERIMENTAL_ instead of just OPENCODE_

Update both files

@opencode-agent
Copy link
Contributor

opencode-agent bot commented Nov 20, 2025

Updated both files to use OPENCODE_EXPERIMENTAL_BASH_MAX_OUTPUT_LENGTH instead of OPENCODE_BASH_MAX_OUTPUT_LENGTH.

New%20session%20-%202025-11-20T16%3A42%3A45.241Z
opencode session  |  github run

@rekram1-node
Copy link
Collaborator

I'm going to make this experimental for now because ideally the settings should all be configurable in a much better way.

Experimental doesnt mean im getting rid of it next week it's just so that we dont have to be committed to this var forever

@rekram1-node rekram1-node merged commit a9c56b8 into sst:dev Nov 20, 2025
3 checks passed
@cc-bjojac cc-bjojac deleted the max_output_length_overridable branch November 21, 2025 07:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants