feat(web): let users turn off composer collapse on blur and scroll

[juliusmarminge]

On web and desktop, an existing thread's composer rests into a single line whenever it loses focus or the conversation is scrolled. Some users want it to stay expanded, and there was no way to opt out of either trigger.

A Settings → General → Collapse composer row now offers a multi-select dropdown of On unfocus / On scroll, backed by two client settings (composerCollapseOnBlur, composerCollapseOnScroll). Both default on, so behavior is unchanged unless a user deselects one. The trigger summarises the selection ("On unfocus, On scroll" / "On scroll" / "Never"). With blur collapse off, losing focus never rests the composer; scrolling still does whenever the composer is expanded, focused or not, and lifts on the next composer interaction. With scroll collapse off, the wheel gesture is never eligible. Both off keeps the composer expanded.

The change lives in shouldUseRestingComposerLayout, which now takes the scroll-collapsed flag and the blur preference as separate inputs instead of folding the scroll state into isFocused. The wheel handler used to require editor focus as a proxy for "expanded"; it now keys off the resting state directly, so scroll can rest an unfocused-but-expanded composer. The settings row, search entry, changed-settings list, restore-defaults, and the user docs follow. SelectItem gains an opt-in showCheck so multi-select popups can show every chosen item; single-select callers are untouched.

Settings

Defaults	Open	Neither selected (reset arrow appears)

Before (defaults, unchanged)

Click away from a focused composer → rests into a single line.

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/c3fdd7b5b652ba2d/demo-before.mp4

After

Blur off, scroll on. Clicking away keeps it expanded; scrolling the conversation still rests it.

Click away	Scroll up

Both off. Neither scrolling nor clicking away collapses it.

Scroll up	Click away

Demo: toggling both off in Settings, then typing, scrolling up, and clicking away in a thread. (Recorded with an earlier two-switch layout of the row; the control is now the multi-select dropdown above and the composer behavior is identical.)

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/e76f183fb7494c0c/demo-after.mp4

Surfaces

• Web and desktop share this path. Mobile has its own focus-driven collapse and is unaffected; both new keys are client settings, so they are per-device.
• The Settings → General row, settings search, the changed-settings summary, and Restore defaults all know about the new keys.
• Docs: docs/user/composer.md.

Verification

• vp test run on composerFooterLayout.test.ts, settings.test.ts, DesktopClientSettings.test.ts (111 passing).
• tsgo --noEmit in contracts, web, desktop.
• Manual pass in the web app against a copy of real data for all four setting combinations (screenshots above).

Claude Fable 5 via Claude Code.

🤖 Generated with Claude Code

---

Note

Low Risk
Client-only UI preference with defaults preserving current behavior; scope is composer layout and settings, not auth or data.

Overview
Adds Settings → General → Collapse composer, a multi-select for On unfocus and On scroll, backed by client settings composerCollapseOnBlur and composerCollapseOnScroll (both default on, so existing behavior is unchanged until the user opts out).

Resting layout logic in shouldUseRestingComposerLayout now treats blur and scroll as separate inputs: scroll collapse can rest the composer even while it is focused; with blur collapse off, unfocus alone never rests it. Scroll collapse in ChatComposer respects composerCollapseOnScroll, only runs while the composer is expanded (not already resting), and no longer requires the prompt editor to be focused for wheel gestures.

Also adds settings search/reset/changed-settings wiring, contract decode tests, user docs, and an opt-in showCheck on SelectItem for the multi-select UI.

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

Note

Add user settings to toggle composer collapse on blur and scroll

• Adds composerCollapseOnBlur and composerCollapseOnScroll boolean client settings, both defaulting to true when absent, with independent patch fields in ClientSettingsPatch (settings.ts).
• Adds a searchable General settings multi-select row for choosing unfocus, scroll, both, or neither as collapse triggers (SettingsPanels.tsx).
• Updates shouldUseRestingComposerLayout to honor the new preferences: an existing desktop composer rests when scroll-collapsed (even while focused), and unfocus alone rests only when blur collapse is enabled (composerFooterLayout.ts).
• Adds a showCheck prop to SelectItem so multiple selected options display a check icon (select.tsx).
• Behavioral Change: disabling blur collapse means an unfocused expanded composer no longer rests on its own; it can still rest after an eligible scroll gesture if scroll collapse remains enabled. Disabling scroll collapse clears the scroll-collapsed state.

^{Macroscope summarized 7a0d572.}

