fix(server): stop large thread history from exhausting memory

[t3dotgg]

Large retained threads can exhaust the server heap when their activity history is hydrated, when the compatibility snapshot endpoint reads every thread body, or when a stale client cursor replays the global event log without a bound.

This keeps initial thread detail to the newest 500 work activities while preserving unresolved approval and user-input requests. It switches project resolution to the lightweight command read model, caps reconnect replay at 1,000 events with a projected snapshot fallback, and stops prewarming hidden sidebar thread details. Web and mobile show a small notice when older work activity is omitted. Messages and checkpoints remain complete.

This intentionally defers older-activity pagination. Based on the server work and investigation in #3510 by @olafura.

Fixes#2761. Addresses #996.

Verification:

• 278 focused tests across server, CLI, contracts, web timeline, and sidebar logic
• targeted typechecks for contracts, server, web, and mobile
• targeted lint, formatting, and mobile static checks

Built by gpt-5.6-sol in the Codex harness through T3 Code.

---

Note

High Risk
Changes core projection hydration, snapshot HTTP behavior, and thread WebSocket catch-up—areas that affect memory, reconnect correctness, and whether actionable approvals/user-inputs appear outside the activity window.

Overview
This PR caps memory and reconnect cost for threads with very large activity histories.

Server read model:getThreadDetailById now returns only the latest 500 work activities (plus pinned unresolved approval/user-input rows outside that window) and sets optional hasMoreActivities when older items exist. Messages and checkpoints stay fully loaded.

Compatibility snapshot: The orchestration /snapshot HTTP endpoint and project CLI offline path now use getCommandReadModel() instead of hydrating every thread body.

WebSocket reconnect:subscribeThread bounds event replay to the projection head (max 1,000 events); stale cursors get a fresh thread detail snapshot instead of unbounded readEvents replay.

Clients: Web and mobile show “Earlier work activity not shown” when bounded; the web sidebar stops prewarming hidden thread-detail subscriptions. Contracts add optional hasMoreActivities on thread payloads.

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

Note

Limit thread history to 500 activities to prevent memory exhaustion on large threads

• Thread detail queries in ProjectionSnapshotQuery.ts now window activity to the 500 most recent items, with a hasMoreActivities flag set when older items exist.
• Unresolved pending approvals and user-input requests outside the window are pinned via a separate SQL query so actionable items remain visible.
• WebSocket thread subscriptions in ws.ts now bound catch-up replay to the captured projection head; stale cursors trigger a full snapshot replacement instead of unbounded replay.
• The sidebar no longer prewarms thread detail subscriptions for visible threads — subscriptions are created only on navigation.
• Web and mobile UIs show an 'Earlier work activity not shown' header and suppress the empty-state placeholder when hasMoreActivities is true.
• Behavioral Change: clients on pre-windowing servers will not receive hasMoreActivities and will continue to see full history; the field is optional in the contract for compatibility.

^{Macroscope summarized 1c3bf90.}

