The model ran out of room in the middle of its answer. The API says so: finish_reason: length.
Pengy, until this release, did not act on it. A reply that was cut off mid-sentence, with a half-built
tool call at the end, was treated as a normal response.
Now: a completion with finish_reason: length fails before tool execution and before the
assistant's text is written into history. The partial text is labelled incomplete in the error. A
truncated tool call is never executed, which is the part that matters: a tool call that lost the end of
its arguments is a call with the wrong arguments. The single-shot CLI returns exit 1, and JSON mode
returns a structured error with the partial text and reason.
Note what is deliberately not done: no automatic retry, no context reduction. An output cap is not
evidence of context overflow. It means the answer was longer than max_output_tokens, and the fix is
to raise the cap (default 8192, 16384 on the local presets, per-endpoint and per-model configurable),
not to shrink your history. Conflating the two is how a recovery system starts "fixing" problems it
cannot fix.
The same release fixes a web UI reload bug that made a conversation lose its images and render them twice when you reloaded the chat, and a CLI history bug where the chat's own system prompt was counted as a stored message.