Error instead of silently failing when browsing an unreachable environment

[colonelpanic8]

What Changed

The add-project browser (⌘K → Add project → Local folder) resolves paths on the selected environment's filesystem via filesystemEnvironment.browse, but never read that query's error. This adds an explicit availability check and fails closed instead of failing silently.

• New pure resolveBrowseAvailability in CommandPalette.logic.ts maps the environment's connection phase (available / offline / connecting / reconnecting / error / connected) onto an Available | Unavailable { message } verdict, carrying the underlying reason when there is one. It is keyed on reachability only — a browse failure on a reachable host means the path does not exist yet (the server returns read_directory_failed for a missing parent), which is exactly the Create & Add case, so it must not gate submission.
• The browse RPC is no longer issued at all unless the environment is connected.
• canSubmitBrowsePath is false when unavailable, which disables the Enter path, the submit button, and the clone-destination step (they share it). This also withholds the "create this folder and add it as a project" affordance, so the UI can never offer to create a directory on a host it failed to inspect.
• The reason renders in the results empty state instead of a blank list.
• handleAddProjectForEnvironment refuses with an explicit toast when the target environment is not connected, reusing the same verdict so the toast states the reason rather than a bare status word. This is the layer that covers the desktop folder-picker entry point, which bypasses the browse UI entirely.
• ChatComposer's @-path mention search dropped its error the same way, so an unreachable environment rendered "No matching files or folders." That reads as a definitive answer to a question we never got to ask; it now surfaces the actual failure.

Why

Browsing resolves paths on a machine that may not be reachable, so "no entries" and "could not ask" are very different answers that looked identical.

Reproduced against a paired remote environment that was then killed: the palette rendered an empty Directories group indistinguishable from an empty directory, showed no reason anywhere, and left the Add button enabled. Pressing Enter did nothing at all — no toast, no error, no state change. The failure was entirely invisible.

FileBrowserPanel and FilePreviewPanel already render .error for project file reads, so the add-project browser and the composer path search were the outliers rather than the convention.

UI Changes

Both captures are the same flow — Add project → the remote environment → Local folder → ~/ — against a paired remote whose backend was killed.

Before	After

Before: empty list, no reason, Add enabled, Enter silently does nothing.
After: Reconnecting to railbird-sf. Reason: Failed to fetch remote environment endpoint http://127.0.0.1:47319/.well-known/t3/environment (HttpClientError: Transport error ...), Add disabled.

Verified live in the web app against two t3 serve instances: the second was paired as a remote environment, confirmed Connected, then killed to produce the unreachable state.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• No animation/interaction change, so no video

Validation:

• vp test run apps/web/src/components/CommandPalette.logic.test.ts (14 tests, 9 new)
• vp run --filter @t3tools/web typecheck (no errors in changed files)
• vp lint on all four changed files (no new findings)
• vp fmt --check on all four changed files

---

Note

Low Risk
Focused UI and guard logic with unit tests; behavior is intentionally fail-closed for unreachable hosts but keeps existing-project open and connected-host folder creation paths.

Overview
Unreachable environments no longer look like empty directories in add-project browse, clone destination pickers, and the chat @ path menu.

The palette adds pure helpers resolveBrowseAvailability and resolveProjectPathActionAvailability: availability follows connection phase only (not browse/RPC errors), so Create & Add still works when a connected host returns read_directory_failed for a path that does not exist yet. Browse RPCs are skipped unless the environment is connected; submit/Enter, directory lists, and create-folder affordances are disabled when unavailable, with the reason in the empty state. handleAddProjectForEnvironment toasts the same message when adding a new path (including desktop folder picker); opening an existing project path stays allowed offline.

ChatComposer path mentions now show workspaceEntries.error instead of a generic “No matching files or folders.” when lookup fails.

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

Note

Show errors instead of silently failing when browsing an unreachable environment

• Adds resolveBrowseAvailability in CommandPalette.logic.ts to compute structured availability and user-facing messages based on the environment's connection phase and error.
• The command palette now suppresses browse queries, hides browse groups, and disables submit actions when the selected environment is not connected.
• The 'Add Project' flow shows an error toast and aborts when the target environment is unreachable, while opening an existing project path is still allowed unconditionally.
• The chat composer's path menu now surfaces the workspace error text instead of the generic 'No matching files or folders.' message when loading fails.

^{Macroscope summarized 0dc4377.}

---

Review follow-up (429e392)

Bugbot caught two issues on the first commit; both are fixed.

Browse errors blocked folder creation (high). Real regression, and my fault for unit-testing that branch instead of exercising it. WorkspaceEntries.browse only swallows EACCES/EPERM to an empty listing — ENOENT propagates as read_directory_failed. Treating that as Unavailable made canSubmitBrowsePath false, so Create & Add could never create a folder that did not already exist. Availability is now keyed on connection phase alone. Verified end to end: on a connected environment ~/brand-new-folder-xyz/ shows an enabled Create & Add, and Enter creates the directory and adds the project. Regression test added pinning connected + browse error to Available.

Toast used status, not reason (medium).connectionStatusText renders the bare phase word, so the refusal really did read "Failed to add project — Available". The guard now reuses the availability verdict and reads " isn't connected."

