Brennan Benson 70617dd1a9 fix(native-chat): stop rendering a tool result whose call is outside the window ...

A tool result carries no call id, so it can only be attributed to a tool
call loaded alongside it. Both chat views read a windowed transcript tail
(mobile 40 messages, desktop 300), and the window regularly opens between
an assistant's `tool_use` record and the user-role record that answers it.
Claude also re-emits already-answered `tool_result` records at a `/compact`
boundary, long after their call scrolled out of the window.

`foldToolMessages` had no rule for those: with no assistant predecessor in
the output they were pushed through as standalone messages and rendered as
a bare, unowned block of raw tool output with no tool name — reading as a
message from nowhere mid-conversation. Sampling real Claude transcripts,
176 of 400 sessions (44%) produced one in a mobile-sized first page.

Drop a result no loaded call can own, before folding. It is not lost: it
comes back attached to its call as soon as the owning turn pages in.

2026-08-20 15:46:32 -07:00

..

cli

fix(terminal): refuse a cursor on a screen read, and correct the source docs (#15563)

2026-08-19 22:42:39 -07:00

main

fix(native-chat): stop rendering a tool result whose call is outside the window

2026-08-20 15:46:32 -07:00

preload

fix(remote): search Quick Open paths on the host (#15158)

2026-08-18 13:32:48 -07:00

relay

fix(pty): delete the reply-withholding scheduler (#15578)

2026-08-20 02:15:42 -07:00

renderer

fix(native-chat): stop rendering a tool result whose call is outside the window

2026-08-20 15:46:32 -07:00

shared

fix(native-chat): stop rendering a tool result whose call is outside the window

2026-08-20 15:46:32 -07:00

types

fix(codex): publish Windows system-default sessions (#12611)

2026-08-07 16:53:41 -07:00