[teamleaderleo]

A streaming reply in the agent chat should read like ChatGPT's or Claude desktop's. That means steady words paced to the token rate, and no block that draws one way and then flips as its Markdown forms. It also means room under the newest line instead of the line sitting on the composer's edge, and 60 fps on long turns.

Base already paces the reveal to the arrival rate (streamReveal.ts), parses incrementally and holds back half-written fences, tables and links (safeTail.ts). This PR closes the rest:

• Whole words. The reply grows a word at a time, and each word fades in. It never shows a letter or half a word at a time. wordEdge comes from the stalled Agent chat: streaming replies grow by whole words, no block cursor #22339 (credit to its author). CJK text grows a character at a time. A word over 48 characters, such as a URL, shows as it arrives. The Debug toggle agentPane.debug.streamWords (on) switches back to characters.
• The end of a reply and pauses. Until the whole reply shows, it keeps its streaming parse, so a code span or bold run that the last word closes never flashes its raw Markdown for a frame. When text stops arriving for 600 ms (StreamReveal.stallMs, typically before a tool call), the held last word shows instead of waiting for the next delta.
• No frames skipped in WebKit. The reveal loop used to skip any frame that came less than COMMIT_MS - 1 after the last commit. WebKit rounds frame times to whole milliseconds and they jitter around 17 ms, so on a 60 Hz display one frame in three to five stalled. The loop now learns the display's frame time and skips a frame only on displays faster than 60 Hz. A 120 Hz display still commits 60 times a second. There is now one loop per row, and it reads the latest text itself instead of restarting on every snapshot.
• No Markdown flips. These no longer draw as text first and then turn into their block: a bare list marker (- , 2.), heading hashes before their space, a rule line, a lone * or _, and an open italic run. A fence closer still being typed is held back along with the newline before it, so a code card never shrinks by a line as it closes.
• The closing fence moves nothing in WebKit. Pierre keeps a strip for its horizontal scrollbar under the code rows. That strip is 6 px in WebKit, so the highlighted card came out 6 px taller than the plain card it replaces, and everything under it jumped. The strip now hangs into the card's bottom padding.
• Runway. The transcript keeps 24 px under its last row, on top of the bottom stack's room, so the newest line sits about 32 px above the composer. The runway is always there, so a reply starting or ending moves nothing. It stays well under Agent chat: a reopened chat shows its whole history, with no band above the composer #23064's 96 px "no blank band" limit. With cmux NEXT: the agent turn looks like Codex: finished runs fold, one shimmering live line at the bottom, short labels, check and time on hover #23081 (chat-turn-codex-style's live status line), whichever PR lands second subtracts that line's measured height from the runway, so the two don't stack.
• Less main-thread work per frame. The page's reload copy of the transcript was serialized into sessionStorage on every snapshot, which is every frame while streaming. It is now written at most every 250 ms, and immediately when the page hides or unloads.
• Auto-follow is unchanged: the transcript follows only when you're within 4 px of the bottom (FOLLOW_BOTTOM_DEADBAND_PX). The frame test checks that the pin holds while streaming.

Frame budget test

test/streaming-text-frames.test.ts streams a 5,000-character reply (streamingTextFixture.ts: paragraphs, headings, lists, a code block, a table). The reply goes through the real transcript, with the bottom stack drawn over it, in Chromium and WebKit, at Claude's and Codex's chunk cadences. It samples every display frame and fails on:

• any block above the one being written that moves or changes height
• any element that changes tag as it forms
• the pinned bottom drifting more than 4 px
• a frame's main-thread work over 16.7 ms at p95, or any frame over 50 ms, in either engine, on two runs in a row. Work is the script of every task between two frames plus the layout left for the frame. test/browser/streaming-text.clock.ts times React's scheduler tasks (renders, commits, effects and the layout they force), frame callbacks, resize observers, timers and queued microtasks. Work is wall-clock time, so a starved host can break it once. That is why it gets a second run, while shifts, flips and the pin fail on the first.

Frame intervals are reported but not held. On CI they measure the host as much as the page: shard 3 runs other dev-server browser files beside this one, and at 91e0ad3 one frame in twelve came 33 ms apart. The long frames are Pierre highlighting the closed fence on the main thread (about 120 ms in Chromium, 1.1 s in WebKit). That only happens on the test's dev page, which has no highlight worker; the app's page highlights in one (highlightPool.ts). That time comes off a frame's work, and the report lists those frames separately. Outside them, on cmux16 the intervals were p95 16.7 ms and max 16.8 ms in Chromium, and p95 19 ms and max 26 ms in WebKit.

