Tale v0.4.9

0.4.9 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 web_fetch pages like rag_fetch — a long page is no longer a dead end. The tool used to clip to the first 20,000 characters with no way to continue, so a longer page (a 39.7k-char weather JSON, a long docs article) sent the model into refetch loops until the turn's step limit. Optional offset/limit now select a window of up to 20,000 characters of the extracted text, and a truncated read reports totalChars plus the nextOffset to continue from. (#2982)

Behaviour changes

• web_fetch accepts offset and limit. Same contract as rag_fetch: limit is 1–20,000 (default 20,000); offset indexes the extracted text (HTML goes through htmlToText), not response bytes. Each window re-fetches the live page and slices — an HTTP Range request could never line up after extraction. (#2982)
• A truncated read reports nextOffset. The model is told to keep fetching until nextOffset is absent, or to say which part it read. truncatedAt is gone from the result; the two fetch tools share one paging contract. (#2982)

Migration notes

No new data migrations in 0.4.9 — 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.9
tale deploy    # pulls the 0.4.9 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

• feat(platform): page web_fetch reads with offset/limit windows by @larryro in #2982

Full Changelog: v0.4.8...v0.4.9