Repository navigation
feat(threads): catch a founder up from the last message they saw (release line) - #127
Merged
Merged
Conversation
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> Ported-to: release/native-0.1.10 (CLO-941) Task: CLO-941 port CLO-928 Agent: magpie-port (cherry picked from commit ae7722c)
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) Ported-to: release/native-0.1.10 (CLO-941) Model: claude-opus-5-5 Task: CLO-941 port CLO-928 Agent: magpie-port Lane: magpie Harness: t3/claude-code Model-family: Claude Model-generation: 5.5 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 0f29ca0)
…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) Ported-to: release/native-0.1.10 (CLO-941) Model: claude-opus-5-5 Task: CLO-941 port CLO-928 Agent: magpie-port Lane: magpie Harness: t3/claude-code Model-family: Claude Model-generation: 5.5 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 1f0fb08)
4 tasks done
…arker Adapters on the release line match /compact and /goal exactly, so a catch-up block appended after a slash command turned it into a normal prompt. A slash command now reaches the provider unchanged. A reply that is still streaming is not counted as unseen. Review finding from the CLO-941 port review of the seen-marker catch-up (CLO-928). Model: claude-opus-5-5 Task: CLO-941 port the seen-marker catch-up (CLO-928) to the release line Agent: magpie Lane: magpie Harness: t3/claude-code Model-family: Claude Model-generation: 5.5 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
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.
The seen-marker catch-up (Linear CLO-928) was opened against the stale
mainin #122, where it gets no CI and does not ship. This PR ports its three commits ontorelease/native-0.1.10(Linear CLO-941).The shared, client-runtime, web and mobile seen-marker modules and their tests apply as they are. The rest was rewritten for the release line:
ThreadSeenMarkerrides onmessage.dispatchinorchestrationV2.ts, and its summary is stored on the user message.Orchestrator.dispatchMessagecounts assistant messages after the seen one withProjectionStore.countAssistantMessagesAfter.ProviderTurnStartServiceandProviderTurnControlServiceadd the catch-up text to new turns and steered messages.useComposerSendanduseThreadLifecycle.threadOutboxDelivery.Two call sites from #122 do not exist on the release line: the plan-implementation send and mobile new-thread creation. The
verify-t3codedocs were skipped because that directory is not on this line.Tests: the seen-marker suites pass (shared 3, client-runtime 5, web 4, mobile 4), and so do
Orchestrator.seen-marker.test.tsandProviderTurnControlService.test.ts(5). Typecheck passes for contracts, shared, client-runtime, web, mobile andt3.Review round (claude-fable-5-2), fixed: adapters match
/compactand/goalexactly, so a slash command now reaches the provider without the marker block, and a reply that is still streaming is not counted as unseen. Both new test rows fail before the fix and pass after; typecheck passes for shared andt3.Deploy: fleet
Model: claude-opus-5-5
Task: CLO-941 port the seen-marker catch-up (CLO-928) to the release line
🤖 Generated with Claude Code