Results on cmux16:

	before	after
Elements that changed tag mid-stream	2	0
Gap from newest line to composer, p50	11 px	35 px
Code card height change on closing fence (WebKit)	+6 px	0
Reveal frames with no step (WebKit, Claude / Codex cadence)	72 / 121	0 / 0
Reveal frames with no step (Chromium)	0 / 1	0 / 1
Frame work p95 / max, Chromium (both cadences, 3 runs)		9.3-10.9 / 15-41 ms
Frame work p95 / max, WebKit (both cadences, 3 runs; one 207 ms layout passed on its second run)		6-7 / 15-26 ms

test/code-handoff-height.test.ts checks that the plain and highlighted cards are the same height in both engines. test/streaming-markdown-forming.test.ts checks every prefix of the fixture for flips. test/snapshot-save-throttle.test.ts covers the 250 ms reload copy.

Gallery

The gallery entry agent-pane.streaming-text streams the frame test's reply at both cadences. The Linux gallery run takes its stills. These recordings come from cmux16 at fca0cb22, which has the same tree as 91e0ad3.

Claude cadence, Chromium:

Full quality: streaming-text-claude-chromium.mp4

Codex cadence, WebKit:

Full quality: streaming-text-codex-webkit.mp4

No capture: the only native change is a Debug Settings toggle (agentPane.debug.streamWords, on by default). Everything visible happens in the webview transcript, which the gallery recordings above show.

Changelog

• Changed: Agent chat replies stream in steadily a word at a time, blocks no longer change shape as their Markdown forms, and there is room between the newest line and the composer.

Observed / Not run

