Add environment-aware new thread picker

[colonelpanic8]

What Changed

• Added a chat.newEnvironment command on Mod+Shift+N.
• Added a two-stage new-thread flow: choose an environment, then choose a project available on that environment.
• Presents every environment in one flat Run on list; the primary environment is labeled with its runtime hostname instead of Local.
• Keeps existing Mod+N project/context behavior unchanged.
• Migrates only the previous exact Mod+Shift+N chat.newLocal default while preserving custom chat.newLocal bindings.

Why

Thread creation previously collapsed projects across environments and silently selected one machine. This makes execution location explicit without treating local as a separate mode.

UI Changes

Environment selection:

Environment-scoped project selection:

Checklist

• Focused keybinding and environment-grouping tests pass (92 tests).
• Targeted formatting and lint checks pass.
• Integrated web verification covers environment -> project -> draft.
• Repository-wide vp check completes with only existing warnings outside this change.
• Repository-wide vp run typecheck is blocked by the existing interactive Astro dependency prompt and existing unrelated web type errors; changed packages/files introduce no reported type errors.

---

Note

Medium Risk
Default shortcut behavior changes for all users who relied on Mod+Shift+N for instant local threads; migration is narrow but still touches persisted keybinding config on startup.

Overview
Mod+Shift+N now runs chat.newEnvironment, opening the command palette on a “New thread on…” flow instead of immediately starting a local thread. chat.newLocal remains available for custom bindings but is no longer the default on that chord.

The palette adds a flat Run on list of environments (with per-environment project submenus), waits until environment shells are bootstrapped before opening, and closes if nothing is available. Project rows are built with targetEnvironmentId so choices stay on the chosen machine rather than falling back to another environment’s project.

On the server, startup keybinding sync migrates only the exact legacy default (mod+shift+n + chat.newLocal + !terminalFocus) to chat.newEnvironment, leaving other chat.newLocal entries (e.g. mod+shift+l) untouched. Contracts and settings expose chat.newEnvironment via exported STATIC_KEYBINDING_COMMANDS.

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

Note

Add environment-aware new thread picker with chat.newEnvironment command

• Adds a 'New thread on...' flow to the command palette that lets users pick an environment and project before starting a thread, triggered by mod+shift+n via the new chat.newEnvironment command.
• Updates DEFAULT_KEYBINDINGS in shared/src/keybindings.ts to bind mod+shift+n to chat.newEnvironment instead of chat.newLocal.
• Extends buildSidebarProjectPickerEntries to accept an optional targetEnvironmentId, scoping project entries to that environment without falling back to other machines.
• Migrates existing user keybinding configs at startup: if the legacy chat.newLocal default is found without a chat.newEnvironment binding, it is automatically replaced.
• Behavioral Change: mod+shift+n now opens the environment picker palette instead of directly creating a local thread; users with customized chat.newLocal bindings on other keys are unaffected.

^{Macroscope summarized 5e2155e.}

