Repository navigation
v1.3.1
TheYgent 1.3.1 is a patch release. It finishes the cut-off stream fix from 1.2.1 for remote models.
A remote model's reply cut off mid-stream can be reported (#91)
1.2.1 started checking local engines for streams that stop partway. Remote (openai-compatible) models were still passed through unchecked. When a remote server stopped mid-reply, the dispatch layer closed the stream as though it had finished, and your agent got a shorter answer with nothing to say it was cut off.
- The opt-in. Click a remote chat model in Registries and tick Report a reply cut off mid-stream. Over the management API, it's
"requireFinishReason": trueon the registration. - With it on:
- A streamed reply that stops before the server's own finish reason ends with an
engine_dropped_requesterror frame. - What arrived before the cut is still relayed.
- Streams that end normally are unchanged.
- A streamed reply that stops before the server's own finish reason ends with an
- Why it's off by default. The check relies on the server ending every streamed reply with a finish reason. One that never does would have every reply fail right after the full answer. Anthropic's OpenAI-compatible API was checked and sends one on plain replies, tool calls and replies stopped by a token limit. No other hosted server was checked yet, so the check is opt-in per model.
- Not changed. A request the server drops before it starts replying is named either way, as in 1.2.1. Local engines are always checked.
- The error message. For a remote model,
engine_dropped_requestnow points at the server's own log or the provider's status page.
See A reply cut off mid-stream can read as finished and Troubleshooting.
Also in this release
- Website. The home page now features MoE expert streaming on MLX (#92).
- Contributor docs. Every module has an
AGENTS.mdcontext map, and CI checks that the maps stay in step with the tree (#93).
Upgrading
- No database migrations.
- No changes to existing agents or their content hashes. The new field is on the inference plane's registration only, never on the graph.
- New registration field:
requireFinishReasonon reachable (openai-compatible) bindings, defaultfalse. It is rejected on managed bindings. - Rolling back the inference plane. After 1.3.1 runs,
registry.jsonstoresrequireFinishReasonfor every remote model. An inference plane from 1.3.0 or earlier doesn't know the field and skips those models on load, so re-register them if you roll back.
Full changelog: v1.3.0...v1.3.1