fix: maxOutputTokens was accidentally hardcoded to undefined #10995
Merged
rekram1-node merged 5 commits intoanomalyco:devfrom Jan 29, 2026
Merged
fix: maxOutputTokens was accidentally hardcoded to undefined #10995rekram1-node merged 5 commits intoanomalyco:devfrom
rekram1-node merged 5 commits intoanomalyco:devfrom
Conversation
…disabled The maxOutputTokens was hardcoded to undefined in commit ac53a37, which caused tool calls with large content to be truncated mid-JSON, resulting in "Unterminated string" parse errors.
Contributor
|
Thanks for your contribution! This PR doesn't have a linked issue. All PRs must reference an existing issue. Please:
See CONTRIBUTING.md for details. |
Contributor
|
The following comment was made by an LLM, it may be inaccurate: No duplicate PRs found |
Colin4k1024
pushed a commit
to Colin4k1024/opencode
that referenced
this pull request
Feb 10, 2026
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
maxOutputTokenscalculation that was accidentally disabledProblem
Since v1.1.37, users experienced errors like:
This occurred when the LLM generated
writetool calls with large content (e.g., pasting long code files).Changes
Explanation of the Question
#10967 (comment)
Root Cause
In commit ac53a37, the
maxOutputTokenswas accidentally hardcoded toundefined:Without proper output token limits, some providers would truncate the response at their own default limits, cutting off JSON mid-string and causing parse failures.
When JSON parsing fails, the experimental_repairToolCall of AI SDK cannot fix the malformed input, so it falls back to the invalid tool, resulting in the
[Pasted⚙ invalid [tool=write, error=...error message shown to users.