Unify the new thread project picker

[colonelpanic8]

Summary

• route every new-thread entry point through one command-palette project picker
• prioritize the project from the current route or thread context
• preserve loading and empty states, Add project, and repeat-shortcut refresh behavior
• remove the duplicate Sidebar V2 picker and its separate keyboard-navigation path

Why

T3 Code originally had two project-picker experiences for starting a thread. The command-palette picker was searchable and already served the Ctrl+K flow, while Ctrl+N and the Sidebar V2 button used a separate sidebar-owned modal. Consolidating them gives every entry point the same interaction and removes duplicate UI and keyboard-navigation code.

PR #4269 landed the basic route into the command palette after this PR opened. That means the current main screenshot below is an intermediate state, while the first screenshot is the real product before-state of the consolidation this PR proposed.

UI comparison

Before: standalone Sidebar V2 dialog

The original new-thread flow used a separate project dialog. It duplicated the Ctrl+K picker and did not support incremental filtering.

Current main after #4269

main now routes into the command palette, but the intermediate picker still shows the new-thread shortcut on every project row and does not include Add project in the same result set.

This PR

This PR keeps the command-palette picker, prioritizes the contextual project, and includes Add project as a keyboard-addressable action.

It also uses the same incremental search behavior as Ctrl+K → New thread in…:

Validation

• web package typecheck
• targeted lint on changed files
• CommandPalette.logic.test.ts and keybindings.test.ts (56 tests)
• isolated end-to-end web verification: Ctrl+N opens the Projects command-palette submenu and selecting a project creates a fresh draft
• compared against Ctrl+K → New thread in… to confirm both entry points render the same picker

Exact-head evidence

Revalidated at 9fb451def031 on current main (9a0a071): focused tests, vp check, and vp run typecheck passed. The capture uses only disposable local projects.

---

Note

Medium Risk
Touches thread-creation entry points, global shortcuts, and command-palette navigation across Sidebar V2 and chat routes; behavior changes for zero-project and multi-project cases but logic is largely extracted and unit-tested.

Overview
Unifies starting a new thread behind a single command-palette project picker instead of mixed sidebar and palette flows.

The palette gains a dedicated new-thread-in view: grouped project rows, Add project always in an Actions group (including the > actions filter), and empty/loading copy via new logic helpers. Opening can pass preferredProjectRef on the event bus; resolution combines that with sidebar project scope and thread/route context through resolveNewThreadPickerProjectRef / resolveScopedNewThreadProjectRef, with scope lifted to a shared sidebarProjectScopeStore.

Sidebar V2 and chat route shortcuts (Ctrl+N / chat.new) use resolveChatNewShortcutBehavior: multi-project or zero-project Sidebar V2 opens the picker (with preference); single-project still creates immediately and can close an open palette first. chat.new may refresh while the palette is open; other chat shortcuts stay suppressed. The sidebar New thread control is no longer disabled when there are no projects.

Supporting changes: closeCommandPalette on the bus, add-project back-navigation fix when popping views, and removal of per-row chat.new shortcut on picker projects.

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

Note

Unify the new thread project picker in the command palette with scoped project resolution

• Adds a dedicated 'New thread in…' project picker view to the command palette, replacing inline project embedding with a structured group built by buildNewThreadPickerGroups
• The picker resolves an effective preferred project from explicit preference, sidebar scope, or contextual project via resolveNewThreadPickerProjectRef and resolveScopedNewThreadProjectRef
• Clicking 'New thread' in SidebarV2 now opens the project picker when multiple or zero projects exist, passing a preferredProjectRef; the button is no longer disabled with zero projects
• Global chat shortcuts (ChatRouteGlobalShortcuts) suppress unrelated shortcuts while the palette is open and close the palette before immediate thread creation
• Adds closeCommandPalette/onCloseCommandPalette event utilities and a shared sidebarProjectScopeStore for cross-component scope sharing
• Behavioral Change: resolveChatNewShortcutBehavior replaces a simple project-count check with a three-way decision (open-project-picker, create-immediately, dismiss-and-create) affecting keyboard shortcut behavior

^{Macroscope summarized e2550fb.}

Current combined-stack UI evidence (2026-07-24)

Captured from PR head a5e53a9ce55272a331c6ba6443d3601c82363020 on upstream main ece05087a70e94efcd57441337fa1249559362ba, using combined integration 4dd4cef40 and package /nix/store/pf7fjqw8ykkdgayf3ywsbgxxp6wi1m42-t3code-0.0.29-patched-main-20260724.

The animation shows the Sidebar V2 New thread control opening the shared Projects picker, filtering to Atlas API, and Enter creating the new draft in that project. The picker retains Add project and keyboard hints. All names and paths are disposable seed data.

