Session view tails like tail -f; UI polish; session-replay design#6
Merged
Conversation
The conversation pane reset scrollTop to 0 on every render: a refresh of a long live session landed at the top, and every live pair yanked the scroll out from under the reader. Proper tail semantics now: - open/refresh in live mode lands on the newest turn (snapshots still open at the top — reviewing a finished session is reading, not tailing) - re-renders stick to the bottom only while you're already there - reading history is never interrupted: scroll position is preserved and new activity surfaces as a "↓ new activity" pill instead - folds you toggle survive re-renders (positional restore — turn mutations are tail-only), and the thread sidebar keeps its scroll Polish pass, per the design language now written down in docs/design/ui.md: quiet thin scrollbars, live/offline/snapshot status dot with a heartbeat pulse, accent ::selection and :focus-visible, "/" focuses the filter (Esc blurs), keyboard hints in the empty state, prefers-reduced-motion respected. Session replay is designed but deliberately not built: docs/design/session-replay.md (jobs, wire-data reality, UX model, architecture, P1–P4 phasing) + roadmap entries in README/CHANGELOG. The core call: replay is viewer-side — every existing trace is already a timeline, so P1/P2 need zero capture changes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
1. Live-tail session view (the bug behind "refresh loses my place")
renderConvoPaneended withconvoEl.scrollTop = 0— a refresh of#/session/<key>landed at the top of a long conversation, and every live pair re-render yanked the scroll to top mid-read. Now, propertail -fsemantics:<details>folds you toggled survive re-renders (positional restore — turn mutations are tail-only), and the threads sidebar keeps its scroll.2. Polish pass
Rules written down in
docs/design/ui.md("well-kept terminal": information first, one accent, keyboard first-class, motion budget ~zero). Applied here:::selection+:focus-visiblelive/offline/snapshot)/focuses the filter,Escblurs it; keyboard hints in the empty stateprefers-reduced-motiondisables the pulse and smooth scrolling3. Session replay — designed, deliberately not built
docs/design/session-replay.md: jobs, what the wire already gives us (every trace is already a timeline — P1/P2 need zero capture changes; chunk timing is honestly absent until an opt-in P3), UX model (cursor over the session view, scrubber-as-minimap, idle compression, pair-id deep links), architecture (visibleAt(pairs, cursor)+ existingbuildSession), P1–P4 phasing, non-goals (no re-execution). Roadmap entries added to README + CHANGELOG.Tests
147/147 (
bun test), page-script parse + render smoke, compiled-binary smoke (served page carries the tail machinery). Not verified: real-browser scroll behavior — the logic is four branches over standard scroll metrics, but eyes on it after merge are welcome.🤖 Generated with Claude Code