Skip to content

v1.2.3 — A cut-off tool call is never the answer

Choose a tag to compare

@BE-AI-Research BE-AI-Research released this 07 Oct 01:51
· 209 commits to main since this release

v1.2.3 — A cut-off tool call is never the answer

The fix

On a long run, a local model writing a whole source file into one write_file call could hit
the output limit mid-call. The unfinished call parsed as no call at all, so the raw fragment —
pages of half-escaped JSON — was shown as the model's final answer and the run ended there.

Now:

  • A reply the output limit cuts off inside an embedded tool call is discarded, never shown as
    the answer
    .
  • The model is told once to re-issue the call in smaller steps (write the file in parts:
    write_file the first part, then extend it with edit_file).
  • If the retry is cut off too, the run ends with a clear error naming the output limit —
    raise max_tokens or the backend window, or ask for the change in smaller steps.

Both the <tool_call> JSON form and Qwen's <function= XML layout are recognized.

The full list is in CHANGELOG.md.

Install

curl -fsSL https://raw.githubusercontent.com/BE-AI-Research/be-code-redux/main/install.sh | sh

You can also update with /update inside BE-Code. Binaries are provided for linux/amd64,
linux/arm64, darwin/arm64 and windows/amd64, along with the VS Code extension
(be-code-vscode-1.1.1.vsix). Checksums are in SHA256SUMS.