* feat(transcript): make tool events readable — diffs, content, terminal output
The expanded transcript row printed a tool call's input as raw JSON, so an edit
showed `old_string`/`new_string` as escaped one-line literals — the one event
type where seeing *what changed* matters most. Tool results kept their JSON
string encoding, so every shell result read as a quoted blob with literal `\n`,
in the collapsed summary and in Copy all as well as in the body.
What each kind of event now renders as:
- A replacement reads as a diff. Unchanged runs fold to `⋯` with three lines of
context either side, so a one-line change inside a large `old_string` is not
buried in text that never moved.
- A whole-file write reads as plain content with a line count. There is no
before side to compare against, so a `+` on all of it carries no information.
- A result is unwrapped once, everywhere it appears.
File mutations are identified by the *shape* of the input (`file_path` plus
`old_string`/`new_string`, or `content`), never by tool name: the presenter's
contract is to keep provider-native names verbatim, and those differ per
provider. The write mode keys on `content` rather than on "the before side is
empty", because an edit with an empty old_string is an insertion into a file
that already exists and still reads as a diff.
Highlighting reuses the rich-content engine (`lowlight` and the `.hljs-*` class
contract), so a file looks the same in a transcript as it does in a comment,
with no new dependency. Each side is highlighted as ONE block and then split at
newlines, re-opening the enclosing spans per line — highlighting line by line
would break every multi-line string, comment and template literal. Grammar
comes from the file extension; an unknown extension stays plain rather than
guessing. The hljs palette was scoped to `.rich-text-editor`; it now also
covers `.transcript-code`, with no colour definition duplicated.
Diffing is a small LCS over lines, degrading to a plain replacement block past
250k cells. Line numbers are deliberately absent: the transcript stores only
the tool input, so a snippet's position inside its file is not knowable here,
and relative numbers would read as file lines and mislead.
* fix(transcript): keep the show-all label off the line it covers
The fade overlay does not fully clear the clipped line, so the transparent
"Show all" label rendered on top of whatever text sat behind it — the two
interleaved character by character and neither was readable. Giving the button
an opaque surface separates them.
Pre-existing: any tool output long enough to clip hit it. It became routine
once whole-file writes started rendering their content.
Combines the transcript work (previously split across #5860 virtual
scroll and #5871 reading hierarchy) into one branch on current main,
folding in the runtime-alias display from #5881.
- Virtualize the event list (react-virtuoso) so a multi-thousand-event
run mounts a bounded number of DOM rows (#5733), with firstItemIndex
anchoring for newest-first live prepends.
- Reading hierarchy via a pure trace-event-presenter: agent text and
errors render expanded in place through RichContent (compact,
log-scale markdown); thinking/tool rows fold to one line; tool detail
expands into a quiet surface with "show all".
- Persisted 3-way expand density (smart/expanded/collapsed) with per-row
overrides; legacy defaultExpanded boolean migrated. Filters always
persist (dropped the preserve-filters toggle).
- Two-tier header: identity row (status, agent, trigger source,
triggered-by) + list toolbar (created/duration/events facts left,
shared Button controls right); runtime/provider/workdir/timestamps
move to an ⓘ popover, runtime shown via runtimeDisplayName (#5881).
- Copy-all exports full event bodies (redacted) with RFC 3339 timestamps
(#5873), not the truncated summary.
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
