Repository navigation
Conversation
Contributor
|
The following comment was made by an LLM, it may be inaccurate: No duplicate PRs found |
pschiel
marked this pull request as ready for review
January 12, 2026 19:32
pschiel
force-pushed
the
question-tool-description
branch
4 times, most recently
from
January 19, 2026 16:13
433cd09 to
f8e6aaf
Compare
pschiel
force-pushed
the
question-tool-description
branch
from
January 25, 2026 02:26
f8e6aaf to
bbb1f51
Compare
Contributor
Author
|
updated from 12 to 30 according to new schema |
pschiel
force-pushed
the
question-tool-description
branch
from
January 28, 2026 04:54
bbb1f51 to
3f37116
Compare
opencode-agent
Bot
force-pushed
the
dev
branch
from
January 30, 2026 14:32
00637c0 to
71e0ba2
Compare
thdxr
force-pushed
the
dev
branch
3 times, most recently
from
January 30, 2026 14:37
f1ae801 to
08fa7f7
Compare
pschiel
force-pushed
the
question-tool-description
branch
from
January 31, 2026 23:17
3f37116 to
9f9879d
Compare
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
1 participant
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.
Fixes #7616
Cause: agents sometimes violate the 12-character header limit because JSON Schema constraints like "maxLength": 12 are buried in nested parameter definitions and have lower attention weight compared to prominent natural language instructions in the tool description, causing the LLM occasionally to miss or forget the constraint during generation.
Fix: add it to description text in question.txt