feat(web): add thread.settle keyboard shortcut (mod+shift+s)

[jbmcguire]

What Changed

Adds a thread.settle keybinding command so the active thread can be settled from the keyboard. Default binding is mod+shift+s with when: !terminalFocus.

• packages/contracts/src/keybindings.ts: new thread.settle command in THREAD_KEYBINDING_COMMANDS
• packages/shared/src/keybindings.ts: default mod+shift+s binding (server startup sync distributes it to existing configs)
• apps/web/src/routes/_chat.tsx: global handler dispatches the command for the current route thread via useThreadActions().settleThread, so the existing can-settle guardrails and version-skew checks apply; failures surface with the same toast pattern the sidebar uses, and settling stays on the thread
• Tests: default-binding + shortcut-resolution coverage in apps/web/src/keybindings.test.ts and apps/server/src/keybindings.test.ts
• Docs: docs/user/keybindings.md defaults and command list

The Keybindings settings panel picks the command up automatically (label "Thread: Settle"), and it is rebindable like any other command.

Why

Settling is a high-frequency lifecycle action but was mouse-only (sidebar hover controls). A keyboard shortcut makes triaging threads much faster. mod+shift+s has no conflicts with existing defaults (mod+s remains composer stash) or hardcoded handlers.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes (n/a — no visual change)
• I included a video for animation/interaction changes (n/a)

🤖 Generated with Claude Code

Note

Add thread.settle keyboard shortcut (mod+shift+s) to chat route

• Registers mod+shift+s as the default keybinding for the thread.settle command in packages/shared/src/keybindings.ts, active when the terminal is not focused.
• Adds thread.settle to the ThreadKeybindingCommand type in packages/contracts/src/keybindings.ts.
• Handles the command in apps/web/src/routes/_chat.tsx: calls settleThread on the active thread and shows a 'Failed to settle thread' error toast on non-interrupted failures.

^{Macroscope summarized ac062ed.}

[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: cb9ee101-ff34-4714-8895-614626ff7a36

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: Approved ac062ed

This PR adds a keyboard shortcut to expose existing thread.settle functionality. The implementation follows established patterns in the codebase, includes comprehensive tests, and updates documentation. No new runtime behavior is introduced beyond the keybinding trigger.

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ac062eda38

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Keep new keybinding commands backward-compatible

When a newer server starts, it backfills thread.settle into its persisted defaults and includes that rule in ServerConfig.keybindings; an older desktop/mobile/web client still decodes this field with the previous closed KeybindingCommand literal union, so the unknown command causes initial config decoding to fail and prevents that client from connecting. This affects common remote version-skew scenarios, so the wire decoder needs to tolerate/filter commands unknown to the client, or the server must avoid sending them to older clients.

AGENTS.md reference: AGENTS.md:L19-L21

Useful? React with 👍 / 👎.

[pkelaita]

+1 to this PR, would love to see this feature. Huge for productivity!

[jonalmar]

I would use this daily. A default Command-Shift-S shortcut for settling the active thread would improve my workflow.

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing in favor of merged #8089. It adds the configurable thread.settle shortcut and uses the same shortcut to settle or restore the active thread. Your work is credited in #8089.