fix(server): detect localized Windows command errors

[raulpesilva]

What Changed

Expanded Windows command-not-found detection to recognize localized shell error messages in addition to the existing exit-code check and English stderr match.
This keeps missing-command failures on non-English Windows installs flowing through the same normalized error path instead of being surfaced as a generic process failure.

Why

Today we reliably detect Windows "command not found" errors when the process exits with code 9009 or when stderr contains the English is not recognized as an internal or external command message.
That breaks down on localized Windows environments, where the shell returns the same failure in a translated message. By matching the common localized variants as well, we make error handling more consistent and ensure the UI shows the intended missing-command experience across Windows languages.

UI Changes

Before, localized Windows command-not-found failures could fall back to a generic/raw error state.
After, those same failures are classified correctly and shown through the expected missing-command UI.

before:

after:

Checklist

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

---

Note

Low Risk
Low risk: small, isolated change to Windows-only error classification that expands stderr matching; main risk is false positives/negatives in the new regex patterns affecting error messages.

Overview
Windows missing-command detection is broadened.isWindowsCommandNotFound now checks stderr against a small set of localized cmd.exe "not recognized" regex patterns (in addition to the existing win32/9009 logic) so more non-English setups normalize to Command not found.

Test coverage added. A new unit test verifies matching a German localized error string by temporarily setting process.platform to win32.

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

Note

Fix isWindowsCommandNotFound to detect localized Windows command errors

Extends isWindowsCommandNotFound in processRunner.ts to recognize 'command not found' stderr messages from Windows cmd.exe in multiple locales (English, Portuguese, Italian, French, Spanish, German). Previously only a single English regex was used; now a WINDOWS_COMMAND_NOT_FOUND_PATTERNS array is checked via a new hasWindowsCommandNotFoundMessage helper. Exit code 9009 and platform checks are retained.

^{Macroscope summarized 992c15a.}

[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

Run ID: 991bba8f-9068-44ee-bdce-4b041f5679d5

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 and usage tips.}

[macroscopeapp]

Approvability

Verdict: Approved

Small bug fix that adds regex patterns to detect localized Windows "command not found" errors in multiple languages. The change is self-contained, includes a test, and only affects error message pattern matching with no broader runtime impact.

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

Dismissing prior approval to re-evaluate 08e019e

[cursor]

Cursor Bugbot has reviewed your changes 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 c687ec7. Configure here.}

Dismissing prior approval to re-evaluate a1097c5

[raulpesilva]

What Changed

Expanded Windows command-not-found detection to recognize localized shell error messages in addition to the existing exit-code check and English stderr match.
This keeps missing-command failures on non-English Windows installs flowing through the same normalized error path instead of being surfaced as a generic process failure.

Why

Today we reliably detect Windows "command not found" errors when the process exits with code 9009 or when stderr contains the English is not recognized as an internal or external command message.
That breaks down on localized Windows environments, where the shell returns the same failure in a translated message. By matching the common localized variants as well, we make error handling more consistent and ensure the UI shows the intended missing-command experience across Windows languages.

UI Changes

Before, localized Windows command-not-found failures could fall back to a generic/raw error state.
After, those same failures are classified correctly and shown through the expected missing-command UI.

before:

after:

Checklist

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

---

Note

Low Risk
Low risk: small, isolated change to Windows-only error classification that expands stderr matching; main risk is false positives/negatives in the new regex patterns affecting error messages.

Overview
Windows missing-command detection is broadened.isWindowsCommandNotFound now checks stderr against a small set of localized cmd.exe "not recognized" regex patterns (in addition to the existing win32/9009 logic) so more non-English setups normalize to Command not found.

Test coverage added. A new unit test verifies matching a German localized error string by temporarily setting process.platform to win32.

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

Note

Fix isWindowsCommandNotFound to detect localized Windows command errors

Extends isWindowsCommandNotFound in processRunner.ts to recognize 'command not found' stderr messages from Windows cmd.exe in multiple locales (English, Portuguese, Italian, French, Spanish, German). Previously only a single English regex was used; now a WINDOWS_COMMAND_NOT_FOUND_PATTERNS array is checked via a new hasWindowsCommandNotFoundMessage helper. Exit code 9009 and platform checks are retained.

^{Macroscope summarized 992c15a.}

[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

Run ID: 991bba8f-9068-44ee-bdce-4b041f5679d5

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 and usage tips.}

[macroscopeapp]

Approvability

Verdict: Approved

Small bug fix that adds regex patterns to detect localized Windows "command not found" errors in multiple languages. The change is self-contained, includes a test, and only affects error message pattern matching with no broader runtime impact.

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

Dismissing prior approval to re-evaluate 08e019e

[cursor]

Cursor Bugbot has reviewed your changes 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 c687ec7. Configure here.}

