feat: sync thread read state across clients by t3dotgg · Pull Request #9124 · pingdotgg/t3code

t3dotgg · 2026-09-01T23:34:57Z

Opening a thread on one device did not clear its Done indicator anywhere else. Read state lived in each web client's local storage, and mobile had no read state at all.

The server now owns a viewedAt timestamp per thread, the same way it owns settlement since #8600. Clients send thread.view when a focused, visible thread's latest completion is read and thread.mark-unread from the existing menus, then render the server value directly. There is no optimistic local override, so the indicator flips when the shell update arrives, one round trip later.

Details:

The decider caps the boundary at server time and never moves it backward, so a stale view cannot undo a newer completion or a mark-unread.
Web only acknowledges a view when the document is visible and focused. Mobile only acknowledges when the thread route is focused, the app is active, and the environment is connected.
Viewing does not bump updatedAt, so reading a thread never reorders the list. View-only events are excluded from agent awareness.
Servers without the threadViewState capability keep the previous device-local fallback. Migration 044 backfills existing threads as read.

Replaces #6662, which carried the same server model plus about 550 lines of client-side pending, retry, and reconciliation state. This PR keeps the server half and drops the rest.

Tests: focused decider, migration, projection, relay, contracts, client-runtime, web, and mobile tests, plus typecheck for contracts, client-runtime, server, web, and mobile.

Made with Claude Fable 5.1 through Claude Code.

Note

Medium Risk
Touches orchestration commands, SQLite migration/backfill, and cross-client read semantics; mis-timed client acks or backfill could briefly show wrong Done state until shell sync.

Overview
Adds server-owned thread read state (viewedAt) so clearing the Done indicator on one device updates every connected client. Clients send thread.view (with the completion timestamp the user actually saw) and thread.mark-unread; the UI follows the shell’s viewedAt with no optimistic override, same pattern as settlement.

On the server, new commands persist through existing thread.meta-updated events (view-only updates do not bump updatedAt or reorder the list). The decider caps client boundaries at server time and never moves viewedAt backward. Migration 044 adds viewed_at and backfills existing threads as read. Environments advertise threadViewState; AgentAwarenessRelay ignores view-only meta updates.

Web routes mark-read/unread through useThreadViewState, with capability detection and local-storage fallback on older servers. ChatView only acknowledges a view when the tab is visible and focused, and waits for config/connection when using server commands.

Mobile sends thread.view from the focused thread route when the app is active, connected, detail is loaded, and shouldAcknowledgeThreadView says the latest completion is still unread.

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

Note

Add server-persisted thread `viewedAt` and `thread.view`/`thread.mark-unread` commands

Introduces server-backed thread view state so read/unread status syncs across clients. The server decider validates and caps client-supplied boundaries, prevents viewedAt from moving backward, and emits thread.meta-updated events carrying the new boundary. thread.mark-unread sets the boundary to just before the latest completed turn.
Adds migration 44 (044_ProjectionThreadsViewedAt.ts), which adds a nullable viewed_at column to projection_threads and backfills existing rows from updated_at (falling back to created_at).
Web and mobile clients gain a capability-aware useThreadViewState hook and mobile shouldAcknowledgeThreadView predicate that dispatch server commands on supported environments and fall back to local UI-store on older servers. Sidebar rows, action menus, and archive/settle actions all route through this path.
The AgentAwarenessRelay now suppresses thread.meta-updated events whose only changed field is viewedAt, so view-state sync does not trigger agent notifications.
Risk: migration 44 backfills viewed_at from updated_at for all existing projection threads — verify the backfill result matches expected read state on upgrade. Client view-state writes are suppressed while the environment capability is unresolved, so threads may appear unread until configuration loads.

^{Macroscope summarized 9175d4f.}

