Improve error messaging for short output token lengths #1790
+1
−1
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.
When the output token length is smaller than required for a particular use case, the user sees parsing errors. It is unclear to them that the issue might be with the shorter token length. They might see errors like
for ToolCallingAgents and
for CodeAgents
Issues: #1783, #1732, etc. There are older threads were the issue is mentioned. #201 (comment), Workaround was to increase the output tokens
It is also mentioned that longer contexts are better in an example in the docs
smolagents/docs/source/en/guided_tour.md
Line 189 in f76dee1
This PR tries to