Transcript is jumpy while an agent streams: passed rows change, live text vanishes, Write rows have no path #210
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Seen on run 79 (Aurora Links, fastllm, opencode 2), 2026-10-18. The step transcript is hard to follow while an agent works:
Write. SevenWriterows in a row, with no file name, so the operator cannot tell what was written until a row is opened, if then.Likely causes (from reading the code, not yet confirmed)
osf/agent/v2.py, braid#177). Until then the console draws the deltas as a live piece. When a longreasoningpart settles it collapses into a one-line "Thought" disclosure (Reasoning.tsx), so a screenful of text disappears in one frame and the list below shifts up.useSessionDeltaskeeps one{partId, text}per session, andTranscript.tsx(~lines 200–250) draws one live piece per agent. When the next part starts streaming, the previous part's text leaves the live tail before its settled row has arrived through the log. Text vanishes, then reappears higher up as a settled row, which reads as rows above changing.virtuaVList). A tool row that gains its input or result, or a reasoning row that collapses, changes height, and virtua corrects the scroll offset, producing jumps away from the tail too.format.tslabels the write toolWritewith no path. Either opencode 2 sends the tool input only when the call settles, or the label never includesinput.filePath. Check which.To look into
tools/record_opencode2.py), and replay it in the browser lane to reproduce the jumps.part_id(message, kind, ordinal)) from the live stream and from a backfill ever disagree on opencode 2. That would redraw old rows as new ones.Overall - I would like to update our opencode coding agent pane in Braid to align as closely as possible to how opencode v2 CLI client looks and feels. I was just using the opencode v2 CLI, and I noticed that the edit tasks show the code diff, which would be nice to have in braid. I'm guessing there are a lot of visual features of opencode v2 that should be implemented for braid. I think this may require a live session with opencode itself, taking screenshots and using vision to try and reproduce it accurately in a web browser. Also though, it is worth reading the new v2 documentation closely, perhaps there is a better way entirely to integrate a fully functioning opencode client in the browser, different from how we did it with opencode v1.