Dismissing prior approval to re-evaluate a1097c5

[raulpesilva]

What Changed

Expanded Windows command-not-found detection to recognize localized shell error messages in addition to the existing exit-code check and English stderr match.
This keeps missing-command failures on non-English Windows installs flowing through the same normalized error path instead of being surfaced as a generic process failure.

Why

Today we reliably detect Windows "command not found" errors when the process exits with code 9009 or when stderr contains the English is not recognized as an internal or external command message.
That breaks down on localized Windows environments, where the shell returns the same failure in a translated message. By matching the common localized variants as well, we make error handling more consistent and ensure the UI shows the intended missing-command experience across Windows languages.

UI Changes

Before, localized Windows command-not-found failures could fall back to a generic/raw error state.
After, those same failures are classified correctly and shown through the expected missing-command UI.

before:

after:

Checklist

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

---

Note

Low Risk
Low risk: small, isolated change to Windows-only error classification that expands stderr matching; main risk is false positives/negatives in the new regex patterns affecting error messages.

Overview
Windows missing-command detection is broadened.isWindowsCommandNotFound now checks stderr against a small set of localized cmd.exe "not recognized" regex patterns (in addition to the existing win32/9009 logic) so more non-English setups normalize to Command not found.

Test coverage added. A new unit test verifies matching a German localized error string by temporarily setting process.platform to win32.

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

Note

Fix isWindowsCommandNotFound to detect localized Windows command errors

Extends isWindowsCommandNotFound in processRunner.ts to recognize 'command not found' stderr messages from Windows cmd.exe in multiple locales (English, Portuguese, Italian, French, Spanish, German). Previously only a single English regex was used; now a WINDOWS_COMMAND_NOT_FOUND_PATTERNS array is checked via a new hasWindowsCommandNotFoundMessage helper. Exit code 9009 and platform checks are retained.

^{Macroscope summarized 992c15a.}

[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

Run ID: 991bba8f-9068-44ee-bdce-4b041f5679d5

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 and usage tips.}

[macroscopeapp]

Approvability

Verdict: Approved

Small bug fix that adds regex patterns to detect localized Windows "command not found" errors in multiple languages. The change is self-contained, includes a test, and only affects error message pattern matching with no broader runtime impact.

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

Dismissing prior approval to re-evaluate 08e019e

[cursor]

Cursor Bugbot has reviewed your changes 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 c687ec7. Configure here.}

Dismissing prior approval to re-evaluate a1097c5

[raulpesilva]

What Changed

Expanded Windows command-not-found detection to recognize localized shell error messages in addition to the existing exit-code check and English stderr match.
This keeps missing-command failures on non-English Windows installs flowing through the same normalized error path instead of being surfaced as a generic process failure.

Why

Today we reliably detect Windows "command not found" errors when the process exits with code 9009 or when stderr contains the English is not recognized as an internal or external command message.
That breaks down on localized Windows environments, where the shell returns the same failure in a translated message. By matching the common localized variants as well, we make error handling more consistent and ensure the UI shows the intended missing-command experience across Windows languages.

UI Changes

Before, localized Windows command-not-found failures could fall back to a generic/raw error state.
After, those same failures are classified correctly and shown through the expected missing-command UI.

before:

after:

Checklist

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

---

Note

Low Risk
Low risk: small, isolated change to Windows-only error classification that expands stderr matching; main risk is false positives/negatives in the new regex patterns affecting error messages.

Overview
Windows missing-command detection is broadened.isWindowsCommandNotFound now checks stderr against a small set of localized cmd.exe "not recognized" regex patterns (in addition to the existing win32/9009 logic) so more non-English setups normalize to Command not found.

Test coverage added. A new unit test verifies matching a German localized error string by temporarily setting process.platform to win32.

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

Note

Fix isWindowsCommandNotFound to detect localized Windows command errors

Extends isWindowsCommandNotFound in processRunner.ts to recognize 'command not found' stderr messages from Windows cmd.exe in multiple locales (English, Portuguese, Italian, French, Spanish, German). Previously only a single English regex was used; now a WINDOWS_COMMAND_NOT_FOUND_PATTERNS array is checked via a new hasWindowsCommandNotFoundMessage helper. Exit code 9009 and platform checks are retained.

^{Macroscope summarized 992c15a.}

[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

Run ID: 991bba8f-9068-44ee-bdce-4b041f5679d5

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 and usage tips.}

[macroscopeapp]

Approvability

Verdict: Approved

Small bug fix that adds regex patterns to detect localized Windows "command not found" errors in multiple languages. The change is self-contained, includes a test, and only affects error message pattern matching with no broader runtime impact.

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

Dismissing prior approval to re-evaluate 08e019e

[cursor]

Cursor Bugbot has reviewed your changes 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 c687ec7. Configure here.}

Dismissing prior approval to re-evaluate a1097c5

