feat(web): settle and restore threads with a keyboard shortcut

[t3dotgg]

Settling the active thread required pointer-driven sidebar or header actions, and settled threads had no matching keyboard path back.

Add thread.settle with the default shortcut mod+shift+s. The same shortcut settles an active thread or restores a settled thread, respects existing settlement rules, and never intercepts keys while the terminal has focus. The shortcut is configurable through the existing keybinding settings.

Inspired by and with thanks to:

• @effektsvk for #6446
• @jackmhny for #5940
• @UtkarshUsername for #7881
• @colonelpanic8 for #4277
• @jbmcguire for #4876

Verified with 83 focused contract, server, and web tests, targeted lint and formatting, plus scoped typechecks for contracts, shared, client runtime, server, and web.

Model: GPT-5.6 Sol
Harness: Codex in T3 Code

---

Note

Low Risk
Keyboard-only wiring to existing thread settlement APIs with the same guards as pointer actions; no new auth or data paths.

Overview
Adds a thread.settle keybinding (mod+shift+s, disabled when the terminal has focus) across contracts, shared defaults, and server default tests.

ChatView global shortcuts now handle that command: on a settle-capable server thread they call existing settle / unsettle flows (same rules as UI), with an error toast if settle fails.

Web and contracts tests cover resolution and the !terminalFocus guard; user docs describe the new default.

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

Note

Add mod+shift+s keyboard shortcut to settle and restore threads

• Adds the thread.settle command to THREAD_KEYBINDING_COMMANDS in keybindings.ts and maps mod+shift+s to it in the default keybinding set in keybindings.ts
• Wires the shortcut into ChatViewContent in ChatView.tsx: when pressed on an active server thread that supports settlement, it calls settleThread or handleUnsettleActiveThread if already settled, showing a toast on failure
• The shortcut is gated on !terminalFocus so it does not fire inside the terminal
• Documents the new shortcut in keybindings.md
• Risk: the new global keydown branch in ChatViewContent calls preventDefault on mod+shift+s outside the terminal, which could shadow existing browser or app shortcuts bound to that combination

📊 Macroscope summarized e4f0c37. 1 file reviewed, 1 issue evaluated, 1 issue filtered, 0 comments posted

🗂️ Filtered Issues

apps/web/src/components/ChatView.tsx — 0 comments posted, 1 evaluated, 1 filtered

• line 4933: The new thread.settle branch does not enforce the terminal-focus exclusion itself. resolveShortcutCommand accepts bindings with no whenAst (and users can configure a custom binding without !terminalFocus), so when such a binding matches while a terminal owns focus this branch still calls settleThread/handleUnsettleActiveThread after only checking the server/thread guards. This lets a terminal keystroke unexpectedly settle or restore the active thread, contrary to the shortcut's terminal-focus behavior. [ Filtered as negative feedback ]

[coderabbitai]

Important

Review skipped

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

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 835fea9c-0bda-49b5-91b9-87165eb55b3e

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

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.4 KiB	13.4 KiB	+22 B (+0.2%)	15.1 KiB	✅
Codex	Thread snapshot wire	6.9 KiB	6.9 KiB	+6 B (+0.1%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.5 KiB	+16 B (+0.2%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	55.0 KiB	55.0 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	16	16	0 (0.0%)	21	✅
Claude	Total thread wire	13.5 KiB	13.4 KiB	−14 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	6.9 KiB	6.9 KiB	−5 B (−0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.6 KiB	6.5 KiB	−9 B (−0.1%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	55.8 KiB	55.8 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	16	16	0 (0.0%)	21	✅

Baseline: f035a0f · PR result: e4f0c37 · 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]

One finding: the new thread.settle shortcut skips the environment settlement capability gate that every existing settle surface applies, so on a pre-settlement server the keystroke surfaces an error toast instead of doing nothing.

^{Posted via Macroscope — UI Consistency}

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

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This adds a new global keyboard workflow that can settle or restore the active thread and changes the thread lifecycle from the ChatView runtime. The implementation is localized and capability-gated, but the new user-facing behavior warrants human review.

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

[macroscopeapp]

One finding: the new thread.settle shortcut re-derives the active thread's settled state from the sidebar's snapshot map, so its toggle direction can disagree with the settle affordances rendered for the same thread.

^{Posted via Macroscope — UI Consistency}