[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: 4e74653d-7ec6-4f05-a6aa-8c7a4e1babfa

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 new user-facing functionality: a unified project picker for new threads with modified keyboard shortcut behavior, new state management, and changed command palette interactions. These feature-level changes to the thread creation workflow warrant human review.

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

[juliusmarminge]

BEFORE/AFTER SCREENSHOTS FOR UI CHANGES

[colonelpanic8]

BEFORE/AFTER SCREENSHOTS FOR UI CHANGES

this just gets rid of a duplicated modal where one version is clearly superior to the other. You really need a screenshot for that?

Dismissing prior approval to re-evaluate 891f36e

Dismissing prior approval to re-evaluate 7df1729

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

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

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

[colonelpanic8]

Summary

• route every new-thread entry point through one command-palette project picker
• prioritize the project from the current route or thread context
• preserve loading and empty states, Add project, and repeat-shortcut refresh behavior
• remove the duplicate Sidebar V2 picker and its separate keyboard-navigation path

Why

T3 Code originally had two project-picker experiences for starting a thread. The command-palette picker was searchable and already served the Ctrl+K flow, while Ctrl+N and the Sidebar V2 button used a separate sidebar-owned modal. Consolidating them gives every entry point the same interaction and removes duplicate UI and keyboard-navigation code.

PR #4269 landed the basic route into the command palette after this PR opened. That means the current main screenshot below is an intermediate state, while the first screenshot is the real product before-state of the consolidation this PR proposed.

UI comparison

Before: standalone Sidebar V2 dialog

The original new-thread flow used a separate project dialog. It duplicated the Ctrl+K picker and did not support incremental filtering.

Current main after #4269

main now routes into the command palette, but the intermediate picker still shows the new-thread shortcut on every project row and does not include Add project in the same result set.

This PR

This PR keeps the command-palette picker, prioritizes the contextual project, and includes Add project as a keyboard-addressable action.

It also uses the same incremental search behavior as Ctrl+K → New thread in…:

Validation

• web package typecheck
• targeted lint on changed files
• CommandPalette.logic.test.ts and keybindings.test.ts (56 tests)
• isolated end-to-end web verification: Ctrl+N opens the Projects command-palette submenu and selecting a project creates a fresh draft
• compared against Ctrl+K → New thread in… to confirm both entry points render the same picker

Exact-head evidence

Revalidated at 9fb451def031 on current main (9a0a071): focused tests, vp check, and vp run typecheck passed. The capture uses only disposable local projects.

---

Note

Medium Risk
Touches thread-creation entry points, global shortcuts, and command-palette navigation across Sidebar V2 and chat routes; behavior changes for zero-project and multi-project cases but logic is largely extracted and unit-tested.

Overview
Unifies starting a new thread behind a single command-palette project picker instead of mixed sidebar and palette flows.

The palette gains a dedicated new-thread-in view: grouped project rows, Add project always in an Actions group (including the > actions filter), and empty/loading copy via new logic helpers. Opening can pass preferredProjectRef on the event bus; resolution combines that with sidebar project scope and thread/route context through resolveNewThreadPickerProjectRef / resolveScopedNewThreadProjectRef, with scope lifted to a shared sidebarProjectScopeStore.

Sidebar V2 and chat route shortcuts (Ctrl+N / chat.new) use resolveChatNewShortcutBehavior: multi-project or zero-project Sidebar V2 opens the picker (with preference); single-project still creates immediately and can close an open palette first. chat.new may refresh while the palette is open; other chat shortcuts stay suppressed. The sidebar New thread control is no longer disabled when there are no projects.

Supporting changes: closeCommandPalette on the bus, add-project back-navigation fix when popping views, and removal of per-row chat.new shortcut on picker projects.

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

Note

Unify the new thread project picker in the command palette with scoped project resolution

• Adds a dedicated 'New thread in…' project picker view to the command palette, replacing inline project embedding with a structured group built by buildNewThreadPickerGroups
• The picker resolves an effective preferred project from explicit preference, sidebar scope, or contextual project via resolveNewThreadPickerProjectRef and resolveScopedNewThreadProjectRef
• Clicking 'New thread' in SidebarV2 now opens the project picker when multiple or zero projects exist, passing a preferredProjectRef; the button is no longer disabled with zero projects
• Global chat shortcuts (ChatRouteGlobalShortcuts) suppress unrelated shortcuts while the palette is open and close the palette before immediate thread creation
• Adds closeCommandPalette/onCloseCommandPalette event utilities and a shared sidebarProjectScopeStore for cross-component scope sharing
• Behavioral Change: resolveChatNewShortcutBehavior replaces a simple project-count check with a three-way decision (open-project-picker, create-immediately, dismiss-and-create) affecting keyboard shortcut behavior

^{Macroscope summarized e2550fb.}

Current combined-stack UI evidence (2026-07-24)

Captured from PR head a5e53a9ce55272a331c6ba6443d3601c82363020 on upstream main ece05087a70e94efcd57441337fa1249559362ba, using combined integration 4dd4cef40 and package /nix/store/pf7fjqw8ykkdgayf3ywsbgxxp6wi1m42-t3code-0.0.29-patched-main-20260724.

The animation shows the Sidebar V2 New thread control opening the shared Projects picker, filtering to Atlas API, and Enter creating the new draft in that project. The picker retains Add project and keyboard hints. All names and paths are disposable seed data.

[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: 4e74653d-7ec6-4f05-a6aa-8c7a4e1babfa

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 new user-facing functionality: a unified project picker for new threads with modified keyboard shortcut behavior, new state management, and changed command palette interactions. These feature-level changes to the thread creation workflow warrant human review.

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

[juliusmarminge]

BEFORE/AFTER SCREENSHOTS FOR UI CHANGES

[colonelpanic8]

BEFORE/AFTER SCREENSHOTS FOR UI CHANGES

this just gets rid of a duplicated modal where one version is clearly superior to the other. You really need a screenshot for that?

Dismissing prior approval to re-evaluate 891f36e

Dismissing prior approval to re-evaluate 7df1729

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

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

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

[colonelpanic8]

Summary

• route every new-thread entry point through one command-palette project picker
• prioritize the project from the current route or thread context
• preserve loading and empty states, Add project, and repeat-shortcut refresh behavior
• remove the duplicate Sidebar V2 picker and its separate keyboard-navigation path

Why

T3 Code originally had two project-picker experiences for starting a thread. The command-palette picker was searchable and already served the Ctrl+K flow, while Ctrl+N and the Sidebar V2 button used a separate sidebar-owned modal. Consolidating them gives every entry point the same interaction and removes duplicate UI and keyboard-navigation code.

PR #4269 landed the basic route into the command palette after this PR opened. That means the current main screenshot below is an intermediate state, while the first screenshot is the real product before-state of the consolidation this PR proposed.

UI comparison

Before: standalone Sidebar V2 dialog

The original new-thread flow used a separate project dialog. It duplicated the Ctrl+K picker and did not support incremental filtering.

Current main after #4269

main now routes into the command palette, but the intermediate picker still shows the new-thread shortcut on every project row and does not include Add project in the same result set.

This PR

This PR keeps the command-palette picker, prioritizes the contextual project, and includes Add project as a keyboard-addressable action.

It also uses the same incremental search behavior as Ctrl+K → New thread in…:

Validation

• web package typecheck
• targeted lint on changed files
• CommandPalette.logic.test.ts and keybindings.test.ts (56 tests)
• isolated end-to-end web verification: Ctrl+N opens the Projects command-palette submenu and selecting a project creates a fresh draft
• compared against Ctrl+K → New thread in… to confirm both entry points render the same picker

Exact-head evidence

Revalidated at 9fb451def031 on current main (9a0a071): focused tests, vp check, and vp run typecheck passed. The capture uses only disposable local projects.

---

Note

Medium Risk
Touches thread-creation entry points, global shortcuts, and command-palette navigation across Sidebar V2 and chat routes; behavior changes for zero-project and multi-project cases but logic is largely extracted and unit-tested.

Overview
Unifies starting a new thread behind a single command-palette project picker instead of mixed sidebar and palette flows.

The palette gains a dedicated new-thread-in view: grouped project rows, Add project always in an Actions group (including the > actions filter), and empty/loading copy via new logic helpers. Opening can pass preferredProjectRef on the event bus; resolution combines that with sidebar project scope and thread/route context through resolveNewThreadPickerProjectRef / resolveScopedNewThreadProjectRef, with scope lifted to a shared sidebarProjectScopeStore.

Sidebar V2 and chat route shortcuts (Ctrl+N / chat.new) use resolveChatNewShortcutBehavior: multi-project or zero-project Sidebar V2 opens the picker (with preference); single-project still creates immediately and can close an open palette first. chat.new may refresh while the palette is open; other chat shortcuts stay suppressed. The sidebar New thread control is no longer disabled when there are no projects.

Supporting changes: closeCommandPalette on the bus, add-project back-navigation fix when popping views, and removal of per-row chat.new shortcut on picker projects.

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

Note

Unify the new thread project picker in the command palette with scoped project resolution

• Adds a dedicated 'New thread in…' project picker view to the command palette, replacing inline project embedding with a structured group built by buildNewThreadPickerGroups
• The picker resolves an effective preferred project from explicit preference, sidebar scope, or contextual project via resolveNewThreadPickerProjectRef and resolveScopedNewThreadProjectRef
• Clicking 'New thread' in SidebarV2 now opens the project picker when multiple or zero projects exist, passing a preferredProjectRef; the button is no longer disabled with zero projects
• Global chat shortcuts (ChatRouteGlobalShortcuts) suppress unrelated shortcuts while the palette is open and close the palette before immediate thread creation
• Adds closeCommandPalette/onCloseCommandPalette event utilities and a shared sidebarProjectScopeStore for cross-component scope sharing
• Behavioral Change: resolveChatNewShortcutBehavior replaces a simple project-count check with a three-way decision (open-project-picker, create-immediately, dismiss-and-create) affecting keyboard shortcut behavior

^{Macroscope summarized e2550fb.}

Current combined-stack UI evidence (2026-07-24)

Captured from PR head a5e53a9ce55272a331c6ba6443d3601c82363020 on upstream main ece05087a70e94efcd57441337fa1249559362ba, using combined integration 4dd4cef40 and package /nix/store/pf7fjqw8ykkdgayf3ywsbgxxp6wi1m42-t3code-0.0.29-patched-main-20260724.

The animation shows the Sidebar V2 New thread control opening the shared Projects picker, filtering to Atlas API, and Enter creating the new draft in that project. The picker retains Add project and keyboard hints. All names and paths are disposable seed data.

[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: 4e74653d-7ec6-4f05-a6aa-8c7a4e1babfa

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 new user-facing functionality: a unified project picker for new threads with modified keyboard shortcut behavior, new state management, and changed command palette interactions. These feature-level changes to the thread creation workflow warrant human review.

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

[juliusmarminge]

BEFORE/AFTER SCREENSHOTS FOR UI CHANGES

[colonelpanic8]

BEFORE/AFTER SCREENSHOTS FOR UI CHANGES

this just gets rid of a duplicated modal where one version is clearly superior to the other. You really need a screenshot for that?

Dismissing prior approval to re-evaluate 891f36e

Dismissing prior approval to re-evaluate 7df1729

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

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

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

[colonelpanic8]

Summary

• route every new-thread entry point through one command-palette project picker
• prioritize the project from the current route or thread context
• preserve loading and empty states, Add project, and repeat-shortcut refresh behavior
• remove the duplicate Sidebar V2 picker and its separate keyboard-navigation path

Why

T3 Code originally had two project-picker experiences for starting a thread. The command-palette picker was searchable and already served the Ctrl+K flow, while Ctrl+N and the Sidebar V2 button used a separate sidebar-owned modal. Consolidating them gives every entry point the same interaction and removes duplicate UI and keyboard-navigation code.

PR #4269 landed the basic route into the command palette after this PR opened. That means the current main screenshot below is an intermediate state, while the first screenshot is the real product before-state of the consolidation this PR proposed.

UI comparison

Before: standalone Sidebar V2 dialog

The original new-thread flow used a separate project dialog. It duplicated the Ctrl+K picker and did not support incremental filtering.

Current main after #4269

main now routes into the command palette, but the intermediate picker still shows the new-thread shortcut on every project row and does not include Add project in the same result set.

This PR

This PR keeps the command-palette picker, prioritizes the contextual project, and includes Add project as a keyboard-addressable action.

It also uses the same incremental search behavior as Ctrl+K → New thread in…:

Validation

• web package typecheck
• targeted lint on changed files
• CommandPalette.logic.test.ts and keybindings.test.ts (56 tests)
• isolated end-to-end web verification: Ctrl+N opens the Projects command-palette submenu and selecting a project creates a fresh draft
• compared against Ctrl+K → New thread in… to confirm both entry points render the same picker

Exact-head evidence

Revalidated at 9fb451def031 on current main (9a0a071): focused tests, vp check, and vp run typecheck passed. The capture uses only disposable local projects.

---

Note

Medium Risk
Touches thread-creation entry points, global shortcuts, and command-palette navigation across Sidebar V2 and chat routes; behavior changes for zero-project and multi-project cases but logic is largely extracted and unit-tested.

Overview
Unifies starting a new thread behind a single command-palette project picker instead of mixed sidebar and palette flows.

The palette gains a dedicated new-thread-in view: grouped project rows, Add project always in an Actions group (including the > actions filter), and empty/loading copy via new logic helpers. Opening can pass preferredProjectRef on the event bus; resolution combines that with sidebar project scope and thread/route context through resolveNewThreadPickerProjectRef / resolveScopedNewThreadProjectRef, with scope lifted to a shared sidebarProjectScopeStore.

Sidebar V2 and chat route shortcuts (Ctrl+N / chat.new) use resolveChatNewShortcutBehavior: multi-project or zero-project Sidebar V2 opens the picker (with preference); single-project still creates immediately and can close an open palette first. chat.new may refresh while the palette is open; other chat shortcuts stay suppressed. The sidebar New thread control is no longer disabled when there are no projects.

Supporting changes: closeCommandPalette on the bus, add-project back-navigation fix when popping views, and removal of per-row chat.new shortcut on picker projects.

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

Note

Unify the new thread project picker in the command palette with scoped project resolution

• Adds a dedicated 'New thread in…' project picker view to the command palette, replacing inline project embedding with a structured group built by buildNewThreadPickerGroups
• The picker resolves an effective preferred project from explicit preference, sidebar scope, or contextual project via resolveNewThreadPickerProjectRef and resolveScopedNewThreadProjectRef
• Clicking 'New thread' in SidebarV2 now opens the project picker when multiple or zero projects exist, passing a preferredProjectRef; the button is no longer disabled with zero projects
• Global chat shortcuts (ChatRouteGlobalShortcuts) suppress unrelated shortcuts while the palette is open and close the palette before immediate thread creation
• Adds closeCommandPalette/onCloseCommandPalette event utilities and a shared sidebarProjectScopeStore for cross-component scope sharing
• Behavioral Change: resolveChatNewShortcutBehavior replaces a simple project-count check with a three-way decision (open-project-picker, create-immediately, dismiss-and-create) affecting keyboard shortcut behavior

^{Macroscope summarized e2550fb.}

Current combined-stack UI evidence (2026-07-24)

Captured from PR head a5e53a9ce55272a331c6ba6443d3601c82363020 on upstream main ece05087a70e94efcd57441337fa1249559362ba, using combined integration 4dd4cef40 and package /nix/store/pf7fjqw8ykkdgayf3ywsbgxxp6wi1m42-t3code-0.0.29-patched-main-20260724.

The animation shows the Sidebar V2 New thread control opening the shared Projects picker, filtering to Atlas API, and Enter creating the new draft in that project. The picker retains Add project and keyboard hints. All names and paths are disposable seed data.

[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: 4e74653d-7ec6-4f05-a6aa-8c7a4e1babfa

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 new user-facing functionality: a unified project picker for new threads with modified keyboard shortcut behavior, new state management, and changed command palette interactions. These feature-level changes to the thread creation workflow warrant human review.

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

[juliusmarminge]

BEFORE/AFTER SCREENSHOTS FOR UI CHANGES

[colonelpanic8]

BEFORE/AFTER SCREENSHOTS FOR UI CHANGES

this just gets rid of a duplicated modal where one version is clearly superior to the other. You really need a screenshot for that?

Dismissing prior approval to re-evaluate 891f36e

Dismissing prior approval to re-evaluate 7df1729

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

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

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

[colonelpanic8]

Summary

• route every new-thread entry point through one command-palette project picker
• prioritize the project from the current route or thread context
• preserve loading and empty states, Add project, and repeat-shortcut refresh behavior
• remove the duplicate Sidebar V2 picker and its separate keyboard-navigation path

Why

T3 Code originally had two project-picker experiences for starting a thread. The command-palette picker was searchable and already served the Ctrl+K flow, while Ctrl+N and the Sidebar V2 button used a separate sidebar-owned modal. Consolidating them gives every entry point the same interaction and removes duplicate UI and keyboard-navigation code.

PR #4269 landed the basic route into the command palette after this PR opened. That means the current main screenshot below is an intermediate state, while the first screenshot is the real product before-state of the consolidation this PR proposed.

UI comparison

Before: standalone Sidebar V2 dialog

The original new-thread flow used a separate project dialog. It duplicated the Ctrl+K picker and did not support incremental filtering.

Current main after #4269

main now routes into the command palette, but the intermediate picker still shows the new-thread shortcut on every project row and does not include Add project in the same result set.

This PR

This PR keeps the command-palette picker, prioritizes the contextual project, and includes Add project as a keyboard-addressable action.

It also uses the same incremental search behavior as Ctrl+K → New thread in…:

Validation

• web package typecheck
• targeted lint on changed files
• CommandPalette.logic.test.ts and keybindings.test.ts (56 tests)
• isolated end-to-end web verification: Ctrl+N opens the Projects command-palette submenu and selecting a project creates a fresh draft
• compared against Ctrl+K → New thread in… to confirm both entry points render the same picker

Exact-head evidence

Revalidated at 9fb451def031 on current main (9a0a071): focused tests, vp check, and vp run typecheck passed. The capture uses only disposable local projects.

---

Note

Medium Risk
Touches thread-creation entry points, global shortcuts, and command-palette navigation across Sidebar V2 and chat routes; behavior changes for zero-project and multi-project cases but logic is largely extracted and unit-tested.

Overview
Unifies starting a new thread behind a single command-palette project picker instead of mixed sidebar and palette flows.

The palette gains a dedicated new-thread-in view: grouped project rows, Add project always in an Actions group (including the > actions filter), and empty/loading copy via new logic helpers. Opening can pass preferredProjectRef on the event bus; resolution combines that with sidebar project scope and thread/route context through resolveNewThreadPickerProjectRef / resolveScopedNewThreadProjectRef, with scope lifted to a shared sidebarProjectScopeStore.

Sidebar V2 and chat route shortcuts (Ctrl+N / chat.new) use resolveChatNewShortcutBehavior: multi-project or zero-project Sidebar V2 opens the picker (with preference); single-project still creates immediately and can close an open palette first. chat.new may refresh while the palette is open; other chat shortcuts stay suppressed. The sidebar New thread control is no longer disabled when there are no projects.

Supporting changes: closeCommandPalette on the bus, add-project back-navigation fix when popping views, and removal of per-row chat.new shortcut on picker projects.

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

Note

Unify the new thread project picker in the command palette with scoped project resolution

• Adds a dedicated 'New thread in…' project picker view to the command palette, replacing inline project embedding with a structured group built by buildNewThreadPickerGroups
• The picker resolves an effective preferred project from explicit preference, sidebar scope, or contextual project via resolveNewThreadPickerProjectRef and resolveScopedNewThreadProjectRef
• Clicking 'New thread' in SidebarV2 now opens the project picker when multiple or zero projects exist, passing a preferredProjectRef; the button is no longer disabled with zero projects
• Global chat shortcuts (ChatRouteGlobalShortcuts) suppress unrelated shortcuts while the palette is open and close the palette before immediate thread creation
• Adds closeCommandPalette/onCloseCommandPalette event utilities and a shared sidebarProjectScopeStore for cross-component scope sharing
• Behavioral Change: resolveChatNewShortcutBehavior replaces a simple project-count check with a three-way decision (open-project-picker, create-immediately, dismiss-and-create) affecting keyboard shortcut behavior

^{Macroscope summarized e2550fb.}

Current combined-stack UI evidence (2026-07-24)

Captured from PR head a5e53a9ce55272a331c6ba6443d3601c82363020 on upstream main ece05087a70e94efcd57441337fa1249559362ba, using combined integration 4dd4cef40 and package /nix/store/pf7fjqw8ykkdgayf3ywsbgxxp6wi1m42-t3code-0.0.29-patched-main-20260724.

The animation shows the Sidebar V2 New thread control opening the shared Projects picker, filtering to Atlas API, and Enter creating the new draft in that project. The picker retains Add project and keyboard hints. All names and paths are disposable seed data.

[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: 4e74653d-7ec6-4f05-a6aa-8c7a4e1babfa

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 new user-facing functionality: a unified project picker for new threads with modified keyboard shortcut behavior, new state management, and changed command palette interactions. These feature-level changes to the thread creation workflow warrant human review.

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

[juliusmarminge]

BEFORE/AFTER SCREENSHOTS FOR UI CHANGES

[colonelpanic8]

BEFORE/AFTER SCREENSHOTS FOR UI CHANGES

this just gets rid of a duplicated modal where one version is clearly superior to the other. You really need a screenshot for that?

Dismissing prior approval to re-evaluate 891f36e

Dismissing prior approval to re-evaluate 7df1729

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

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

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

[colonelpanic8]

Summary

• route every new-thread entry point through one command-palette project picker
• prioritize the project from the current route or thread context
• preserve loading and empty states, Add project, and repeat-shortcut refresh behavior
• remove the duplicate Sidebar V2 picker and its separate keyboard-navigation path

Why

T3 Code originally had two project-picker experiences for starting a thread. The command-palette picker was searchable and already served the Ctrl+K flow, while Ctrl+N and the Sidebar V2 button used a separate sidebar-owned modal. Consolidating them gives every entry point the same interaction and removes duplicate UI and keyboard-navigation code.

PR #4269 landed the basic route into the command palette after this PR opened. That means the current main screenshot below is an intermediate state, while the first screenshot is the real product before-state of the consolidation this PR proposed.

UI comparison

Before: standalone Sidebar V2 dialog

The original new-thread flow used a separate project dialog. It duplicated the Ctrl+K picker and did not support incremental filtering.

Current main after #4269

main now routes into the command palette, but the intermediate picker still shows the new-thread shortcut on every project row and does not include Add project in the same result set.

This PR

This PR keeps the command-palette picker, prioritizes the contextual project, and includes Add project as a keyboard-addressable action.

It also uses the same incremental search behavior as Ctrl+K → New thread in…:

Validation

• web package typecheck
• targeted lint on changed files
• CommandPalette.logic.test.ts and keybindings.test.ts (56 tests)
• isolated end-to-end web verification: Ctrl+N opens the Projects command-palette submenu and selecting a project creates a fresh draft
• compared against Ctrl+K → New thread in… to confirm both entry points render the same picker

Exact-head evidence

Revalidated at 9fb451def031 on current main (9a0a071): focused tests, vp check, and vp run typecheck passed. The capture uses only disposable local projects.

---

Note

Medium Risk
Touches thread-creation entry points, global shortcuts, and command-palette navigation across Sidebar V2 and chat routes; behavior changes for zero-project and multi-project cases but logic is largely extracted and unit-tested.

Overview
Unifies starting a new thread behind a single command-palette project picker instead of mixed sidebar and palette flows.

The palette gains a dedicated new-thread-in view: grouped project rows, Add project always in an Actions group (including the > actions filter), and empty/loading copy via new logic helpers. Opening can pass preferredProjectRef on the event bus; resolution combines that with sidebar project scope and thread/route context through resolveNewThreadPickerProjectRef / resolveScopedNewThreadProjectRef, with scope lifted to a shared sidebarProjectScopeStore.

Sidebar V2 and chat route shortcuts (Ctrl+N / chat.new) use resolveChatNewShortcutBehavior: multi-project or zero-project Sidebar V2 opens the picker (with preference); single-project still creates immediately and can close an open palette first. chat.new may refresh while the palette is open; other chat shortcuts stay suppressed. The sidebar New thread control is no longer disabled when there are no projects.

Supporting changes: closeCommandPalette on the bus, add-project back-navigation fix when popping views, and removal of per-row chat.new shortcut on picker projects.

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

Note

Unify the new thread project picker in the command palette with scoped project resolution

• Adds a dedicated 'New thread in…' project picker view to the command palette, replacing inline project embedding with a structured group built by buildNewThreadPickerGroups
• The picker resolves an effective preferred project from explicit preference, sidebar scope, or contextual project via resolveNewThreadPickerProjectRef and resolveScopedNewThreadProjectRef
• Clicking 'New thread' in SidebarV2 now opens the project picker when multiple or zero projects exist, passing a preferredProjectRef; the button is no longer disabled with zero projects
• Global chat shortcuts (ChatRouteGlobalShortcuts) suppress unrelated shortcuts while the palette is open and close the palette before immediate thread creation
• Adds closeCommandPalette/onCloseCommandPalette event utilities and a shared sidebarProjectScopeStore for cross-component scope sharing
• Behavioral Change: resolveChatNewShortcutBehavior replaces a simple project-count check with a three-way decision (open-project-picker, create-immediately, dismiss-and-create) affecting keyboard shortcut behavior

^{Macroscope summarized e2550fb.}

Current combined-stack UI evidence (2026-07-24)

Captured from PR head a5e53a9ce55272a331c6ba6443d3601c82363020 on upstream main ece05087a70e94efcd57441337fa1249559362ba, using combined integration 4dd4cef40 and package /nix/store/pf7fjqw8ykkdgayf3ywsbgxxp6wi1m42-t3code-0.0.29-patched-main-20260724.

The animation shows the Sidebar V2 New thread control opening the shared Projects picker, filtering to Atlas API, and Enter creating the new draft in that project. The picker retains Add project and keyboard hints. All names and paths are disposable seed data.

[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: 4e74653d-7ec6-4f05-a6aa-8c7a4e1babfa

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 new user-facing functionality: a unified project picker for new threads with modified keyboard shortcut behavior, new state management, and changed command palette interactions. These feature-level changes to the thread creation workflow warrant human review.

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

[juliusmarminge]

BEFORE/AFTER SCREENSHOTS FOR UI CHANGES

[colonelpanic8]

BEFORE/AFTER SCREENSHOTS FOR UI CHANGES

this just gets rid of a duplicated modal where one version is clearly superior to the other. You really need a screenshot for that?

Dismissing prior approval to re-evaluate 891f36e

Dismissing prior approval to re-evaluate 7df1729

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

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

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

[colonelpanic8]

Summary

• route every new-thread entry point through one command-palette project picker
• prioritize the project from the current route or thread context
• preserve loading and empty states, Add project, and repeat-shortcut refresh behavior
• remove the duplicate Sidebar V2 picker and its separate keyboard-navigation path

Why

T3 Code originally had two project-picker experiences for starting a thread. The command-palette picker was searchable and already served the Ctrl+K flow, while Ctrl+N and the Sidebar V2 button used a separate sidebar-owned modal. Consolidating them gives every entry point the same interaction and removes duplicate UI and keyboard-navigation code.

PR #4269 landed the basic route into the command palette after this PR opened. That means the current main screenshot below is an intermediate state, while the first screenshot is the real product before-state of the consolidation this PR proposed.

UI comparison

Before: standalone Sidebar V2 dialog

The original new-thread flow used a separate project dialog. It duplicated the Ctrl+K picker and did not support incremental filtering.

Current main after #4269

main now routes into the command palette, but the intermediate picker still shows the new-thread shortcut on every project row and does not include Add project in the same result set.

This PR

This PR keeps the command-palette picker, prioritizes the contextual project, and includes Add project as a keyboard-addressable action.

It also uses the same incremental search behavior as Ctrl+K → New thread in…:

Validation

• web package typecheck
• targeted lint on changed files
• CommandPalette.logic.test.ts and keybindings.test.ts (56 tests)
• isolated end-to-end web verification: Ctrl+N opens the Projects command-palette submenu and selecting a project creates a fresh draft
• compared against Ctrl+K → New thread in… to confirm both entry points render the same picker

Exact-head evidence

Revalidated at 9fb451def031 on current main (9a0a071): focused tests, vp check, and vp run typecheck passed. The capture uses only disposable local projects.

---

Note

Medium Risk
Touches thread-creation entry points, global shortcuts, and command-palette navigation across Sidebar V2 and chat routes; behavior changes for zero-project and multi-project cases but logic is largely extracted and unit-tested.

Overview
Unifies starting a new thread behind a single command-palette project picker instead of mixed sidebar and palette flows.

The palette gains a dedicated new-thread-in view: grouped project rows, Add project always in an Actions group (including the > actions filter), and empty/loading copy via new logic helpers. Opening can pass preferredProjectRef on the event bus; resolution combines that with sidebar project scope and thread/route context through resolveNewThreadPickerProjectRef / resolveScopedNewThreadProjectRef, with scope lifted to a shared sidebarProjectScopeStore.

Sidebar V2 and chat route shortcuts (Ctrl+N / chat.new) use resolveChatNewShortcutBehavior: multi-project or zero-project Sidebar V2 opens the picker (with preference); single-project still creates immediately and can close an open palette first. chat.new may refresh while the palette is open; other chat shortcuts stay suppressed. The sidebar New thread control is no longer disabled when there are no projects.

Supporting changes: closeCommandPalette on the bus, add-project back-navigation fix when popping views, and removal of per-row chat.new shortcut on picker projects.

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

Note

Unify the new thread project picker in the command palette with scoped project resolution

• Adds a dedicated 'New thread in…' project picker view to the command palette, replacing inline project embedding with a structured group built by buildNewThreadPickerGroups
• The picker resolves an effective preferred project from explicit preference, sidebar scope, or contextual project via resolveNewThreadPickerProjectRef and resolveScopedNewThreadProjectRef
• Clicking 'New thread' in SidebarV2 now opens the project picker when multiple or zero projects exist, passing a preferredProjectRef; the button is no longer disabled with zero projects
• Global chat shortcuts (ChatRouteGlobalShortcuts) suppress unrelated shortcuts while the palette is open and close the palette before immediate thread creation
• Adds closeCommandPalette/onCloseCommandPalette event utilities and a shared sidebarProjectScopeStore for cross-component scope sharing
• Behavioral Change: resolveChatNewShortcutBehavior replaces a simple project-count check with a three-way decision (open-project-picker, create-immediately, dismiss-and-create) affecting keyboard shortcut behavior

^{Macroscope summarized e2550fb.}

Current combined-stack UI evidence (2026-07-24)

Captured from PR head a5e53a9ce55272a331c6ba6443d3601c82363020 on upstream main ece05087a70e94efcd57441337fa1249559362ba, using combined integration 4dd4cef40 and package /nix/store/pf7fjqw8ykkdgayf3ywsbgxxp6wi1m42-t3code-0.0.29-patched-main-20260724.

The animation shows the Sidebar V2 New thread control opening the shared Projects picker, filtering to Atlas API, and Enter creating the new draft in that project. The picker retains Add project and keyboard hints. All names and paths are disposable seed data.

[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: 4e74653d-7ec6-4f05-a6aa-8c7a4e1babfa

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 new user-facing functionality: a unified project picker for new threads with modified keyboard shortcut behavior, new state management, and changed command palette interactions. These feature-level changes to the thread creation workflow warrant human review.

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

[juliusmarminge]

BEFORE/AFTER SCREENSHOTS FOR UI CHANGES

[colonelpanic8]

BEFORE/AFTER SCREENSHOTS FOR UI CHANGES

this just gets rid of a duplicated modal where one version is clearly superior to the other. You really need a screenshot for that?

Dismissing prior approval to re-evaluate 891f36e

Dismissing prior approval to re-evaluate 7df1729

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

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

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

[colonelpanic8]

Summary

• route every new-thread entry point through one command-palette project picker
• prioritize the project from the current route or thread context
• preserve loading and empty states, Add project, and repeat-shortcut refresh behavior
• remove the duplicate Sidebar V2 picker and its separate keyboard-navigation path

Why

T3 Code originally had two project-picker experiences for starting a thread. The command-palette picker was searchable and already served the Ctrl+K flow, while Ctrl+N and the Sidebar V2 button used a separate sidebar-owned modal. Consolidating them gives every entry point the same interaction and removes duplicate UI and keyboard-navigation code.

PR #4269 landed the basic route into the command palette after this PR opened. That means the current main screenshot below is an intermediate state, while the first screenshot is the real product before-state of the consolidation this PR proposed.

UI comparison

Before: standalone Sidebar V2 dialog

The original new-thread flow used a separate project dialog. It duplicated the Ctrl+K picker and did not support incremental filtering.

Current main after #4269

main now routes into the command palette, but the intermediate picker still shows the new-thread shortcut on every project row and does not include Add project in the same result set.

This PR

This PR keeps the command-palette picker, prioritizes the contextual project, and includes Add project as a keyboard-addressable action.

It also uses the same incremental search behavior as Ctrl+K → New thread in…:

Validation

• web package typecheck
• targeted lint on changed files
• CommandPalette.logic.test.ts and keybindings.test.ts (56 tests)
• isolated end-to-end web verification: Ctrl+N opens the Projects command-palette submenu and selecting a project creates a fresh draft
• compared against Ctrl+K → New thread in… to confirm both entry points render the same picker

Exact-head evidence

Revalidated at 9fb451def031 on current main (9a0a071): focused tests, vp check, and vp run typecheck passed. The capture uses only disposable local projects.

---

Note

Medium Risk
Touches thread-creation entry points, global shortcuts, and command-palette navigation across Sidebar V2 and chat routes; behavior changes for zero-project and multi-project cases but logic is largely extracted and unit-tested.

Overview
Unifies starting a new thread behind a single command-palette project picker instead of mixed sidebar and palette flows.

The palette gains a dedicated new-thread-in view: grouped project rows, Add project always in an Actions group (including the > actions filter), and empty/loading copy via new logic helpers. Opening can pass preferredProjectRef on the event bus; resolution combines that with sidebar project scope and thread/route context through resolveNewThreadPickerProjectRef / resolveScopedNewThreadProjectRef, with scope lifted to a shared sidebarProjectScopeStore.

Sidebar V2 and chat route shortcuts (Ctrl+N / chat.new) use resolveChatNewShortcutBehavior: multi-project or zero-project Sidebar V2 opens the picker (with preference); single-project still creates immediately and can close an open palette first. chat.new may refresh while the palette is open; other chat shortcuts stay suppressed. The sidebar New thread control is no longer disabled when there are no projects.

Supporting changes: closeCommandPalette on the bus, add-project back-navigation fix when popping views, and removal of per-row chat.new shortcut on picker projects.

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

Note

Unify the new thread project picker in the command palette with scoped project resolution

• Adds a dedicated 'New thread in…' project picker view to the command palette, replacing inline project embedding with a structured group built by buildNewThreadPickerGroups
• The picker resolves an effective preferred project from explicit preference, sidebar scope, or contextual project via resolveNewThreadPickerProjectRef and resolveScopedNewThreadProjectRef
• Clicking 'New thread' in SidebarV2 now opens the project picker when multiple or zero projects exist, passing a preferredProjectRef; the button is no longer disabled with zero projects
• Global chat shortcuts (ChatRouteGlobalShortcuts) suppress unrelated shortcuts while the palette is open and close the palette before immediate thread creation
• Adds closeCommandPalette/onCloseCommandPalette event utilities and a shared sidebarProjectScopeStore for cross-component scope sharing
• Behavioral Change: resolveChatNewShortcutBehavior replaces a simple project-count check with a three-way decision (open-project-picker, create-immediately, dismiss-and-create) affecting keyboard shortcut behavior

^{Macroscope summarized e2550fb.}

Current combined-stack UI evidence (2026-07-24)

Captured from PR head a5e53a9ce55272a331c6ba6443d3601c82363020 on upstream main ece05087a70e94efcd57441337fa1249559362ba, using combined integration 4dd4cef40 and package /nix/store/pf7fjqw8ykkdgayf3ywsbgxxp6wi1m42-t3code-0.0.29-patched-main-20260724.

The animation shows the Sidebar V2 New thread control opening the shared Projects picker, filtering to Atlas API, and Enter creating the new draft in that project. The picker retains Add project and keyboard hints. All names and paths are disposable seed data.

[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: 4e74653d-7ec6-4f05-a6aa-8c7a4e1babfa

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 new user-facing functionality: a unified project picker for new threads with modified keyboard shortcut behavior, new state management, and changed command palette interactions. These feature-level changes to the thread creation workflow warrant human review.

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

[juliusmarminge]

BEFORE/AFTER SCREENSHOTS FOR UI CHANGES

[colonelpanic8]

BEFORE/AFTER SCREENSHOTS FOR UI CHANGES

this just gets rid of a duplicated modal where one version is clearly superior to the other. You really need a screenshot for that?

Dismissing prior approval to re-evaluate 891f36e

Dismissing prior approval to re-evaluate 7df1729

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

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

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