[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.6 KiB	13.5 KiB	−39 B (−0.3%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	+2 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.5 KiB	−41 B (−0.6%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	57.0 KiB	−44 B (−0.1%)	66.4 KiB	✅
Codex	Live turn messages	9	8	−1 (−11.1%)	21	✅
Claude	Total thread wire	13.8 KiB	13.5 KiB	−219 B (−1.6%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+7 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.7 KiB	6.5 KiB	−226 B (−3.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	59.3 KiB	57.8 KiB	−1.5 KiB (−2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	8	−2 (−20.0%)	21	✅

Baseline: d5825e1 · PR result: 7a0d572 · 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: 113.8 KiB
• Claude decoded thread snapshot: 114.5 KiB

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

[macroscopeapp]

Approvability

Verdict: Approved at 7a0d572

Macroscope's review found this PR approvable — Adds a client-side, opt-out preference for existing composer-collapse behavior while keeping both triggers enabled by default. Runtime impact is limited to web/desktop layout and settings persistence, with backward-compatible contracts, targeted tests, and no sensitive or deployment-related changes.

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

Dismissing prior approval to re-evaluate 5893781

Dismissing prior approval to re-evaluate 7037198

[github-actions]

Web preview

https://t3code-qedvn2fcf-pinglabs.vercel.app (for 7a0d572)

Open this exact URL — the hosted-app origin is baked in at build time.
Pair a server into it with t3 pair --tailscale, or paste a host + pairing
code under Settings → Connections.

Dismissing prior approval to re-evaluate 81a18d6

Dismissing prior approval to re-evaluate 7a0d572

[juliusmarminge]

On web and desktop, an existing thread's composer rests into a single line whenever it loses focus or the conversation is scrolled. Some users want it to stay expanded, and there was no way to opt out of either trigger.

A Settings → General → Collapse composer row now offers a multi-select dropdown of On unfocus / On scroll, backed by two client settings (composerCollapseOnBlur, composerCollapseOnScroll). Both default on, so behavior is unchanged unless a user deselects one. The trigger summarises the selection ("On unfocus, On scroll" / "On scroll" / "Never"). With blur collapse off, losing focus never rests the composer; scrolling still does whenever the composer is expanded, focused or not, and lifts on the next composer interaction. With scroll collapse off, the wheel gesture is never eligible. Both off keeps the composer expanded.

The change lives in shouldUseRestingComposerLayout, which now takes the scroll-collapsed flag and the blur preference as separate inputs instead of folding the scroll state into isFocused. The wheel handler used to require editor focus as a proxy for "expanded"; it now keys off the resting state directly, so scroll can rest an unfocused-but-expanded composer. The settings row, search entry, changed-settings list, restore-defaults, and the user docs follow. SelectItem gains an opt-in showCheck so multi-select popups can show every chosen item; single-select callers are untouched.

Settings

Defaults	Open	Neither selected (reset arrow appears)

Before (defaults, unchanged)

Click away from a focused composer → rests into a single line.

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/c3fdd7b5b652ba2d/demo-before.mp4

After

Blur off, scroll on. Clicking away keeps it expanded; scrolling the conversation still rests it.

Click away	Scroll up

Both off. Neither scrolling nor clicking away collapses it.

Scroll up	Click away

Demo: toggling both off in Settings, then typing, scrolling up, and clicking away in a thread. (Recorded with an earlier two-switch layout of the row; the control is now the multi-select dropdown above and the composer behavior is identical.)

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/e76f183fb7494c0c/demo-after.mp4

Surfaces

• Web and desktop share this path. Mobile has its own focus-driven collapse and is unaffected; both new keys are client settings, so they are per-device.
• The Settings → General row, settings search, the changed-settings summary, and Restore defaults all know about the new keys.
• Docs: docs/user/composer.md.

Verification

• vp test run on composerFooterLayout.test.ts, settings.test.ts, DesktopClientSettings.test.ts (111 passing).
• tsgo --noEmit in contracts, web, desktop.
• Manual pass in the web app against a copy of real data for all four setting combinations (screenshots above).

Claude Fable 5 via Claude Code.

🤖 Generated with Claude Code

---

Note

Low Risk
Client-only UI preference with defaults preserving current behavior; scope is composer layout and settings, not auth or data.

Overview
Adds Settings → General → Collapse composer, a multi-select for On unfocus and On scroll, backed by client settings composerCollapseOnBlur and composerCollapseOnScroll (both default on, so existing behavior is unchanged until the user opts out).

Resting layout logic in shouldUseRestingComposerLayout now treats blur and scroll as separate inputs: scroll collapse can rest the composer even while it is focused; with blur collapse off, unfocus alone never rests it. Scroll collapse in ChatComposer respects composerCollapseOnScroll, only runs while the composer is expanded (not already resting), and no longer requires the prompt editor to be focused for wheel gestures.

Also adds settings search/reset/changed-settings wiring, contract decode tests, user docs, and an opt-in showCheck on SelectItem for the multi-select UI.

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

Note

Add user settings to toggle composer collapse on blur and scroll

• Adds composerCollapseOnBlur and composerCollapseOnScroll boolean client settings, both defaulting to true when absent, with independent patch fields in ClientSettingsPatch (settings.ts).
• Adds a searchable General settings multi-select row for choosing unfocus, scroll, both, or neither as collapse triggers (SettingsPanels.tsx).
• Updates shouldUseRestingComposerLayout to honor the new preferences: an existing desktop composer rests when scroll-collapsed (even while focused), and unfocus alone rests only when blur collapse is enabled (composerFooterLayout.ts).
• Adds a showCheck prop to SelectItem so multiple selected options display a check icon (select.tsx).
• Behavioral Change: disabling blur collapse means an unfocused expanded composer no longer rests on its own; it can still rest after an eligible scroll gesture if scroll collapse remains enabled. Disabling scroll collapse clears the scroll-collapsed state.

^{Macroscope summarized 7a0d572.}

[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.6 KiB	13.5 KiB	−39 B (−0.3%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	+2 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.5 KiB	−41 B (−0.6%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	57.0 KiB	−44 B (−0.1%)	66.4 KiB	✅
Codex	Live turn messages	9	8	−1 (−11.1%)	21	✅
Claude	Total thread wire	13.8 KiB	13.5 KiB	−219 B (−1.6%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+7 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.7 KiB	6.5 KiB	−226 B (−3.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	59.3 KiB	57.8 KiB	−1.5 KiB (−2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	8	−2 (−20.0%)	21	✅

Baseline: d5825e1 · PR result: 7a0d572 · 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: 113.8 KiB
• Claude decoded thread snapshot: 114.5 KiB

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

[macroscopeapp]

Approvability

Verdict: Approved at 7a0d572

Macroscope's review found this PR approvable — Adds a client-side, opt-out preference for existing composer-collapse behavior while keeping both triggers enabled by default. Runtime impact is limited to web/desktop layout and settings persistence, with backward-compatible contracts, targeted tests, and no sensitive or deployment-related changes.

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

Dismissing prior approval to re-evaluate 5893781

Dismissing prior approval to re-evaluate 7037198

[github-actions]

Web preview

https://t3code-qedvn2fcf-pinglabs.vercel.app (for 7a0d572)

Open this exact URL — the hosted-app origin is baked in at build time.
Pair a server into it with t3 pair --tailscale, or paste a host + pairing
code under Settings → Connections.

Dismissing prior approval to re-evaluate 81a18d6

Dismissing prior approval to re-evaluate 7a0d572

[juliusmarminge]

On web and desktop, an existing thread's composer rests into a single line whenever it loses focus or the conversation is scrolled. Some users want it to stay expanded, and there was no way to opt out of either trigger.

A Settings → General → Collapse composer row now offers a multi-select dropdown of On unfocus / On scroll, backed by two client settings (composerCollapseOnBlur, composerCollapseOnScroll). Both default on, so behavior is unchanged unless a user deselects one. The trigger summarises the selection ("On unfocus, On scroll" / "On scroll" / "Never"). With blur collapse off, losing focus never rests the composer; scrolling still does whenever the composer is expanded, focused or not, and lifts on the next composer interaction. With scroll collapse off, the wheel gesture is never eligible. Both off keeps the composer expanded.

The change lives in shouldUseRestingComposerLayout, which now takes the scroll-collapsed flag and the blur preference as separate inputs instead of folding the scroll state into isFocused. The wheel handler used to require editor focus as a proxy for "expanded"; it now keys off the resting state directly, so scroll can rest an unfocused-but-expanded composer. The settings row, search entry, changed-settings list, restore-defaults, and the user docs follow. SelectItem gains an opt-in showCheck so multi-select popups can show every chosen item; single-select callers are untouched.

Settings

Defaults	Open	Neither selected (reset arrow appears)

Before (defaults, unchanged)

Click away from a focused composer → rests into a single line.

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/c3fdd7b5b652ba2d/demo-before.mp4

After

Blur off, scroll on. Clicking away keeps it expanded; scrolling the conversation still rests it.

Click away	Scroll up

Both off. Neither scrolling nor clicking away collapses it.

Scroll up	Click away

Demo: toggling both off in Settings, then typing, scrolling up, and clicking away in a thread. (Recorded with an earlier two-switch layout of the row; the control is now the multi-select dropdown above and the composer behavior is identical.)

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/e76f183fb7494c0c/demo-after.mp4

Surfaces

• Web and desktop share this path. Mobile has its own focus-driven collapse and is unaffected; both new keys are client settings, so they are per-device.
• The Settings → General row, settings search, the changed-settings summary, and Restore defaults all know about the new keys.
• Docs: docs/user/composer.md.

Verification

• vp test run on composerFooterLayout.test.ts, settings.test.ts, DesktopClientSettings.test.ts (111 passing).
• tsgo --noEmit in contracts, web, desktop.
• Manual pass in the web app against a copy of real data for all four setting combinations (screenshots above).

Claude Fable 5 via Claude Code.

🤖 Generated with Claude Code

---

Note

Low Risk
Client-only UI preference with defaults preserving current behavior; scope is composer layout and settings, not auth or data.

Overview
Adds Settings → General → Collapse composer, a multi-select for On unfocus and On scroll, backed by client settings composerCollapseOnBlur and composerCollapseOnScroll (both default on, so existing behavior is unchanged until the user opts out).

Resting layout logic in shouldUseRestingComposerLayout now treats blur and scroll as separate inputs: scroll collapse can rest the composer even while it is focused; with blur collapse off, unfocus alone never rests it. Scroll collapse in ChatComposer respects composerCollapseOnScroll, only runs while the composer is expanded (not already resting), and no longer requires the prompt editor to be focused for wheel gestures.

Also adds settings search/reset/changed-settings wiring, contract decode tests, user docs, and an opt-in showCheck on SelectItem for the multi-select UI.

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

Note

Add user settings to toggle composer collapse on blur and scroll

• Adds composerCollapseOnBlur and composerCollapseOnScroll boolean client settings, both defaulting to true when absent, with independent patch fields in ClientSettingsPatch (settings.ts).
• Adds a searchable General settings multi-select row for choosing unfocus, scroll, both, or neither as collapse triggers (SettingsPanels.tsx).
• Updates shouldUseRestingComposerLayout to honor the new preferences: an existing desktop composer rests when scroll-collapsed (even while focused), and unfocus alone rests only when blur collapse is enabled (composerFooterLayout.ts).
• Adds a showCheck prop to SelectItem so multiple selected options display a check icon (select.tsx).
• Behavioral Change: disabling blur collapse means an unfocused expanded composer no longer rests on its own; it can still rest after an eligible scroll gesture if scroll collapse remains enabled. Disabling scroll collapse clears the scroll-collapsed state.

^{Macroscope summarized 7a0d572.}

[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.6 KiB	13.5 KiB	−39 B (−0.3%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	+2 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.5 KiB	−41 B (−0.6%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	57.0 KiB	−44 B (−0.1%)	66.4 KiB	✅
Codex	Live turn messages	9	8	−1 (−11.1%)	21	✅
Claude	Total thread wire	13.8 KiB	13.5 KiB	−219 B (−1.6%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+7 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.7 KiB	6.5 KiB	−226 B (−3.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	59.3 KiB	57.8 KiB	−1.5 KiB (−2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	8	−2 (−20.0%)	21	✅

Baseline: d5825e1 · PR result: 7a0d572 · 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: 113.8 KiB
• Claude decoded thread snapshot: 114.5 KiB

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

[macroscopeapp]

Approvability

Verdict: Approved at 7a0d572

Macroscope's review found this PR approvable — Adds a client-side, opt-out preference for existing composer-collapse behavior while keeping both triggers enabled by default. Runtime impact is limited to web/desktop layout and settings persistence, with backward-compatible contracts, targeted tests, and no sensitive or deployment-related changes.

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

Dismissing prior approval to re-evaluate 5893781

Dismissing prior approval to re-evaluate 7037198

[github-actions]

Web preview

https://t3code-qedvn2fcf-pinglabs.vercel.app (for 7a0d572)

Open this exact URL — the hosted-app origin is baked in at build time.
Pair a server into it with t3 pair --tailscale, or paste a host + pairing
code under Settings → Connections.

Dismissing prior approval to re-evaluate 81a18d6

Dismissing prior approval to re-evaluate 7a0d572

[juliusmarminge]

On web and desktop, an existing thread's composer rests into a single line whenever it loses focus or the conversation is scrolled. Some users want it to stay expanded, and there was no way to opt out of either trigger.

A Settings → General → Collapse composer row now offers a multi-select dropdown of On unfocus / On scroll, backed by two client settings (composerCollapseOnBlur, composerCollapseOnScroll). Both default on, so behavior is unchanged unless a user deselects one. The trigger summarises the selection ("On unfocus, On scroll" / "On scroll" / "Never"). With blur collapse off, losing focus never rests the composer; scrolling still does whenever the composer is expanded, focused or not, and lifts on the next composer interaction. With scroll collapse off, the wheel gesture is never eligible. Both off keeps the composer expanded.

The change lives in shouldUseRestingComposerLayout, which now takes the scroll-collapsed flag and the blur preference as separate inputs instead of folding the scroll state into isFocused. The wheel handler used to require editor focus as a proxy for "expanded"; it now keys off the resting state directly, so scroll can rest an unfocused-but-expanded composer. The settings row, search entry, changed-settings list, restore-defaults, and the user docs follow. SelectItem gains an opt-in showCheck so multi-select popups can show every chosen item; single-select callers are untouched.

Settings

Defaults	Open	Neither selected (reset arrow appears)

Before (defaults, unchanged)

Click away from a focused composer → rests into a single line.

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/c3fdd7b5b652ba2d/demo-before.mp4

After

Blur off, scroll on. Clicking away keeps it expanded; scrolling the conversation still rests it.

Click away	Scroll up

Both off. Neither scrolling nor clicking away collapses it.

Scroll up	Click away

Demo: toggling both off in Settings, then typing, scrolling up, and clicking away in a thread. (Recorded with an earlier two-switch layout of the row; the control is now the multi-select dropdown above and the composer behavior is identical.)

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/e76f183fb7494c0c/demo-after.mp4

Surfaces

• Web and desktop share this path. Mobile has its own focus-driven collapse and is unaffected; both new keys are client settings, so they are per-device.
• The Settings → General row, settings search, the changed-settings summary, and Restore defaults all know about the new keys.
• Docs: docs/user/composer.md.

Verification

• vp test run on composerFooterLayout.test.ts, settings.test.ts, DesktopClientSettings.test.ts (111 passing).
• tsgo --noEmit in contracts, web, desktop.
• Manual pass in the web app against a copy of real data for all four setting combinations (screenshots above).

Claude Fable 5 via Claude Code.

🤖 Generated with Claude Code

---

Note

Low Risk
Client-only UI preference with defaults preserving current behavior; scope is composer layout and settings, not auth or data.

Overview
Adds Settings → General → Collapse composer, a multi-select for On unfocus and On scroll, backed by client settings composerCollapseOnBlur and composerCollapseOnScroll (both default on, so existing behavior is unchanged until the user opts out).

Resting layout logic in shouldUseRestingComposerLayout now treats blur and scroll as separate inputs: scroll collapse can rest the composer even while it is focused; with blur collapse off, unfocus alone never rests it. Scroll collapse in ChatComposer respects composerCollapseOnScroll, only runs while the composer is expanded (not already resting), and no longer requires the prompt editor to be focused for wheel gestures.

Also adds settings search/reset/changed-settings wiring, contract decode tests, user docs, and an opt-in showCheck on SelectItem for the multi-select UI.

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

Note

Add user settings to toggle composer collapse on blur and scroll

• Adds composerCollapseOnBlur and composerCollapseOnScroll boolean client settings, both defaulting to true when absent, with independent patch fields in ClientSettingsPatch (settings.ts).
• Adds a searchable General settings multi-select row for choosing unfocus, scroll, both, or neither as collapse triggers (SettingsPanels.tsx).
• Updates shouldUseRestingComposerLayout to honor the new preferences: an existing desktop composer rests when scroll-collapsed (even while focused), and unfocus alone rests only when blur collapse is enabled (composerFooterLayout.ts).
• Adds a showCheck prop to SelectItem so multiple selected options display a check icon (select.tsx).
• Behavioral Change: disabling blur collapse means an unfocused expanded composer no longer rests on its own; it can still rest after an eligible scroll gesture if scroll collapse remains enabled. Disabling scroll collapse clears the scroll-collapsed state.

^{Macroscope summarized 7a0d572.}

[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.6 KiB	13.5 KiB	−39 B (−0.3%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	+2 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.5 KiB	−41 B (−0.6%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	57.0 KiB	−44 B (−0.1%)	66.4 KiB	✅
Codex	Live turn messages	9	8	−1 (−11.1%)	21	✅
Claude	Total thread wire	13.8 KiB	13.5 KiB	−219 B (−1.6%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+7 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.7 KiB	6.5 KiB	−226 B (−3.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	59.3 KiB	57.8 KiB	−1.5 KiB (−2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	8	−2 (−20.0%)	21	✅

Baseline: d5825e1 · PR result: 7a0d572 · 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: 113.8 KiB
• Claude decoded thread snapshot: 114.5 KiB

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

[macroscopeapp]

Approvability

Verdict: Approved at 7a0d572

Macroscope's review found this PR approvable — Adds a client-side, opt-out preference for existing composer-collapse behavior while keeping both triggers enabled by default. Runtime impact is limited to web/desktop layout and settings persistence, with backward-compatible contracts, targeted tests, and no sensitive or deployment-related changes.

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

Dismissing prior approval to re-evaluate 5893781

Dismissing prior approval to re-evaluate 7037198

[github-actions]

Web preview

https://t3code-qedvn2fcf-pinglabs.vercel.app (for 7a0d572)

Open this exact URL — the hosted-app origin is baked in at build time.
Pair a server into it with t3 pair --tailscale, or paste a host + pairing
code under Settings → Connections.

Dismissing prior approval to re-evaluate 81a18d6

Dismissing prior approval to re-evaluate 7a0d572

[juliusmarminge]

On web and desktop, an existing thread's composer rests into a single line whenever it loses focus or the conversation is scrolled. Some users want it to stay expanded, and there was no way to opt out of either trigger.

A Settings → General → Collapse composer row now offers a multi-select dropdown of On unfocus / On scroll, backed by two client settings (composerCollapseOnBlur, composerCollapseOnScroll). Both default on, so behavior is unchanged unless a user deselects one. The trigger summarises the selection ("On unfocus, On scroll" / "On scroll" / "Never"). With blur collapse off, losing focus never rests the composer; scrolling still does whenever the composer is expanded, focused or not, and lifts on the next composer interaction. With scroll collapse off, the wheel gesture is never eligible. Both off keeps the composer expanded.

The change lives in shouldUseRestingComposerLayout, which now takes the scroll-collapsed flag and the blur preference as separate inputs instead of folding the scroll state into isFocused. The wheel handler used to require editor focus as a proxy for "expanded"; it now keys off the resting state directly, so scroll can rest an unfocused-but-expanded composer. The settings row, search entry, changed-settings list, restore-defaults, and the user docs follow. SelectItem gains an opt-in showCheck so multi-select popups can show every chosen item; single-select callers are untouched.

Settings

Defaults	Open	Neither selected (reset arrow appears)

Before (defaults, unchanged)

Click away from a focused composer → rests into a single line.

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/c3fdd7b5b652ba2d/demo-before.mp4

After

Blur off, scroll on. Clicking away keeps it expanded; scrolling the conversation still rests it.

Click away	Scroll up

Both off. Neither scrolling nor clicking away collapses it.

Scroll up	Click away

Demo: toggling both off in Settings, then typing, scrolling up, and clicking away in a thread. (Recorded with an earlier two-switch layout of the row; the control is now the multi-select dropdown above and the composer behavior is identical.)

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/e76f183fb7494c0c/demo-after.mp4

Surfaces

• Web and desktop share this path. Mobile has its own focus-driven collapse and is unaffected; both new keys are client settings, so they are per-device.
• The Settings → General row, settings search, the changed-settings summary, and Restore defaults all know about the new keys.
• Docs: docs/user/composer.md.

Verification

• vp test run on composerFooterLayout.test.ts, settings.test.ts, DesktopClientSettings.test.ts (111 passing).
• tsgo --noEmit in contracts, web, desktop.
• Manual pass in the web app against a copy of real data for all four setting combinations (screenshots above).

Claude Fable 5 via Claude Code.

🤖 Generated with Claude Code

---

Note

Low Risk
Client-only UI preference with defaults preserving current behavior; scope is composer layout and settings, not auth or data.

Overview
Adds Settings → General → Collapse composer, a multi-select for On unfocus and On scroll, backed by client settings composerCollapseOnBlur and composerCollapseOnScroll (both default on, so existing behavior is unchanged until the user opts out).

Resting layout logic in shouldUseRestingComposerLayout now treats blur and scroll as separate inputs: scroll collapse can rest the composer even while it is focused; with blur collapse off, unfocus alone never rests it. Scroll collapse in ChatComposer respects composerCollapseOnScroll, only runs while the composer is expanded (not already resting), and no longer requires the prompt editor to be focused for wheel gestures.

Also adds settings search/reset/changed-settings wiring, contract decode tests, user docs, and an opt-in showCheck on SelectItem for the multi-select UI.

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

Note

Add user settings to toggle composer collapse on blur and scroll

• Adds composerCollapseOnBlur and composerCollapseOnScroll boolean client settings, both defaulting to true when absent, with independent patch fields in ClientSettingsPatch (settings.ts).
• Adds a searchable General settings multi-select row for choosing unfocus, scroll, both, or neither as collapse triggers (SettingsPanels.tsx).
• Updates shouldUseRestingComposerLayout to honor the new preferences: an existing desktop composer rests when scroll-collapsed (even while focused), and unfocus alone rests only when blur collapse is enabled (composerFooterLayout.ts).
• Adds a showCheck prop to SelectItem so multiple selected options display a check icon (select.tsx).
• Behavioral Change: disabling blur collapse means an unfocused expanded composer no longer rests on its own; it can still rest after an eligible scroll gesture if scroll collapse remains enabled. Disabling scroll collapse clears the scroll-collapsed state.

^{Macroscope summarized 7a0d572.}

[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.6 KiB	13.5 KiB	−39 B (−0.3%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	+2 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.5 KiB	−41 B (−0.6%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	57.0 KiB	−44 B (−0.1%)	66.4 KiB	✅
Codex	Live turn messages	9	8	−1 (−11.1%)	21	✅
Claude	Total thread wire	13.8 KiB	13.5 KiB	−219 B (−1.6%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+7 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.7 KiB	6.5 KiB	−226 B (−3.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	59.3 KiB	57.8 KiB	−1.5 KiB (−2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	8	−2 (−20.0%)	21	✅

Baseline: d5825e1 · PR result: 7a0d572 · 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: 113.8 KiB
• Claude decoded thread snapshot: 114.5 KiB

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

[macroscopeapp]

Approvability

Verdict: Approved at 7a0d572

Macroscope's review found this PR approvable — Adds a client-side, opt-out preference for existing composer-collapse behavior while keeping both triggers enabled by default. Runtime impact is limited to web/desktop layout and settings persistence, with backward-compatible contracts, targeted tests, and no sensitive or deployment-related changes.

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

Dismissing prior approval to re-evaluate 5893781

Dismissing prior approval to re-evaluate 7037198

[github-actions]

Web preview

https://t3code-qedvn2fcf-pinglabs.vercel.app (for 7a0d572)

Open this exact URL — the hosted-app origin is baked in at build time.
Pair a server into it with t3 pair --tailscale, or paste a host + pairing
code under Settings → Connections.

Dismissing prior approval to re-evaluate 81a18d6

Dismissing prior approval to re-evaluate 7a0d572

[juliusmarminge]

On web and desktop, an existing thread's composer rests into a single line whenever it loses focus or the conversation is scrolled. Some users want it to stay expanded, and there was no way to opt out of either trigger.

A Settings → General → Collapse composer row now offers a multi-select dropdown of On unfocus / On scroll, backed by two client settings (composerCollapseOnBlur, composerCollapseOnScroll). Both default on, so behavior is unchanged unless a user deselects one. The trigger summarises the selection ("On unfocus, On scroll" / "On scroll" / "Never"). With blur collapse off, losing focus never rests the composer; scrolling still does whenever the composer is expanded, focused or not, and lifts on the next composer interaction. With scroll collapse off, the wheel gesture is never eligible. Both off keeps the composer expanded.

The change lives in shouldUseRestingComposerLayout, which now takes the scroll-collapsed flag and the blur preference as separate inputs instead of folding the scroll state into isFocused. The wheel handler used to require editor focus as a proxy for "expanded"; it now keys off the resting state directly, so scroll can rest an unfocused-but-expanded composer. The settings row, search entry, changed-settings list, restore-defaults, and the user docs follow. SelectItem gains an opt-in showCheck so multi-select popups can show every chosen item; single-select callers are untouched.

Settings

Defaults	Open	Neither selected (reset arrow appears)

Before (defaults, unchanged)

Click away from a focused composer → rests into a single line.

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/c3fdd7b5b652ba2d/demo-before.mp4

After

Blur off, scroll on. Clicking away keeps it expanded; scrolling the conversation still rests it.

Click away	Scroll up

Both off. Neither scrolling nor clicking away collapses it.

Scroll up	Click away

Demo: toggling both off in Settings, then typing, scrolling up, and clicking away in a thread. (Recorded with an earlier two-switch layout of the row; the control is now the multi-select dropdown above and the composer behavior is identical.)

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/e76f183fb7494c0c/demo-after.mp4

Surfaces

• Web and desktop share this path. Mobile has its own focus-driven collapse and is unaffected; both new keys are client settings, so they are per-device.
• The Settings → General row, settings search, the changed-settings summary, and Restore defaults all know about the new keys.
• Docs: docs/user/composer.md.

Verification

• vp test run on composerFooterLayout.test.ts, settings.test.ts, DesktopClientSettings.test.ts (111 passing).
• tsgo --noEmit in contracts, web, desktop.
• Manual pass in the web app against a copy of real data for all four setting combinations (screenshots above).

Claude Fable 5 via Claude Code.

🤖 Generated with Claude Code

---

Note

Low Risk
Client-only UI preference with defaults preserving current behavior; scope is composer layout and settings, not auth or data.

Overview
Adds Settings → General → Collapse composer, a multi-select for On unfocus and On scroll, backed by client settings composerCollapseOnBlur and composerCollapseOnScroll (both default on, so existing behavior is unchanged until the user opts out).

Resting layout logic in shouldUseRestingComposerLayout now treats blur and scroll as separate inputs: scroll collapse can rest the composer even while it is focused; with blur collapse off, unfocus alone never rests it. Scroll collapse in ChatComposer respects composerCollapseOnScroll, only runs while the composer is expanded (not already resting), and no longer requires the prompt editor to be focused for wheel gestures.

Also adds settings search/reset/changed-settings wiring, contract decode tests, user docs, and an opt-in showCheck on SelectItem for the multi-select UI.

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

Note

Add user settings to toggle composer collapse on blur and scroll

• Adds composerCollapseOnBlur and composerCollapseOnScroll boolean client settings, both defaulting to true when absent, with independent patch fields in ClientSettingsPatch (settings.ts).
• Adds a searchable General settings multi-select row for choosing unfocus, scroll, both, or neither as collapse triggers (SettingsPanels.tsx).
• Updates shouldUseRestingComposerLayout to honor the new preferences: an existing desktop composer rests when scroll-collapsed (even while focused), and unfocus alone rests only when blur collapse is enabled (composerFooterLayout.ts).
• Adds a showCheck prop to SelectItem so multiple selected options display a check icon (select.tsx).
• Behavioral Change: disabling blur collapse means an unfocused expanded composer no longer rests on its own; it can still rest after an eligible scroll gesture if scroll collapse remains enabled. Disabling scroll collapse clears the scroll-collapsed state.

^{Macroscope summarized 7a0d572.}

[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.6 KiB	13.5 KiB	−39 B (−0.3%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	+2 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.5 KiB	−41 B (−0.6%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	57.0 KiB	−44 B (−0.1%)	66.4 KiB	✅
Codex	Live turn messages	9	8	−1 (−11.1%)	21	✅
Claude	Total thread wire	13.8 KiB	13.5 KiB	−219 B (−1.6%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+7 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.7 KiB	6.5 KiB	−226 B (−3.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	59.3 KiB	57.8 KiB	−1.5 KiB (−2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	8	−2 (−20.0%)	21	✅

Baseline: d5825e1 · PR result: 7a0d572 · 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: 113.8 KiB
• Claude decoded thread snapshot: 114.5 KiB

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

[macroscopeapp]

Approvability

Verdict: Approved at 7a0d572

Macroscope's review found this PR approvable — Adds a client-side, opt-out preference for existing composer-collapse behavior while keeping both triggers enabled by default. Runtime impact is limited to web/desktop layout and settings persistence, with backward-compatible contracts, targeted tests, and no sensitive or deployment-related changes.

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

Dismissing prior approval to re-evaluate 5893781

Dismissing prior approval to re-evaluate 7037198

[github-actions]

Web preview

https://t3code-qedvn2fcf-pinglabs.vercel.app (for 7a0d572)

Open this exact URL — the hosted-app origin is baked in at build time.
Pair a server into it with t3 pair --tailscale, or paste a host + pairing
code under Settings → Connections.

Dismissing prior approval to re-evaluate 81a18d6

Dismissing prior approval to re-evaluate 7a0d572

[juliusmarminge]

On web and desktop, an existing thread's composer rests into a single line whenever it loses focus or the conversation is scrolled. Some users want it to stay expanded, and there was no way to opt out of either trigger.

A Settings → General → Collapse composer row now offers a multi-select dropdown of On unfocus / On scroll, backed by two client settings (composerCollapseOnBlur, composerCollapseOnScroll). Both default on, so behavior is unchanged unless a user deselects one. The trigger summarises the selection ("On unfocus, On scroll" / "On scroll" / "Never"). With blur collapse off, losing focus never rests the composer; scrolling still does whenever the composer is expanded, focused or not, and lifts on the next composer interaction. With scroll collapse off, the wheel gesture is never eligible. Both off keeps the composer expanded.

The change lives in shouldUseRestingComposerLayout, which now takes the scroll-collapsed flag and the blur preference as separate inputs instead of folding the scroll state into isFocused. The wheel handler used to require editor focus as a proxy for "expanded"; it now keys off the resting state directly, so scroll can rest an unfocused-but-expanded composer. The settings row, search entry, changed-settings list, restore-defaults, and the user docs follow. SelectItem gains an opt-in showCheck so multi-select popups can show every chosen item; single-select callers are untouched.

Settings

Defaults	Open	Neither selected (reset arrow appears)

Before (defaults, unchanged)

Click away from a focused composer → rests into a single line.

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/c3fdd7b5b652ba2d/demo-before.mp4

After

Blur off, scroll on. Clicking away keeps it expanded; scrolling the conversation still rests it.

Click away	Scroll up

Both off. Neither scrolling nor clicking away collapses it.

Scroll up	Click away

Demo: toggling both off in Settings, then typing, scrolling up, and clicking away in a thread. (Recorded with an earlier two-switch layout of the row; the control is now the multi-select dropdown above and the composer behavior is identical.)

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/e76f183fb7494c0c/demo-after.mp4

Surfaces

• Web and desktop share this path. Mobile has its own focus-driven collapse and is unaffected; both new keys are client settings, so they are per-device.
• The Settings → General row, settings search, the changed-settings summary, and Restore defaults all know about the new keys.
• Docs: docs/user/composer.md.

Verification

• vp test run on composerFooterLayout.test.ts, settings.test.ts, DesktopClientSettings.test.ts (111 passing).
• tsgo --noEmit in contracts, web, desktop.
• Manual pass in the web app against a copy of real data for all four setting combinations (screenshots above).

Claude Fable 5 via Claude Code.

🤖 Generated with Claude Code

---

Note

Low Risk
Client-only UI preference with defaults preserving current behavior; scope is composer layout and settings, not auth or data.

Overview
Adds Settings → General → Collapse composer, a multi-select for On unfocus and On scroll, backed by client settings composerCollapseOnBlur and composerCollapseOnScroll (both default on, so existing behavior is unchanged until the user opts out).

Resting layout logic in shouldUseRestingComposerLayout now treats blur and scroll as separate inputs: scroll collapse can rest the composer even while it is focused; with blur collapse off, unfocus alone never rests it. Scroll collapse in ChatComposer respects composerCollapseOnScroll, only runs while the composer is expanded (not already resting), and no longer requires the prompt editor to be focused for wheel gestures.

Also adds settings search/reset/changed-settings wiring, contract decode tests, user docs, and an opt-in showCheck on SelectItem for the multi-select UI.

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

Note

Add user settings to toggle composer collapse on blur and scroll

• Adds composerCollapseOnBlur and composerCollapseOnScroll boolean client settings, both defaulting to true when absent, with independent patch fields in ClientSettingsPatch (settings.ts).
• Adds a searchable General settings multi-select row for choosing unfocus, scroll, both, or neither as collapse triggers (SettingsPanels.tsx).
• Updates shouldUseRestingComposerLayout to honor the new preferences: an existing desktop composer rests when scroll-collapsed (even while focused), and unfocus alone rests only when blur collapse is enabled (composerFooterLayout.ts).
• Adds a showCheck prop to SelectItem so multiple selected options display a check icon (select.tsx).
• Behavioral Change: disabling blur collapse means an unfocused expanded composer no longer rests on its own; it can still rest after an eligible scroll gesture if scroll collapse remains enabled. Disabling scroll collapse clears the scroll-collapsed state.

^{Macroscope summarized 7a0d572.}

[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.6 KiB	13.5 KiB	−39 B (−0.3%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	+2 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.5 KiB	−41 B (−0.6%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	57.0 KiB	−44 B (−0.1%)	66.4 KiB	✅
Codex	Live turn messages	9	8	−1 (−11.1%)	21	✅
Claude	Total thread wire	13.8 KiB	13.5 KiB	−219 B (−1.6%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+7 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.7 KiB	6.5 KiB	−226 B (−3.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	59.3 KiB	57.8 KiB	−1.5 KiB (−2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	8	−2 (−20.0%)	21	✅

Baseline: d5825e1 · PR result: 7a0d572 · 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: 113.8 KiB
• Claude decoded thread snapshot: 114.5 KiB

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

[macroscopeapp]

Approvability

Verdict: Approved at 7a0d572

Macroscope's review found this PR approvable — Adds a client-side, opt-out preference for existing composer-collapse behavior while keeping both triggers enabled by default. Runtime impact is limited to web/desktop layout and settings persistence, with backward-compatible contracts, targeted tests, and no sensitive or deployment-related changes.

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

Dismissing prior approval to re-evaluate 5893781

Dismissing prior approval to re-evaluate 7037198

[github-actions]

Web preview

https://t3code-qedvn2fcf-pinglabs.vercel.app (for 7a0d572)

Open this exact URL — the hosted-app origin is baked in at build time.
Pair a server into it with t3 pair --tailscale, or paste a host + pairing
code under Settings → Connections.

Dismissing prior approval to re-evaluate 81a18d6

Dismissing prior approval to re-evaluate 7a0d572

[juliusmarminge]

On web and desktop, an existing thread's composer rests into a single line whenever it loses focus or the conversation is scrolled. Some users want it to stay expanded, and there was no way to opt out of either trigger.

A Settings → General → Collapse composer row now offers a multi-select dropdown of On unfocus / On scroll, backed by two client settings (composerCollapseOnBlur, composerCollapseOnScroll). Both default on, so behavior is unchanged unless a user deselects one. The trigger summarises the selection ("On unfocus, On scroll" / "On scroll" / "Never"). With blur collapse off, losing focus never rests the composer; scrolling still does whenever the composer is expanded, focused or not, and lifts on the next composer interaction. With scroll collapse off, the wheel gesture is never eligible. Both off keeps the composer expanded.

The change lives in shouldUseRestingComposerLayout, which now takes the scroll-collapsed flag and the blur preference as separate inputs instead of folding the scroll state into isFocused. The wheel handler used to require editor focus as a proxy for "expanded"; it now keys off the resting state directly, so scroll can rest an unfocused-but-expanded composer. The settings row, search entry, changed-settings list, restore-defaults, and the user docs follow. SelectItem gains an opt-in showCheck so multi-select popups can show every chosen item; single-select callers are untouched.

Settings

Defaults	Open	Neither selected (reset arrow appears)

Before (defaults, unchanged)

Click away from a focused composer → rests into a single line.

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/c3fdd7b5b652ba2d/demo-before.mp4

After

Blur off, scroll on. Clicking away keeps it expanded; scrolling the conversation still rests it.

Click away	Scroll up

Both off. Neither scrolling nor clicking away collapses it.

Scroll up	Click away

Demo: toggling both off in Settings, then typing, scrolling up, and clicking away in a thread. (Recorded with an earlier two-switch layout of the row; the control is now the multi-select dropdown above and the composer behavior is identical.)

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/e76f183fb7494c0c/demo-after.mp4

Surfaces

• Web and desktop share this path. Mobile has its own focus-driven collapse and is unaffected; both new keys are client settings, so they are per-device.
• The Settings → General row, settings search, the changed-settings summary, and Restore defaults all know about the new keys.
• Docs: docs/user/composer.md.

Verification

• vp test run on composerFooterLayout.test.ts, settings.test.ts, DesktopClientSettings.test.ts (111 passing).
• tsgo --noEmit in contracts, web, desktop.
• Manual pass in the web app against a copy of real data for all four setting combinations (screenshots above).

Claude Fable 5 via Claude Code.

🤖 Generated with Claude Code

---

Note

Low Risk
Client-only UI preference with defaults preserving current behavior; scope is composer layout and settings, not auth or data.

Overview
Adds Settings → General → Collapse composer, a multi-select for On unfocus and On scroll, backed by client settings composerCollapseOnBlur and composerCollapseOnScroll (both default on, so existing behavior is unchanged until the user opts out).

Resting layout logic in shouldUseRestingComposerLayout now treats blur and scroll as separate inputs: scroll collapse can rest the composer even while it is focused; with blur collapse off, unfocus alone never rests it. Scroll collapse in ChatComposer respects composerCollapseOnScroll, only runs while the composer is expanded (not already resting), and no longer requires the prompt editor to be focused for wheel gestures.

Also adds settings search/reset/changed-settings wiring, contract decode tests, user docs, and an opt-in showCheck on SelectItem for the multi-select UI.

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

Note

Add user settings to toggle composer collapse on blur and scroll

• Adds composerCollapseOnBlur and composerCollapseOnScroll boolean client settings, both defaulting to true when absent, with independent patch fields in ClientSettingsPatch (settings.ts).
• Adds a searchable General settings multi-select row for choosing unfocus, scroll, both, or neither as collapse triggers (SettingsPanels.tsx).
• Updates shouldUseRestingComposerLayout to honor the new preferences: an existing desktop composer rests when scroll-collapsed (even while focused), and unfocus alone rests only when blur collapse is enabled (composerFooterLayout.ts).
• Adds a showCheck prop to SelectItem so multiple selected options display a check icon (select.tsx).
• Behavioral Change: disabling blur collapse means an unfocused expanded composer no longer rests on its own; it can still rest after an eligible scroll gesture if scroll collapse remains enabled. Disabling scroll collapse clears the scroll-collapsed state.

^{Macroscope summarized 7a0d572.}

[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.6 KiB	13.5 KiB	−39 B (−0.3%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	+2 B (+0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.5 KiB	−41 B (−0.6%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	57.0 KiB	57.0 KiB	−44 B (−0.1%)	66.4 KiB	✅
Codex	Live turn messages	9	8	−1 (−11.1%)	21	✅
Claude	Total thread wire	13.8 KiB	13.5 KiB	−219 B (−1.6%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	+7 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.7 KiB	6.5 KiB	−226 B (−3.3%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	59.3 KiB	57.8 KiB	−1.5 KiB (−2.5%)	66.4 KiB	✅
Claude	Live turn messages	10	8	−2 (−20.0%)	21	✅

Baseline: d5825e1 · PR result: 7a0d572 · 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: 113.8 KiB
• Claude decoded thread snapshot: 114.5 KiB

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

[macroscopeapp]

Approvability

Verdict: Approved at 7a0d572

Macroscope's review found this PR approvable — Adds a client-side, opt-out preference for existing composer-collapse behavior while keeping both triggers enabled by default. Runtime impact is limited to web/desktop layout and settings persistence, with backward-compatible contracts, targeted tests, and no sensitive or deployment-related changes.

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

Dismissing prior approval to re-evaluate 5893781

Dismissing prior approval to re-evaluate 7037198

[github-actions]

Web preview

https://t3code-qedvn2fcf-pinglabs.vercel.app (for 7a0d572)

Open this exact URL — the hosted-app origin is baked in at build time.
Pair a server into it with t3 pair --tailscale, or paste a host + pairing
code under Settings → Connections.

Dismissing prior approval to re-evaluate 81a18d6

Dismissing prior approval to re-evaluate 7a0d572