feat(web): add PageUp/PageDown chat navigation

[Yash-Singh1]

What Changed

• Added PageUp/PageDown keyboard navigation for the chat timeline.
• Added a shared page-scroll controller with focused tests for scroll behavior and boundaries.
• Updated the composer and chat components to coordinate keyboard navigation with the message timeline.
• Removed obsolete environment machine icons, settings, contracts, and related legacy code.

Why

Chat users can now move through long conversations one viewport at a time without relying on the mouse or scrollbar. The scrolling logic is isolated and tested so navigation remains predictable at the start and end of the timeline.

UI Changes

• Added keyboard-driven PageUp/PageDown navigation in the web chat view.
• No screenshots or video included; the interaction is keyboard-based and does not add animation.

Checklist

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

---

Note

Medium Risk
Changes timeline scroll and live-follow opt-out behavior on PageUp; a noted edge case can disable follow without an actual upward scroll when already at the top of an overflowing anchored view.

Overview
Adds keyboard PageUp/PageDown navigation for the message timeline when the chat composer is focused, so users can move through long threads without the mouse.

A new pageScrollController drives the timeline list: one viewport per tap (with easing), hold-to-repeat scrolling that ramps speed, boundary checks, and bottom padding from the composer overlay height. getTimelinePageScrollKey keeps Page keys on the composer while its textarea can still scroll, then hands off to the timeline at the editor edge (including IME/modifier guards).

ChatView mounts the controller on the timeline scroll node and wires key down/up/release from ChatComposer → ComposerPromptEditor. Starting a timeline PageUp scroll can cancel timeline live-follow when content overflows the viewport, matching manual navigation elsewhere.

Unit tests cover composer handoff, scroll distance/velocity, tap vs hold, and boundary no-ops.

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

Note

Add PageUp/PageDown animated timeline scrolling to chat view

• Adds createPageScrollController in pageScrollController.ts to animate tap-page scrolls and delayed, accelerating continuous scrolling when PageUp or PageDown is held. Scrolling stops on key-up, blur, direction change, boundary, or disposal.
• Wires the controller through ChatViewContent → ChatComposer → ComposerPromptEditor so that unmodified PageUp/PageDown presses at a composer scroll boundary are delegated to the timeline, while non-boundary presses keep native composer scrolling. An accepted PageUp also cancels timeline live-follow.
• Page distance is computed from viewport height minus a 36-pixel alignment offset and composer overlay padding. Held scrolling ramps linearly to a 2× multiplier over 400 ms. Boundary requests within a one-pixel tolerance are rejected.
• Risk: getTimelinePageScrollKey classifies which key presses are delegated; if composer scroll-position detection is inaccurate, PageUp/PageDown may be stolen from or inappropriately handed back to the editor. Verify canScrollInDirection against fractional-pixel scroll positions in the target browsers.

