Tale v0.4.7

0.4.7 is a fix release on the 0.4 line — an in-place update: tale update, then tale deploy. No data migrations ship with it.

Highlights

Chat no longer dies mid-plan when the tool-round budget runs out, and reply ceilings follow the model catalog. A document-heavy turn that hit MAX_TOOL_ROUNDS used to withhold tools on the forced last round and say nothing — the model announced its next lookup and stopped. The last offered round now tells it to batch every remaining lookup as parallel calls; the forced round tells it the budget is spent, to answer from what it read, and to state coverage honestly. The reply ceiling was a constant 4096 whatever the catalog declared — a 1M-context / 384k-output model still got max_tokens: 4096 and cut off mid-sentence. Default and thinking maxTokens now follow the declared maxOutputTokens; 4096 survives only as the undeclared-entry fallback. (#2980)

Behaviour changes

• The tool-round budget is steered on the wire, not enforced silently. Two user-role notices (truncation-notice pattern; never persisted): the last offered round asks the model to batch remaining lookups as parallel calls; the forced round says the budget is spent and to answer from what it already read. Tool docs declare the per-reply lookup budget up front. (#2980)
• Reply and history ceilings come from the catalog. maxTokens follows declared maxOutputTokens; the remaining structural rule is the output share (half the window) so a huge declared output cannot starve the history slice. Governance that shrinks the effective window re-fits sampling so the maxTokens > budgetTokens wire invariant survives. (#2980)
• The flat 96k history cap is gone. The history slice is the effective window minus output reserve and system prompt. Cost control is the explicit governance maxContextTokens cap, not a hidden constant — long threads on 1M-window models now replay what the window allows. (#2980)

Migration notes

No new data migrations in 0.4.7 — tale deploy is an image update only. Updating straight from 0.4.0 applies the four 0.4.1 migrations automatically on the way.

Upgrading

tale update    # a 0.4.x CLI stays on the 0.4 line and picks up 0.4.7
tale deploy    # pulls the 0.4.7 images

On 0.3.x? The 0.3 → 0.4 cutover is a fresh deployment, not an upgrade — read the v0.4.0 release notes and Upgrades → 0.3 → 0.4: breaking cutover before moving.

What's Changed

• fix(platform): steer chat tool budget and derive limits from catalog by @larryro in #2980

Full Changelog: v0.4.6...v0.4.7