Improvement0.0.81
SDK v0.0.81 — Session snapshots no longer include full conversation transcripts
Session snapshot events previously embedded the entire message history, causing massive bandwidth and memory overhead on large tasks. Snapshots now contain only state metadata (status, usage, model, workspace, checkpoint), with transcripts fetched separately via the session.messages command.
- Session snapshot events no longer carry the full conversation transcript. Every
session.updated(andsession.created/session.detached/run.started) event embedded the session's entire message history, so on a multi-megabyte task each status flip shipped megabytes to every subscriber, flooded the durable event log, and could grow the hub process by one transcript copy per event — reported as a 25 GBclineprocess on a 16 GB machine. Snapshots are now state-only (status, usage, model, workspace, checkpoint); transcripts are fetched with thesession.messagescommand. Checkpoint-restore replies, which carry messages in their own field, are unaffected
Full Changelog: sdk/sdk/v0.0.80...sdk/sdk/v0.0.81
sdkperformancememoryeventssessions
Source: original entry ↗