• Red/green on cmux16: cd webviews && bun test src/agent-session/acpmux/conversation/RevealedMarkdown.test.tsx. At the test commit 24956479 the three new tests fail (the code span shows "Run `bun", the paused reply stays at "Let me check the", wordEdge returns 53 for 60) and the other five pass. At fca0cb22 all 8 pass.
• CI at c98ae83: test/streaming-text-frames.test.ts, test/code-handoff-height.test.ts and test/agent-pane-recap-card.test.ts pass. The CmuxNextAgentPane module, where the tunable lives, compiled in the fast tier. Every remaining red is also red on base:
  • RemoteChildSessionsTests doesn't compile (fixed on base by cmux-next tests: RemoteChildSessionsTests' fake client states isReadOnly (base red: tests don't compile) #23362).
  • The "Companion workflows" check is missing base-autofix-repair.sh.
  • agent-pane-scrollbar-full-height's two "grows and shrinks" tests end with the composer card 20 px off its starting height. They failed 3 of 3 times at base bc70489a on cmux16.
• At 11a3ffb, agent-pane-recap-card's fit test failed because of this PR: the pane was sized for a chat with no runway. c98ae83 fixes it.
• Gate on cmux16 at 11a3ffb (review fixes: highlight time counted once, scroll listeners timed): bun run check passes, prepush-gate passes, test/streaming-text-frames.test.ts passes 4 of 4 at load 28-37 with no retry. Work p95 / max was 10 / 15.2 ms (Chromium, Claude), 9.6 / 22.9 ms (Chromium, Codex), 7 / 25 ms (WebKit, Claude) and 6 / 30 ms (WebKit, Codex). Chromium's only long task (119-123 ms) is Pierre tokenizing the closed fence.
• Gate on cmux16 at e2875bd (base merged at 8214250; its one conflict was rowsHeight in App.tsx, where Agent chat: growing the composer never moves the transcript or its scrollbar #23097's held room replaced dockSpace and the runway stays on top): bun run check passes, prepush-gate passes, the 54 unit tests pass, and test/agent-pane-scrollbar-full-height.test.ts (Agent chat: growing the composer never moves the transcript or its scrollbar #23097's tests) and test/code-handoff-height.test.ts pass. test/streaming-text-frames.test.ts passed 4 of 4 at load 20-33: 0 shifts, 0 flips, pin 1 px. One WebKit Codex run went over the work budget once, with a 207 ms forced layout, and passed on its second run. An earlier run at load 25-36 failed two engines on long tasks of 540-650 ms with a grammar load taking 850 ms (normally 20). That run predates the retry.
• Gate on cmux16 at df8c327: typecheck and vp lint pass, prepush-gate passes, the 54 unit tests pass, and test/code-handoff-height.test.ts passes in both engines. test/streaming-text-frames.test.ts passes 4 of 4 at load 8-20: 0 shifts, 0 flips, work p95 7.1 ms in Chromium and 4 ms in WebKit. bun run check fails only check:switch-fetches, on composer/keptAttachments.ts (from cmux-next composer: a chat's unsent pictures and files come back when it is reopened or restored #23139, already on the base 9912487; this PR doesn't touch it).
• At 91e0ad3, CI's react-apps-check (3) failed the frame test in Chromium: a 300 ms frame and a 33.3 ms p95 interval. Everything else held: 0 shifts, 0 flips, pin 1 px. df8c327 changed the timing budget to per-frame work. Review of df8c327 found that its work figure missed commit-time layout, layout effects and resize observers, e2875bd times every task instead, and 11a3ffb fixes the second review's findings. CI never ran df8c327, because the PR conflicted with base.
• Earlier gate on cmux16 at fca0cb22: typecheck, vp lint, bun run check, prepush-gate, the 54 unit tests this PR touches, test/code-handoff-height.test.ts (both engines) pass. test/streaming-text-frames.test.ts on cmux16 at load 36-98 had 0 layout shifts and 0 tag flips in Chromium, but missed the timing budgets (one 10 s frame, after which the view rested 326 px from its end for 2 frames), and WebKit timed out at 180 s. That is host load; PR CI's browser lane runs this test. scripts/web-lint.sh could not start there (node is not on cmux16's PATH); its vp check passed in the check step and CI runs it.
• The Swift tunable test was added but not run locally (no Mac builds here). CI compiles it.
• Frame timings on cmux16 are noisy (load ~130). Chromium max-frame spikes of 100 to 300 ms appeared at both base and head while the host was loaded. The Chromium budgets are meant for the CI runner.

Follow-up

• incrementalMarkdown.ts's fenceOpen is now read only by test/incremental-markdown.test.ts.
• The gallery entry's draw frame loop is not cancelled on unmount (gallery only).
• model.ts estimates a wide code block's scrollbar at 15 px (SCROLLBAR_HEIGHT), which is too high now that the strip hangs into the padding. The virtualizer corrects it on measure, but the estimate should match.

Leo-ask: ask-76c0ef9f1c (this PR adds the 24 px runway under a streaming reply. The caret was already removed by #22730, words already fade in (RevealedMarkdown FADE_MS), and growth at the latest row already glides into place)

Agent session: cosmic-gray

🤖 Generated with Claude Code

[github-actions]

cmux status _{(one comment, edited in place; each line is updated by the job that owns it)}

Review c98ae83: HQ feed card · gallery before/after runs · checks

App of this head (app.zip, kept 1 day)

gh workflow run reload-build.yml -R manaflow-ai/cmux --ref feat-cmux-next -f tag=pr23094 -f ref=feat/next-streaming-text -f platform=macos -f backend_mode=local

Gallery before/after for c98ae83: 16 states rendered, 14 images differ, 1409 more touched states not rendered. Images are in the run's artifact, not on this public PR.

gh run download 39594033591 -R manaflow-ai/cmux -n gallery-advisory-23094-c98ae8366ca2d9ad414b1843a6567d6bb18a85e4 (then read gallery-review.json)

States

State	Theme	Status	Diff	Picked by
agent-pane.chat-width/standard	Apple System Colors Light	changed	7.43%	own App.tsx
agent-pane.chat-width/standard	Apple System Colors	changed	6.24%	own App.tsx
agent-pane.chat-width/wide	Apple System Colors Light	changed	7.43%	own App.tsx
agent-pane.chat-width/wide	Apple System Colors	changed	6.24%	own App.tsx
agent-pane.chat-width/wide-blocks	Apple System Colors Light	changed	7.43%	own App.tsx
agent-pane.chat-width/wide-blocks	Apple System Colors	changed	6.24%	own App.tsx
agent-pane.composer-floats/scrolled-to-end	Apple System Colors Light	changed	13.1%	own App.tsx
agent-pane.composer-floats/scrolled-to-end	Apple System Colors	changed	12.9%	own App.tsx
agent-pane.composer-floats/composer-grown	Apple System Colors	changed	10.7%	own App.tsx
agent-pane.composer-floats/composer-grown	Apple System Colors Light	changed	10.6%	own App.tsx
agent-pane.docked-chat/new-chat	Apple System Colors Light	unchanged	0%	own App.tsx
agent-pane.docked-chat/new-chat	Apple System Colors	unchanged	0%	own App.tsx
agent-pane.docked-chat/after-turn	Apple System Colors Light	unchanged	0%	own App.tsx
agent-pane.docked-chat/after-turn	Apple System Colors	unchanged	0%	own App.tsx
agent-pane.docked-chat/working	Apple System Colors Light	unchanged	0%	own App.tsx
agent-pane.docked-chat/working	Apple System Colors	unchanged	0%	own App.tsx
agent-pane.docked-chat/typing-in-dock	Apple System Colors Light	unchanged	0%	own App.tsx
agent-pane.docked-chat/typing-in-dock	Apple System Colors	unchanged	0%	own App.tsx
agent-pane.docked-chat/long-title	Apple System Colors Light	unchanged	0%	own App.tsx
agent-pane.docked-chat/long-title	Apple System Colors	unchanged	0%	own App.tsx
agent-pane.orchestration-lab/local-queue	Apple System Colors Light	unchanged	0%	own App.tsx
agent-pane.orchestration-lab/local-queue	Apple System Colors	unchanged	0%	own App.tsx
agent-pane.orchestration-lab/huge-blue	Apple System Colors Light	unchanged	0%	own App.tsx
agent-pane.orchestration-lab/huge-blue	Apple System Colors	unchanged	0%	own App.tsx
agent-pane.orchestration-lab/cloud-fair-share	Apple System Colors Light	unchanged	0%	own App.tsx
agent-pane.orchestration-lab/cloud-fair-share	Apple System Colors	unchanged	0%	own App.tsx
agent-pane.streaming-follow-motion/stream	Apple System Colors Light	unchanged	0%	own App.tsx
agent-pane.streaming-follow-motion/stream	Apple System Colors	unchanged	0%	own App.tsx
agent-pane.streaming-text/claude	Apple System Colors Light	new	0%	own App.tsx
agent-pane.streaming-text/claude	Apple System Colors	new	0%	own App.tsx
agent-pane.streaming-text/codex	Apple System Colors Light	new	0%	own App.tsx
agent-pane.streaming-text/codex	Apple System Colors	new	0%	own App.tsx

_{Pick other states with a Gallery: entry.id, entry.id/variant line in the PR body.}

Unclear: web / react-apps-check failed: no known signature; failed step: Check webview test shards.

CI failed on c98ae8366c (run 39594033497 attempt 1): 1 code, 1 unknown.
macOS jobs did not run: compile and app tests were skipped: Fast static checks skipped.

Job	Verdict	Why
web / react-apps-check (3)	code	a web test failed
web / react-apps-check	unknown	no known signature; failed step: Check webview test shards

Failures:

• seen on other PRs agent-pane-scrollbar-full-height.test.ts a composer that grows and shrinks leaves the rows a reader reads where they were on every frame: failed (job)
• seen on other PRs agent-pane-scrollbar-full-height.test.ts a composer that grows and shrinks keeps a followed view at its end on every frame: failed (job)

Matched log lines

web / react-apps-check (3): (fail) a composer that grows and shrinks leaves the rows a reader reads where they were on every frame [4314.22ms]

Not re-run automatically: web / react-apps-check (3), web / react-apps-check are not machine failures.

Written by scripts/ci/classify_failures.py (ci-failure-attribution.yml); signatures are its SIGNATURES table. A machine verdict is the runner's fault, not this PR's; yours means the failing file is one this PR changes, also red on main that main's latest full suite fails the same way, seen on other PRs that it failed on another pull request's run lately.

red: cmux-next checks (god files, concurrency, crash safety, l10n); base red: the same failure on the base ef40118; does not block
red: web / Web status; base red: the same failure on the base ef40118; does not block
red: web / react-apps-check; base red: the same failure on the base ef40118; does not block
red: web / react-apps-check (3); NEW: Expected: <= 1 Received: 20 at <anonymous> (/home/runner/_work/cmux/cmux/webviews/test/agent-pane-scrollbar-full-height.test.ts:441:53) (+1 more) is not red on the base ef40118; do not merge until green; see lane-rules

CI fast guards failed on c98ae8366c (https://github.com/manaflow-ai/cmux/actions/runs/39594033497). It does not block the merge; a red guard merged into main breaks it for every open PR.
The log named no failed step; see the run.

Agents: python3 scripts/ci/guard_attribution.py fix applies the mechanical fixes locally.

Tour of c98ae8366c (run): no media. The tour job failed before the tour ran (build or setup); the run log has the output.

[teamleaderleo]

Owned by projects-a4 on cosmic-gray · session

[teamleaderleo]

Owned by projects-a4 on cosmic-gray · session

[blacksmith-sh]

Found 7 test failures on Blacksmith runners:

Failures

Test	View Logs
/tmp/tmpme6f8tc2/summary-fail.json (live):/summary-fail.json (live):	View Logs
/tmp/tmppn5maueq/summary-missing.json (live):/summary-missing.json (live):	View Logs
test/agent-pane-scrollbar-full-height.test.ts/agent-pane-scrollbar-full-height.test	View Logs
test/agent-pane-scrollbar-full-height.test.ts/agent-pane-scrollbar-full-height.test	View Logs
test_a_pull_request_that_changes_the_shortcut_inputs_still_rewrites_them (main.Sett ingsOnlyArtifactLeavesTheActionFollowers.test_a_pull_request_that_changes_the_shortcut_ inputs_still_rewrites_them) (job='autofix')/ test_a_pull_request_that_changes_the_shortcut_inputs_still_rewrites_them (main.Sett ingsOnlyArtifactLeavesTheActionFollowers.test_a_pull_request_that_changes_the_shortcut_ inputs_still_rewrites_them) (job='autofix')	View Logs
test_regenerated_action_exports_bring_the_followers (main.SettingsOnlyArtifactLeave sTheActionFollowers.test_regenerated_action_exports_bring_the_followers) (job='autofix' )/ test_regenerated_action_exports_bring_the_followers (main.SettingsOnlyArtifactLeave sTheActionFollowers.test_regenerated_action_exports_bring_the_followers) (job='autofix' )	View Logs
test_settings_exports_alone (main.SettingsOnlyArtifactLeavesTheActionFollowers.test _settings_exports_alone) (job='autofix')/ test_settings_exports_alone (main.SettingsOnlyArtifactLeavesTheActionFollowers.test _settings_exports_alone) (job='autofix')	View Logs

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[teamleaderleo]

Bead cx-vgc4l created for this PR by the cmux coordinator.

[teamleaderleo]

PR capture check / pr-capture-check is red on 24 of 30 fresh feat-cmux-next PR heads in the last 2:00:00, so it is most likely a base red, not this PR's. The base-reds lane has it; a base merge picks up the fix once it lands.

[teamleaderleo]

codex-review: SHIP at 11a3ffb

• Reviewed the current diff, its focused tests, and the affected call paths; no correctness bug found.

[teamleaderleo]

Review (independent subagent): SHIP at c98ae83

Review rounds:

• Earlier rounds: round 2 passed fca0cb22. 91e0ad3 is the same series, which the range-diff confirms.
• df8c327: changes requested. The per-frame work figure counted React's render and the residual layout. It missed commit-time layout, layout effects and resize observers.
• e2875bd: changes requested. This commit merged base and times every main-thread task. The merge resolution of rowsHeight (Agent chat: growing the composer never moves the transcript or its scrollbar #23097's held room, with the runway on top) passed. Finding: WebKit's nested highlight time was subtracted twice, and the scroll listener wasn't timed.
• 11a3ffb: SHIP. It counts each highlight once, times event listeners, warns on a retry, and updates the comments.
• 2707e29 (second base merge, clean) and c98ae83: SHIP. c98ae83 sizes the recap card's fit test to leave the runway; the constant moved to model.ts.

CI at c98ae83:

• Passed, this PR's: streaming-text-frames, code-handoff-height and agent-pane-recap-card. The CmuxNextAgentPane module compiled in the fast tier.
• Red, also red on base:
  • RemoteChildSessionsTests.FakeClient doesn't conform to AgentSessionRemoteClient. This failed fast tier, generated files and swift test. It is fixed on base by cmux-next tests: RemoteChildSessionsTests' fake client states isReadOnly (base red: tests don't compile) #23362, and this PR touches no file in that target.
  • "Companion workflows" in cmux-next checks: scripts/cmux-next/base-autofix-repair.sh doesn't exist, and this PR touches no scripts or workflows.
  • agent-pane-scrollbar-full-height's two "grows and shrinks" tests: the composer card ends 20 px off its starting height. They failed 3 of 3 times at base bc70489a on cmux16. react-apps-check, Web status and the shard check are wrappers of this red.
• Still pending: Release and Debug compile are still queued.

[github-actions]

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.3961849180901 (00f97d8084)
• cmux NEXT nightly 1.0.0-nightly.3961976052101 (02d61172e1)
• cmux NEXT nightly 1.0.0-nightly.3962134573301 (c6459deaec)