Skip to content

[main] fix: recover tool json without false positives - #144

Closed
Tomlord1122 wants to merge 1 commit into
mainfrom
chore/default-max-tokens-8192
Closed

Tomlord1122 wants to merge 1 commit into
mainfrom
chore/default-max-tokens-8192

Conversation

@Tomlord1122

@Tomlord1122 Tomlord1122 commented Sep 13, 2026

Copy link
Copy Markdown
Member

Background

A single model step still shares one output budget across assistant text and tool JSON. The previous 2048 default cut off medium job descriptions before the arguments were valid JSON. After that recovery landed, reading a file that mentioned the error marker could also look like a schema failure and skip later tools.

d38c627: New installs and unset maxTokens now default to 4096. Saved settings keep whatever the user already chose.

bb1fa41: Schema recovery now uses an explicit invalid-input flag instead of scanning tool output. Complete JSON objects in the same step still run after two truncated payloads.

New installs and unset maxTokens now allow 8k output per model step so
medium documents are less likely to truncate a write_file or run_command
payload. Existing saved settings are unchanged.

Signed-off-by: Tom Liu (Liu Hsiu-Chi) <0xtomlord1122@gmail.com>
@Tomlord1122 Tomlord1122 changed the title [main] chore: raise default max tokens to 8192 [main] fix: recover tool json without false positives Sep 13, 2026
@Tomlord1122
Tomlord1122 deleted the chore/default-max-tokens-8192 branch September 13, 2026 03:01
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.

1 participant