github-actions · 2026-09-01T23:38:24Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	+30 B (+0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	+5 B (+0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+25 B (+0.4%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+16 B (+0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−3 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+19 B (+0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 80c708a · PR result: 9175d4f · 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: 109.5 KiB
Claude decoded thread snapshot: 110.2 KiB

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

macroscopeapp · 2026-09-01T23:54:52Z

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces durable server-owned read state, new orchestration commands, a database migration/backfill, and coordinated behavior changes across web, mobile, and shared runtime paths. Its cross-client UX impact and changed read-state defaults make the change broader than a small additive update.

No code changes detected at 9175d4f. Prior analysis still applies.

^{You can add or adjust custom eligibility rules. Learn more.}

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 d6aad18. Configure here.}

Thread read and unread state lived in each web client's local storage, so opening a thread on one device did not clear its Done indicator anywhere else. The server now owns a viewedAt timestamp per thread. Clients send thread.view when a focused, visible thread's latest completion is read and thread.mark-unread from the existing menus. The decider caps the boundary at server time and never moves it backward. Clients render the server value directly, with no optimistic override, the same shape as server-side settlement. Servers without the threadViewState capability keep the previous local fallback. Migration 044 backfills existing threads as read. Made with Claude Fable 5.1 through Claude Code.

An acknowledgement sent before the capability loaded fell through to local storage and never reached other clients.

readEnvironmentSupportsViewState now returns undefined until the config arrives, and the hook drops the write instead of falling back to local storage on every entry point.

…nd load Web kept its focus listeners only until the first acknowledgement, so a thread marked unread elsewhere was not re-acked on refocus. It also sent the acknowledgement while disconnected, where it failed silently with no retry. Mobile acknowledged from the thread shell before messages loaded. Web now keeps the listeners for the life of the effect and waits for a connected environment, re-running on reconnect. Mobile acknowledges only once the loaded detail includes the completion.

…edging a view

t3dotgg · 2026-09-01T23:34:57Z

Opening a thread on one device did not clear its Done indicator anywhere else. Read state lived in each web client's local storage, and mobile had no read state at all.

The server now owns a viewedAt timestamp per thread, the same way it owns settlement since #8600. Clients send thread.view when a focused, visible thread's latest completion is read and thread.mark-unread from the existing menus, then render the server value directly. There is no optimistic local override, so the indicator flips when the shell update arrives, one round trip later.

Details:

The decider caps the boundary at server time and never moves it backward, so a stale view cannot undo a newer completion or a mark-unread.
Web only acknowledges a view when the document is visible and focused. Mobile only acknowledges when the thread route is focused, the app is active, and the environment is connected.
Viewing does not bump updatedAt, so reading a thread never reorders the list. View-only events are excluded from agent awareness.
Servers without the threadViewState capability keep the previous device-local fallback. Migration 044 backfills existing threads as read.

Replaces #6662, which carried the same server model plus about 550 lines of client-side pending, retry, and reconciliation state. This PR keeps the server half and drops the rest.

Tests: focused decider, migration, projection, relay, contracts, client-runtime, web, and mobile tests, plus typecheck for contracts, client-runtime, server, web, and mobile.

Made with Claude Fable 5.1 through Claude Code.

Note

Medium Risk
Touches orchestration commands, SQLite migration/backfill, and cross-client read semantics; mis-timed client acks or backfill could briefly show wrong Done state until shell sync.

Overview
Adds server-owned thread read state (viewedAt) so clearing the Done indicator on one device updates every connected client. Clients send thread.view (with the completion timestamp the user actually saw) and thread.mark-unread; the UI follows the shell’s viewedAt with no optimistic override, same pattern as settlement.

On the server, new commands persist through existing thread.meta-updated events (view-only updates do not bump updatedAt or reorder the list). The decider caps client boundaries at server time and never moves viewedAt backward. Migration 044 adds viewed_at and backfills existing threads as read. Environments advertise threadViewState; AgentAwarenessRelay ignores view-only meta updates.

Web routes mark-read/unread through useThreadViewState, with capability detection and local-storage fallback on older servers. ChatView only acknowledges a view when the tab is visible and focused, and waits for config/connection when using server commands.

Mobile sends thread.view from the focused thread route when the app is active, connected, detail is loaded, and shouldAcknowledgeThreadView says the latest completion is still unread.

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

Note

Add server-persisted thread `viewedAt` and `thread.view`/`thread.mark-unread` commands

Introduces server-backed thread view state so read/unread status syncs across clients. The server decider validates and caps client-supplied boundaries, prevents viewedAt from moving backward, and emits thread.meta-updated events carrying the new boundary. thread.mark-unread sets the boundary to just before the latest completed turn.
Adds migration 44 (044_ProjectionThreadsViewedAt.ts), which adds a nullable viewed_at column to projection_threads and backfills existing rows from updated_at (falling back to created_at).
Web and mobile clients gain a capability-aware useThreadViewState hook and mobile shouldAcknowledgeThreadView predicate that dispatch server commands on supported environments and fall back to local UI-store on older servers. Sidebar rows, action menus, and archive/settle actions all route through this path.
The AgentAwarenessRelay now suppresses thread.meta-updated events whose only changed field is viewedAt, so view-state sync does not trigger agent notifications.
Risk: migration 44 backfills viewed_at from updated_at for all existing projection threads — verify the backfill result matches expected read state on upgrade. Client view-state writes are suppressed while the environment capability is unresolved, so threads may appear unread until configuration loads.

^{Macroscope summarized 9175d4f.}

github-actions · 2026-09-01T23:38:24Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	+30 B (+0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	+5 B (+0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+25 B (+0.4%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+16 B (+0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−3 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+19 B (+0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 80c708a · PR result: 9175d4f · 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: 109.5 KiB
Claude decoded thread snapshot: 110.2 KiB

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

macroscopeapp · 2026-09-01T23:54:52Z

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces durable server-owned read state, new orchestration commands, a database migration/backfill, and coordinated behavior changes across web, mobile, and shared runtime paths. Its cross-client UX impact and changed read-state defaults make the change broader than a small additive update.

No code changes detected at 9175d4f. Prior analysis still applies.

^{You can add or adjust custom eligibility rules. Learn more.}

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 d6aad18. Configure here.}

Thread read and unread state lived in each web client's local storage, so opening a thread on one device did not clear its Done indicator anywhere else. The server now owns a viewedAt timestamp per thread. Clients send thread.view when a focused, visible thread's latest completion is read and thread.mark-unread from the existing menus. The decider caps the boundary at server time and never moves it backward. Clients render the server value directly, with no optimistic override, the same shape as server-side settlement. Servers without the threadViewState capability keep the previous local fallback. Migration 044 backfills existing threads as read. Made with Claude Fable 5.1 through Claude Code.

An acknowledgement sent before the capability loaded fell through to local storage and never reached other clients.

readEnvironmentSupportsViewState now returns undefined until the config arrives, and the hook drops the write instead of falling back to local storage on every entry point.

…nd load Web kept its focus listeners only until the first acknowledgement, so a thread marked unread elsewhere was not re-acked on refocus. It also sent the acknowledgement while disconnected, where it failed silently with no retry. Mobile acknowledged from the thread shell before messages loaded. Web now keeps the listeners for the life of the effect and waits for a connected environment, re-running on reconnect. Mobile acknowledges only once the loaded detail includes the completion.

…edging a view

t3dotgg · 2026-09-01T23:34:57Z

Opening a thread on one device did not clear its Done indicator anywhere else. Read state lived in each web client's local storage, and mobile had no read state at all.

The server now owns a viewedAt timestamp per thread, the same way it owns settlement since #8600. Clients send thread.view when a focused, visible thread's latest completion is read and thread.mark-unread from the existing menus, then render the server value directly. There is no optimistic local override, so the indicator flips when the shell update arrives, one round trip later.

Details:

The decider caps the boundary at server time and never moves it backward, so a stale view cannot undo a newer completion or a mark-unread.
Web only acknowledges a view when the document is visible and focused. Mobile only acknowledges when the thread route is focused, the app is active, and the environment is connected.
Viewing does not bump updatedAt, so reading a thread never reorders the list. View-only events are excluded from agent awareness.
Servers without the threadViewState capability keep the previous device-local fallback. Migration 044 backfills existing threads as read.

Replaces #6662, which carried the same server model plus about 550 lines of client-side pending, retry, and reconciliation state. This PR keeps the server half and drops the rest.

Tests: focused decider, migration, projection, relay, contracts, client-runtime, web, and mobile tests, plus typecheck for contracts, client-runtime, server, web, and mobile.

Made with Claude Fable 5.1 through Claude Code.

Note

Medium Risk
Touches orchestration commands, SQLite migration/backfill, and cross-client read semantics; mis-timed client acks or backfill could briefly show wrong Done state until shell sync.

Overview
Adds server-owned thread read state (viewedAt) so clearing the Done indicator on one device updates every connected client. Clients send thread.view (with the completion timestamp the user actually saw) and thread.mark-unread; the UI follows the shell’s viewedAt with no optimistic override, same pattern as settlement.

On the server, new commands persist through existing thread.meta-updated events (view-only updates do not bump updatedAt or reorder the list). The decider caps client boundaries at server time and never moves viewedAt backward. Migration 044 adds viewed_at and backfills existing threads as read. Environments advertise threadViewState; AgentAwarenessRelay ignores view-only meta updates.

Web routes mark-read/unread through useThreadViewState, with capability detection and local-storage fallback on older servers. ChatView only acknowledges a view when the tab is visible and focused, and waits for config/connection when using server commands.

Mobile sends thread.view from the focused thread route when the app is active, connected, detail is loaded, and shouldAcknowledgeThreadView says the latest completion is still unread.

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

Note

Add server-persisted thread `viewedAt` and `thread.view`/`thread.mark-unread` commands

Introduces server-backed thread view state so read/unread status syncs across clients. The server decider validates and caps client-supplied boundaries, prevents viewedAt from moving backward, and emits thread.meta-updated events carrying the new boundary. thread.mark-unread sets the boundary to just before the latest completed turn.
Adds migration 44 (044_ProjectionThreadsViewedAt.ts), which adds a nullable viewed_at column to projection_threads and backfills existing rows from updated_at (falling back to created_at).
Web and mobile clients gain a capability-aware useThreadViewState hook and mobile shouldAcknowledgeThreadView predicate that dispatch server commands on supported environments and fall back to local UI-store on older servers. Sidebar rows, action menus, and archive/settle actions all route through this path.
The AgentAwarenessRelay now suppresses thread.meta-updated events whose only changed field is viewedAt, so view-state sync does not trigger agent notifications.
Risk: migration 44 backfills viewed_at from updated_at for all existing projection threads — verify the backfill result matches expected read state on upgrade. Client view-state writes are suppressed while the environment capability is unresolved, so threads may appear unread until configuration loads.

^{Macroscope summarized 9175d4f.}

github-actions · 2026-09-01T23:38:24Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	+30 B (+0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	+5 B (+0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+25 B (+0.4%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+16 B (+0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−3 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+19 B (+0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 80c708a · PR result: 9175d4f · 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: 109.5 KiB
Claude decoded thread snapshot: 110.2 KiB

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

macroscopeapp · 2026-09-01T23:54:52Z

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces durable server-owned read state, new orchestration commands, a database migration/backfill, and coordinated behavior changes across web, mobile, and shared runtime paths. Its cross-client UX impact and changed read-state defaults make the change broader than a small additive update.

No code changes detected at 9175d4f. Prior analysis still applies.

^{You can add or adjust custom eligibility rules. Learn more.}

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 d6aad18. Configure here.}

Thread read and unread state lived in each web client's local storage, so opening a thread on one device did not clear its Done indicator anywhere else. The server now owns a viewedAt timestamp per thread. Clients send thread.view when a focused, visible thread's latest completion is read and thread.mark-unread from the existing menus. The decider caps the boundary at server time and never moves it backward. Clients render the server value directly, with no optimistic override, the same shape as server-side settlement. Servers without the threadViewState capability keep the previous local fallback. Migration 044 backfills existing threads as read. Made with Claude Fable 5.1 through Claude Code.

An acknowledgement sent before the capability loaded fell through to local storage and never reached other clients.

readEnvironmentSupportsViewState now returns undefined until the config arrives, and the hook drops the write instead of falling back to local storage on every entry point.

…nd load Web kept its focus listeners only until the first acknowledgement, so a thread marked unread elsewhere was not re-acked on refocus. It also sent the acknowledgement while disconnected, where it failed silently with no retry. Mobile acknowledged from the thread shell before messages loaded. Web now keeps the listeners for the life of the effect and waits for a connected environment, re-running on reconnect. Mobile acknowledges only once the loaded detail includes the completion.

…edging a view

t3dotgg · 2026-09-01T23:34:57Z

Opening a thread on one device did not clear its Done indicator anywhere else. Read state lived in each web client's local storage, and mobile had no read state at all.

The server now owns a viewedAt timestamp per thread, the same way it owns settlement since #8600. Clients send thread.view when a focused, visible thread's latest completion is read and thread.mark-unread from the existing menus, then render the server value directly. There is no optimistic local override, so the indicator flips when the shell update arrives, one round trip later.

Details:

The decider caps the boundary at server time and never moves it backward, so a stale view cannot undo a newer completion or a mark-unread.
Web only acknowledges a view when the document is visible and focused. Mobile only acknowledges when the thread route is focused, the app is active, and the environment is connected.
Viewing does not bump updatedAt, so reading a thread never reorders the list. View-only events are excluded from agent awareness.
Servers without the threadViewState capability keep the previous device-local fallback. Migration 044 backfills existing threads as read.

Replaces #6662, which carried the same server model plus about 550 lines of client-side pending, retry, and reconciliation state. This PR keeps the server half and drops the rest.

Tests: focused decider, migration, projection, relay, contracts, client-runtime, web, and mobile tests, plus typecheck for contracts, client-runtime, server, web, and mobile.

Made with Claude Fable 5.1 through Claude Code.

Note

Medium Risk
Touches orchestration commands, SQLite migration/backfill, and cross-client read semantics; mis-timed client acks or backfill could briefly show wrong Done state until shell sync.

Overview
Adds server-owned thread read state (viewedAt) so clearing the Done indicator on one device updates every connected client. Clients send thread.view (with the completion timestamp the user actually saw) and thread.mark-unread; the UI follows the shell’s viewedAt with no optimistic override, same pattern as settlement.

On the server, new commands persist through existing thread.meta-updated events (view-only updates do not bump updatedAt or reorder the list). The decider caps client boundaries at server time and never moves viewedAt backward. Migration 044 adds viewed_at and backfills existing threads as read. Environments advertise threadViewState; AgentAwarenessRelay ignores view-only meta updates.

Web routes mark-read/unread through useThreadViewState, with capability detection and local-storage fallback on older servers. ChatView only acknowledges a view when the tab is visible and focused, and waits for config/connection when using server commands.

Mobile sends thread.view from the focused thread route when the app is active, connected, detail is loaded, and shouldAcknowledgeThreadView says the latest completion is still unread.

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

Note

Add server-persisted thread `viewedAt` and `thread.view`/`thread.mark-unread` commands

Introduces server-backed thread view state so read/unread status syncs across clients. The server decider validates and caps client-supplied boundaries, prevents viewedAt from moving backward, and emits thread.meta-updated events carrying the new boundary. thread.mark-unread sets the boundary to just before the latest completed turn.
Adds migration 44 (044_ProjectionThreadsViewedAt.ts), which adds a nullable viewed_at column to projection_threads and backfills existing rows from updated_at (falling back to created_at).
Web and mobile clients gain a capability-aware useThreadViewState hook and mobile shouldAcknowledgeThreadView predicate that dispatch server commands on supported environments and fall back to local UI-store on older servers. Sidebar rows, action menus, and archive/settle actions all route through this path.
The AgentAwarenessRelay now suppresses thread.meta-updated events whose only changed field is viewedAt, so view-state sync does not trigger agent notifications.
Risk: migration 44 backfills viewed_at from updated_at for all existing projection threads — verify the backfill result matches expected read state on upgrade. Client view-state writes are suppressed while the environment capability is unresolved, so threads may appear unread until configuration loads.

^{Macroscope summarized 9175d4f.}

github-actions · 2026-09-01T23:38:24Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	+30 B (+0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	+5 B (+0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+25 B (+0.4%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+16 B (+0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−3 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+19 B (+0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 80c708a · PR result: 9175d4f · 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: 109.5 KiB
Claude decoded thread snapshot: 110.2 KiB

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

macroscopeapp · 2026-09-01T23:54:52Z

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces durable server-owned read state, new orchestration commands, a database migration/backfill, and coordinated behavior changes across web, mobile, and shared runtime paths. Its cross-client UX impact and changed read-state defaults make the change broader than a small additive update.

No code changes detected at 9175d4f. Prior analysis still applies.

^{You can add or adjust custom eligibility rules. Learn more.}

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 d6aad18. Configure here.}

Thread read and unread state lived in each web client's local storage, so opening a thread on one device did not clear its Done indicator anywhere else. The server now owns a viewedAt timestamp per thread. Clients send thread.view when a focused, visible thread's latest completion is read and thread.mark-unread from the existing menus. The decider caps the boundary at server time and never moves it backward. Clients render the server value directly, with no optimistic override, the same shape as server-side settlement. Servers without the threadViewState capability keep the previous local fallback. Migration 044 backfills existing threads as read. Made with Claude Fable 5.1 through Claude Code.

An acknowledgement sent before the capability loaded fell through to local storage and never reached other clients.

readEnvironmentSupportsViewState now returns undefined until the config arrives, and the hook drops the write instead of falling back to local storage on every entry point.

…nd load Web kept its focus listeners only until the first acknowledgement, so a thread marked unread elsewhere was not re-acked on refocus. It also sent the acknowledgement while disconnected, where it failed silently with no retry. Mobile acknowledged from the thread shell before messages loaded. Web now keeps the listeners for the life of the effect and waits for a connected environment, re-running on reconnect. Mobile acknowledges only once the loaded detail includes the completion.

…edging a view

t3dotgg · 2026-09-01T23:34:57Z

Opening a thread on one device did not clear its Done indicator anywhere else. Read state lived in each web client's local storage, and mobile had no read state at all.

The server now owns a viewedAt timestamp per thread, the same way it owns settlement since #8600. Clients send thread.view when a focused, visible thread's latest completion is read and thread.mark-unread from the existing menus, then render the server value directly. There is no optimistic local override, so the indicator flips when the shell update arrives, one round trip later.

Details:

The decider caps the boundary at server time and never moves it backward, so a stale view cannot undo a newer completion or a mark-unread.
Web only acknowledges a view when the document is visible and focused. Mobile only acknowledges when the thread route is focused, the app is active, and the environment is connected.
Viewing does not bump updatedAt, so reading a thread never reorders the list. View-only events are excluded from agent awareness.
Servers without the threadViewState capability keep the previous device-local fallback. Migration 044 backfills existing threads as read.

Replaces #6662, which carried the same server model plus about 550 lines of client-side pending, retry, and reconciliation state. This PR keeps the server half and drops the rest.

Tests: focused decider, migration, projection, relay, contracts, client-runtime, web, and mobile tests, plus typecheck for contracts, client-runtime, server, web, and mobile.

Made with Claude Fable 5.1 through Claude Code.

Note

Medium Risk
Touches orchestration commands, SQLite migration/backfill, and cross-client read semantics; mis-timed client acks or backfill could briefly show wrong Done state until shell sync.

Overview
Adds server-owned thread read state (viewedAt) so clearing the Done indicator on one device updates every connected client. Clients send thread.view (with the completion timestamp the user actually saw) and thread.mark-unread; the UI follows the shell’s viewedAt with no optimistic override, same pattern as settlement.

On the server, new commands persist through existing thread.meta-updated events (view-only updates do not bump updatedAt or reorder the list). The decider caps client boundaries at server time and never moves viewedAt backward. Migration 044 adds viewed_at and backfills existing threads as read. Environments advertise threadViewState; AgentAwarenessRelay ignores view-only meta updates.

Web routes mark-read/unread through useThreadViewState, with capability detection and local-storage fallback on older servers. ChatView only acknowledges a view when the tab is visible and focused, and waits for config/connection when using server commands.

Mobile sends thread.view from the focused thread route when the app is active, connected, detail is loaded, and shouldAcknowledgeThreadView says the latest completion is still unread.

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

Note

Add server-persisted thread `viewedAt` and `thread.view`/`thread.mark-unread` commands

Introduces server-backed thread view state so read/unread status syncs across clients. The server decider validates and caps client-supplied boundaries, prevents viewedAt from moving backward, and emits thread.meta-updated events carrying the new boundary. thread.mark-unread sets the boundary to just before the latest completed turn.
Adds migration 44 (044_ProjectionThreadsViewedAt.ts), which adds a nullable viewed_at column to projection_threads and backfills existing rows from updated_at (falling back to created_at).
Web and mobile clients gain a capability-aware useThreadViewState hook and mobile shouldAcknowledgeThreadView predicate that dispatch server commands on supported environments and fall back to local UI-store on older servers. Sidebar rows, action menus, and archive/settle actions all route through this path.
The AgentAwarenessRelay now suppresses thread.meta-updated events whose only changed field is viewedAt, so view-state sync does not trigger agent notifications.
Risk: migration 44 backfills viewed_at from updated_at for all existing projection threads — verify the backfill result matches expected read state on upgrade. Client view-state writes are suppressed while the environment capability is unresolved, so threads may appear unread until configuration loads.

^{Macroscope summarized 9175d4f.}

github-actions · 2026-09-01T23:38:24Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	+30 B (+0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	+5 B (+0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+25 B (+0.4%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+16 B (+0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−3 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+19 B (+0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 80c708a · PR result: 9175d4f · 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: 109.5 KiB
Claude decoded thread snapshot: 110.2 KiB

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

macroscopeapp · 2026-09-01T23:54:52Z

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces durable server-owned read state, new orchestration commands, a database migration/backfill, and coordinated behavior changes across web, mobile, and shared runtime paths. Its cross-client UX impact and changed read-state defaults make the change broader than a small additive update.

No code changes detected at 9175d4f. Prior analysis still applies.

^{You can add or adjust custom eligibility rules. Learn more.}

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 d6aad18. Configure here.}

Thread read and unread state lived in each web client's local storage, so opening a thread on one device did not clear its Done indicator anywhere else. The server now owns a viewedAt timestamp per thread. Clients send thread.view when a focused, visible thread's latest completion is read and thread.mark-unread from the existing menus. The decider caps the boundary at server time and never moves it backward. Clients render the server value directly, with no optimistic override, the same shape as server-side settlement. Servers without the threadViewState capability keep the previous local fallback. Migration 044 backfills existing threads as read. Made with Claude Fable 5.1 through Claude Code.

An acknowledgement sent before the capability loaded fell through to local storage and never reached other clients.

readEnvironmentSupportsViewState now returns undefined until the config arrives, and the hook drops the write instead of falling back to local storage on every entry point.

…nd load Web kept its focus listeners only until the first acknowledgement, so a thread marked unread elsewhere was not re-acked on refocus. It also sent the acknowledgement while disconnected, where it failed silently with no retry. Mobile acknowledged from the thread shell before messages loaded. Web now keeps the listeners for the life of the effect and waits for a connected environment, re-running on reconnect. Mobile acknowledges only once the loaded detail includes the completion.

…edging a view

t3dotgg · 2026-09-01T23:34:57Z

Opening a thread on one device did not clear its Done indicator anywhere else. Read state lived in each web client's local storage, and mobile had no read state at all.

The server now owns a viewedAt timestamp per thread, the same way it owns settlement since #8600. Clients send thread.view when a focused, visible thread's latest completion is read and thread.mark-unread from the existing menus, then render the server value directly. There is no optimistic local override, so the indicator flips when the shell update arrives, one round trip later.

Details:

The decider caps the boundary at server time and never moves it backward, so a stale view cannot undo a newer completion or a mark-unread.
Web only acknowledges a view when the document is visible and focused. Mobile only acknowledges when the thread route is focused, the app is active, and the environment is connected.
Viewing does not bump updatedAt, so reading a thread never reorders the list. View-only events are excluded from agent awareness.
Servers without the threadViewState capability keep the previous device-local fallback. Migration 044 backfills existing threads as read.

Replaces #6662, which carried the same server model plus about 550 lines of client-side pending, retry, and reconciliation state. This PR keeps the server half and drops the rest.

Tests: focused decider, migration, projection, relay, contracts, client-runtime, web, and mobile tests, plus typecheck for contracts, client-runtime, server, web, and mobile.

Made with Claude Fable 5.1 through Claude Code.

Note

Medium Risk
Touches orchestration commands, SQLite migration/backfill, and cross-client read semantics; mis-timed client acks or backfill could briefly show wrong Done state until shell sync.

Overview
Adds server-owned thread read state (viewedAt) so clearing the Done indicator on one device updates every connected client. Clients send thread.view (with the completion timestamp the user actually saw) and thread.mark-unread; the UI follows the shell’s viewedAt with no optimistic override, same pattern as settlement.

On the server, new commands persist through existing thread.meta-updated events (view-only updates do not bump updatedAt or reorder the list). The decider caps client boundaries at server time and never moves viewedAt backward. Migration 044 adds viewed_at and backfills existing threads as read. Environments advertise threadViewState; AgentAwarenessRelay ignores view-only meta updates.

Web routes mark-read/unread through useThreadViewState, with capability detection and local-storage fallback on older servers. ChatView only acknowledges a view when the tab is visible and focused, and waits for config/connection when using server commands.

Mobile sends thread.view from the focused thread route when the app is active, connected, detail is loaded, and shouldAcknowledgeThreadView says the latest completion is still unread.

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

Note

Add server-persisted thread `viewedAt` and `thread.view`/`thread.mark-unread` commands

Introduces server-backed thread view state so read/unread status syncs across clients. The server decider validates and caps client-supplied boundaries, prevents viewedAt from moving backward, and emits thread.meta-updated events carrying the new boundary. thread.mark-unread sets the boundary to just before the latest completed turn.
Adds migration 44 (044_ProjectionThreadsViewedAt.ts), which adds a nullable viewed_at column to projection_threads and backfills existing rows from updated_at (falling back to created_at).
Web and mobile clients gain a capability-aware useThreadViewState hook and mobile shouldAcknowledgeThreadView predicate that dispatch server commands on supported environments and fall back to local UI-store on older servers. Sidebar rows, action menus, and archive/settle actions all route through this path.
The AgentAwarenessRelay now suppresses thread.meta-updated events whose only changed field is viewedAt, so view-state sync does not trigger agent notifications.
Risk: migration 44 backfills viewed_at from updated_at for all existing projection threads — verify the backfill result matches expected read state on upgrade. Client view-state writes are suppressed while the environment capability is unresolved, so threads may appear unread until configuration loads.

^{Macroscope summarized 9175d4f.}

github-actions · 2026-09-01T23:38:24Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	+30 B (+0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	+5 B (+0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+25 B (+0.4%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+16 B (+0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−3 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+19 B (+0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 80c708a · PR result: 9175d4f · 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: 109.5 KiB
Claude decoded thread snapshot: 110.2 KiB

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

macroscopeapp · 2026-09-01T23:54:52Z

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces durable server-owned read state, new orchestration commands, a database migration/backfill, and coordinated behavior changes across web, mobile, and shared runtime paths. Its cross-client UX impact and changed read-state defaults make the change broader than a small additive update.

No code changes detected at 9175d4f. Prior analysis still applies.

^{You can add or adjust custom eligibility rules. Learn more.}

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 d6aad18. Configure here.}

Thread read and unread state lived in each web client's local storage, so opening a thread on one device did not clear its Done indicator anywhere else. The server now owns a viewedAt timestamp per thread. Clients send thread.view when a focused, visible thread's latest completion is read and thread.mark-unread from the existing menus. The decider caps the boundary at server time and never moves it backward. Clients render the server value directly, with no optimistic override, the same shape as server-side settlement. Servers without the threadViewState capability keep the previous local fallback. Migration 044 backfills existing threads as read. Made with Claude Fable 5.1 through Claude Code.

An acknowledgement sent before the capability loaded fell through to local storage and never reached other clients.

readEnvironmentSupportsViewState now returns undefined until the config arrives, and the hook drops the write instead of falling back to local storage on every entry point.

…nd load Web kept its focus listeners only until the first acknowledgement, so a thread marked unread elsewhere was not re-acked on refocus. It also sent the acknowledgement while disconnected, where it failed silently with no retry. Mobile acknowledged from the thread shell before messages loaded. Web now keeps the listeners for the life of the effect and waits for a connected environment, re-running on reconnect. Mobile acknowledges only once the loaded detail includes the completion.

…edging a view

t3dotgg · 2026-09-01T23:34:57Z

Opening a thread on one device did not clear its Done indicator anywhere else. Read state lived in each web client's local storage, and mobile had no read state at all.

The server now owns a viewedAt timestamp per thread, the same way it owns settlement since #8600. Clients send thread.view when a focused, visible thread's latest completion is read and thread.mark-unread from the existing menus, then render the server value directly. There is no optimistic local override, so the indicator flips when the shell update arrives, one round trip later.

Details:

The decider caps the boundary at server time and never moves it backward, so a stale view cannot undo a newer completion or a mark-unread.
Web only acknowledges a view when the document is visible and focused. Mobile only acknowledges when the thread route is focused, the app is active, and the environment is connected.
Viewing does not bump updatedAt, so reading a thread never reorders the list. View-only events are excluded from agent awareness.
Servers without the threadViewState capability keep the previous device-local fallback. Migration 044 backfills existing threads as read.

Replaces #6662, which carried the same server model plus about 550 lines of client-side pending, retry, and reconciliation state. This PR keeps the server half and drops the rest.

Tests: focused decider, migration, projection, relay, contracts, client-runtime, web, and mobile tests, plus typecheck for contracts, client-runtime, server, web, and mobile.

Made with Claude Fable 5.1 through Claude Code.

Note

Medium Risk
Touches orchestration commands, SQLite migration/backfill, and cross-client read semantics; mis-timed client acks or backfill could briefly show wrong Done state until shell sync.

Overview
Adds server-owned thread read state (viewedAt) so clearing the Done indicator on one device updates every connected client. Clients send thread.view (with the completion timestamp the user actually saw) and thread.mark-unread; the UI follows the shell’s viewedAt with no optimistic override, same pattern as settlement.

On the server, new commands persist through existing thread.meta-updated events (view-only updates do not bump updatedAt or reorder the list). The decider caps client boundaries at server time and never moves viewedAt backward. Migration 044 adds viewed_at and backfills existing threads as read. Environments advertise threadViewState; AgentAwarenessRelay ignores view-only meta updates.

Web routes mark-read/unread through useThreadViewState, with capability detection and local-storage fallback on older servers. ChatView only acknowledges a view when the tab is visible and focused, and waits for config/connection when using server commands.

Mobile sends thread.view from the focused thread route when the app is active, connected, detail is loaded, and shouldAcknowledgeThreadView says the latest completion is still unread.

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

Note

Add server-persisted thread `viewedAt` and `thread.view`/`thread.mark-unread` commands

Introduces server-backed thread view state so read/unread status syncs across clients. The server decider validates and caps client-supplied boundaries, prevents viewedAt from moving backward, and emits thread.meta-updated events carrying the new boundary. thread.mark-unread sets the boundary to just before the latest completed turn.
Adds migration 44 (044_ProjectionThreadsViewedAt.ts), which adds a nullable viewed_at column to projection_threads and backfills existing rows from updated_at (falling back to created_at).
Web and mobile clients gain a capability-aware useThreadViewState hook and mobile shouldAcknowledgeThreadView predicate that dispatch server commands on supported environments and fall back to local UI-store on older servers. Sidebar rows, action menus, and archive/settle actions all route through this path.
The AgentAwarenessRelay now suppresses thread.meta-updated events whose only changed field is viewedAt, so view-state sync does not trigger agent notifications.
Risk: migration 44 backfills viewed_at from updated_at for all existing projection threads — verify the backfill result matches expected read state on upgrade. Client view-state writes are suppressed while the environment capability is unresolved, so threads may appear unread until configuration loads.

^{Macroscope summarized 9175d4f.}

github-actions · 2026-09-01T23:38:24Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	+30 B (+0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	+5 B (+0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+25 B (+0.4%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+16 B (+0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−3 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+19 B (+0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 80c708a · PR result: 9175d4f · 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: 109.5 KiB
Claude decoded thread snapshot: 110.2 KiB

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

macroscopeapp · 2026-09-01T23:54:52Z

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces durable server-owned read state, new orchestration commands, a database migration/backfill, and coordinated behavior changes across web, mobile, and shared runtime paths. Its cross-client UX impact and changed read-state defaults make the change broader than a small additive update.

No code changes detected at 9175d4f. Prior analysis still applies.

^{You can add or adjust custom eligibility rules. Learn more.}

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 d6aad18. Configure here.}

Thread read and unread state lived in each web client's local storage, so opening a thread on one device did not clear its Done indicator anywhere else. The server now owns a viewedAt timestamp per thread. Clients send thread.view when a focused, visible thread's latest completion is read and thread.mark-unread from the existing menus. The decider caps the boundary at server time and never moves it backward. Clients render the server value directly, with no optimistic override, the same shape as server-side settlement. Servers without the threadViewState capability keep the previous local fallback. Migration 044 backfills existing threads as read. Made with Claude Fable 5.1 through Claude Code.

An acknowledgement sent before the capability loaded fell through to local storage and never reached other clients.

readEnvironmentSupportsViewState now returns undefined until the config arrives, and the hook drops the write instead of falling back to local storage on every entry point.

…nd load Web kept its focus listeners only until the first acknowledgement, so a thread marked unread elsewhere was not re-acked on refocus. It also sent the acknowledgement while disconnected, where it failed silently with no retry. Mobile acknowledged from the thread shell before messages loaded. Web now keeps the listeners for the life of the effect and waits for a connected environment, re-running on reconnect. Mobile acknowledges only once the loaded detail includes the completion.

…edging a view

t3dotgg · 2026-09-01T23:34:57Z

Opening a thread on one device did not clear its Done indicator anywhere else. Read state lived in each web client's local storage, and mobile had no read state at all.

The server now owns a viewedAt timestamp per thread, the same way it owns settlement since #8600. Clients send thread.view when a focused, visible thread's latest completion is read and thread.mark-unread from the existing menus, then render the server value directly. There is no optimistic local override, so the indicator flips when the shell update arrives, one round trip later.

Details:

The decider caps the boundary at server time and never moves it backward, so a stale view cannot undo a newer completion or a mark-unread.
Web only acknowledges a view when the document is visible and focused. Mobile only acknowledges when the thread route is focused, the app is active, and the environment is connected.
Viewing does not bump updatedAt, so reading a thread never reorders the list. View-only events are excluded from agent awareness.
Servers without the threadViewState capability keep the previous device-local fallback. Migration 044 backfills existing threads as read.

Replaces #6662, which carried the same server model plus about 550 lines of client-side pending, retry, and reconciliation state. This PR keeps the server half and drops the rest.

Tests: focused decider, migration, projection, relay, contracts, client-runtime, web, and mobile tests, plus typecheck for contracts, client-runtime, server, web, and mobile.

Made with Claude Fable 5.1 through Claude Code.

Note

Medium Risk
Touches orchestration commands, SQLite migration/backfill, and cross-client read semantics; mis-timed client acks or backfill could briefly show wrong Done state until shell sync.

Overview
Adds server-owned thread read state (viewedAt) so clearing the Done indicator on one device updates every connected client. Clients send thread.view (with the completion timestamp the user actually saw) and thread.mark-unread; the UI follows the shell’s viewedAt with no optimistic override, same pattern as settlement.

On the server, new commands persist through existing thread.meta-updated events (view-only updates do not bump updatedAt or reorder the list). The decider caps client boundaries at server time and never moves viewedAt backward. Migration 044 adds viewed_at and backfills existing threads as read. Environments advertise threadViewState; AgentAwarenessRelay ignores view-only meta updates.

Web routes mark-read/unread through useThreadViewState, with capability detection and local-storage fallback on older servers. ChatView only acknowledges a view when the tab is visible and focused, and waits for config/connection when using server commands.

Mobile sends thread.view from the focused thread route when the app is active, connected, detail is loaded, and shouldAcknowledgeThreadView says the latest completion is still unread.

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

Note

Add server-persisted thread `viewedAt` and `thread.view`/`thread.mark-unread` commands

Introduces server-backed thread view state so read/unread status syncs across clients. The server decider validates and caps client-supplied boundaries, prevents viewedAt from moving backward, and emits thread.meta-updated events carrying the new boundary. thread.mark-unread sets the boundary to just before the latest completed turn.
Adds migration 44 (044_ProjectionThreadsViewedAt.ts), which adds a nullable viewed_at column to projection_threads and backfills existing rows from updated_at (falling back to created_at).
Web and mobile clients gain a capability-aware useThreadViewState hook and mobile shouldAcknowledgeThreadView predicate that dispatch server commands on supported environments and fall back to local UI-store on older servers. Sidebar rows, action menus, and archive/settle actions all route through this path.
The AgentAwarenessRelay now suppresses thread.meta-updated events whose only changed field is viewedAt, so view-state sync does not trigger agent notifications.
Risk: migration 44 backfills viewed_at from updated_at for all existing projection threads — verify the backfill result matches expected read state on upgrade. Client view-state writes are suppressed while the environment capability is unresolved, so threads may appear unread until configuration loads.

^{Macroscope summarized 9175d4f.}

github-actions · 2026-09-01T23:38:24Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.3 KiB	13.3 KiB	+30 B (+0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	+5 B (+0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+25 B (+0.4%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.6 KiB	55.6 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.3 KiB	+16 B (+0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−3 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.4 KiB	+19 B (+0.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	56.4 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 80c708a · PR result: 9175d4f · 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: 109.5 KiB
Claude decoded thread snapshot: 110.2 KiB

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

macroscopeapp · 2026-09-01T23:54:52Z

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces durable server-owned read state, new orchestration commands, a database migration/backfill, and coordinated behavior changes across web, mobile, and shared runtime paths. Its cross-client UX impact and changed read-state defaults make the change broader than a small additive update.

No code changes detected at 9175d4f. Prior analysis still applies.

^{You can add or adjust custom eligibility rules. Learn more.}

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 d6aad18. Configure here.}

Thread read and unread state lived in each web client's local storage, so opening a thread on one device did not clear its Done indicator anywhere else. The server now owns a viewedAt timestamp per thread. Clients send thread.view when a focused, visible thread's latest completion is read and thread.mark-unread from the existing menus. The decider caps the boundary at server time and never moves it backward. Clients render the server value directly, with no optimistic override, the same shape as server-side settlement. Servers without the threadViewState capability keep the previous local fallback. Migration 044 backfills existing threads as read. Made with Claude Fable 5.1 through Claude Code.

An acknowledgement sent before the capability loaded fell through to local storage and never reached other clients.

readEnvironmentSupportsViewState now returns undefined until the config arrives, and the hook drops the write instead of falling back to local storage on every entry point.

…nd load Web kept its focus listeners only until the first acknowledgement, so a thread marked unread elsewhere was not re-acked on refocus. It also sent the acknowledgement while disconnected, where it failed silently with no retry. Mobile acknowledged from the thread shell before messages loaded. Web now keeps the listeners for the life of the effect and waits for a connected environment, re-running on reconnect. Mobile acknowledges only once the loaded detail includes the completion.

…edging a view

t3dotgg mentioned this pull request Sep 1, 2026
feat: sync thread unread state across clients #6662
Closed

github-actionsBot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:L 100-499 changed lines (additions + deletions). labels Sep 1, 2026

macroscopeappBot reviewed Sep 1, 2026
View reviewed changes

Comment threadapps/web/src/hooks/useThreadViewState.ts Outdated
Comment threadpackages/contracts/src/orchestration.ts

github-actionsBot added size:XL 500-999 changed lines (additions + deletions). and removed size:L 100-499 changed lines (additions + deletions). labels Sep 1, 2026

macroscopeappBot reviewed Sep 1, 2026
View reviewed changes

Comment threadapps/web/src/components/ChatView.tsx

cursorBot reviewed Sep 2, 2026
View reviewed changes

Comment threadapps/web/src/components/ChatView.tsx Outdated

macroscopeappBot reviewed Sep 2, 2026
View reviewed changes

Comment threadapps/web/src/components/ChatView.tsx Outdated

t3dotgg added 6 commits September 1, 2026 18:51

fix(web): wait for environment config before acknowledging a view
f016512
An acknowledgement sent before the capability loaded fell through to local storage and never reached other clients.

fix(web): do not misfile view state while environment config loads
8be9a4d
readEnvironmentSupportsViewState now returns undefined until the config arrives, and the hook drops the write instead of falling back to local storage on every entry point.

fix(web): treat an unknown environment as disconnected before acknowl…
8b98cc5
…edging a view

fix(web): keep the local view fallback working offline
9175d4f

t3dotgg force-pushed the t3code/server-owned-thread-read-state branch from 3626c5c to 9175d4fCompare September 2, 2026 01:52