Skip to main content

Module summary

Module summary 

Source
Expand description

The extractive line text: what the view says about messages it does not carry whole.

Everything here is mechanical — heads and counts read off the messages themselves. No model call belongs to the transcript in v1 (spec §7.4): the lines cost no latency and cannot be wrong about what happened, only short. A later compactor replaces exactly the text generators below; the addresses stay.

Constants§

HEAD_BYTES
Byte cap on one quoted head inside a line.
RANGE_HEAD_BYTES
Byte cap on one structural line covering a range.

Functions§

head
text on one line, at most cap bytes, cut on a char boundary with an ellipsis when longer.
message_bytes
The bytes a message costs on the wire: text, tool-call arguments, and tool-result content, summed. This is the unit the view’s budget spends.
one_line
Newlines and tab runs become single spaces: a line is one line.
render_message
The whole render of one message, as zoom(id, 1) returns it: user and assistant text verbatim, tool calls and results spelled out. Uncapped — the zoom pages.