Skip to content

feat(threads): catch a founder up from the last message they saw - #122

Closed
nullStack65 wants to merge 3 commits into
mainfrom
feat/clo-928-last-seen-marker
Closed

nullStack65 wants to merge 3 commits into
mainfrom
feat/clo-928-last-seen-marker

Conversation

@nullStack65

Copy link
Copy Markdown
Owner

What Changed

A focused, visible window remembers the newest message that stays on screen for about 2 seconds. The next send on that thread carries the message id and the time. The server counts assistant messages after that id and, when there is something unseen, puts one catch-up line at the start of the provider prompt. Web, desktop, and mobile share the same memory. Compact on the open thread carries it too.

Scrolling, dwelling, hiding, or blurring only updates that memory. It does not dispatch a command or open a socket. A send with no marker, which is every MCP or bot send, is unchanged. A thread read never records a view.

Why

Founders do not read every bot message. The reply should catch them up on only the part they have not seen, and looking at the thread must never start a new turn. The count is computed on the server so a client cannot invent it, and the marker is omitted when the id is missing or nothing is unseen.

The browser drive in verify-t3code cannot see this: the marker is not rendered. The proof is the focused unit tests for dwell, focus, quiet scroll, the decider summary, and the provider line.

UI Changes

No visible UI change.

Checklist

  • This PR is small and focused
  • I explained what changed and why
  • I included before/after screenshots for any UI changes
  • I included a video for animation/interaction changes

Provenance

Model: grok-4.7
Task: feature

Work in progress for the founder catch-up marker. Adds an optional
seenMarker on thread.turn.start, carries it onto the turn-start event,
and prepends a catch-up line to the provider text. The web timeline
tracks a 2 s dwell on the newest visible message in a focused window.
Untested; mobile wiring and tests still to come.

Model: claude-opus-5-5
Task: feat
Agent: claude-code
Lane: magpie
Harness: t3/claude-code
Model-family: Claude
Model-generation: 5.5
Skills-SHA: 0540352af0d6
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A focused window remembers the newest message that stayed on screen for two seconds. The next send carries that id, and the server counts the assistant messages after it so the provider prompt opens with a catch-up. Scrolling never starts a turn, and a send with no marker, including an MCP send, stays unchanged.

Model: grok-4.7
Task: feature
Agent: grok
Lane: seen-marker
Harness: t3/codex
Model-family: Grok
Model-generation: 4.7
Skills-SHA: unknown (source unavailable)
@coderabbitai

coderabbitai Bot commented Nov 20, 2026 •

Copy link
Copy Markdown

Important

  • Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

…en marker

A catch-up ahead of the prompt turned /compact and /review into prose, so a command stays first and the catch-up follows. Blur, focus, and hiding the page sample immediately, and a reply that is still streaming is not marked seen.

Model: grok-4.7
Task: feature
Agent: grok
Lane: seen-marker
Harness: t3/codex
Model-family: Grok
Model-generation: 4.7
Skills-SHA: unknown (source unavailable)
@nullStack65

Copy link
Copy Markdown
Owner Author

Moved: main gets no CI and does not ship. This change is ported onto release/native-0.1.10, the line the fleet builds, in #127 (Linear CLO-941). The branch is kept.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants