pub const CONVERSATION_CAP_BYTES: usize = _ /* 67_108_864usize */;Expand description
How many bytes one copy of a conversation keeps, as frames weigh on the wire.
Sized from the seats that made #1637, and it binds only them. Across
the seven largest transcripts on the author’s machine (2026-10-17) every
window outside the two giant seats weighs 8.7-23.4 MiB and serves a
twenty-turn page of 0.8-5.2 MiB, while the giants’ windows weigh 319 and
467 MiB and their pages 95 and 105 MiB - about 2x under the client’s
256 MiB frame cap rather than orders under it. 64 MiB leaves every ordinary
seat untouched and comes down on exactly the giants, where the count alone
could not: what those seats serve on open becomes the window whole rather
than the newest twenty turns, and the rest of the history is reached the
way any window’s is - a more below the floor, answered from the
transcript.
Every figure above weighs the frames a read serves, the shape a page
carries. A served frame runs within a percent of the transcript row it
came from (measured over the newest four thousand), while roughly half of a
giant transcript’s LINES are rows no reader is served: control bookkeeping
(worktree-state, tag, last-prompt, mode, queue-operation and the
like - about 32,000 of 114,000 on the seat measured) and attachment rows
that are not queued commands (hook_success, total_tokens_reminder and
the like). A measurement taken from the file’s newest lines therefore finds
about half the frames and about half the bytes, which is the disagreement a
re-measurement from disk runs into.