feat(chat)!: remove per-message checkpoint marker; flatten chat-message rendering#471
Merged
Conversation
…ge rendering The chat library no longer ships a built-in time-travel UI on individual assistant messages. The bare gutter dot was undiscoverable, the rewind-vs-refresh distinction was invisible to most users, and the LangGraph-specific concept leaked into the UI for a feature only power users used. Refresh (in the actions bar) covers the universal 'redo this turn' intent that every chat UI exposes. Removals: - chat-checkpoint-marker primitive (component + spec + public-api export) - chat-message inputs: checkpointId, checkpointActive - chat-message outputs: replayRequested, forkRequested - chat-message gutter/layout/main wrapper DOM and CSS — template is now flat (bubble + citations + controls) - replayRequested/forkRequested outputs on chat, chat-sidebar, chat-popup compositions and their forwarding - demo-shell onTimelineReplay/onTimelineFork handlers + the bindings in embed-mode/popup-mode/sidebar-mode Kept: - AgentWithHistory contract + agent.history Signal — adapter authors can still expose checkpoint state - agent.replayFromCheckpoint / forkFromCheckpoint methods on the runtime contract — consumers can build their own time-travel UI - ChatTimelineSliderComponent standalone primitive — explicit opt-in surface for consumers who want a time-travel UI Side benefit: the chat-message layout flattens significantly. No more flex row with gutter (14px) + main; messages are simple block-level containers. Fixes the long-standing alignment glitch where the gutter dot floated ~16px above the first line of bubble text. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Summary
Removes the per-assistant-message checkpoint UI (gutter dot + rewind/fork pill) from the chat library. Refresh (in the existing message actions bar) covers the universal "redo this turn" intent every chat UI exposes; the bare gutter dot was undiscoverable, the rewind-vs-refresh distinction was invisible to most users, and the LangGraph-specific concept was leaking into the UI for a feature only power users used.
Removed
Kept (deliberately)
Side benefits
@ngaf/* 0.0.43. Breaking removal of outputs + inputs flagged with `!` in the commit subject.
Test plan
🤖 Generated with Claude Code