[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: aa6d1f79-adec-4771-85b7-9bada1d7ab6a

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

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new feature with significant new UI flows, command palette logic, keybinding changes, and migration behavior. The scope and complexity of new user-facing behavior warrant human review.

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

[cursor]

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

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

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

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

This branch changes the same new-thread picker flow as #4263. We are keeping that unified picker as the active implementation instead of reviewing another competing version.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[colonelpanic8]

What Changed

• Added a chat.newEnvironment command on Mod+Shift+N.
• Added a two-stage new-thread flow: choose an environment, then choose a project available on that environment.
• Presents every environment in one flat Run on list; the primary environment is labeled with its runtime hostname instead of Local.
• Keeps existing Mod+N project/context behavior unchanged.
• Migrates only the previous exact Mod+Shift+N chat.newLocal default while preserving custom chat.newLocal bindings.

Why

Thread creation previously collapsed projects across environments and silently selected one machine. This makes execution location explicit without treating local as a separate mode.

UI Changes

Environment selection:

Environment-scoped project selection:

Checklist

• Focused keybinding and environment-grouping tests pass (92 tests).
• Targeted formatting and lint checks pass.
• Integrated web verification covers environment -> project -> draft.
• Repository-wide vp check completes with only existing warnings outside this change.
• Repository-wide vp run typecheck is blocked by the existing interactive Astro dependency prompt and existing unrelated web type errors; changed packages/files introduce no reported type errors.

---

Note

Medium Risk
Default shortcut behavior changes for all users who relied on Mod+Shift+N for instant local threads; migration is narrow but still touches persisted keybinding config on startup.

Overview
Mod+Shift+N now runs chat.newEnvironment, opening the command palette on a “New thread on…” flow instead of immediately starting a local thread. chat.newLocal remains available for custom bindings but is no longer the default on that chord.

The palette adds a flat Run on list of environments (with per-environment project submenus), waits until environment shells are bootstrapped before opening, and closes if nothing is available. Project rows are built with targetEnvironmentId so choices stay on the chosen machine rather than falling back to another environment’s project.

On the server, startup keybinding sync migrates only the exact legacy default (mod+shift+n + chat.newLocal + !terminalFocus) to chat.newEnvironment, leaving other chat.newLocal entries (e.g. mod+shift+l) untouched. Contracts and settings expose chat.newEnvironment via exported STATIC_KEYBINDING_COMMANDS.

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

Note

Add environment-aware new thread picker with chat.newEnvironment command

• Adds a 'New thread on...' flow to the command palette that lets users pick an environment and project before starting a thread, triggered by mod+shift+n via the new chat.newEnvironment command.
• Updates DEFAULT_KEYBINDINGS in shared/src/keybindings.ts to bind mod+shift+n to chat.newEnvironment instead of chat.newLocal.
• Extends buildSidebarProjectPickerEntries to accept an optional targetEnvironmentId, scoping project entries to that environment without falling back to other machines.
• Migrates existing user keybinding configs at startup: if the legacy chat.newLocal default is found without a chat.newEnvironment binding, it is automatically replaced.
• Behavioral Change: mod+shift+n now opens the environment picker palette instead of directly creating a local thread; users with customized chat.newLocal bindings on other keys are unaffected.

^{Macroscope summarized 5e2155e.}

[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: aa6d1f79-adec-4771-85b7-9bada1d7ab6a

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

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new feature with significant new UI flows, command palette logic, keybinding changes, and migration behavior. The scope and complexity of new user-facing behavior warrant human review.

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

[cursor]

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

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

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

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

This branch changes the same new-thread picker flow as #4263. We are keeping that unified picker as the active implementation instead of reviewing another competing version.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[colonelpanic8]

What Changed

• Added a chat.newEnvironment command on Mod+Shift+N.
• Added a two-stage new-thread flow: choose an environment, then choose a project available on that environment.
• Presents every environment in one flat Run on list; the primary environment is labeled with its runtime hostname instead of Local.
• Keeps existing Mod+N project/context behavior unchanged.
• Migrates only the previous exact Mod+Shift+N chat.newLocal default while preserving custom chat.newLocal bindings.

Why

Thread creation previously collapsed projects across environments and silently selected one machine. This makes execution location explicit without treating local as a separate mode.

UI Changes

Environment selection:

Environment-scoped project selection:

Checklist

• Focused keybinding and environment-grouping tests pass (92 tests).
• Targeted formatting and lint checks pass.
• Integrated web verification covers environment -> project -> draft.
• Repository-wide vp check completes with only existing warnings outside this change.
• Repository-wide vp run typecheck is blocked by the existing interactive Astro dependency prompt and existing unrelated web type errors; changed packages/files introduce no reported type errors.

---

Note

Medium Risk
Default shortcut behavior changes for all users who relied on Mod+Shift+N for instant local threads; migration is narrow but still touches persisted keybinding config on startup.

Overview
Mod+Shift+N now runs chat.newEnvironment, opening the command palette on a “New thread on…” flow instead of immediately starting a local thread. chat.newLocal remains available for custom bindings but is no longer the default on that chord.

The palette adds a flat Run on list of environments (with per-environment project submenus), waits until environment shells are bootstrapped before opening, and closes if nothing is available. Project rows are built with targetEnvironmentId so choices stay on the chosen machine rather than falling back to another environment’s project.

On the server, startup keybinding sync migrates only the exact legacy default (mod+shift+n + chat.newLocal + !terminalFocus) to chat.newEnvironment, leaving other chat.newLocal entries (e.g. mod+shift+l) untouched. Contracts and settings expose chat.newEnvironment via exported STATIC_KEYBINDING_COMMANDS.

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

Note

Add environment-aware new thread picker with chat.newEnvironment command

• Adds a 'New thread on...' flow to the command palette that lets users pick an environment and project before starting a thread, triggered by mod+shift+n via the new chat.newEnvironment command.
• Updates DEFAULT_KEYBINDINGS in shared/src/keybindings.ts to bind mod+shift+n to chat.newEnvironment instead of chat.newLocal.
• Extends buildSidebarProjectPickerEntries to accept an optional targetEnvironmentId, scoping project entries to that environment without falling back to other machines.
• Migrates existing user keybinding configs at startup: if the legacy chat.newLocal default is found without a chat.newEnvironment binding, it is automatically replaced.
• Behavioral Change: mod+shift+n now opens the environment picker palette instead of directly creating a local thread; users with customized chat.newLocal bindings on other keys are unaffected.

^{Macroscope summarized 5e2155e.}

[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: aa6d1f79-adec-4771-85b7-9bada1d7ab6a

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

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new feature with significant new UI flows, command palette logic, keybinding changes, and migration behavior. The scope and complexity of new user-facing behavior warrant human review.

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

[cursor]

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

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

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

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

This branch changes the same new-thread picker flow as #4263. We are keeping that unified picker as the active implementation instead of reviewing another competing version.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[colonelpanic8]

What Changed

• Added a chat.newEnvironment command on Mod+Shift+N.
• Added a two-stage new-thread flow: choose an environment, then choose a project available on that environment.
• Presents every environment in one flat Run on list; the primary environment is labeled with its runtime hostname instead of Local.
• Keeps existing Mod+N project/context behavior unchanged.
• Migrates only the previous exact Mod+Shift+N chat.newLocal default while preserving custom chat.newLocal bindings.

Why

Thread creation previously collapsed projects across environments and silently selected one machine. This makes execution location explicit without treating local as a separate mode.

UI Changes

Environment selection:

Environment-scoped project selection:

Checklist

• Focused keybinding and environment-grouping tests pass (92 tests).
• Targeted formatting and lint checks pass.
• Integrated web verification covers environment -> project -> draft.
• Repository-wide vp check completes with only existing warnings outside this change.
• Repository-wide vp run typecheck is blocked by the existing interactive Astro dependency prompt and existing unrelated web type errors; changed packages/files introduce no reported type errors.

---

Note

Medium Risk
Default shortcut behavior changes for all users who relied on Mod+Shift+N for instant local threads; migration is narrow but still touches persisted keybinding config on startup.

Overview
Mod+Shift+N now runs chat.newEnvironment, opening the command palette on a “New thread on…” flow instead of immediately starting a local thread. chat.newLocal remains available for custom bindings but is no longer the default on that chord.

The palette adds a flat Run on list of environments (with per-environment project submenus), waits until environment shells are bootstrapped before opening, and closes if nothing is available. Project rows are built with targetEnvironmentId so choices stay on the chosen machine rather than falling back to another environment’s project.

On the server, startup keybinding sync migrates only the exact legacy default (mod+shift+n + chat.newLocal + !terminalFocus) to chat.newEnvironment, leaving other chat.newLocal entries (e.g. mod+shift+l) untouched. Contracts and settings expose chat.newEnvironment via exported STATIC_KEYBINDING_COMMANDS.

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

Note

Add environment-aware new thread picker with chat.newEnvironment command

• Adds a 'New thread on...' flow to the command palette that lets users pick an environment and project before starting a thread, triggered by mod+shift+n via the new chat.newEnvironment command.
• Updates DEFAULT_KEYBINDINGS in shared/src/keybindings.ts to bind mod+shift+n to chat.newEnvironment instead of chat.newLocal.
• Extends buildSidebarProjectPickerEntries to accept an optional targetEnvironmentId, scoping project entries to that environment without falling back to other machines.
• Migrates existing user keybinding configs at startup: if the legacy chat.newLocal default is found without a chat.newEnvironment binding, it is automatically replaced.
• Behavioral Change: mod+shift+n now opens the environment picker palette instead of directly creating a local thread; users with customized chat.newLocal bindings on other keys are unaffected.

^{Macroscope summarized 5e2155e.}

[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: aa6d1f79-adec-4771-85b7-9bada1d7ab6a

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

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new feature with significant new UI flows, command palette logic, keybinding changes, and migration behavior. The scope and complexity of new user-facing behavior warrant human review.

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

[cursor]

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

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

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

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

This branch changes the same new-thread picker flow as #4263. We are keeping that unified picker as the active implementation instead of reviewing another competing version.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[colonelpanic8]

What Changed

• Added a chat.newEnvironment command on Mod+Shift+N.
• Added a two-stage new-thread flow: choose an environment, then choose a project available on that environment.
• Presents every environment in one flat Run on list; the primary environment is labeled with its runtime hostname instead of Local.
• Keeps existing Mod+N project/context behavior unchanged.
• Migrates only the previous exact Mod+Shift+N chat.newLocal default while preserving custom chat.newLocal bindings.

Why

Thread creation previously collapsed projects across environments and silently selected one machine. This makes execution location explicit without treating local as a separate mode.

UI Changes

Environment selection:

Environment-scoped project selection:

Checklist

• Focused keybinding and environment-grouping tests pass (92 tests).
• Targeted formatting and lint checks pass.
• Integrated web verification covers environment -> project -> draft.
• Repository-wide vp check completes with only existing warnings outside this change.
• Repository-wide vp run typecheck is blocked by the existing interactive Astro dependency prompt and existing unrelated web type errors; changed packages/files introduce no reported type errors.

---

Note

Medium Risk
Default shortcut behavior changes for all users who relied on Mod+Shift+N for instant local threads; migration is narrow but still touches persisted keybinding config on startup.

Overview
Mod+Shift+N now runs chat.newEnvironment, opening the command palette on a “New thread on…” flow instead of immediately starting a local thread. chat.newLocal remains available for custom bindings but is no longer the default on that chord.

The palette adds a flat Run on list of environments (with per-environment project submenus), waits until environment shells are bootstrapped before opening, and closes if nothing is available. Project rows are built with targetEnvironmentId so choices stay on the chosen machine rather than falling back to another environment’s project.

On the server, startup keybinding sync migrates only the exact legacy default (mod+shift+n + chat.newLocal + !terminalFocus) to chat.newEnvironment, leaving other chat.newLocal entries (e.g. mod+shift+l) untouched. Contracts and settings expose chat.newEnvironment via exported STATIC_KEYBINDING_COMMANDS.

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

Note

Add environment-aware new thread picker with chat.newEnvironment command

• Adds a 'New thread on...' flow to the command palette that lets users pick an environment and project before starting a thread, triggered by mod+shift+n via the new chat.newEnvironment command.
• Updates DEFAULT_KEYBINDINGS in shared/src/keybindings.ts to bind mod+shift+n to chat.newEnvironment instead of chat.newLocal.
• Extends buildSidebarProjectPickerEntries to accept an optional targetEnvironmentId, scoping project entries to that environment without falling back to other machines.
• Migrates existing user keybinding configs at startup: if the legacy chat.newLocal default is found without a chat.newEnvironment binding, it is automatically replaced.
• Behavioral Change: mod+shift+n now opens the environment picker palette instead of directly creating a local thread; users with customized chat.newLocal bindings on other keys are unaffected.

^{Macroscope summarized 5e2155e.}

[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: aa6d1f79-adec-4771-85b7-9bada1d7ab6a

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

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new feature with significant new UI flows, command palette logic, keybinding changes, and migration behavior. The scope and complexity of new user-facing behavior warrant human review.

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

[cursor]

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

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

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

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

This branch changes the same new-thread picker flow as #4263. We are keeping that unified picker as the active implementation instead of reviewing another competing version.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[colonelpanic8]

What Changed

• Added a chat.newEnvironment command on Mod+Shift+N.
• Added a two-stage new-thread flow: choose an environment, then choose a project available on that environment.
• Presents every environment in one flat Run on list; the primary environment is labeled with its runtime hostname instead of Local.
• Keeps existing Mod+N project/context behavior unchanged.
• Migrates only the previous exact Mod+Shift+N chat.newLocal default while preserving custom chat.newLocal bindings.

Why

Thread creation previously collapsed projects across environments and silently selected one machine. This makes execution location explicit without treating local as a separate mode.

UI Changes

Environment selection:

Environment-scoped project selection:

Checklist

• Focused keybinding and environment-grouping tests pass (92 tests).
• Targeted formatting and lint checks pass.
• Integrated web verification covers environment -> project -> draft.
• Repository-wide vp check completes with only existing warnings outside this change.
• Repository-wide vp run typecheck is blocked by the existing interactive Astro dependency prompt and existing unrelated web type errors; changed packages/files introduce no reported type errors.

---

Note

Medium Risk
Default shortcut behavior changes for all users who relied on Mod+Shift+N for instant local threads; migration is narrow but still touches persisted keybinding config on startup.

Overview
Mod+Shift+N now runs chat.newEnvironment, opening the command palette on a “New thread on…” flow instead of immediately starting a local thread. chat.newLocal remains available for custom bindings but is no longer the default on that chord.

The palette adds a flat Run on list of environments (with per-environment project submenus), waits until environment shells are bootstrapped before opening, and closes if nothing is available. Project rows are built with targetEnvironmentId so choices stay on the chosen machine rather than falling back to another environment’s project.

On the server, startup keybinding sync migrates only the exact legacy default (mod+shift+n + chat.newLocal + !terminalFocus) to chat.newEnvironment, leaving other chat.newLocal entries (e.g. mod+shift+l) untouched. Contracts and settings expose chat.newEnvironment via exported STATIC_KEYBINDING_COMMANDS.

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

Note

Add environment-aware new thread picker with chat.newEnvironment command

• Adds a 'New thread on...' flow to the command palette that lets users pick an environment and project before starting a thread, triggered by mod+shift+n via the new chat.newEnvironment command.
• Updates DEFAULT_KEYBINDINGS in shared/src/keybindings.ts to bind mod+shift+n to chat.newEnvironment instead of chat.newLocal.
• Extends buildSidebarProjectPickerEntries to accept an optional targetEnvironmentId, scoping project entries to that environment without falling back to other machines.
• Migrates existing user keybinding configs at startup: if the legacy chat.newLocal default is found without a chat.newEnvironment binding, it is automatically replaced.
• Behavioral Change: mod+shift+n now opens the environment picker palette instead of directly creating a local thread; users with customized chat.newLocal bindings on other keys are unaffected.

^{Macroscope summarized 5e2155e.}

[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: aa6d1f79-adec-4771-85b7-9bada1d7ab6a

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

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new feature with significant new UI flows, command palette logic, keybinding changes, and migration behavior. The scope and complexity of new user-facing behavior warrant human review.

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

[cursor]

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

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

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

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

This branch changes the same new-thread picker flow as #4263. We are keeping that unified picker as the active implementation instead of reviewing another competing version.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[colonelpanic8]

What Changed

• Added a chat.newEnvironment command on Mod+Shift+N.
• Added a two-stage new-thread flow: choose an environment, then choose a project available on that environment.
• Presents every environment in one flat Run on list; the primary environment is labeled with its runtime hostname instead of Local.
• Keeps existing Mod+N project/context behavior unchanged.
• Migrates only the previous exact Mod+Shift+N chat.newLocal default while preserving custom chat.newLocal bindings.

Why

Thread creation previously collapsed projects across environments and silently selected one machine. This makes execution location explicit without treating local as a separate mode.

UI Changes

Environment selection:

Environment-scoped project selection:

Checklist

• Focused keybinding and environment-grouping tests pass (92 tests).
• Targeted formatting and lint checks pass.
• Integrated web verification covers environment -> project -> draft.
• Repository-wide vp check completes with only existing warnings outside this change.
• Repository-wide vp run typecheck is blocked by the existing interactive Astro dependency prompt and existing unrelated web type errors; changed packages/files introduce no reported type errors.

---

Note

Medium Risk
Default shortcut behavior changes for all users who relied on Mod+Shift+N for instant local threads; migration is narrow but still touches persisted keybinding config on startup.

Overview
Mod+Shift+N now runs chat.newEnvironment, opening the command palette on a “New thread on…” flow instead of immediately starting a local thread. chat.newLocal remains available for custom bindings but is no longer the default on that chord.

The palette adds a flat Run on list of environments (with per-environment project submenus), waits until environment shells are bootstrapped before opening, and closes if nothing is available. Project rows are built with targetEnvironmentId so choices stay on the chosen machine rather than falling back to another environment’s project.

On the server, startup keybinding sync migrates only the exact legacy default (mod+shift+n + chat.newLocal + !terminalFocus) to chat.newEnvironment, leaving other chat.newLocal entries (e.g. mod+shift+l) untouched. Contracts and settings expose chat.newEnvironment via exported STATIC_KEYBINDING_COMMANDS.

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

Note

Add environment-aware new thread picker with chat.newEnvironment command

• Adds a 'New thread on...' flow to the command palette that lets users pick an environment and project before starting a thread, triggered by mod+shift+n via the new chat.newEnvironment command.
• Updates DEFAULT_KEYBINDINGS in shared/src/keybindings.ts to bind mod+shift+n to chat.newEnvironment instead of chat.newLocal.
• Extends buildSidebarProjectPickerEntries to accept an optional targetEnvironmentId, scoping project entries to that environment without falling back to other machines.
• Migrates existing user keybinding configs at startup: if the legacy chat.newLocal default is found without a chat.newEnvironment binding, it is automatically replaced.
• Behavioral Change: mod+shift+n now opens the environment picker palette instead of directly creating a local thread; users with customized chat.newLocal bindings on other keys are unaffected.

^{Macroscope summarized 5e2155e.}

[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: aa6d1f79-adec-4771-85b7-9bada1d7ab6a

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

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new feature with significant new UI flows, command palette logic, keybinding changes, and migration behavior. The scope and complexity of new user-facing behavior warrant human review.

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

[cursor]

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

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

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

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

This branch changes the same new-thread picker flow as #4263. We are keeping that unified picker as the active implementation instead of reviewing another competing version.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.

[colonelpanic8]

What Changed

• Added a chat.newEnvironment command on Mod+Shift+N.
• Added a two-stage new-thread flow: choose an environment, then choose a project available on that environment.
• Presents every environment in one flat Run on list; the primary environment is labeled with its runtime hostname instead of Local.
• Keeps existing Mod+N project/context behavior unchanged.
• Migrates only the previous exact Mod+Shift+N chat.newLocal default while preserving custom chat.newLocal bindings.

Why

Thread creation previously collapsed projects across environments and silently selected one machine. This makes execution location explicit without treating local as a separate mode.

UI Changes

Environment selection:

Environment-scoped project selection:

Checklist

• Focused keybinding and environment-grouping tests pass (92 tests).
• Targeted formatting and lint checks pass.
• Integrated web verification covers environment -> project -> draft.
• Repository-wide vp check completes with only existing warnings outside this change.
• Repository-wide vp run typecheck is blocked by the existing interactive Astro dependency prompt and existing unrelated web type errors; changed packages/files introduce no reported type errors.

---

Note

Medium Risk
Default shortcut behavior changes for all users who relied on Mod+Shift+N for instant local threads; migration is narrow but still touches persisted keybinding config on startup.

Overview
Mod+Shift+N now runs chat.newEnvironment, opening the command palette on a “New thread on…” flow instead of immediately starting a local thread. chat.newLocal remains available for custom bindings but is no longer the default on that chord.

The palette adds a flat Run on list of environments (with per-environment project submenus), waits until environment shells are bootstrapped before opening, and closes if nothing is available. Project rows are built with targetEnvironmentId so choices stay on the chosen machine rather than falling back to another environment’s project.

On the server, startup keybinding sync migrates only the exact legacy default (mod+shift+n + chat.newLocal + !terminalFocus) to chat.newEnvironment, leaving other chat.newLocal entries (e.g. mod+shift+l) untouched. Contracts and settings expose chat.newEnvironment via exported STATIC_KEYBINDING_COMMANDS.

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

Note

Add environment-aware new thread picker with chat.newEnvironment command

• Adds a 'New thread on...' flow to the command palette that lets users pick an environment and project before starting a thread, triggered by mod+shift+n via the new chat.newEnvironment command.
• Updates DEFAULT_KEYBINDINGS in shared/src/keybindings.ts to bind mod+shift+n to chat.newEnvironment instead of chat.newLocal.
• Extends buildSidebarProjectPickerEntries to accept an optional targetEnvironmentId, scoping project entries to that environment without falling back to other machines.
• Migrates existing user keybinding configs at startup: if the legacy chat.newLocal default is found without a chat.newEnvironment binding, it is automatically replaced.
• Behavioral Change: mod+shift+n now opens the environment picker palette instead of directly creating a local thread; users with customized chat.newLocal bindings on other keys are unaffected.

^{Macroscope summarized 5e2155e.}

[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: aa6d1f79-adec-4771-85b7-9bada1d7ab6a

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

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new feature with significant new UI flows, command palette logic, keybinding changes, and migration behavior. The scope and complexity of new user-facing behavior warrant human review.

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

[cursor]

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

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

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

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

We're closing this PR as we clean up the T3 Code backlog. Thank you for taking the time to put this together.

This branch changes the same new-thread picker flow as #4263. We are keeping that unified picker as the active implementation instead of reviewing another competing version.

If you believe we closed this in error, please reopen the PR and leave a comment explaining what we missed.