Repository navigation
cmux NEXT transcript: no caret at the end of a streaming reply - #22730
Conversation
Red: bun test src/agent-session/acpmux/conversation/StreamingEdge.test.tsx fails with the .cv-caret span after the newest character. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The live-edge bar after streaming text (R104) and its wait pulse are gone, with the waiting/is-waiting plumbing and the reveal hook's settled state that only fed it. The newest characters still fade in. Green: bun test src/agent-session/acpmux/conversation/StreamingEdge.test.tsx Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
cmux status (one comment, edited in place; each line is updated by the job that owns it) Review App of this head (app.zip, kept 1 day)
Unclear: CI failed on
Failures:
Matched log linesNot re-run automatically: Written by red: web / Web status; NEW: green on the base 9290a83; do not merge until green; see lane-rules
Agents: Tour of |
|
Bead |
|
|
|
Found 6 test failures on Blacksmith runners: Failures
|
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?harness=claude&session=01a15c08-af57-7bb3-9f61-498ade344f20&host=cosmic-gray
|
Shipped in:
|
|
Shipped in:
|
Conflicts: RevealedMarkdown.tsx keeps base's away/flushSync backlog path and applies wordEdge to the reveal length before it; Markdown.tsx keeps the no-block-cursor comment. Base #22730 already removed the caret CSS. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Agent-Session: https://cmux.com/deeplink/agent?harness=claude&session=01a15bbf-a30f-7992-abba-3e3ca6f5adc1&host=cosmic-gray
Summary
A streaming agent reply no longer draws the soft bar after its newest character, and the bar no longer pulses while the reveal waits for more text. The reply simply ends at its last character; the newest characters still fade in as before.
The removal takes the plumbing that only fed the bar with it: the
.cv-caretspan and CSS, thewaitingprop and.cv-md.is-waitingclass, and thesettledstate inuseStreamReveal(which cost one extra render when a reveal caught up).static-status-loops.test.tsdrops the caret from its list of loops.git log -S cv-caret origin/feat-cmux-nexthas no removal; #20432 and #20434 (hide it once idle) were closed unmerged.Testing
From
webviews/:bun test src/agent-session/acpmux/conversation/StreamingEdge.test.tsx: red on the first commit (the.cv-caretspan afterworld), green on the fix.bun test src/agent-session/acpmux/conversation: 49 pass.bunx tsc --noEmit -p .: clean.Not run locally:
static-status-loops.test.ts(browser lane, runs in this PR'sweb / react-apps-check).verify-local.py --affected:localization(41087 parity errors) andpackage-groupsfail the same way on the base; this PR touches neither.Changelog
Removed: the blinking caret at the end of a streaming agent reply
🤖 Generated with Claude Code
Agent session: cosmic-gray
Need help on this PR? Tag
@codesmith-botwith what you need.Summary by cubic
A streaming agent reply no longer draws the blinking caret after its newest character, and the caret no longer pulses while the stream waits for more text. The reply simply ends at its last character; newest characters still fade in as before.
.cv-caretspan and its CSS, thewaitingprop and.cv-md.is-waitingclass, and thesettledstate inuseStreamReveal, which caused an extra render when the reveal caught up.Written for commit a7aba81. Summary will update on new commits.