Reported News
Cloudflare Agents SDK 0.33.0 moves the Pi harness to Pi 1.5, cutting storage writes, with no rollback
Cloudflare Agents SDK agents@0.33.0 (November 3, 2026) moves the Pi harness to Pi 1.5, which the release notes say "cuts storage transactions about 27x for long answers" over SQLite. It adds session.watch(), session.continue() and defaults.maxTurns, removes retry() and the parked status, and once a conversation runs on Pi 1.5 a deployment cannot roll back past this release.
- Changes reported
- 6
- listed below, each from a source we read
- We tested
- Not tested yet
- reported from sources; we did not run it ourselves
- Gaps we flag
- 3
- things we could not verify
- Sources
- 1
- 1 primary, linked below
What changed
| # | What the source says | Status |
|---|---|---|
| 01 | The Pi harness, agents/models/pi-ai and the Pi tools now run on Pi 1.5 (~1.5.0); Pi 1.4 is no longer supported, and once a conversation runs on Pi 1.5, Pi 1.4 cannot read it, so a deployment cannot roll back past this release. | Reported |
| 02 | Pi now writes streamed answers and tool output in batches at least every second; the notes say this cuts SQLite storage transactions about 27x for long answers and 5.7x for parallel-tool turns, but a crash can lose up to about a second of output. | Reported |
| 03 | With many sessions, one Pi harness with 2,048 sessions went from 88 to 459 agent runs per second on SQLite, per the notes, and streaming a 500 KB tool call no longer takes about 20 s of CPU and a 100 MB heap. | Reported |
| 04 | session.watch() replaces session.events() and returns the newest transcript entries plus live state; session.entries() pages older entries. | Reported |
| 05 | New session.continue() restarts a run on the existing transcript without a new message, and defaults.maxTurns caps tool rounds, ending a run with reason turn_limit. | Reported |
| 06 | Breaking for Pi users: retry() and the parked status are removed, tool schemas move to the new @earendil-works/pi-schema peer, and onReport now takes one report tagged by kind (session_failed becomes storage_failed). | Reported |
reported by the sourcemeasured or run by usnot verified
Primary source: GitHub release: cloudflare/agents agents@0.33.0. We are the fast, independent index; the vendor’s own page is the source of record for this release.
In the source’s words
“Over SQLite this cuts storage transactions about 27x for long answers and 5.7x for turns with parallel tools, and CPU by about a quarter.”
“Once a conversation runs on Pi 1.5, Pi 1.4 cannot read it, so a deployment cannot roll back past this release.”
Early verdict
If you use the Pi harness, treat 0.33.0 as a one-way upgrade: test it before deploying because you cannot roll back, then update session.events(), retry() and tool schemas. Teams not on Pi can upgrade without code changes, per the notes.
Basis: Based only on the agents@0.33.0 release notes; we have not run this version.
What we have not verified
- We did not run this release or measure the reported storage, throughput or memory numbers; they are Cloudflare's figures.
- We did not review the full pi-durable 1.5.0 changelog the notes link to for further breaking changes.
- The notes say only Pi harness, pi-ai and Pi tool users need changes; we did not check other agents APIs for side effects.
This brief is Reported: written from the sources below, not from running the release ourselves.
Sources
- GitHub release: cloudflare/agents agents@0.33.0primary source · fetched 2026-11-03
Related
Spotted an error? See our corrections policy or email the address on the contact page. Markdown version for agents: /news/cloudflare-agents-0-33-0.md
Want these briefs in your Google Top Stories? Add Agentic Weekly as a preferred source on Google.
Newsletter
The Weekly Verdict. Free, every Monday.
A free email every Monday: the week's few big AI releases, then 5 short use cases for the new models, each with a prompt you can paste.
Free. Double opt-in. One click to unsubscribe.