Repository navigation
Fade a new reply in word by word, in the Read view and the lead chat - #217
Merged
Merged
Conversation
…ad view and the lead chat Replies reach the log whole, so this paces their words out the way a streamed answer comes in: in reading order, about 40 words a second, capped at 1.4s for a long reply. Words sit in their final places from the start, so nothing reflows. React's own text nodes keep their identity and get their text back when the fade ends. Code blocks, pictures and buttons come in as one piece. Off with reduced motion. The mock lead now sometimes answers with a card, so a card landing in the chat can be seen. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
yobazy
marked this pull request as ready for review
November 12, 2026 20:49
Owner
Author
|
Fail: the code looks right and CI passes, but the PR's own description says it isn't ready to merge, and nothing on the PR says otherwise.
VERDICT: FAIL |
# Conflicts: # src/components/ProjectChat.tsx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A reply that lands while you're watching now comes in the way Claude and ChatGPT show one: word by word, each word fading in, in reading order.
How it works. The log hands over a reply whole (we poll it every 2.5s), so there's no token stream to show.
src/nebula/reveal.tspaces the words out the way chat apps smooth a stream: about 40 words a second, faster for a long reply so the last word starts within 1.4s. Each word fades in over 360ms, which gives the soft trailing edge.The mock lead now sometimes answers with a card, so a card landing in the chat can be seen.
Lead chat, plain reply (frames at 0 / 250 / 500 / 800ms / done):
Lead chat, card reply:
Checked:
npm run build && npm test(621 pass, newtests/reveal.test.mjs). Watched in the browser mock with Playwright: plain and card replies fade in, and afterwards the reply's DOM is as React left it (no leftover spans). Rust is untouched.Not checked: the Read view live. It uses the same hook on
.rd-reply.is-new, but the mock never adds a reply to a thread. Draft until it's been watched on a real thread.🤖 Generated with Claude Code