feat(web): add toggle shortcut for settling threads

[UtkarshUsername]

What Changed

Add shortcut to settle the active thread with default mod+shift+s (when: !terminalFocus). Dispatch in ChatRouteGlobalShortcuts (apps/web/src/routes/_chat.tsx) toggles the active thread using effectiveSettled classification (mirroring Sidebar partition) and calls settleThread/unsettleThread.

Why

Settling a thread had no keyboard shortcut. It was only available via sidebar hover, action menu, and header menu.

Video

settle.mp4

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
Touches thread settlement mutations and VCS-based classification, so a mismatch could settle or un-settle the wrong thread. Scope is a single shortcut path with existing action helpers.

Overview
Adds a thread.settle.toggle shortcut (default mod+shift+s, when the terminal is not focused) so the active thread can be settled or un-settled from the keyboard instead of only via sidebar/header menus.

The chat-route global key handler classifies the active thread with the same effectiveSettled + live VCS PR resolution used by ChatView, then calls settleThread / unsettleThread when the environment supports settlement. Failures surface as stacked error toasts.

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

Note

Add thread.settle.toggle keyboard shortcut bound to mod+shift+s

• Registers the new thread.settle.toggle command in STATIC_KEYBINDING_COMMANDS and maps it to mod+shift+s (when terminal is not focused) in DEFAULT_KEYBINDINGS
• Wires the command in ChatRouteGlobalShortcuts: it resolves the active thread PR via live git status and snapshots, checks the settled state with effectiveSettled, and calls settleThread or unsettleThread accordingly
• The handler issues a VCS status query for the active thread's worktree (or workspace root) to inform settlement classification, and surfaces failures as stacked error toasts
• Behavioral Change: the shortcut only fires when the environment advertises the threadSettlement capability and a route thread with an active shell is present

^{Macroscope summarized ed7f8e4.}

[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: 8bd2fce9-51cb-4775-b85b-4c4aa8f306e2

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

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[macroscopeapp]

Approvability

Verdict: Skipped

Macroscope did not run approvability analysis for this PR. Macroscope could not determine whether this PR modifies its approvability configuration, so the PR was not approved automatically. A PR that may change the rules that govern approval is never approved automatically.

[UtkarshUsername]

Fixed: exclude snoozed threads from isSettled to match Sidebar partition ordering (snoozed outranks settled). Now checks effectiveSnoozed before effectiveSettled - a snoozed thread that also satisfies effectiveSettled will correctly settle instead of being incorrectly unsettled. See 6fe4f8a.

[macroscopeapp]

One finding: the new thread.settle.toggle shortcut classifies the open thread's settled state differently from the two surfaces that display that state for the same thread, so the shortcut can do the opposite of the visible affordance. Details inline on apps/web/src/routes/_chat.tsx.

No styling, primitive, or Tailwind/CSS ownership issues in this diff.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the settle toggle resolves its changeRequest input from a different source than the two surfaces it is documented to match, so the toggle direction can invert relative to what the user sees.

^{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 6742b00. Configure here.}