Skip to content

v1.2.1

Choose a tag to compare

@al2m4n al2m4n released this 19 Oct 10:46
bc687d5

TheYgent 1.2.1 is a patch release with two fixes that apply to every tool, not only to the new ones.

Tool results are capped (#89)

An llm's tool loop used to send each tool result back to the model whole. One web tool returning three pages produced a 50,000-character message, more than a local model's context holds.

  • The cap. Every tool result is now cut at a limit:
    • It applies to builtin, REST, MCP and retrieval tools, in both interactive and durable runs.
    • A marker ends the cut result, saying how many characters were left out.
    • The model still answers from the part it saw.
  • The default. The limit comes from a new platform setting, tools.result_max_chars, on a new Settings → Tools tab.
    • The default is 16,000 characters (about 4,000 tokens).
    • The allowed range is 1,000 to 1,000,000.
    • A change applies from the next run.
  • Per node. An llm node can set its own max tool result characters in its Tools panel. In the IR it's the optional maxToolResultChars; graphs without it keep their content hashes.
  • What the trace records. The run inspector still records each whole result. Each tool span adds tool.result_chars and tool.result_truncated.

A dropped engine request is named, not blank (#89)

mlx-lm's Qwen3 tool parser fails when a model writes plain text where a list or object argument is expected. The failure escapes the engine's handler, and the engine closes the connection without a response.

  • Before:
    • Non-streaming requests ran the same generation three times, through retries, and then failed with an opaque connection error.
    • Streaming requests ended as a blank, apparently successful answer.
  • Now:
    • The inference plane answers 502 engine_dropped_request after one attempt, naming the engine log.
    • On MLX with tools offered, the message also names the likely parser cause.
    • A streaming request ends with an error frame carrying the same code.
  • The engine keeps serving. Later requests to the same engine are unaffected.
  • No retries to managed engines. The inference plane no longer retries a request to a managed engine, because a failure there repeats.

Docs

Upgrading

  • No database migrations.
  • No changes to existing agents or their content hashes; the new IR field is optional.
  • New error code: engine_dropped_request, on the inference plane's /v1/chat/completions.
  • New setting: tools.result_max_chars.

Full changelog: v1.2.0...v1.2.1