[raulpesilva]

What Changed

Expanded Windows command-not-found detection to recognize localized shell error messages in addition to the existing exit-code check and English stderr match.
This keeps missing-command failures on non-English Windows installs flowing through the same normalized error path instead of being surfaced as a generic process failure.

Why

Today we reliably detect Windows "command not found" errors when the process exits with code 9009 or when stderr contains the English is not recognized as an internal or external command message.
That breaks down on localized Windows environments, where the shell returns the same failure in a translated message. By matching the common localized variants as well, we make error handling more consistent and ensure the UI shows the intended missing-command experience across Windows languages.

UI Changes

Before, localized Windows command-not-found failures could fall back to a generic/raw error state.
After, those same failures are classified correctly and shown through the expected missing-command UI.

before:

after:

Checklist

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

---

Note

Low Risk
Low risk: small, isolated change to Windows-only error classification that expands stderr matching; main risk is false positives/negatives in the new regex patterns affecting error messages.

Overview
Windows missing-command detection is broadened.isWindowsCommandNotFound now checks stderr against a small set of localized cmd.exe "not recognized" regex patterns (in addition to the existing win32/9009 logic) so more non-English setups normalize to Command not found.

Test coverage added. A new unit test verifies matching a German localized error string by temporarily setting process.platform to win32.

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

Note

Fix isWindowsCommandNotFound to detect localized Windows command errors

Extends isWindowsCommandNotFound in processRunner.ts to recognize 'command not found' stderr messages from Windows cmd.exe in multiple locales (English, Portuguese, Italian, French, Spanish, German). Previously only a single English regex was used; now a WINDOWS_COMMAND_NOT_FOUND_PATTERNS array is checked via a new hasWindowsCommandNotFoundMessage helper. Exit code 9009 and platform checks are retained.

^{Macroscope summarized 992c15a.}

[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

Run ID: 991bba8f-9068-44ee-bdce-4b041f5679d5

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 and usage tips.}

[macroscopeapp]

Approvability

Verdict: Approved

Small bug fix that adds regex patterns to detect localized Windows "command not found" errors in multiple languages. The change is self-contained, includes a test, and only affects error message pattern matching with no broader runtime impact.

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

Dismissing prior approval to re-evaluate 08e019e

[cursor]

Cursor Bugbot has reviewed your changes 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 c687ec7. Configure here.}

Dismissing prior approval to re-evaluate a1097c5

[raulpesilva]

What Changed

Expanded Windows command-not-found detection to recognize localized shell error messages in addition to the existing exit-code check and English stderr match.
This keeps missing-command failures on non-English Windows installs flowing through the same normalized error path instead of being surfaced as a generic process failure.

Why

Today we reliably detect Windows "command not found" errors when the process exits with code 9009 or when stderr contains the English is not recognized as an internal or external command message.
That breaks down on localized Windows environments, where the shell returns the same failure in a translated message. By matching the common localized variants as well, we make error handling more consistent and ensure the UI shows the intended missing-command experience across Windows languages.

UI Changes

Before, localized Windows command-not-found failures could fall back to a generic/raw error state.
After, those same failures are classified correctly and shown through the expected missing-command UI.

before:

after:

Checklist

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

---

Note

Low Risk
Low risk: small, isolated change to Windows-only error classification that expands stderr matching; main risk is false positives/negatives in the new regex patterns affecting error messages.

Overview
Windows missing-command detection is broadened.isWindowsCommandNotFound now checks stderr against a small set of localized cmd.exe "not recognized" regex patterns (in addition to the existing win32/9009 logic) so more non-English setups normalize to Command not found.

Test coverage added. A new unit test verifies matching a German localized error string by temporarily setting process.platform to win32.

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

Note

Fix isWindowsCommandNotFound to detect localized Windows command errors

Extends isWindowsCommandNotFound in processRunner.ts to recognize 'command not found' stderr messages from Windows cmd.exe in multiple locales (English, Portuguese, Italian, French, Spanish, German). Previously only a single English regex was used; now a WINDOWS_COMMAND_NOT_FOUND_PATTERNS array is checked via a new hasWindowsCommandNotFoundMessage helper. Exit code 9009 and platform checks are retained.

^{Macroscope summarized 992c15a.}

[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

Run ID: 991bba8f-9068-44ee-bdce-4b041f5679d5

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 and usage tips.}

[macroscopeapp]

Approvability

Verdict: Approved

Small bug fix that adds regex patterns to detect localized Windows "command not found" errors in multiple languages. The change is self-contained, includes a test, and only affects error message pattern matching with no broader runtime impact.

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

Dismissing prior approval to re-evaluate 08e019e

[cursor]

Cursor Bugbot has reviewed your changes 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 c687ec7. Configure here.}

Dismissing prior approval to re-evaluate a1097c5