^{Macroscope summarized 9bebc8b.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.5 KiB	13.2 KiB	−249 B (−1.8%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	0 B (0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.6 KiB	6.3 KiB	−249 B (−3.7%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	55.5 KiB	−1.5 KiB (−2.6%)	66.4 KiB	✅
Codex	Live turn messages	10	8	−2 (−20.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.5 KiB	+174 B (+1.3%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+8 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.6 KiB	+166 B (+2.5%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	57.8 KiB	+1.4 KiB (+2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 9409dd2 · PR result: 9bebc8b · 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.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a new default chat interaction spanning the composer and timeline, including custom animated scrolling, held-key acceleration, and live-follow coordination. Its production-path behavior and cross-component integration exceed a small self-contained change and merit human review.

^{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 99da696. Configure here.}

[Yash-Singh1]

What Changed

• Added PageUp/PageDown keyboard navigation for the chat timeline.
• Added a shared page-scroll controller with focused tests for scroll behavior and boundaries.
• Updated the composer and chat components to coordinate keyboard navigation with the message timeline.
• Removed obsolete environment machine icons, settings, contracts, and related legacy code.

Why

Chat users can now move through long conversations one viewport at a time without relying on the mouse or scrollbar. The scrolling logic is isolated and tested so navigation remains predictable at the start and end of the timeline.

UI Changes

• Added keyboard-driven PageUp/PageDown navigation in the web chat view.
• No screenshots or video included; the interaction is keyboard-based and does not add animation.

Checklist

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

---

Note

Medium Risk
Changes timeline scroll and live-follow opt-out behavior on PageUp; a noted edge case can disable follow without an actual upward scroll when already at the top of an overflowing anchored view.

Overview
Adds keyboard PageUp/PageDown navigation for the message timeline when the chat composer is focused, so users can move through long threads without the mouse.

A new pageScrollController drives the timeline list: one viewport per tap (with easing), hold-to-repeat scrolling that ramps speed, boundary checks, and bottom padding from the composer overlay height. getTimelinePageScrollKey keeps Page keys on the composer while its textarea can still scroll, then hands off to the timeline at the editor edge (including IME/modifier guards).

ChatView mounts the controller on the timeline scroll node and wires key down/up/release from ChatComposer → ComposerPromptEditor. Starting a timeline PageUp scroll can cancel timeline live-follow when content overflows the viewport, matching manual navigation elsewhere.

Unit tests cover composer handoff, scroll distance/velocity, tap vs hold, and boundary no-ops.

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

Note

Add PageUp/PageDown animated timeline scrolling to chat view

• Adds createPageScrollController in pageScrollController.ts to animate tap-page scrolls and delayed, accelerating continuous scrolling when PageUp or PageDown is held. Scrolling stops on key-up, blur, direction change, boundary, or disposal.
• Wires the controller through ChatViewContent → ChatComposer → ComposerPromptEditor so that unmodified PageUp/PageDown presses at a composer scroll boundary are delegated to the timeline, while non-boundary presses keep native composer scrolling. An accepted PageUp also cancels timeline live-follow.
• Page distance is computed from viewport height minus a 36-pixel alignment offset and composer overlay padding. Held scrolling ramps linearly to a 2× multiplier over 400 ms. Boundary requests within a one-pixel tolerance are rejected.
• Risk: getTimelinePageScrollKey classifies which key presses are delegated; if composer scroll-position detection is inaccurate, PageUp/PageDown may be stolen from or inappropriately handed back to the editor. Verify canScrollInDirection against fractional-pixel scroll positions in the target browsers.

^{Macroscope summarized 9bebc8b.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.5 KiB	13.2 KiB	−249 B (−1.8%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	0 B (0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.6 KiB	6.3 KiB	−249 B (−3.7%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	55.5 KiB	−1.5 KiB (−2.6%)	66.4 KiB	✅
Codex	Live turn messages	10	8	−2 (−20.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.5 KiB	+174 B (+1.3%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+8 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.6 KiB	+166 B (+2.5%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	57.8 KiB	+1.4 KiB (+2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 9409dd2 · PR result: 9bebc8b · 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.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a new default chat interaction spanning the composer and timeline, including custom animated scrolling, held-key acceleration, and live-follow coordination. Its production-path behavior and cross-component integration exceed a small self-contained change and merit human review.

^{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 99da696. Configure here.}

[Yash-Singh1]

What Changed

• Added PageUp/PageDown keyboard navigation for the chat timeline.
• Added a shared page-scroll controller with focused tests for scroll behavior and boundaries.
• Updated the composer and chat components to coordinate keyboard navigation with the message timeline.
• Removed obsolete environment machine icons, settings, contracts, and related legacy code.

Why

Chat users can now move through long conversations one viewport at a time without relying on the mouse or scrollbar. The scrolling logic is isolated and tested so navigation remains predictable at the start and end of the timeline.

UI Changes

• Added keyboard-driven PageUp/PageDown navigation in the web chat view.
• No screenshots or video included; the interaction is keyboard-based and does not add animation.

Checklist

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

---

Note

Medium Risk
Changes timeline scroll and live-follow opt-out behavior on PageUp; a noted edge case can disable follow without an actual upward scroll when already at the top of an overflowing anchored view.

Overview
Adds keyboard PageUp/PageDown navigation for the message timeline when the chat composer is focused, so users can move through long threads without the mouse.

A new pageScrollController drives the timeline list: one viewport per tap (with easing), hold-to-repeat scrolling that ramps speed, boundary checks, and bottom padding from the composer overlay height. getTimelinePageScrollKey keeps Page keys on the composer while its textarea can still scroll, then hands off to the timeline at the editor edge (including IME/modifier guards).

ChatView mounts the controller on the timeline scroll node and wires key down/up/release from ChatComposer → ComposerPromptEditor. Starting a timeline PageUp scroll can cancel timeline live-follow when content overflows the viewport, matching manual navigation elsewhere.

Unit tests cover composer handoff, scroll distance/velocity, tap vs hold, and boundary no-ops.

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

Note

Add PageUp/PageDown animated timeline scrolling to chat view

• Adds createPageScrollController in pageScrollController.ts to animate tap-page scrolls and delayed, accelerating continuous scrolling when PageUp or PageDown is held. Scrolling stops on key-up, blur, direction change, boundary, or disposal.
• Wires the controller through ChatViewContent → ChatComposer → ComposerPromptEditor so that unmodified PageUp/PageDown presses at a composer scroll boundary are delegated to the timeline, while non-boundary presses keep native composer scrolling. An accepted PageUp also cancels timeline live-follow.
• Page distance is computed from viewport height minus a 36-pixel alignment offset and composer overlay padding. Held scrolling ramps linearly to a 2× multiplier over 400 ms. Boundary requests within a one-pixel tolerance are rejected.
• Risk: getTimelinePageScrollKey classifies which key presses are delegated; if composer scroll-position detection is inaccurate, PageUp/PageDown may be stolen from or inappropriately handed back to the editor. Verify canScrollInDirection against fractional-pixel scroll positions in the target browsers.

^{Macroscope summarized 9bebc8b.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.5 KiB	13.2 KiB	−249 B (−1.8%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	0 B (0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.6 KiB	6.3 KiB	−249 B (−3.7%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	55.5 KiB	−1.5 KiB (−2.6%)	66.4 KiB	✅
Codex	Live turn messages	10	8	−2 (−20.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.5 KiB	+174 B (+1.3%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+8 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.6 KiB	+166 B (+2.5%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	57.8 KiB	+1.4 KiB (+2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 9409dd2 · PR result: 9bebc8b · 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.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a new default chat interaction spanning the composer and timeline, including custom animated scrolling, held-key acceleration, and live-follow coordination. Its production-path behavior and cross-component integration exceed a small self-contained change and merit human review.

^{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 99da696. Configure here.}

[Yash-Singh1]

What Changed

• Added PageUp/PageDown keyboard navigation for the chat timeline.
• Added a shared page-scroll controller with focused tests for scroll behavior and boundaries.
• Updated the composer and chat components to coordinate keyboard navigation with the message timeline.
• Removed obsolete environment machine icons, settings, contracts, and related legacy code.

Why

Chat users can now move through long conversations one viewport at a time without relying on the mouse or scrollbar. The scrolling logic is isolated and tested so navigation remains predictable at the start and end of the timeline.

UI Changes

• Added keyboard-driven PageUp/PageDown navigation in the web chat view.
• No screenshots or video included; the interaction is keyboard-based and does not add animation.

Checklist

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

---

Note

Medium Risk
Changes timeline scroll and live-follow opt-out behavior on PageUp; a noted edge case can disable follow without an actual upward scroll when already at the top of an overflowing anchored view.

Overview
Adds keyboard PageUp/PageDown navigation for the message timeline when the chat composer is focused, so users can move through long threads without the mouse.

A new pageScrollController drives the timeline list: one viewport per tap (with easing), hold-to-repeat scrolling that ramps speed, boundary checks, and bottom padding from the composer overlay height. getTimelinePageScrollKey keeps Page keys on the composer while its textarea can still scroll, then hands off to the timeline at the editor edge (including IME/modifier guards).

ChatView mounts the controller on the timeline scroll node and wires key down/up/release from ChatComposer → ComposerPromptEditor. Starting a timeline PageUp scroll can cancel timeline live-follow when content overflows the viewport, matching manual navigation elsewhere.

Unit tests cover composer handoff, scroll distance/velocity, tap vs hold, and boundary no-ops.

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

Note

Add PageUp/PageDown animated timeline scrolling to chat view

• Adds createPageScrollController in pageScrollController.ts to animate tap-page scrolls and delayed, accelerating continuous scrolling when PageUp or PageDown is held. Scrolling stops on key-up, blur, direction change, boundary, or disposal.
• Wires the controller through ChatViewContent → ChatComposer → ComposerPromptEditor so that unmodified PageUp/PageDown presses at a composer scroll boundary are delegated to the timeline, while non-boundary presses keep native composer scrolling. An accepted PageUp also cancels timeline live-follow.
• Page distance is computed from viewport height minus a 36-pixel alignment offset and composer overlay padding. Held scrolling ramps linearly to a 2× multiplier over 400 ms. Boundary requests within a one-pixel tolerance are rejected.
• Risk: getTimelinePageScrollKey classifies which key presses are delegated; if composer scroll-position detection is inaccurate, PageUp/PageDown may be stolen from or inappropriately handed back to the editor. Verify canScrollInDirection against fractional-pixel scroll positions in the target browsers.

^{Macroscope summarized 9bebc8b.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.5 KiB	13.2 KiB	−249 B (−1.8%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	0 B (0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.6 KiB	6.3 KiB	−249 B (−3.7%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	55.5 KiB	−1.5 KiB (−2.6%)	66.4 KiB	✅
Codex	Live turn messages	10	8	−2 (−20.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.5 KiB	+174 B (+1.3%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+8 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.6 KiB	+166 B (+2.5%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	57.8 KiB	+1.4 KiB (+2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 9409dd2 · PR result: 9bebc8b · 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.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a new default chat interaction spanning the composer and timeline, including custom animated scrolling, held-key acceleration, and live-follow coordination. Its production-path behavior and cross-component integration exceed a small self-contained change and merit human review.

^{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 99da696. Configure here.}

[Yash-Singh1]

What Changed

• Added PageUp/PageDown keyboard navigation for the chat timeline.
• Added a shared page-scroll controller with focused tests for scroll behavior and boundaries.
• Updated the composer and chat components to coordinate keyboard navigation with the message timeline.
• Removed obsolete environment machine icons, settings, contracts, and related legacy code.

Why

Chat users can now move through long conversations one viewport at a time without relying on the mouse or scrollbar. The scrolling logic is isolated and tested so navigation remains predictable at the start and end of the timeline.

UI Changes

• Added keyboard-driven PageUp/PageDown navigation in the web chat view.
• No screenshots or video included; the interaction is keyboard-based and does not add animation.

Checklist

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

---

Note

Medium Risk
Changes timeline scroll and live-follow opt-out behavior on PageUp; a noted edge case can disable follow without an actual upward scroll when already at the top of an overflowing anchored view.

Overview
Adds keyboard PageUp/PageDown navigation for the message timeline when the chat composer is focused, so users can move through long threads without the mouse.

A new pageScrollController drives the timeline list: one viewport per tap (with easing), hold-to-repeat scrolling that ramps speed, boundary checks, and bottom padding from the composer overlay height. getTimelinePageScrollKey keeps Page keys on the composer while its textarea can still scroll, then hands off to the timeline at the editor edge (including IME/modifier guards).

ChatView mounts the controller on the timeline scroll node and wires key down/up/release from ChatComposer → ComposerPromptEditor. Starting a timeline PageUp scroll can cancel timeline live-follow when content overflows the viewport, matching manual navigation elsewhere.

Unit tests cover composer handoff, scroll distance/velocity, tap vs hold, and boundary no-ops.

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

Note

Add PageUp/PageDown animated timeline scrolling to chat view

• Adds createPageScrollController in pageScrollController.ts to animate tap-page scrolls and delayed, accelerating continuous scrolling when PageUp or PageDown is held. Scrolling stops on key-up, blur, direction change, boundary, or disposal.
• Wires the controller through ChatViewContent → ChatComposer → ComposerPromptEditor so that unmodified PageUp/PageDown presses at a composer scroll boundary are delegated to the timeline, while non-boundary presses keep native composer scrolling. An accepted PageUp also cancels timeline live-follow.
• Page distance is computed from viewport height minus a 36-pixel alignment offset and composer overlay padding. Held scrolling ramps linearly to a 2× multiplier over 400 ms. Boundary requests within a one-pixel tolerance are rejected.
• Risk: getTimelinePageScrollKey classifies which key presses are delegated; if composer scroll-position detection is inaccurate, PageUp/PageDown may be stolen from or inappropriately handed back to the editor. Verify canScrollInDirection against fractional-pixel scroll positions in the target browsers.

^{Macroscope summarized 9bebc8b.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.5 KiB	13.2 KiB	−249 B (−1.8%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	0 B (0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.6 KiB	6.3 KiB	−249 B (−3.7%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	55.5 KiB	−1.5 KiB (−2.6%)	66.4 KiB	✅
Codex	Live turn messages	10	8	−2 (−20.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.5 KiB	+174 B (+1.3%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+8 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.6 KiB	+166 B (+2.5%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	57.8 KiB	+1.4 KiB (+2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 9409dd2 · PR result: 9bebc8b · 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.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a new default chat interaction spanning the composer and timeline, including custom animated scrolling, held-key acceleration, and live-follow coordination. Its production-path behavior and cross-component integration exceed a small self-contained change and merit human review.

^{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 99da696. Configure here.}

[Yash-Singh1]

What Changed

• Added PageUp/PageDown keyboard navigation for the chat timeline.
• Added a shared page-scroll controller with focused tests for scroll behavior and boundaries.
• Updated the composer and chat components to coordinate keyboard navigation with the message timeline.
• Removed obsolete environment machine icons, settings, contracts, and related legacy code.

Why

Chat users can now move through long conversations one viewport at a time without relying on the mouse or scrollbar. The scrolling logic is isolated and tested so navigation remains predictable at the start and end of the timeline.

UI Changes

• Added keyboard-driven PageUp/PageDown navigation in the web chat view.
• No screenshots or video included; the interaction is keyboard-based and does not add animation.

Checklist

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

---

Note

Medium Risk
Changes timeline scroll and live-follow opt-out behavior on PageUp; a noted edge case can disable follow without an actual upward scroll when already at the top of an overflowing anchored view.

Overview
Adds keyboard PageUp/PageDown navigation for the message timeline when the chat composer is focused, so users can move through long threads without the mouse.

A new pageScrollController drives the timeline list: one viewport per tap (with easing), hold-to-repeat scrolling that ramps speed, boundary checks, and bottom padding from the composer overlay height. getTimelinePageScrollKey keeps Page keys on the composer while its textarea can still scroll, then hands off to the timeline at the editor edge (including IME/modifier guards).

ChatView mounts the controller on the timeline scroll node and wires key down/up/release from ChatComposer → ComposerPromptEditor. Starting a timeline PageUp scroll can cancel timeline live-follow when content overflows the viewport, matching manual navigation elsewhere.

Unit tests cover composer handoff, scroll distance/velocity, tap vs hold, and boundary no-ops.

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

Note

Add PageUp/PageDown animated timeline scrolling to chat view

• Adds createPageScrollController in pageScrollController.ts to animate tap-page scrolls and delayed, accelerating continuous scrolling when PageUp or PageDown is held. Scrolling stops on key-up, blur, direction change, boundary, or disposal.
• Wires the controller through ChatViewContent → ChatComposer → ComposerPromptEditor so that unmodified PageUp/PageDown presses at a composer scroll boundary are delegated to the timeline, while non-boundary presses keep native composer scrolling. An accepted PageUp also cancels timeline live-follow.
• Page distance is computed from viewport height minus a 36-pixel alignment offset and composer overlay padding. Held scrolling ramps linearly to a 2× multiplier over 400 ms. Boundary requests within a one-pixel tolerance are rejected.
• Risk: getTimelinePageScrollKey classifies which key presses are delegated; if composer scroll-position detection is inaccurate, PageUp/PageDown may be stolen from or inappropriately handed back to the editor. Verify canScrollInDirection against fractional-pixel scroll positions in the target browsers.

^{Macroscope summarized 9bebc8b.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.5 KiB	13.2 KiB	−249 B (−1.8%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	0 B (0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.6 KiB	6.3 KiB	−249 B (−3.7%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	55.5 KiB	−1.5 KiB (−2.6%)	66.4 KiB	✅
Codex	Live turn messages	10	8	−2 (−20.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.5 KiB	+174 B (+1.3%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+8 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.6 KiB	+166 B (+2.5%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	57.8 KiB	+1.4 KiB (+2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 9409dd2 · PR result: 9bebc8b · 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.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a new default chat interaction spanning the composer and timeline, including custom animated scrolling, held-key acceleration, and live-follow coordination. Its production-path behavior and cross-component integration exceed a small self-contained change and merit human review.

^{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 99da696. Configure here.}

[Yash-Singh1]

What Changed

• Added PageUp/PageDown keyboard navigation for the chat timeline.
• Added a shared page-scroll controller with focused tests for scroll behavior and boundaries.
• Updated the composer and chat components to coordinate keyboard navigation with the message timeline.
• Removed obsolete environment machine icons, settings, contracts, and related legacy code.

Why

Chat users can now move through long conversations one viewport at a time without relying on the mouse or scrollbar. The scrolling logic is isolated and tested so navigation remains predictable at the start and end of the timeline.

UI Changes

• Added keyboard-driven PageUp/PageDown navigation in the web chat view.
• No screenshots or video included; the interaction is keyboard-based and does not add animation.

Checklist

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

---

Note

Medium Risk
Changes timeline scroll and live-follow opt-out behavior on PageUp; a noted edge case can disable follow without an actual upward scroll when already at the top of an overflowing anchored view.

Overview
Adds keyboard PageUp/PageDown navigation for the message timeline when the chat composer is focused, so users can move through long threads without the mouse.

A new pageScrollController drives the timeline list: one viewport per tap (with easing), hold-to-repeat scrolling that ramps speed, boundary checks, and bottom padding from the composer overlay height. getTimelinePageScrollKey keeps Page keys on the composer while its textarea can still scroll, then hands off to the timeline at the editor edge (including IME/modifier guards).

ChatView mounts the controller on the timeline scroll node and wires key down/up/release from ChatComposer → ComposerPromptEditor. Starting a timeline PageUp scroll can cancel timeline live-follow when content overflows the viewport, matching manual navigation elsewhere.

Unit tests cover composer handoff, scroll distance/velocity, tap vs hold, and boundary no-ops.

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

Note

Add PageUp/PageDown animated timeline scrolling to chat view

• Adds createPageScrollController in pageScrollController.ts to animate tap-page scrolls and delayed, accelerating continuous scrolling when PageUp or PageDown is held. Scrolling stops on key-up, blur, direction change, boundary, or disposal.
• Wires the controller through ChatViewContent → ChatComposer → ComposerPromptEditor so that unmodified PageUp/PageDown presses at a composer scroll boundary are delegated to the timeline, while non-boundary presses keep native composer scrolling. An accepted PageUp also cancels timeline live-follow.
• Page distance is computed from viewport height minus a 36-pixel alignment offset and composer overlay padding. Held scrolling ramps linearly to a 2× multiplier over 400 ms. Boundary requests within a one-pixel tolerance are rejected.
• Risk: getTimelinePageScrollKey classifies which key presses are delegated; if composer scroll-position detection is inaccurate, PageUp/PageDown may be stolen from or inappropriately handed back to the editor. Verify canScrollInDirection against fractional-pixel scroll positions in the target browsers.

^{Macroscope summarized 9bebc8b.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.5 KiB	13.2 KiB	−249 B (−1.8%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	0 B (0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.6 KiB	6.3 KiB	−249 B (−3.7%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	55.5 KiB	−1.5 KiB (−2.6%)	66.4 KiB	✅
Codex	Live turn messages	10	8	−2 (−20.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.5 KiB	+174 B (+1.3%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+8 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.6 KiB	+166 B (+2.5%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	57.8 KiB	+1.4 KiB (+2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 9409dd2 · PR result: 9bebc8b · 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.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a new default chat interaction spanning the composer and timeline, including custom animated scrolling, held-key acceleration, and live-follow coordination. Its production-path behavior and cross-component integration exceed a small self-contained change and merit human review.

^{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 99da696. Configure here.}

[Yash-Singh1]

What Changed

• Added PageUp/PageDown keyboard navigation for the chat timeline.
• Added a shared page-scroll controller with focused tests for scroll behavior and boundaries.
• Updated the composer and chat components to coordinate keyboard navigation with the message timeline.
• Removed obsolete environment machine icons, settings, contracts, and related legacy code.

Why

Chat users can now move through long conversations one viewport at a time without relying on the mouse or scrollbar. The scrolling logic is isolated and tested so navigation remains predictable at the start and end of the timeline.

UI Changes

• Added keyboard-driven PageUp/PageDown navigation in the web chat view.
• No screenshots or video included; the interaction is keyboard-based and does not add animation.

Checklist

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

---

Note

Medium Risk
Changes timeline scroll and live-follow opt-out behavior on PageUp; a noted edge case can disable follow without an actual upward scroll when already at the top of an overflowing anchored view.

Overview
Adds keyboard PageUp/PageDown navigation for the message timeline when the chat composer is focused, so users can move through long threads without the mouse.

A new pageScrollController drives the timeline list: one viewport per tap (with easing), hold-to-repeat scrolling that ramps speed, boundary checks, and bottom padding from the composer overlay height. getTimelinePageScrollKey keeps Page keys on the composer while its textarea can still scroll, then hands off to the timeline at the editor edge (including IME/modifier guards).

ChatView mounts the controller on the timeline scroll node and wires key down/up/release from ChatComposer → ComposerPromptEditor. Starting a timeline PageUp scroll can cancel timeline live-follow when content overflows the viewport, matching manual navigation elsewhere.

Unit tests cover composer handoff, scroll distance/velocity, tap vs hold, and boundary no-ops.

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

Note

Add PageUp/PageDown animated timeline scrolling to chat view

• Adds createPageScrollController in pageScrollController.ts to animate tap-page scrolls and delayed, accelerating continuous scrolling when PageUp or PageDown is held. Scrolling stops on key-up, blur, direction change, boundary, or disposal.
• Wires the controller through ChatViewContent → ChatComposer → ComposerPromptEditor so that unmodified PageUp/PageDown presses at a composer scroll boundary are delegated to the timeline, while non-boundary presses keep native composer scrolling. An accepted PageUp also cancels timeline live-follow.
• Page distance is computed from viewport height minus a 36-pixel alignment offset and composer overlay padding. Held scrolling ramps linearly to a 2× multiplier over 400 ms. Boundary requests within a one-pixel tolerance are rejected.
• Risk: getTimelinePageScrollKey classifies which key presses are delegated; if composer scroll-position detection is inaccurate, PageUp/PageDown may be stolen from or inappropriately handed back to the editor. Verify canScrollInDirection against fractional-pixel scroll positions in the target browsers.

^{Macroscope summarized 9bebc8b.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.5 KiB	13.2 KiB	−249 B (−1.8%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	0 B (0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.6 KiB	6.3 KiB	−249 B (−3.7%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	55.5 KiB	−1.5 KiB (−2.6%)	66.4 KiB	✅
Codex	Live turn messages	10	8	−2 (−20.0%)	21	✅
Claude	Total thread wire	13.3 KiB	13.5 KiB	+174 B (+1.3%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	+8 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.4 KiB	6.6 KiB	+166 B (+2.5%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	56.4 KiB	57.8 KiB	+1.4 KiB (+2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 9409dd2 · PR result: 9bebc8b · 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.4 KiB
• Claude decoded thread snapshot: 110.1 KiB

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a new default chat interaction spanning the composer and timeline, including custom animated scrolling, held-key acceleration, and live-follow coordination. Its production-path behavior and cross-component integration exceed a small self-contained change and merit human review.

^{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 99da696. Configure here.}