Add shortcut to settle the open thread

[colonelpanic8]

What Changed

• add thread.settle as a configurable keybinding command with Mod+Shift+X as the default
• show a confirmation dialog for the open thread before settling
• focus the primary action so Enter confirms, while Escape cancels
• preserve Sidebar V2's existing move-to-next-thread behavior after a successful settle
• document the command and cover default/resolution behavior with tests

Why

Settling the thread currently requires targeting a hover-only sidebar action. A global shortcut makes this frequent lifecycle action available without leaving the keyboard, while the focused confirmation prevents accidental settles and makes the confirmation keystroke explicit.

UI Changes

The shortcut opens an in-app alert dialog naming the thread and explaining that it moves out of active work. The Settle thread button is the initial focus target and displays an Enter key hint; Escape cancels.

Exact-head browser verification completed in an isolated environment against a disposable thread; the focused confirmation state is shown below.

Checklist

• vp check
• vp run typecheck
• vp test apps/web/src/keybindings.test.ts apps/server/src/keybindings.test.ts
• vp run --filter @t3tools/web build

Exact-head evidence

Revalidated at 2d4990a: focused tests, vp check, and vp run typecheck passed. Integrated browser verification confirmed Mod+Shift+X opens the settle dialog from the focused composer while preserving draft text, and Mod+Shift+Enter no longer triggers settlement. The capture uses only disposable local projects.

---

Note

Medium Risk
Touches shared sidebar keyboard routing and post-settle navigation across v1/v2; incorrect eligibility or PR-state reporting could mis-settle threads or navigate to the wrong route.

Overview
Adds thread.settle (mod+shift+x, disabled when the terminal has focus) as a configurable command in defaults, contracts, and docs.

Both Sidebar and SidebarV2 route thread keyboard handling through resolveThreadSidebarShortcutAction, which opens a confirmation dialog for settle, blocks prev/next/jump while that dialog is open, and consumes settle when the route thread cannot be settled or is already settling.

After a confirmed settle, navigation uses resolveNextActiveThreadIdAfterSettle to pick the next non–effectively-settled thread (visible list first, then full unarchived fallback), or starts a new thread when none remain.

Hidden PR/change-request reporters keep settlement state accurate for collapsed, preview-hidden, and off-screen threads via isSidebarThreadEffectivelySettled and shared resolveSidebarThreadGitCwd.

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

Note

Add thread.settle keyboard shortcut with confirmation dialog to sidebar

• Adds mod+shift+x as the default keybinding for thread.settle in both sidebar V1 and V2, triggering a confirmation AlertDialog before settling the current thread.
• After settling, the sidebar navigates to the next active thread (skipping effectively settled ones) using resolveNextActiveThreadIdAfterSettle, preferring visible order with a fallback to full logical order, or starts a new thread if none remain.
• Adds isSidebarThreadEffectivelySettled to classify threads as settled based on server capability, inactivity timing, and PR/change-request state; hidden threads get background PR-state reporters to keep this classification current.
• Adds resolveThreadSidebarShortcutAction to uniformly interpret thread keybinding commands into typed actions (navigate, confirm-settle, consume, none), shared across both sidebars.
• Shortcuts are suppressed while the command palette or model picker is open; the confirmation dialog consumes all thread shortcuts and can be confirmed with Enter.

^{Macroscope summarized 60ff41d.}

[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: aba91b88-e8ec-44cc-bd74-31bec2ab3b6a

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new user-facing feature: a keyboard shortcut (mod+shift+x) to settle threads with a confirmation dialog and auto-navigation to the next active thread. New features with user-facing workflows warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit a6d2a79. Configure here.}