[raulpesilva]

What Changed

Expanded Windows command-not-found detection to recognize localized shell error messages in addition to the existing exit-code check and English stderr match.
This keeps missing-command failures on non-English Windows installs flowing through the same normalized error path instead of being surfaced as a generic process failure.

Why

Today we reliably detect Windows "command not found" errors when the process exits with code 9009 or when stderr contains the English is not recognized as an internal or external command message.
That breaks down on localized Windows environments, where the shell returns the same failure in a translated message. By matching the common localized variants as well, we make error handling more consistent and ensure the UI shows the intended missing-command experience across Windows languages.

UI Changes

Before, localized Windows command-not-found failures could fall back to a generic/raw error state.
After, those same failures are classified correctly and shown through the expected missing-command UI.

before:

after:

Checklist

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

---

Note

Low Risk
Low risk: small, isolated change to Windows-only error classification that expands stderr matching; main risk is false positives/negatives in the new regex patterns affecting error messages.

Overview
Windows missing-command detection is broadened.isWindowsCommandNotFound now checks stderr against a small set of localized cmd.exe "not recognized" regex patterns (in addition to the existing win32/9009 logic) so more non-English setups normalize to Command not found.

Test coverage added. A new unit test verifies matching a German localized error string by temporarily setting process.platform to win32.

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

Note

Fix isWindowsCommandNotFound to detect localized Windows command errors

Extends isWindowsCommandNotFound in processRunner.ts to recognize 'command not found' stderr messages from Windows cmd.exe in multiple locales (English, Portuguese, Italian, French, Spanish, German). Previously only a single English regex was used; now a WINDOWS_COMMAND_NOT_FOUND_PATTERNS array is checked via a new hasWindowsCommandNotFoundMessage helper. Exit code 9009 and platform checks are retained.

^{Macroscope summarized 992c15a.}

[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

Run ID: 991bba8f-9068-44ee-bdce-4b041f5679d5

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 and usage tips.}

[macroscopeapp]

Approvability

Verdict: Approved

Small bug fix that adds regex patterns to detect localized Windows "command not found" errors in multiple languages. The change is self-contained, includes a test, and only affects error message pattern matching with no broader runtime impact.

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

Dismissing prior approval to re-evaluate 08e019e

[cursor]

Cursor Bugbot has reviewed your changes 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 c687ec7. Configure here.}

Dismissing prior approval to re-evaluate a1097c5

[raulpesilva]

What Changed

Expanded Windows command-not-found detection to recognize localized shell error messages in addition to the existing exit-code check and English stderr match.
This keeps missing-command failures on non-English Windows installs flowing through the same normalized error path instead of being surfaced as a generic process failure.

Why

Today we reliably detect Windows "command not found" errors when the process exits with code 9009 or when stderr contains the English is not recognized as an internal or external command message.
That breaks down on localized Windows environments, where the shell returns the same failure in a translated message. By matching the common localized variants as well, we make error handling more consistent and ensure the UI shows the intended missing-command experience across Windows languages.

UI Changes

Before, localized Windows command-not-found failures could fall back to a generic/raw error state.
After, those same failures are classified correctly and shown through the expected missing-command UI.

before:

after:

Checklist

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

---

Note

Low Risk
Low risk: small, isolated change to Windows-only error classification that expands stderr matching; main risk is false positives/negatives in the new regex patterns affecting error messages.

Overview
Windows missing-command detection is broadened.isWindowsCommandNotFound now checks stderr against a small set of localized cmd.exe "not recognized" regex patterns (in addition to the existing win32/9009 logic) so more non-English setups normalize to Command not found.

Test coverage added. A new unit test verifies matching a German localized error string by temporarily setting process.platform to win32.

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

Note

Fix isWindowsCommandNotFound to detect localized Windows command errors

Extends isWindowsCommandNotFound in processRunner.ts to recognize 'command not found' stderr messages from Windows cmd.exe in multiple locales (English, Portuguese, Italian, French, Spanish, German). Previously only a single English regex was used; now a WINDOWS_COMMAND_NOT_FOUND_PATTERNS array is checked via a new hasWindowsCommandNotFoundMessage helper. Exit code 9009 and platform checks are retained.

^{Macroscope summarized 992c15a.}

[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

Run ID: 991bba8f-9068-44ee-bdce-4b041f5679d5

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 and usage tips.}

[macroscopeapp]

Approvability

Verdict: Approved

Small bug fix that adds regex patterns to detect localized Windows "command not found" errors in multiple languages. The change is self-contained, includes a test, and only affects error message pattern matching with no broader runtime impact.

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

Dismissing prior approval to re-evaluate 08e019e

[cursor]

Cursor Bugbot has reviewed your changes 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 c687ec7. Configure here.}

Dismissing prior approval to re-evaluate a1097c5