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
Mutates thread settlement from a global shortcut using live VCS status and auto-settle settings; a stale or missing git status could toggle the opposite of the visible UI.

Overview
Adds a thread.settle.toggle shortcut (default mod+shift+s, when not in the terminal) so the active thread can be settled or un-settled from the keyboard, matching the banner/header menu.

The chat-route global handler classifies the thread with effectiveSettled using live VCS status plus change-request snapshots, then calls settleThread / unsettleThread. It no-ops without an active thread, on key repeat, or if the environment lacks threadSettlement, and toasts non-interrupted failures.

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

Note

Add thread.settle.toggle shortcut bound to mod+shift+s in chat route

• Registers the new thread.settle.toggle command in keybindings.ts and maps it to mod+shift+s when !terminalFocus in keybindings.ts
• The handler in _chat.tsx resolves the displayed PR against live VCS status and snapshots, computes effectiveSettled with minute-quantized time and auto-settle settings, then calls settleThread or unsettleThread accordingly
• Shows an error toast on non-interrupted command failure; no action when no active thread/shell, command repeats, or the environment lacks threadSettlement capability
• Risk: the handler reads several reactive values (activeThreadShell, gitStatusQuery.data, serverConfigs, auto-settle settings) into the keydown effect's dependency array — stale or missing VCS status data could cause incorrect settle/unsettle decisions

^{Macroscope summarized af57392.}