[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: 89143f16-ec72-4b85-88a8-7499acda4b8b

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.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a significant runtime behavior change that limits thread activity history to 500 items to prevent memory exhaustion. Users with large threads will see truncated history with an indicator. The change also removes sidebar thread prewarming and adds complex pinned-activity logic to preserve actionable items. Human review recommended due to the user-visible impact.

^{You can customize Macroscope's approvability policy. 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 450b199. Configure here.}

[t3dotgg]

This is slop

[t3dotgg]

Large retained threads can exhaust the server heap when their activity history is hydrated, when the compatibility snapshot endpoint reads every thread body, or when a stale client cursor replays the global event log without a bound.

This keeps initial thread detail to the newest 500 work activities while preserving unresolved approval and user-input requests. It switches project resolution to the lightweight command read model, caps reconnect replay at 1,000 events with a projected snapshot fallback, and stops prewarming hidden sidebar thread details. Web and mobile show a small notice when older work activity is omitted. Messages and checkpoints remain complete.

This intentionally defers older-activity pagination. Based on the server work and investigation in #3510 by @olafura.

Fixes#2761. Addresses #996.

Verification:

• 278 focused tests across server, CLI, contracts, web timeline, and sidebar logic
• targeted typechecks for contracts, server, web, and mobile
• targeted lint, formatting, and mobile static checks

Built by gpt-5.6-sol in the Codex harness through T3 Code.

---

Note

High Risk
Changes core projection hydration, snapshot HTTP behavior, and thread WebSocket catch-up—areas that affect memory, reconnect correctness, and whether actionable approvals/user-inputs appear outside the activity window.

Overview
This PR caps memory and reconnect cost for threads with very large activity histories.

Server read model:getThreadDetailById now returns only the latest 500 work activities (plus pinned unresolved approval/user-input rows outside that window) and sets optional hasMoreActivities when older items exist. Messages and checkpoints stay fully loaded.

Compatibility snapshot: The orchestration /snapshot HTTP endpoint and project CLI offline path now use getCommandReadModel() instead of hydrating every thread body.

WebSocket reconnect:subscribeThread bounds event replay to the projection head (max 1,000 events); stale cursors get a fresh thread detail snapshot instead of unbounded readEvents replay.

Clients: Web and mobile show “Earlier work activity not shown” when bounded; the web sidebar stops prewarming hidden thread-detail subscriptions. Contracts add optional hasMoreActivities on thread payloads.

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

Note

Limit thread history to 500 activities to prevent memory exhaustion on large threads

• Thread detail queries in ProjectionSnapshotQuery.ts now window activity to the 500 most recent items, with a hasMoreActivities flag set when older items exist.
• Unresolved pending approvals and user-input requests outside the window are pinned via a separate SQL query so actionable items remain visible.
• WebSocket thread subscriptions in ws.ts now bound catch-up replay to the captured projection head; stale cursors trigger a full snapshot replacement instead of unbounded replay.
• The sidebar no longer prewarms thread detail subscriptions for visible threads — subscriptions are created only on navigation.
• Web and mobile UIs show an 'Earlier work activity not shown' header and suppress the empty-state placeholder when hasMoreActivities is true.
• Behavioral Change: clients on pre-windowing servers will not receive hasMoreActivities and will continue to see full history; the field is optional in the contract for compatibility.

^{Macroscope summarized 1c3bf90.}

[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: 89143f16-ec72-4b85-88a8-7499acda4b8b

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.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a significant runtime behavior change that limits thread activity history to 500 items to prevent memory exhaustion. Users with large threads will see truncated history with an indicator. The change also removes sidebar thread prewarming and adds complex pinned-activity logic to preserve actionable items. Human review recommended due to the user-visible impact.

^{You can customize Macroscope's approvability policy. 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 450b199. Configure here.}

[t3dotgg]

This is slop

[t3dotgg]

Large retained threads can exhaust the server heap when their activity history is hydrated, when the compatibility snapshot endpoint reads every thread body, or when a stale client cursor replays the global event log without a bound.

This keeps initial thread detail to the newest 500 work activities while preserving unresolved approval and user-input requests. It switches project resolution to the lightweight command read model, caps reconnect replay at 1,000 events with a projected snapshot fallback, and stops prewarming hidden sidebar thread details. Web and mobile show a small notice when older work activity is omitted. Messages and checkpoints remain complete.

This intentionally defers older-activity pagination. Based on the server work and investigation in #3510 by @olafura.

Fixes#2761. Addresses #996.

Verification:

• 278 focused tests across server, CLI, contracts, web timeline, and sidebar logic
• targeted typechecks for contracts, server, web, and mobile
• targeted lint, formatting, and mobile static checks

Built by gpt-5.6-sol in the Codex harness through T3 Code.

---

Note

High Risk
Changes core projection hydration, snapshot HTTP behavior, and thread WebSocket catch-up—areas that affect memory, reconnect correctness, and whether actionable approvals/user-inputs appear outside the activity window.

Overview
This PR caps memory and reconnect cost for threads with very large activity histories.

Server read model:getThreadDetailById now returns only the latest 500 work activities (plus pinned unresolved approval/user-input rows outside that window) and sets optional hasMoreActivities when older items exist. Messages and checkpoints stay fully loaded.

Compatibility snapshot: The orchestration /snapshot HTTP endpoint and project CLI offline path now use getCommandReadModel() instead of hydrating every thread body.

WebSocket reconnect:subscribeThread bounds event replay to the projection head (max 1,000 events); stale cursors get a fresh thread detail snapshot instead of unbounded readEvents replay.

Clients: Web and mobile show “Earlier work activity not shown” when bounded; the web sidebar stops prewarming hidden thread-detail subscriptions. Contracts add optional hasMoreActivities on thread payloads.

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

Note

Limit thread history to 500 activities to prevent memory exhaustion on large threads

• Thread detail queries in ProjectionSnapshotQuery.ts now window activity to the 500 most recent items, with a hasMoreActivities flag set when older items exist.
• Unresolved pending approvals and user-input requests outside the window are pinned via a separate SQL query so actionable items remain visible.
• WebSocket thread subscriptions in ws.ts now bound catch-up replay to the captured projection head; stale cursors trigger a full snapshot replacement instead of unbounded replay.
• The sidebar no longer prewarms thread detail subscriptions for visible threads — subscriptions are created only on navigation.
• Web and mobile UIs show an 'Earlier work activity not shown' header and suppress the empty-state placeholder when hasMoreActivities is true.
• Behavioral Change: clients on pre-windowing servers will not receive hasMoreActivities and will continue to see full history; the field is optional in the contract for compatibility.

^{Macroscope summarized 1c3bf90.}

[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: 89143f16-ec72-4b85-88a8-7499acda4b8b

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.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a significant runtime behavior change that limits thread activity history to 500 items to prevent memory exhaustion. Users with large threads will see truncated history with an indicator. The change also removes sidebar thread prewarming and adds complex pinned-activity logic to preserve actionable items. Human review recommended due to the user-visible impact.

^{You can customize Macroscope's approvability policy. 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 450b199. Configure here.}

[t3dotgg]

This is slop

[t3dotgg]

Large retained threads can exhaust the server heap when their activity history is hydrated, when the compatibility snapshot endpoint reads every thread body, or when a stale client cursor replays the global event log without a bound.

This keeps initial thread detail to the newest 500 work activities while preserving unresolved approval and user-input requests. It switches project resolution to the lightweight command read model, caps reconnect replay at 1,000 events with a projected snapshot fallback, and stops prewarming hidden sidebar thread details. Web and mobile show a small notice when older work activity is omitted. Messages and checkpoints remain complete.

This intentionally defers older-activity pagination. Based on the server work and investigation in #3510 by @olafura.

Fixes#2761. Addresses #996.

Verification:

• 278 focused tests across server, CLI, contracts, web timeline, and sidebar logic
• targeted typechecks for contracts, server, web, and mobile
• targeted lint, formatting, and mobile static checks

Built by gpt-5.6-sol in the Codex harness through T3 Code.

---

Note

High Risk
Changes core projection hydration, snapshot HTTP behavior, and thread WebSocket catch-up—areas that affect memory, reconnect correctness, and whether actionable approvals/user-inputs appear outside the activity window.

Overview
This PR caps memory and reconnect cost for threads with very large activity histories.

Server read model:getThreadDetailById now returns only the latest 500 work activities (plus pinned unresolved approval/user-input rows outside that window) and sets optional hasMoreActivities when older items exist. Messages and checkpoints stay fully loaded.

Compatibility snapshot: The orchestration /snapshot HTTP endpoint and project CLI offline path now use getCommandReadModel() instead of hydrating every thread body.

WebSocket reconnect:subscribeThread bounds event replay to the projection head (max 1,000 events); stale cursors get a fresh thread detail snapshot instead of unbounded readEvents replay.

Clients: Web and mobile show “Earlier work activity not shown” when bounded; the web sidebar stops prewarming hidden thread-detail subscriptions. Contracts add optional hasMoreActivities on thread payloads.

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

Note

Limit thread history to 500 activities to prevent memory exhaustion on large threads

• Thread detail queries in ProjectionSnapshotQuery.ts now window activity to the 500 most recent items, with a hasMoreActivities flag set when older items exist.
• Unresolved pending approvals and user-input requests outside the window are pinned via a separate SQL query so actionable items remain visible.
• WebSocket thread subscriptions in ws.ts now bound catch-up replay to the captured projection head; stale cursors trigger a full snapshot replacement instead of unbounded replay.
• The sidebar no longer prewarms thread detail subscriptions for visible threads — subscriptions are created only on navigation.
• Web and mobile UIs show an 'Earlier work activity not shown' header and suppress the empty-state placeholder when hasMoreActivities is true.
• Behavioral Change: clients on pre-windowing servers will not receive hasMoreActivities and will continue to see full history; the field is optional in the contract for compatibility.

^{Macroscope summarized 1c3bf90.}

[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: 89143f16-ec72-4b85-88a8-7499acda4b8b

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.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a significant runtime behavior change that limits thread activity history to 500 items to prevent memory exhaustion. Users with large threads will see truncated history with an indicator. The change also removes sidebar thread prewarming and adds complex pinned-activity logic to preserve actionable items. Human review recommended due to the user-visible impact.

^{You can customize Macroscope's approvability policy. 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 450b199. Configure here.}

[t3dotgg]

This is slop

[t3dotgg]

Large retained threads can exhaust the server heap when their activity history is hydrated, when the compatibility snapshot endpoint reads every thread body, or when a stale client cursor replays the global event log without a bound.

This keeps initial thread detail to the newest 500 work activities while preserving unresolved approval and user-input requests. It switches project resolution to the lightweight command read model, caps reconnect replay at 1,000 events with a projected snapshot fallback, and stops prewarming hidden sidebar thread details. Web and mobile show a small notice when older work activity is omitted. Messages and checkpoints remain complete.

This intentionally defers older-activity pagination. Based on the server work and investigation in #3510 by @olafura.

Fixes#2761. Addresses #996.

Verification:

• 278 focused tests across server, CLI, contracts, web timeline, and sidebar logic
• targeted typechecks for contracts, server, web, and mobile
• targeted lint, formatting, and mobile static checks

Built by gpt-5.6-sol in the Codex harness through T3 Code.

---

Note

High Risk
Changes core projection hydration, snapshot HTTP behavior, and thread WebSocket catch-up—areas that affect memory, reconnect correctness, and whether actionable approvals/user-inputs appear outside the activity window.

Overview
This PR caps memory and reconnect cost for threads with very large activity histories.

Server read model:getThreadDetailById now returns only the latest 500 work activities (plus pinned unresolved approval/user-input rows outside that window) and sets optional hasMoreActivities when older items exist. Messages and checkpoints stay fully loaded.

Compatibility snapshot: The orchestration /snapshot HTTP endpoint and project CLI offline path now use getCommandReadModel() instead of hydrating every thread body.

WebSocket reconnect:subscribeThread bounds event replay to the projection head (max 1,000 events); stale cursors get a fresh thread detail snapshot instead of unbounded readEvents replay.

Clients: Web and mobile show “Earlier work activity not shown” when bounded; the web sidebar stops prewarming hidden thread-detail subscriptions. Contracts add optional hasMoreActivities on thread payloads.

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

Note

Limit thread history to 500 activities to prevent memory exhaustion on large threads

• Thread detail queries in ProjectionSnapshotQuery.ts now window activity to the 500 most recent items, with a hasMoreActivities flag set when older items exist.
• Unresolved pending approvals and user-input requests outside the window are pinned via a separate SQL query so actionable items remain visible.
• WebSocket thread subscriptions in ws.ts now bound catch-up replay to the captured projection head; stale cursors trigger a full snapshot replacement instead of unbounded replay.
• The sidebar no longer prewarms thread detail subscriptions for visible threads — subscriptions are created only on navigation.
• Web and mobile UIs show an 'Earlier work activity not shown' header and suppress the empty-state placeholder when hasMoreActivities is true.
• Behavioral Change: clients on pre-windowing servers will not receive hasMoreActivities and will continue to see full history; the field is optional in the contract for compatibility.

^{Macroscope summarized 1c3bf90.}

[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: 89143f16-ec72-4b85-88a8-7499acda4b8b

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.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a significant runtime behavior change that limits thread activity history to 500 items to prevent memory exhaustion. Users with large threads will see truncated history with an indicator. The change also removes sidebar thread prewarming and adds complex pinned-activity logic to preserve actionable items. Human review recommended due to the user-visible impact.

^{You can customize Macroscope's approvability policy. 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 450b199. Configure here.}

[t3dotgg]

This is slop

[t3dotgg]

Large retained threads can exhaust the server heap when their activity history is hydrated, when the compatibility snapshot endpoint reads every thread body, or when a stale client cursor replays the global event log without a bound.

This keeps initial thread detail to the newest 500 work activities while preserving unresolved approval and user-input requests. It switches project resolution to the lightweight command read model, caps reconnect replay at 1,000 events with a projected snapshot fallback, and stops prewarming hidden sidebar thread details. Web and mobile show a small notice when older work activity is omitted. Messages and checkpoints remain complete.

This intentionally defers older-activity pagination. Based on the server work and investigation in #3510 by @olafura.

Fixes#2761. Addresses #996.

Verification:

• 278 focused tests across server, CLI, contracts, web timeline, and sidebar logic
• targeted typechecks for contracts, server, web, and mobile
• targeted lint, formatting, and mobile static checks

Built by gpt-5.6-sol in the Codex harness through T3 Code.

---

Note

High Risk
Changes core projection hydration, snapshot HTTP behavior, and thread WebSocket catch-up—areas that affect memory, reconnect correctness, and whether actionable approvals/user-inputs appear outside the activity window.

Overview
This PR caps memory and reconnect cost for threads with very large activity histories.

Server read model:getThreadDetailById now returns only the latest 500 work activities (plus pinned unresolved approval/user-input rows outside that window) and sets optional hasMoreActivities when older items exist. Messages and checkpoints stay fully loaded.

Compatibility snapshot: The orchestration /snapshot HTTP endpoint and project CLI offline path now use getCommandReadModel() instead of hydrating every thread body.

WebSocket reconnect:subscribeThread bounds event replay to the projection head (max 1,000 events); stale cursors get a fresh thread detail snapshot instead of unbounded readEvents replay.

Clients: Web and mobile show “Earlier work activity not shown” when bounded; the web sidebar stops prewarming hidden thread-detail subscriptions. Contracts add optional hasMoreActivities on thread payloads.

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

Note

Limit thread history to 500 activities to prevent memory exhaustion on large threads

• Thread detail queries in ProjectionSnapshotQuery.ts now window activity to the 500 most recent items, with a hasMoreActivities flag set when older items exist.
• Unresolved pending approvals and user-input requests outside the window are pinned via a separate SQL query so actionable items remain visible.
• WebSocket thread subscriptions in ws.ts now bound catch-up replay to the captured projection head; stale cursors trigger a full snapshot replacement instead of unbounded replay.
• The sidebar no longer prewarms thread detail subscriptions for visible threads — subscriptions are created only on navigation.
• Web and mobile UIs show an 'Earlier work activity not shown' header and suppress the empty-state placeholder when hasMoreActivities is true.
• Behavioral Change: clients on pre-windowing servers will not receive hasMoreActivities and will continue to see full history; the field is optional in the contract for compatibility.

^{Macroscope summarized 1c3bf90.}

[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: 89143f16-ec72-4b85-88a8-7499acda4b8b

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.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a significant runtime behavior change that limits thread activity history to 500 items to prevent memory exhaustion. Users with large threads will see truncated history with an indicator. The change also removes sidebar thread prewarming and adds complex pinned-activity logic to preserve actionable items. Human review recommended due to the user-visible impact.

^{You can customize Macroscope's approvability policy. 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 450b199. Configure here.}

[t3dotgg]

This is slop

[t3dotgg]

Large retained threads can exhaust the server heap when their activity history is hydrated, when the compatibility snapshot endpoint reads every thread body, or when a stale client cursor replays the global event log without a bound.

This keeps initial thread detail to the newest 500 work activities while preserving unresolved approval and user-input requests. It switches project resolution to the lightweight command read model, caps reconnect replay at 1,000 events with a projected snapshot fallback, and stops prewarming hidden sidebar thread details. Web and mobile show a small notice when older work activity is omitted. Messages and checkpoints remain complete.

This intentionally defers older-activity pagination. Based on the server work and investigation in #3510 by @olafura.

Fixes#2761. Addresses #996.

Verification:

• 278 focused tests across server, CLI, contracts, web timeline, and sidebar logic
• targeted typechecks for contracts, server, web, and mobile
• targeted lint, formatting, and mobile static checks

Built by gpt-5.6-sol in the Codex harness through T3 Code.

---

Note

High Risk
Changes core projection hydration, snapshot HTTP behavior, and thread WebSocket catch-up—areas that affect memory, reconnect correctness, and whether actionable approvals/user-inputs appear outside the activity window.

Overview
This PR caps memory and reconnect cost for threads with very large activity histories.

Server read model:getThreadDetailById now returns only the latest 500 work activities (plus pinned unresolved approval/user-input rows outside that window) and sets optional hasMoreActivities when older items exist. Messages and checkpoints stay fully loaded.

Compatibility snapshot: The orchestration /snapshot HTTP endpoint and project CLI offline path now use getCommandReadModel() instead of hydrating every thread body.

WebSocket reconnect:subscribeThread bounds event replay to the projection head (max 1,000 events); stale cursors get a fresh thread detail snapshot instead of unbounded readEvents replay.

Clients: Web and mobile show “Earlier work activity not shown” when bounded; the web sidebar stops prewarming hidden thread-detail subscriptions. Contracts add optional hasMoreActivities on thread payloads.

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

Note

Limit thread history to 500 activities to prevent memory exhaustion on large threads

• Thread detail queries in ProjectionSnapshotQuery.ts now window activity to the 500 most recent items, with a hasMoreActivities flag set when older items exist.
• Unresolved pending approvals and user-input requests outside the window are pinned via a separate SQL query so actionable items remain visible.
• WebSocket thread subscriptions in ws.ts now bound catch-up replay to the captured projection head; stale cursors trigger a full snapshot replacement instead of unbounded replay.
• The sidebar no longer prewarms thread detail subscriptions for visible threads — subscriptions are created only on navigation.
• Web and mobile UIs show an 'Earlier work activity not shown' header and suppress the empty-state placeholder when hasMoreActivities is true.
• Behavioral Change: clients on pre-windowing servers will not receive hasMoreActivities and will continue to see full history; the field is optional in the contract for compatibility.

^{Macroscope summarized 1c3bf90.}

[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: 89143f16-ec72-4b85-88a8-7499acda4b8b

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.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a significant runtime behavior change that limits thread activity history to 500 items to prevent memory exhaustion. Users with large threads will see truncated history with an indicator. The change also removes sidebar thread prewarming and adds complex pinned-activity logic to preserve actionable items. Human review recommended due to the user-visible impact.

^{You can customize Macroscope's approvability policy. 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 450b199. Configure here.}

[t3dotgg]

This is slop

[t3dotgg]

Large retained threads can exhaust the server heap when their activity history is hydrated, when the compatibility snapshot endpoint reads every thread body, or when a stale client cursor replays the global event log without a bound.

This keeps initial thread detail to the newest 500 work activities while preserving unresolved approval and user-input requests. It switches project resolution to the lightweight command read model, caps reconnect replay at 1,000 events with a projected snapshot fallback, and stops prewarming hidden sidebar thread details. Web and mobile show a small notice when older work activity is omitted. Messages and checkpoints remain complete.

This intentionally defers older-activity pagination. Based on the server work and investigation in #3510 by @olafura.

Fixes#2761. Addresses #996.

Verification:

• 278 focused tests across server, CLI, contracts, web timeline, and sidebar logic
• targeted typechecks for contracts, server, web, and mobile
• targeted lint, formatting, and mobile static checks

Built by gpt-5.6-sol in the Codex harness through T3 Code.

---

Note

High Risk
Changes core projection hydration, snapshot HTTP behavior, and thread WebSocket catch-up—areas that affect memory, reconnect correctness, and whether actionable approvals/user-inputs appear outside the activity window.

Overview
This PR caps memory and reconnect cost for threads with very large activity histories.

Server read model:getThreadDetailById now returns only the latest 500 work activities (plus pinned unresolved approval/user-input rows outside that window) and sets optional hasMoreActivities when older items exist. Messages and checkpoints stay fully loaded.

Compatibility snapshot: The orchestration /snapshot HTTP endpoint and project CLI offline path now use getCommandReadModel() instead of hydrating every thread body.

WebSocket reconnect:subscribeThread bounds event replay to the projection head (max 1,000 events); stale cursors get a fresh thread detail snapshot instead of unbounded readEvents replay.

Clients: Web and mobile show “Earlier work activity not shown” when bounded; the web sidebar stops prewarming hidden thread-detail subscriptions. Contracts add optional hasMoreActivities on thread payloads.

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

Note

Limit thread history to 500 activities to prevent memory exhaustion on large threads

• Thread detail queries in ProjectionSnapshotQuery.ts now window activity to the 500 most recent items, with a hasMoreActivities flag set when older items exist.
• Unresolved pending approvals and user-input requests outside the window are pinned via a separate SQL query so actionable items remain visible.
• WebSocket thread subscriptions in ws.ts now bound catch-up replay to the captured projection head; stale cursors trigger a full snapshot replacement instead of unbounded replay.
• The sidebar no longer prewarms thread detail subscriptions for visible threads — subscriptions are created only on navigation.
• Web and mobile UIs show an 'Earlier work activity not shown' header and suppress the empty-state placeholder when hasMoreActivities is true.
• Behavioral Change: clients on pre-windowing servers will not receive hasMoreActivities and will continue to see full history; the field is optional in the contract for compatibility.

^{Macroscope summarized 1c3bf90.}

[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: 89143f16-ec72-4b85-88a8-7499acda4b8b

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.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a significant runtime behavior change that limits thread activity history to 500 items to prevent memory exhaustion. Users with large threads will see truncated history with an indicator. The change also removes sidebar thread prewarming and adds complex pinned-activity logic to preserve actionable items. Human review recommended due to the user-visible impact.

^{You can customize Macroscope's approvability policy. 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 450b199. Configure here.}

[t3dotgg]

This is slop