fix(web): reading a thread clears Done; Woke is dismissible

[t3dotgg]

Problem

Since #5486, opening and reading a finished thread no longer clears the sidebar's "Done" badge. That PR removed the visit-on-open effect in ChatView (to stop mere visits from eating the Woke signal) but didn't replace it for read tracking, so lastVisitedAt only updated on woke-acknowledge, settle, or archive. Any thread whose last turn completed after your stored visit showed Done forever.

Solution

• Reading clears Done. ChatView stamps markThreadVisited with the open thread's latestTurn.completedAt (not updatedAt/now). This clears exactly the completion you're looking at while preserving fix(web): clear woke state on explicit thread actions #5486's woke semantics: a timer wake stamped later than the completion still shows its pill, and markThreadVisited never moves the timestamp backwards.
• Woke banner in the open thread. A woken thread now shows a dismissible info banner in the composer banner stack, so dismissal has a prominent home beyond the small sidebar pill (which stays clickable too). Dismissing uses the same acknowledgment as the pill; sending a message already clears it via the send path, as do settle and archive.
• Merged/closed PR suppresses Woke. If the thread's PR merged or closed while it was snoozed, the work is finished — no wake-up call needed. Applied consistently in the sidebar row and the banner.

Also moved the sidebar row's git-status/PR lookup above the status computation so Woke can see the PR state (no behavior change otherwise).

---

🤖 Generated with Claude Code using the Claude Fable 5 model.

---

Note

Low Risk
Client-side read/visit and banner UX only; no auth, API, or data-model changes beyond existing local visit timestamps.

Overview
Fixes Done badges sticking after you open a finished thread by stamping markThreadVisited with latestTurn.completedAt when the thread is open (not “now”), so you clear the completion you’re viewing without wiping a later Woke signal.

Adds a dismissible “This thread woke from snooze” info banner in the composer stack (same acknowledgment as the sidebar pill; send/settle/archive still clear it). Woke visibility in chat and the sidebar now matches: suppressed for merged/closed PRs, and the open-thread check folds in the completion visit floor to avoid a one-frame flash.

Sidebar v2 only reorders git/PR lookup so Woke can read PR state before computing the pill.

^{Reviewed by Cursor Bugbot for commit b41a398. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix Done badge clearing and add dismissible woke banner in thread chat view

• Opening a finished server thread now calls markThreadVisited at the thread's completedAt timestamp, which clears the sidebar's Done badge for that thread.
• Adds a dismissible "woke from snooze" banner in ChatView.tsx for the active thread when its wake is unseen; dismissing it calls acknowledgeActiveThreadWoke.
• Both the woke banner and the sidebar Woke pill in SidebarV2.tsx are suppressed when the thread's associated PR is merged or closed.

^{Macroscope summarized b41a398.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0f9a8a7d-0020-4969-a3df-06ba4bc76881

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	11.3 KiB	11.3 KiB	−9 B (−0.1%)	15.1 KiB	✅
Codex	Thread snapshot wire	5.4 KiB	5.5 KiB	+2 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	5.9 KiB	5.9 KiB	−11 B (−0.2%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	49.7 KiB	49.7 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	16	16	0 (0.0%)	21	✅
Claude	Total thread wire	11.3 KiB	11.3 KiB	−10 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	5.5 KiB	5.5 KiB	+1 B (+0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	5.9 KiB	5.9 KiB	−11 B (−0.2%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	50.6 KiB	50.6 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	16	16	0 (0.0%)	21	✅

Baseline: a8cd2ad · PR result: b41a398 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 94.6 KiB
• Claude decoded thread snapshot: 95.3 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit b41a398. Configure here.}

[cursor]

Visit stamp skipped while loading

Medium Severity

When a finished thread is opened while its details are still loading, the useEffect that marks it as visited doesn't run. This occurs because the effect's serverThread dependency is null during the loading phase. As a result, the sidebar's "Done" badge and "Woke" indicator incorrectly persist until the thread's full details load.

 

^{Reviewed by Cursor Bugbot for commit b41a398. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces runtime UI behavior changes affecting when Done badges clear and adds a new dismissible Woke banner. An unresolved review comment identifies a potential bug where visit stamps are skipped during loading, causing badges to incorrectly persist. The combination of behavior changes and the unresolved bug finding warrants human review.

^{You can customize Macroscope's approvability policy. Learn more.}