[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: 5165ec70-43f3-4fc5-a871-e031f5782a83

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: Not approved

Macroscope's review found this PR not approvable — This adds a new global shortcut that performs persistent settle/un-settle mutations and relies on active-thread and PR/VCS state classification. The behavior is focused and reuses existing actions, but its user-facing lifecycle impact warrants human review.

Notes:

• No code objects were reviewed. Approvability was decided on eligibility alone.

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

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

[macroscopeapp]

One finding: the new pending-state fallback makes the settle shortcut classify the open thread differently from the banner and header menu that render its settled state. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the settle-toggle's PR resolution can disagree with the settled state the same thread renders in ChatView's banner and the chat-header menu. Details inline.

^{Posted via Macroscope — UI Consistency}

[UtkarshUsername]

#8089

[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
Mutates thread settlement from a global shortcut using live VCS status and auto-settle settings; a stale or missing git status could toggle the opposite of the visible UI.

Overview
Adds a thread.settle.toggle shortcut (default mod+shift+s, when not in the terminal) so the active thread can be settled or un-settled from the keyboard, matching the banner/header menu.

The chat-route global handler classifies the thread with effectiveSettled using live VCS status plus change-request snapshots, then calls settleThread / unsettleThread. It no-ops without an active thread, on key repeat, or if the environment lacks threadSettlement, and toasts non-interrupted failures.

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

Note

Add thread.settle.toggle shortcut bound to mod+shift+s in chat route

• Registers the new thread.settle.toggle command in keybindings.ts and maps it to mod+shift+s when !terminalFocus in keybindings.ts
• The handler in _chat.tsx resolves the displayed PR against live VCS status and snapshots, computes effectiveSettled with minute-quantized time and auto-settle settings, then calls settleThread or unsettleThread accordingly
• Shows an error toast on non-interrupted command failure; no action when no active thread/shell, command repeats, or the environment lacks threadSettlement capability
• Risk: the handler reads several reactive values (activeThreadShell, gitStatusQuery.data, serverConfigs, auto-settle settings) into the keydown effect's dependency array — stale or missing VCS status data could cause incorrect settle/unsettle decisions

^{Macroscope summarized af57392.}

[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: 5165ec70-43f3-4fc5-a871-e031f5782a83

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: Not approved

Macroscope's review found this PR not approvable — This adds a new global shortcut that performs persistent settle/un-settle mutations and relies on active-thread and PR/VCS state classification. The behavior is focused and reuses existing actions, but its user-facing lifecycle impact warrants human review.

Notes:

• No code objects were reviewed. Approvability was decided on eligibility alone.

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

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

[macroscopeapp]

One finding: the new pending-state fallback makes the settle shortcut classify the open thread differently from the banner and header menu that render its settled state. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the settle-toggle's PR resolution can disagree with the settled state the same thread renders in ChatView's banner and the chat-header menu. Details inline.

^{Posted via Macroscope — UI Consistency}

[UtkarshUsername]

#8089

[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
Mutates thread settlement from a global shortcut using live VCS status and auto-settle settings; a stale or missing git status could toggle the opposite of the visible UI.

Overview
Adds a thread.settle.toggle shortcut (default mod+shift+s, when not in the terminal) so the active thread can be settled or un-settled from the keyboard, matching the banner/header menu.

The chat-route global handler classifies the thread with effectiveSettled using live VCS status plus change-request snapshots, then calls settleThread / unsettleThread. It no-ops without an active thread, on key repeat, or if the environment lacks threadSettlement, and toasts non-interrupted failures.

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

Note

Add thread.settle.toggle shortcut bound to mod+shift+s in chat route

• Registers the new thread.settle.toggle command in keybindings.ts and maps it to mod+shift+s when !terminalFocus in keybindings.ts
• The handler in _chat.tsx resolves the displayed PR against live VCS status and snapshots, computes effectiveSettled with minute-quantized time and auto-settle settings, then calls settleThread or unsettleThread accordingly
• Shows an error toast on non-interrupted command failure; no action when no active thread/shell, command repeats, or the environment lacks threadSettlement capability
• Risk: the handler reads several reactive values (activeThreadShell, gitStatusQuery.data, serverConfigs, auto-settle settings) into the keydown effect's dependency array — stale or missing VCS status data could cause incorrect settle/unsettle decisions

^{Macroscope summarized af57392.}

[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: 5165ec70-43f3-4fc5-a871-e031f5782a83

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: Not approved

Macroscope's review found this PR not approvable — This adds a new global shortcut that performs persistent settle/un-settle mutations and relies on active-thread and PR/VCS state classification. The behavior is focused and reuses existing actions, but its user-facing lifecycle impact warrants human review.

Notes:

• No code objects were reviewed. Approvability was decided on eligibility alone.

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

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

[macroscopeapp]

One finding: the new pending-state fallback makes the settle shortcut classify the open thread differently from the banner and header menu that render its settled state. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the settle-toggle's PR resolution can disagree with the settled state the same thread renders in ChatView's banner and the chat-header menu. Details inline.

^{Posted via Macroscope — UI Consistency}

[UtkarshUsername]

#8089

[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
Mutates thread settlement from a global shortcut using live VCS status and auto-settle settings; a stale or missing git status could toggle the opposite of the visible UI.

Overview
Adds a thread.settle.toggle shortcut (default mod+shift+s, when not in the terminal) so the active thread can be settled or un-settled from the keyboard, matching the banner/header menu.

The chat-route global handler classifies the thread with effectiveSettled using live VCS status plus change-request snapshots, then calls settleThread / unsettleThread. It no-ops without an active thread, on key repeat, or if the environment lacks threadSettlement, and toasts non-interrupted failures.

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

Note

Add thread.settle.toggle shortcut bound to mod+shift+s in chat route

• Registers the new thread.settle.toggle command in keybindings.ts and maps it to mod+shift+s when !terminalFocus in keybindings.ts
• The handler in _chat.tsx resolves the displayed PR against live VCS status and snapshots, computes effectiveSettled with minute-quantized time and auto-settle settings, then calls settleThread or unsettleThread accordingly
• Shows an error toast on non-interrupted command failure; no action when no active thread/shell, command repeats, or the environment lacks threadSettlement capability
• Risk: the handler reads several reactive values (activeThreadShell, gitStatusQuery.data, serverConfigs, auto-settle settings) into the keydown effect's dependency array — stale or missing VCS status data could cause incorrect settle/unsettle decisions

^{Macroscope summarized af57392.}

[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: 5165ec70-43f3-4fc5-a871-e031f5782a83

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: Not approved

Macroscope's review found this PR not approvable — This adds a new global shortcut that performs persistent settle/un-settle mutations and relies on active-thread and PR/VCS state classification. The behavior is focused and reuses existing actions, but its user-facing lifecycle impact warrants human review.

Notes:

• No code objects were reviewed. Approvability was decided on eligibility alone.

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

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

[macroscopeapp]

One finding: the new pending-state fallback makes the settle shortcut classify the open thread differently from the banner and header menu that render its settled state. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the settle-toggle's PR resolution can disagree with the settled state the same thread renders in ChatView's banner and the chat-header menu. Details inline.

^{Posted via Macroscope — UI Consistency}

[UtkarshUsername]

#8089

[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
Mutates thread settlement from a global shortcut using live VCS status and auto-settle settings; a stale or missing git status could toggle the opposite of the visible UI.

Overview
Adds a thread.settle.toggle shortcut (default mod+shift+s, when not in the terminal) so the active thread can be settled or un-settled from the keyboard, matching the banner/header menu.

The chat-route global handler classifies the thread with effectiveSettled using live VCS status plus change-request snapshots, then calls settleThread / unsettleThread. It no-ops without an active thread, on key repeat, or if the environment lacks threadSettlement, and toasts non-interrupted failures.

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

Note

Add thread.settle.toggle shortcut bound to mod+shift+s in chat route

• Registers the new thread.settle.toggle command in keybindings.ts and maps it to mod+shift+s when !terminalFocus in keybindings.ts
• The handler in _chat.tsx resolves the displayed PR against live VCS status and snapshots, computes effectiveSettled with minute-quantized time and auto-settle settings, then calls settleThread or unsettleThread accordingly
• Shows an error toast on non-interrupted command failure; no action when no active thread/shell, command repeats, or the environment lacks threadSettlement capability
• Risk: the handler reads several reactive values (activeThreadShell, gitStatusQuery.data, serverConfigs, auto-settle settings) into the keydown effect's dependency array — stale or missing VCS status data could cause incorrect settle/unsettle decisions

^{Macroscope summarized af57392.}

[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: 5165ec70-43f3-4fc5-a871-e031f5782a83

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: Not approved

Macroscope's review found this PR not approvable — This adds a new global shortcut that performs persistent settle/un-settle mutations and relies on active-thread and PR/VCS state classification. The behavior is focused and reuses existing actions, but its user-facing lifecycle impact warrants human review.

Notes:

• No code objects were reviewed. Approvability was decided on eligibility alone.

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

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

[macroscopeapp]

One finding: the new pending-state fallback makes the settle shortcut classify the open thread differently from the banner and header menu that render its settled state. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the settle-toggle's PR resolution can disagree with the settled state the same thread renders in ChatView's banner and the chat-header menu. Details inline.

^{Posted via Macroscope — UI Consistency}

[UtkarshUsername]

#8089

[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
Mutates thread settlement from a global shortcut using live VCS status and auto-settle settings; a stale or missing git status could toggle the opposite of the visible UI.

Overview
Adds a thread.settle.toggle shortcut (default mod+shift+s, when not in the terminal) so the active thread can be settled or un-settled from the keyboard, matching the banner/header menu.

The chat-route global handler classifies the thread with effectiveSettled using live VCS status plus change-request snapshots, then calls settleThread / unsettleThread. It no-ops without an active thread, on key repeat, or if the environment lacks threadSettlement, and toasts non-interrupted failures.

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

Note

Add thread.settle.toggle shortcut bound to mod+shift+s in chat route

• Registers the new thread.settle.toggle command in keybindings.ts and maps it to mod+shift+s when !terminalFocus in keybindings.ts
• The handler in _chat.tsx resolves the displayed PR against live VCS status and snapshots, computes effectiveSettled with minute-quantized time and auto-settle settings, then calls settleThread or unsettleThread accordingly
• Shows an error toast on non-interrupted command failure; no action when no active thread/shell, command repeats, or the environment lacks threadSettlement capability
• Risk: the handler reads several reactive values (activeThreadShell, gitStatusQuery.data, serverConfigs, auto-settle settings) into the keydown effect's dependency array — stale or missing VCS status data could cause incorrect settle/unsettle decisions

^{Macroscope summarized af57392.}

[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: 5165ec70-43f3-4fc5-a871-e031f5782a83

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: Not approved

Macroscope's review found this PR not approvable — This adds a new global shortcut that performs persistent settle/un-settle mutations and relies on active-thread and PR/VCS state classification. The behavior is focused and reuses existing actions, but its user-facing lifecycle impact warrants human review.

Notes:

• No code objects were reviewed. Approvability was decided on eligibility alone.

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

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

[macroscopeapp]

One finding: the new pending-state fallback makes the settle shortcut classify the open thread differently from the banner and header menu that render its settled state. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the settle-toggle's PR resolution can disagree with the settled state the same thread renders in ChatView's banner and the chat-header menu. Details inline.

^{Posted via Macroscope — UI Consistency}

[UtkarshUsername]

#8089

[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
Mutates thread settlement from a global shortcut using live VCS status and auto-settle settings; a stale or missing git status could toggle the opposite of the visible UI.

Overview
Adds a thread.settle.toggle shortcut (default mod+shift+s, when not in the terminal) so the active thread can be settled or un-settled from the keyboard, matching the banner/header menu.

The chat-route global handler classifies the thread with effectiveSettled using live VCS status plus change-request snapshots, then calls settleThread / unsettleThread. It no-ops without an active thread, on key repeat, or if the environment lacks threadSettlement, and toasts non-interrupted failures.

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

Note

Add thread.settle.toggle shortcut bound to mod+shift+s in chat route

• Registers the new thread.settle.toggle command in keybindings.ts and maps it to mod+shift+s when !terminalFocus in keybindings.ts
• The handler in _chat.tsx resolves the displayed PR against live VCS status and snapshots, computes effectiveSettled with minute-quantized time and auto-settle settings, then calls settleThread or unsettleThread accordingly
• Shows an error toast on non-interrupted command failure; no action when no active thread/shell, command repeats, or the environment lacks threadSettlement capability
• Risk: the handler reads several reactive values (activeThreadShell, gitStatusQuery.data, serverConfigs, auto-settle settings) into the keydown effect's dependency array — stale or missing VCS status data could cause incorrect settle/unsettle decisions

^{Macroscope summarized af57392.}

[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: 5165ec70-43f3-4fc5-a871-e031f5782a83

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: Not approved

Macroscope's review found this PR not approvable — This adds a new global shortcut that performs persistent settle/un-settle mutations and relies on active-thread and PR/VCS state classification. The behavior is focused and reuses existing actions, but its user-facing lifecycle impact warrants human review.

Notes:

• No code objects were reviewed. Approvability was decided on eligibility alone.

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

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

[macroscopeapp]

One finding: the new pending-state fallback makes the settle shortcut classify the open thread differently from the banner and header menu that render its settled state. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the settle-toggle's PR resolution can disagree with the settled state the same thread renders in ChatView's banner and the chat-header menu. Details inline.

^{Posted via Macroscope — UI Consistency}

[UtkarshUsername]

#8089

[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
Mutates thread settlement from a global shortcut using live VCS status and auto-settle settings; a stale or missing git status could toggle the opposite of the visible UI.

Overview
Adds a thread.settle.toggle shortcut (default mod+shift+s, when not in the terminal) so the active thread can be settled or un-settled from the keyboard, matching the banner/header menu.

The chat-route global handler classifies the thread with effectiveSettled using live VCS status plus change-request snapshots, then calls settleThread / unsettleThread. It no-ops without an active thread, on key repeat, or if the environment lacks threadSettlement, and toasts non-interrupted failures.

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

Note

Add thread.settle.toggle shortcut bound to mod+shift+s in chat route

• Registers the new thread.settle.toggle command in keybindings.ts and maps it to mod+shift+s when !terminalFocus in keybindings.ts
• The handler in _chat.tsx resolves the displayed PR against live VCS status and snapshots, computes effectiveSettled with minute-quantized time and auto-settle settings, then calls settleThread or unsettleThread accordingly
• Shows an error toast on non-interrupted command failure; no action when no active thread/shell, command repeats, or the environment lacks threadSettlement capability
• Risk: the handler reads several reactive values (activeThreadShell, gitStatusQuery.data, serverConfigs, auto-settle settings) into the keydown effect's dependency array — stale or missing VCS status data could cause incorrect settle/unsettle decisions

^{Macroscope summarized af57392.}

[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: 5165ec70-43f3-4fc5-a871-e031f5782a83

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: Not approved

Macroscope's review found this PR not approvable — This adds a new global shortcut that performs persistent settle/un-settle mutations and relies on active-thread and PR/VCS state classification. The behavior is focused and reuses existing actions, but its user-facing lifecycle impact warrants human review.

Notes:

• No code objects were reviewed. Approvability was decided on eligibility alone.

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

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

[macroscopeapp]

One finding: the new pending-state fallback makes the settle shortcut classify the open thread differently from the banner and header menu that render its settled state. Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the settle-toggle's PR resolution can disagree with the settled state the same thread renders in ChatView's banner and the chat-header menu. Details inline.

^{Posted via Macroscope — UI Consistency}

[UtkarshUsername]

#8089