[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: f5d10fa2-593b-4924-96ac-0f5fc4d02c48

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 is a reasonable bug fix that improves error messaging when environments are unreachable. The logic is straightforward and well-tested. However, the author appears to be new to this codebase (no prior commits found), so a human review is recommended to verify alignment with team conventions.

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

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

Dismissing prior approval to re-evaluate 5d0b5cc

[colonelpanic8]

What Changed

The add-project browser (⌘K → Add project → Local folder) resolves paths on the selected environment's filesystem via filesystemEnvironment.browse, but never read that query's error. This adds an explicit availability check and fails closed instead of failing silently.

• New pure resolveBrowseAvailability in CommandPalette.logic.ts maps the environment's connection phase (available / offline / connecting / reconnecting / error / connected) onto an Available | Unavailable { message } verdict, carrying the underlying reason when there is one. It is keyed on reachability only — a browse failure on a reachable host means the path does not exist yet (the server returns read_directory_failed for a missing parent), which is exactly the Create & Add case, so it must not gate submission.
• The browse RPC is no longer issued at all unless the environment is connected.
• canSubmitBrowsePath is false when unavailable, which disables the Enter path, the submit button, and the clone-destination step (they share it). This also withholds the "create this folder and add it as a project" affordance, so the UI can never offer to create a directory on a host it failed to inspect.
• The reason renders in the results empty state instead of a blank list.
• handleAddProjectForEnvironment refuses with an explicit toast when the target environment is not connected, reusing the same verdict so the toast states the reason rather than a bare status word. This is the layer that covers the desktop folder-picker entry point, which bypasses the browse UI entirely.
• ChatComposer's @-path mention search dropped its error the same way, so an unreachable environment rendered "No matching files or folders." That reads as a definitive answer to a question we never got to ask; it now surfaces the actual failure.

Why

Browsing resolves paths on a machine that may not be reachable, so "no entries" and "could not ask" are very different answers that looked identical.

Reproduced against a paired remote environment that was then killed: the palette rendered an empty Directories group indistinguishable from an empty directory, showed no reason anywhere, and left the Add button enabled. Pressing Enter did nothing at all — no toast, no error, no state change. The failure was entirely invisible.

FileBrowserPanel and FilePreviewPanel already render .error for project file reads, so the add-project browser and the composer path search were the outliers rather than the convention.

UI Changes

Both captures are the same flow — Add project → the remote environment → Local folder → ~/ — against a paired remote whose backend was killed.

Before	After

Before: empty list, no reason, Add enabled, Enter silently does nothing.
After: Reconnecting to railbird-sf. Reason: Failed to fetch remote environment endpoint http://127.0.0.1:47319/.well-known/t3/environment (HttpClientError: Transport error ...), Add disabled.

Verified live in the web app against two t3 serve instances: the second was paired as a remote environment, confirmed Connected, then killed to produce the unreachable state.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• No animation/interaction change, so no video

Validation:

• vp test run apps/web/src/components/CommandPalette.logic.test.ts (14 tests, 9 new)
• vp run --filter @t3tools/web typecheck (no errors in changed files)
• vp lint on all four changed files (no new findings)
• vp fmt --check on all four changed files

---

Note

Low Risk
Focused UI and guard logic with unit tests; behavior is intentionally fail-closed for unreachable hosts but keeps existing-project open and connected-host folder creation paths.

Overview
Unreachable environments no longer look like empty directories in add-project browse, clone destination pickers, and the chat @ path menu.

The palette adds pure helpers resolveBrowseAvailability and resolveProjectPathActionAvailability: availability follows connection phase only (not browse/RPC errors), so Create & Add still works when a connected host returns read_directory_failed for a path that does not exist yet. Browse RPCs are skipped unless the environment is connected; submit/Enter, directory lists, and create-folder affordances are disabled when unavailable, with the reason in the empty state. handleAddProjectForEnvironment toasts the same message when adding a new path (including desktop folder picker); opening an existing project path stays allowed offline.

ChatComposer path mentions now show workspaceEntries.error instead of a generic “No matching files or folders.” when lookup fails.

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

Note

Show errors instead of silently failing when browsing an unreachable environment

• Adds resolveBrowseAvailability in CommandPalette.logic.ts to compute structured availability and user-facing messages based on the environment's connection phase and error.
• The command palette now suppresses browse queries, hides browse groups, and disables submit actions when the selected environment is not connected.
• The 'Add Project' flow shows an error toast and aborts when the target environment is unreachable, while opening an existing project path is still allowed unconditionally.
• The chat composer's path menu now surfaces the workspace error text instead of the generic 'No matching files or folders.' message when loading fails.

^{Macroscope summarized 0dc4377.}

---

Review follow-up (429e392)

Bugbot caught two issues on the first commit; both are fixed.

Browse errors blocked folder creation (high). Real regression, and my fault for unit-testing that branch instead of exercising it. WorkspaceEntries.browse only swallows EACCES/EPERM to an empty listing — ENOENT propagates as read_directory_failed. Treating that as Unavailable made canSubmitBrowsePath false, so Create & Add could never create a folder that did not already exist. Availability is now keyed on connection phase alone. Verified end to end: on a connected environment ~/brand-new-folder-xyz/ shows an enabled Create & Add, and Enter creates the directory and adds the project. Regression test added pinning connected + browse error to Available.

Toast used status, not reason (medium).connectionStatusText renders the bare phase word, so the refusal really did read "Failed to add project — Available". The guard now reuses the availability verdict and reads " isn't connected."

[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: f5d10fa2-593b-4924-96ac-0f5fc4d02c48

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 is a reasonable bug fix that improves error messaging when environments are unreachable. The logic is straightforward and well-tested. However, the author appears to be new to this codebase (no prior commits found), so a human review is recommended to verify alignment with team conventions.

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

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

Dismissing prior approval to re-evaluate 5d0b5cc

[colonelpanic8]

What Changed

The add-project browser (⌘K → Add project → Local folder) resolves paths on the selected environment's filesystem via filesystemEnvironment.browse, but never read that query's error. This adds an explicit availability check and fails closed instead of failing silently.

• New pure resolveBrowseAvailability in CommandPalette.logic.ts maps the environment's connection phase (available / offline / connecting / reconnecting / error / connected) onto an Available | Unavailable { message } verdict, carrying the underlying reason when there is one. It is keyed on reachability only — a browse failure on a reachable host means the path does not exist yet (the server returns read_directory_failed for a missing parent), which is exactly the Create & Add case, so it must not gate submission.
• The browse RPC is no longer issued at all unless the environment is connected.
• canSubmitBrowsePath is false when unavailable, which disables the Enter path, the submit button, and the clone-destination step (they share it). This also withholds the "create this folder and add it as a project" affordance, so the UI can never offer to create a directory on a host it failed to inspect.
• The reason renders in the results empty state instead of a blank list.
• handleAddProjectForEnvironment refuses with an explicit toast when the target environment is not connected, reusing the same verdict so the toast states the reason rather than a bare status word. This is the layer that covers the desktop folder-picker entry point, which bypasses the browse UI entirely.
• ChatComposer's @-path mention search dropped its error the same way, so an unreachable environment rendered "No matching files or folders." That reads as a definitive answer to a question we never got to ask; it now surfaces the actual failure.

Why

Browsing resolves paths on a machine that may not be reachable, so "no entries" and "could not ask" are very different answers that looked identical.

Reproduced against a paired remote environment that was then killed: the palette rendered an empty Directories group indistinguishable from an empty directory, showed no reason anywhere, and left the Add button enabled. Pressing Enter did nothing at all — no toast, no error, no state change. The failure was entirely invisible.

FileBrowserPanel and FilePreviewPanel already render .error for project file reads, so the add-project browser and the composer path search were the outliers rather than the convention.

UI Changes

Both captures are the same flow — Add project → the remote environment → Local folder → ~/ — against a paired remote whose backend was killed.

Before	After

Before: empty list, no reason, Add enabled, Enter silently does nothing.
After: Reconnecting to railbird-sf. Reason: Failed to fetch remote environment endpoint http://127.0.0.1:47319/.well-known/t3/environment (HttpClientError: Transport error ...), Add disabled.

Verified live in the web app against two t3 serve instances: the second was paired as a remote environment, confirmed Connected, then killed to produce the unreachable state.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• No animation/interaction change, so no video

Validation:

• vp test run apps/web/src/components/CommandPalette.logic.test.ts (14 tests, 9 new)
• vp run --filter @t3tools/web typecheck (no errors in changed files)
• vp lint on all four changed files (no new findings)
• vp fmt --check on all four changed files

---

Note

Low Risk
Focused UI and guard logic with unit tests; behavior is intentionally fail-closed for unreachable hosts but keeps existing-project open and connected-host folder creation paths.

Overview
Unreachable environments no longer look like empty directories in add-project browse, clone destination pickers, and the chat @ path menu.

The palette adds pure helpers resolveBrowseAvailability and resolveProjectPathActionAvailability: availability follows connection phase only (not browse/RPC errors), so Create & Add still works when a connected host returns read_directory_failed for a path that does not exist yet. Browse RPCs are skipped unless the environment is connected; submit/Enter, directory lists, and create-folder affordances are disabled when unavailable, with the reason in the empty state. handleAddProjectForEnvironment toasts the same message when adding a new path (including desktop folder picker); opening an existing project path stays allowed offline.

ChatComposer path mentions now show workspaceEntries.error instead of a generic “No matching files or folders.” when lookup fails.

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

Note

Show errors instead of silently failing when browsing an unreachable environment

• Adds resolveBrowseAvailability in CommandPalette.logic.ts to compute structured availability and user-facing messages based on the environment's connection phase and error.
• The command palette now suppresses browse queries, hides browse groups, and disables submit actions when the selected environment is not connected.
• The 'Add Project' flow shows an error toast and aborts when the target environment is unreachable, while opening an existing project path is still allowed unconditionally.
• The chat composer's path menu now surfaces the workspace error text instead of the generic 'No matching files or folders.' message when loading fails.

^{Macroscope summarized 0dc4377.}

---

Review follow-up (429e392)

Bugbot caught two issues on the first commit; both are fixed.

Browse errors blocked folder creation (high). Real regression, and my fault for unit-testing that branch instead of exercising it. WorkspaceEntries.browse only swallows EACCES/EPERM to an empty listing — ENOENT propagates as read_directory_failed. Treating that as Unavailable made canSubmitBrowsePath false, so Create & Add could never create a folder that did not already exist. Availability is now keyed on connection phase alone. Verified end to end: on a connected environment ~/brand-new-folder-xyz/ shows an enabled Create & Add, and Enter creates the directory and adds the project. Regression test added pinning connected + browse error to Available.

Toast used status, not reason (medium).connectionStatusText renders the bare phase word, so the refusal really did read "Failed to add project — Available". The guard now reuses the availability verdict and reads " isn't connected."

[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: f5d10fa2-593b-4924-96ac-0f5fc4d02c48

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 is a reasonable bug fix that improves error messaging when environments are unreachable. The logic is straightforward and well-tested. However, the author appears to be new to this codebase (no prior commits found), so a human review is recommended to verify alignment with team conventions.

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

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

Dismissing prior approval to re-evaluate 5d0b5cc

[colonelpanic8]

What Changed

The add-project browser (⌘K → Add project → Local folder) resolves paths on the selected environment's filesystem via filesystemEnvironment.browse, but never read that query's error. This adds an explicit availability check and fails closed instead of failing silently.

• New pure resolveBrowseAvailability in CommandPalette.logic.ts maps the environment's connection phase (available / offline / connecting / reconnecting / error / connected) onto an Available | Unavailable { message } verdict, carrying the underlying reason when there is one. It is keyed on reachability only — a browse failure on a reachable host means the path does not exist yet (the server returns read_directory_failed for a missing parent), which is exactly the Create & Add case, so it must not gate submission.
• The browse RPC is no longer issued at all unless the environment is connected.
• canSubmitBrowsePath is false when unavailable, which disables the Enter path, the submit button, and the clone-destination step (they share it). This also withholds the "create this folder and add it as a project" affordance, so the UI can never offer to create a directory on a host it failed to inspect.
• The reason renders in the results empty state instead of a blank list.
• handleAddProjectForEnvironment refuses with an explicit toast when the target environment is not connected, reusing the same verdict so the toast states the reason rather than a bare status word. This is the layer that covers the desktop folder-picker entry point, which bypasses the browse UI entirely.
• ChatComposer's @-path mention search dropped its error the same way, so an unreachable environment rendered "No matching files or folders." That reads as a definitive answer to a question we never got to ask; it now surfaces the actual failure.

Why

Browsing resolves paths on a machine that may not be reachable, so "no entries" and "could not ask" are very different answers that looked identical.

Reproduced against a paired remote environment that was then killed: the palette rendered an empty Directories group indistinguishable from an empty directory, showed no reason anywhere, and left the Add button enabled. Pressing Enter did nothing at all — no toast, no error, no state change. The failure was entirely invisible.

FileBrowserPanel and FilePreviewPanel already render .error for project file reads, so the add-project browser and the composer path search were the outliers rather than the convention.

UI Changes

Both captures are the same flow — Add project → the remote environment → Local folder → ~/ — against a paired remote whose backend was killed.

Before	After

Before: empty list, no reason, Add enabled, Enter silently does nothing.
After: Reconnecting to railbird-sf. Reason: Failed to fetch remote environment endpoint http://127.0.0.1:47319/.well-known/t3/environment (HttpClientError: Transport error ...), Add disabled.

Verified live in the web app against two t3 serve instances: the second was paired as a remote environment, confirmed Connected, then killed to produce the unreachable state.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• No animation/interaction change, so no video

Validation:

• vp test run apps/web/src/components/CommandPalette.logic.test.ts (14 tests, 9 new)
• vp run --filter @t3tools/web typecheck (no errors in changed files)
• vp lint on all four changed files (no new findings)
• vp fmt --check on all four changed files

---

Note

Low Risk
Focused UI and guard logic with unit tests; behavior is intentionally fail-closed for unreachable hosts but keeps existing-project open and connected-host folder creation paths.

Overview
Unreachable environments no longer look like empty directories in add-project browse, clone destination pickers, and the chat @ path menu.

The palette adds pure helpers resolveBrowseAvailability and resolveProjectPathActionAvailability: availability follows connection phase only (not browse/RPC errors), so Create & Add still works when a connected host returns read_directory_failed for a path that does not exist yet. Browse RPCs are skipped unless the environment is connected; submit/Enter, directory lists, and create-folder affordances are disabled when unavailable, with the reason in the empty state. handleAddProjectForEnvironment toasts the same message when adding a new path (including desktop folder picker); opening an existing project path stays allowed offline.

ChatComposer path mentions now show workspaceEntries.error instead of a generic “No matching files or folders.” when lookup fails.

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

Note

Show errors instead of silently failing when browsing an unreachable environment

• Adds resolveBrowseAvailability in CommandPalette.logic.ts to compute structured availability and user-facing messages based on the environment's connection phase and error.
• The command palette now suppresses browse queries, hides browse groups, and disables submit actions when the selected environment is not connected.
• The 'Add Project' flow shows an error toast and aborts when the target environment is unreachable, while opening an existing project path is still allowed unconditionally.
• The chat composer's path menu now surfaces the workspace error text instead of the generic 'No matching files or folders.' message when loading fails.

^{Macroscope summarized 0dc4377.}

---

Review follow-up (429e392)

Bugbot caught two issues on the first commit; both are fixed.

Browse errors blocked folder creation (high). Real regression, and my fault for unit-testing that branch instead of exercising it. WorkspaceEntries.browse only swallows EACCES/EPERM to an empty listing — ENOENT propagates as read_directory_failed. Treating that as Unavailable made canSubmitBrowsePath false, so Create & Add could never create a folder that did not already exist. Availability is now keyed on connection phase alone. Verified end to end: on a connected environment ~/brand-new-folder-xyz/ shows an enabled Create & Add, and Enter creates the directory and adds the project. Regression test added pinning connected + browse error to Available.

Toast used status, not reason (medium).connectionStatusText renders the bare phase word, so the refusal really did read "Failed to add project — Available". The guard now reuses the availability verdict and reads " isn't connected."

[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: f5d10fa2-593b-4924-96ac-0f5fc4d02c48

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 is a reasonable bug fix that improves error messaging when environments are unreachable. The logic is straightforward and well-tested. However, the author appears to be new to this codebase (no prior commits found), so a human review is recommended to verify alignment with team conventions.

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

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

Dismissing prior approval to re-evaluate 5d0b5cc

[colonelpanic8]

What Changed

The add-project browser (⌘K → Add project → Local folder) resolves paths on the selected environment's filesystem via filesystemEnvironment.browse, but never read that query's error. This adds an explicit availability check and fails closed instead of failing silently.

• New pure resolveBrowseAvailability in CommandPalette.logic.ts maps the environment's connection phase (available / offline / connecting / reconnecting / error / connected) onto an Available | Unavailable { message } verdict, carrying the underlying reason when there is one. It is keyed on reachability only — a browse failure on a reachable host means the path does not exist yet (the server returns read_directory_failed for a missing parent), which is exactly the Create & Add case, so it must not gate submission.
• The browse RPC is no longer issued at all unless the environment is connected.
• canSubmitBrowsePath is false when unavailable, which disables the Enter path, the submit button, and the clone-destination step (they share it). This also withholds the "create this folder and add it as a project" affordance, so the UI can never offer to create a directory on a host it failed to inspect.
• The reason renders in the results empty state instead of a blank list.
• handleAddProjectForEnvironment refuses with an explicit toast when the target environment is not connected, reusing the same verdict so the toast states the reason rather than a bare status word. This is the layer that covers the desktop folder-picker entry point, which bypasses the browse UI entirely.
• ChatComposer's @-path mention search dropped its error the same way, so an unreachable environment rendered "No matching files or folders." That reads as a definitive answer to a question we never got to ask; it now surfaces the actual failure.

Why

Browsing resolves paths on a machine that may not be reachable, so "no entries" and "could not ask" are very different answers that looked identical.

Reproduced against a paired remote environment that was then killed: the palette rendered an empty Directories group indistinguishable from an empty directory, showed no reason anywhere, and left the Add button enabled. Pressing Enter did nothing at all — no toast, no error, no state change. The failure was entirely invisible.

FileBrowserPanel and FilePreviewPanel already render .error for project file reads, so the add-project browser and the composer path search were the outliers rather than the convention.

UI Changes

Both captures are the same flow — Add project → the remote environment → Local folder → ~/ — against a paired remote whose backend was killed.

Before	After

Before: empty list, no reason, Add enabled, Enter silently does nothing.
After: Reconnecting to railbird-sf. Reason: Failed to fetch remote environment endpoint http://127.0.0.1:47319/.well-known/t3/environment (HttpClientError: Transport error ...), Add disabled.

Verified live in the web app against two t3 serve instances: the second was paired as a remote environment, confirmed Connected, then killed to produce the unreachable state.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• No animation/interaction change, so no video

Validation:

• vp test run apps/web/src/components/CommandPalette.logic.test.ts (14 tests, 9 new)
• vp run --filter @t3tools/web typecheck (no errors in changed files)
• vp lint on all four changed files (no new findings)
• vp fmt --check on all four changed files

---

Note

Low Risk
Focused UI and guard logic with unit tests; behavior is intentionally fail-closed for unreachable hosts but keeps existing-project open and connected-host folder creation paths.

Overview
Unreachable environments no longer look like empty directories in add-project browse, clone destination pickers, and the chat @ path menu.

The palette adds pure helpers resolveBrowseAvailability and resolveProjectPathActionAvailability: availability follows connection phase only (not browse/RPC errors), so Create & Add still works when a connected host returns read_directory_failed for a path that does not exist yet. Browse RPCs are skipped unless the environment is connected; submit/Enter, directory lists, and create-folder affordances are disabled when unavailable, with the reason in the empty state. handleAddProjectForEnvironment toasts the same message when adding a new path (including desktop folder picker); opening an existing project path stays allowed offline.

ChatComposer path mentions now show workspaceEntries.error instead of a generic “No matching files or folders.” when lookup fails.

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

Note

Show errors instead of silently failing when browsing an unreachable environment

• Adds resolveBrowseAvailability in CommandPalette.logic.ts to compute structured availability and user-facing messages based on the environment's connection phase and error.
• The command palette now suppresses browse queries, hides browse groups, and disables submit actions when the selected environment is not connected.
• The 'Add Project' flow shows an error toast and aborts when the target environment is unreachable, while opening an existing project path is still allowed unconditionally.
• The chat composer's path menu now surfaces the workspace error text instead of the generic 'No matching files or folders.' message when loading fails.

^{Macroscope summarized 0dc4377.}

---

Review follow-up (429e392)

Bugbot caught two issues on the first commit; both are fixed.

Browse errors blocked folder creation (high). Real regression, and my fault for unit-testing that branch instead of exercising it. WorkspaceEntries.browse only swallows EACCES/EPERM to an empty listing — ENOENT propagates as read_directory_failed. Treating that as Unavailable made canSubmitBrowsePath false, so Create & Add could never create a folder that did not already exist. Availability is now keyed on connection phase alone. Verified end to end: on a connected environment ~/brand-new-folder-xyz/ shows an enabled Create & Add, and Enter creates the directory and adds the project. Regression test added pinning connected + browse error to Available.

Toast used status, not reason (medium).connectionStatusText renders the bare phase word, so the refusal really did read "Failed to add project — Available". The guard now reuses the availability verdict and reads " isn't connected."

[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: f5d10fa2-593b-4924-96ac-0f5fc4d02c48

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 is a reasonable bug fix that improves error messaging when environments are unreachable. The logic is straightforward and well-tested. However, the author appears to be new to this codebase (no prior commits found), so a human review is recommended to verify alignment with team conventions.

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

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

Dismissing prior approval to re-evaluate 5d0b5cc

[colonelpanic8]

What Changed

The add-project browser (⌘K → Add project → Local folder) resolves paths on the selected environment's filesystem via filesystemEnvironment.browse, but never read that query's error. This adds an explicit availability check and fails closed instead of failing silently.

• New pure resolveBrowseAvailability in CommandPalette.logic.ts maps the environment's connection phase (available / offline / connecting / reconnecting / error / connected) onto an Available | Unavailable { message } verdict, carrying the underlying reason when there is one. It is keyed on reachability only — a browse failure on a reachable host means the path does not exist yet (the server returns read_directory_failed for a missing parent), which is exactly the Create & Add case, so it must not gate submission.
• The browse RPC is no longer issued at all unless the environment is connected.
• canSubmitBrowsePath is false when unavailable, which disables the Enter path, the submit button, and the clone-destination step (they share it). This also withholds the "create this folder and add it as a project" affordance, so the UI can never offer to create a directory on a host it failed to inspect.
• The reason renders in the results empty state instead of a blank list.
• handleAddProjectForEnvironment refuses with an explicit toast when the target environment is not connected, reusing the same verdict so the toast states the reason rather than a bare status word. This is the layer that covers the desktop folder-picker entry point, which bypasses the browse UI entirely.
• ChatComposer's @-path mention search dropped its error the same way, so an unreachable environment rendered "No matching files or folders." That reads as a definitive answer to a question we never got to ask; it now surfaces the actual failure.

Why

Browsing resolves paths on a machine that may not be reachable, so "no entries" and "could not ask" are very different answers that looked identical.

Reproduced against a paired remote environment that was then killed: the palette rendered an empty Directories group indistinguishable from an empty directory, showed no reason anywhere, and left the Add button enabled. Pressing Enter did nothing at all — no toast, no error, no state change. The failure was entirely invisible.

FileBrowserPanel and FilePreviewPanel already render .error for project file reads, so the add-project browser and the composer path search were the outliers rather than the convention.

UI Changes

Both captures are the same flow — Add project → the remote environment → Local folder → ~/ — against a paired remote whose backend was killed.

Before	After

Before: empty list, no reason, Add enabled, Enter silently does nothing.
After: Reconnecting to railbird-sf. Reason: Failed to fetch remote environment endpoint http://127.0.0.1:47319/.well-known/t3/environment (HttpClientError: Transport error ...), Add disabled.

Verified live in the web app against two t3 serve instances: the second was paired as a remote environment, confirmed Connected, then killed to produce the unreachable state.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• No animation/interaction change, so no video

Validation:

• vp test run apps/web/src/components/CommandPalette.logic.test.ts (14 tests, 9 new)
• vp run --filter @t3tools/web typecheck (no errors in changed files)
• vp lint on all four changed files (no new findings)
• vp fmt --check on all four changed files

---

Note

Low Risk
Focused UI and guard logic with unit tests; behavior is intentionally fail-closed for unreachable hosts but keeps existing-project open and connected-host folder creation paths.

Overview
Unreachable environments no longer look like empty directories in add-project browse, clone destination pickers, and the chat @ path menu.

The palette adds pure helpers resolveBrowseAvailability and resolveProjectPathActionAvailability: availability follows connection phase only (not browse/RPC errors), so Create & Add still works when a connected host returns read_directory_failed for a path that does not exist yet. Browse RPCs are skipped unless the environment is connected; submit/Enter, directory lists, and create-folder affordances are disabled when unavailable, with the reason in the empty state. handleAddProjectForEnvironment toasts the same message when adding a new path (including desktop folder picker); opening an existing project path stays allowed offline.

ChatComposer path mentions now show workspaceEntries.error instead of a generic “No matching files or folders.” when lookup fails.

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

Note

Show errors instead of silently failing when browsing an unreachable environment

• Adds resolveBrowseAvailability in CommandPalette.logic.ts to compute structured availability and user-facing messages based on the environment's connection phase and error.
• The command palette now suppresses browse queries, hides browse groups, and disables submit actions when the selected environment is not connected.
• The 'Add Project' flow shows an error toast and aborts when the target environment is unreachable, while opening an existing project path is still allowed unconditionally.
• The chat composer's path menu now surfaces the workspace error text instead of the generic 'No matching files or folders.' message when loading fails.

^{Macroscope summarized 0dc4377.}

---

Review follow-up (429e392)

Bugbot caught two issues on the first commit; both are fixed.

Browse errors blocked folder creation (high). Real regression, and my fault for unit-testing that branch instead of exercising it. WorkspaceEntries.browse only swallows EACCES/EPERM to an empty listing — ENOENT propagates as read_directory_failed. Treating that as Unavailable made canSubmitBrowsePath false, so Create & Add could never create a folder that did not already exist. Availability is now keyed on connection phase alone. Verified end to end: on a connected environment ~/brand-new-folder-xyz/ shows an enabled Create & Add, and Enter creates the directory and adds the project. Regression test added pinning connected + browse error to Available.

Toast used status, not reason (medium).connectionStatusText renders the bare phase word, so the refusal really did read "Failed to add project — Available". The guard now reuses the availability verdict and reads " isn't connected."

[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: f5d10fa2-593b-4924-96ac-0f5fc4d02c48

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 is a reasonable bug fix that improves error messaging when environments are unreachable. The logic is straightforward and well-tested. However, the author appears to be new to this codebase (no prior commits found), so a human review is recommended to verify alignment with team conventions.

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

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

Dismissing prior approval to re-evaluate 5d0b5cc

[colonelpanic8]

What Changed

The add-project browser (⌘K → Add project → Local folder) resolves paths on the selected environment's filesystem via filesystemEnvironment.browse, but never read that query's error. This adds an explicit availability check and fails closed instead of failing silently.

• New pure resolveBrowseAvailability in CommandPalette.logic.ts maps the environment's connection phase (available / offline / connecting / reconnecting / error / connected) onto an Available | Unavailable { message } verdict, carrying the underlying reason when there is one. It is keyed on reachability only — a browse failure on a reachable host means the path does not exist yet (the server returns read_directory_failed for a missing parent), which is exactly the Create & Add case, so it must not gate submission.
• The browse RPC is no longer issued at all unless the environment is connected.
• canSubmitBrowsePath is false when unavailable, which disables the Enter path, the submit button, and the clone-destination step (they share it). This also withholds the "create this folder and add it as a project" affordance, so the UI can never offer to create a directory on a host it failed to inspect.
• The reason renders in the results empty state instead of a blank list.
• handleAddProjectForEnvironment refuses with an explicit toast when the target environment is not connected, reusing the same verdict so the toast states the reason rather than a bare status word. This is the layer that covers the desktop folder-picker entry point, which bypasses the browse UI entirely.
• ChatComposer's @-path mention search dropped its error the same way, so an unreachable environment rendered "No matching files or folders." That reads as a definitive answer to a question we never got to ask; it now surfaces the actual failure.

Why

Browsing resolves paths on a machine that may not be reachable, so "no entries" and "could not ask" are very different answers that looked identical.

Reproduced against a paired remote environment that was then killed: the palette rendered an empty Directories group indistinguishable from an empty directory, showed no reason anywhere, and left the Add button enabled. Pressing Enter did nothing at all — no toast, no error, no state change. The failure was entirely invisible.

FileBrowserPanel and FilePreviewPanel already render .error for project file reads, so the add-project browser and the composer path search were the outliers rather than the convention.

UI Changes

Both captures are the same flow — Add project → the remote environment → Local folder → ~/ — against a paired remote whose backend was killed.

Before	After

Before: empty list, no reason, Add enabled, Enter silently does nothing.
After: Reconnecting to railbird-sf. Reason: Failed to fetch remote environment endpoint http://127.0.0.1:47319/.well-known/t3/environment (HttpClientError: Transport error ...), Add disabled.

Verified live in the web app against two t3 serve instances: the second was paired as a remote environment, confirmed Connected, then killed to produce the unreachable state.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• No animation/interaction change, so no video

Validation:

• vp test run apps/web/src/components/CommandPalette.logic.test.ts (14 tests, 9 new)
• vp run --filter @t3tools/web typecheck (no errors in changed files)
• vp lint on all four changed files (no new findings)
• vp fmt --check on all four changed files

---

Note

Low Risk
Focused UI and guard logic with unit tests; behavior is intentionally fail-closed for unreachable hosts but keeps existing-project open and connected-host folder creation paths.

Overview
Unreachable environments no longer look like empty directories in add-project browse, clone destination pickers, and the chat @ path menu.

The palette adds pure helpers resolveBrowseAvailability and resolveProjectPathActionAvailability: availability follows connection phase only (not browse/RPC errors), so Create & Add still works when a connected host returns read_directory_failed for a path that does not exist yet. Browse RPCs are skipped unless the environment is connected; submit/Enter, directory lists, and create-folder affordances are disabled when unavailable, with the reason in the empty state. handleAddProjectForEnvironment toasts the same message when adding a new path (including desktop folder picker); opening an existing project path stays allowed offline.

ChatComposer path mentions now show workspaceEntries.error instead of a generic “No matching files or folders.” when lookup fails.

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

Note

Show errors instead of silently failing when browsing an unreachable environment

• Adds resolveBrowseAvailability in CommandPalette.logic.ts to compute structured availability and user-facing messages based on the environment's connection phase and error.
• The command palette now suppresses browse queries, hides browse groups, and disables submit actions when the selected environment is not connected.
• The 'Add Project' flow shows an error toast and aborts when the target environment is unreachable, while opening an existing project path is still allowed unconditionally.
• The chat composer's path menu now surfaces the workspace error text instead of the generic 'No matching files or folders.' message when loading fails.

^{Macroscope summarized 0dc4377.}

---

Review follow-up (429e392)

Bugbot caught two issues on the first commit; both are fixed.

Browse errors blocked folder creation (high). Real regression, and my fault for unit-testing that branch instead of exercising it. WorkspaceEntries.browse only swallows EACCES/EPERM to an empty listing — ENOENT propagates as read_directory_failed. Treating that as Unavailable made canSubmitBrowsePath false, so Create & Add could never create a folder that did not already exist. Availability is now keyed on connection phase alone. Verified end to end: on a connected environment ~/brand-new-folder-xyz/ shows an enabled Create & Add, and Enter creates the directory and adds the project. Regression test added pinning connected + browse error to Available.

Toast used status, not reason (medium).connectionStatusText renders the bare phase word, so the refusal really did read "Failed to add project — Available". The guard now reuses the availability verdict and reads " isn't connected."

[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: f5d10fa2-593b-4924-96ac-0f5fc4d02c48

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 is a reasonable bug fix that improves error messaging when environments are unreachable. The logic is straightforward and well-tested. However, the author appears to be new to this codebase (no prior commits found), so a human review is recommended to verify alignment with team conventions.

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

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

Dismissing prior approval to re-evaluate 5d0b5cc

[colonelpanic8]

What Changed

The add-project browser (⌘K → Add project → Local folder) resolves paths on the selected environment's filesystem via filesystemEnvironment.browse, but never read that query's error. This adds an explicit availability check and fails closed instead of failing silently.

• New pure resolveBrowseAvailability in CommandPalette.logic.ts maps the environment's connection phase (available / offline / connecting / reconnecting / error / connected) onto an Available | Unavailable { message } verdict, carrying the underlying reason when there is one. It is keyed on reachability only — a browse failure on a reachable host means the path does not exist yet (the server returns read_directory_failed for a missing parent), which is exactly the Create & Add case, so it must not gate submission.
• The browse RPC is no longer issued at all unless the environment is connected.
• canSubmitBrowsePath is false when unavailable, which disables the Enter path, the submit button, and the clone-destination step (they share it). This also withholds the "create this folder and add it as a project" affordance, so the UI can never offer to create a directory on a host it failed to inspect.
• The reason renders in the results empty state instead of a blank list.
• handleAddProjectForEnvironment refuses with an explicit toast when the target environment is not connected, reusing the same verdict so the toast states the reason rather than a bare status word. This is the layer that covers the desktop folder-picker entry point, which bypasses the browse UI entirely.
• ChatComposer's @-path mention search dropped its error the same way, so an unreachable environment rendered "No matching files or folders." That reads as a definitive answer to a question we never got to ask; it now surfaces the actual failure.

Why

Browsing resolves paths on a machine that may not be reachable, so "no entries" and "could not ask" are very different answers that looked identical.

Reproduced against a paired remote environment that was then killed: the palette rendered an empty Directories group indistinguishable from an empty directory, showed no reason anywhere, and left the Add button enabled. Pressing Enter did nothing at all — no toast, no error, no state change. The failure was entirely invisible.

FileBrowserPanel and FilePreviewPanel already render .error for project file reads, so the add-project browser and the composer path search were the outliers rather than the convention.

UI Changes

Both captures are the same flow — Add project → the remote environment → Local folder → ~/ — against a paired remote whose backend was killed.

Before	After

Before: empty list, no reason, Add enabled, Enter silently does nothing.
After: Reconnecting to railbird-sf. Reason: Failed to fetch remote environment endpoint http://127.0.0.1:47319/.well-known/t3/environment (HttpClientError: Transport error ...), Add disabled.

Verified live in the web app against two t3 serve instances: the second was paired as a remote environment, confirmed Connected, then killed to produce the unreachable state.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• No animation/interaction change, so no video

Validation:

• vp test run apps/web/src/components/CommandPalette.logic.test.ts (14 tests, 9 new)
• vp run --filter @t3tools/web typecheck (no errors in changed files)
• vp lint on all four changed files (no new findings)
• vp fmt --check on all four changed files

---

Note

Low Risk
Focused UI and guard logic with unit tests; behavior is intentionally fail-closed for unreachable hosts but keeps existing-project open and connected-host folder creation paths.

Overview
Unreachable environments no longer look like empty directories in add-project browse, clone destination pickers, and the chat @ path menu.

The palette adds pure helpers resolveBrowseAvailability and resolveProjectPathActionAvailability: availability follows connection phase only (not browse/RPC errors), so Create & Add still works when a connected host returns read_directory_failed for a path that does not exist yet. Browse RPCs are skipped unless the environment is connected; submit/Enter, directory lists, and create-folder affordances are disabled when unavailable, with the reason in the empty state. handleAddProjectForEnvironment toasts the same message when adding a new path (including desktop folder picker); opening an existing project path stays allowed offline.

ChatComposer path mentions now show workspaceEntries.error instead of a generic “No matching files or folders.” when lookup fails.

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

Note

Show errors instead of silently failing when browsing an unreachable environment

• Adds resolveBrowseAvailability in CommandPalette.logic.ts to compute structured availability and user-facing messages based on the environment's connection phase and error.
• The command palette now suppresses browse queries, hides browse groups, and disables submit actions when the selected environment is not connected.
• The 'Add Project' flow shows an error toast and aborts when the target environment is unreachable, while opening an existing project path is still allowed unconditionally.
• The chat composer's path menu now surfaces the workspace error text instead of the generic 'No matching files or folders.' message when loading fails.

^{Macroscope summarized 0dc4377.}

---

Review follow-up (429e392)

Bugbot caught two issues on the first commit; both are fixed.

Browse errors blocked folder creation (high). Real regression, and my fault for unit-testing that branch instead of exercising it. WorkspaceEntries.browse only swallows EACCES/EPERM to an empty listing — ENOENT propagates as read_directory_failed. Treating that as Unavailable made canSubmitBrowsePath false, so Create & Add could never create a folder that did not already exist. Availability is now keyed on connection phase alone. Verified end to end: on a connected environment ~/brand-new-folder-xyz/ shows an enabled Create & Add, and Enter creates the directory and adds the project. Regression test added pinning connected + browse error to Available.

Toast used status, not reason (medium).connectionStatusText renders the bare phase word, so the refusal really did read "Failed to add project — Available". The guard now reuses the availability verdict and reads " isn't connected."

[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: f5d10fa2-593b-4924-96ac-0f5fc4d02c48

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 is a reasonable bug fix that improves error messaging when environments are unreachable. The logic is straightforward and well-tested. However, the author appears to be new to this codebase (no prior commits found), so a human review is recommended to verify alignment with team conventions.

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

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

Dismissing prior approval to re-evaluate 5d0b5cc