fix(server): handle localized Windows provider probe output

[raulpesilva]

What Changed

• Fixed Windows provider health checks for codex and claude so localized shell output is decoded correctly instead of showing garbled accented characters in Settings.
• Added a shared server-side path for Windows provider probes that handles Unicode cmd.exe output consistently.
• Expanded Windows "command not found" detection to recognize localized messages, so missing CLIs are reported as unavailable instead of "installed but failed to run."
• Added regression coverage for localized Windows output and provider status handling.

Why

The Settings screen was rendering broken accented characters on Windows because localized cmd.exe output was being decoded incorrectly by the server before it reached the UI.
This also caused a second issue: when codex or claude were missing from PATH, the server could misclassify them as installed but failing to run because the "command not found" check only matched English output. Fixing this at the subprocess boundary keeps the UI simple, makes provider checks more reliable, and ensures the correct status/message is shown across localized Windows environments.

UI Changes

before:

after:

Checklist

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

---

Note

Medium Risk
Changes Windows process spawning and output decoding for provider health checks, which can affect whether codex/claude are detected as installed and how their probe commands execute (shell vs direct). Risk is mitigated by added regression tests but could still vary across Windows locales/encodings.

Overview
Fixes Windows provider health checks so codex/claude probe output is decoded correctly (including UTF-16LE cmd.exe stderr) and missing-CLI errors are recognized even when localized.

Adds shared helpers in providerSnapshot to quote Windows shell arguments, run provider commands via a Windows shell command string when needed, and collect raw output bytes before decoding; ClaudeProvider/CodexProvider now use this shared makeProviderCommand. Test coverage is expanded to validate localized “command not found” detection and UTF-16LE decoding, plus a small test helper cleanup in the web environment catalog tests.

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

Note

Fix Windows provider probe to detect localized 'command not found' stderr output

• Extends isWindowsCommandNotFound in processRunner.ts to match localized error messages (e.g. Portuguese) using a set of regex patterns instead of a single English string.
• Rewrites collectStreamAsString in providerSnapshot.ts to accumulate raw Uint8Array chunks before decoding, enabling correct UTF-16LE decoding of Windows process output across arbitrary chunk boundaries.
• Adds quoteWindowsShellArgument and updates makeProviderCommand to wrap paths with spaces in quotes and set shell: true on Windows, replacing direct ChildProcess.make calls in ClaudeProvider and CodexProvider.
• Behavioral Change: on Windows, provider probe commands now run via the shell with quoted arguments rather than direct process invocation.

^{Macroscope summarized 96b5318.}

[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: 620ebe9c-bbe3-4629-bf8a-e83908ccc45b

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: Needs human review

This PR changes runtime behavior on Windows by modifying how provider commands are spawned (new shell quoting approach) and how process output is decoded (UTF-16LE heuristic detection). While the fix for localized error messages is well-tested and scoped, the changes to command execution and output decoding patterns affect core provider functionality and warrant human review.

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

[raulpesilva]

Maybe this PR ended up a bit larger than ideal, but I think the changes are still clear and easy to follow.
Please feel free to close this PR if you'd prefer a smaller split-up version.

[cursor]

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

[raulpesilva]

#2152

[raulpesilva]

What Changed

• Fixed Windows provider health checks for codex and claude so localized shell output is decoded correctly instead of showing garbled accented characters in Settings.
• Added a shared server-side path for Windows provider probes that handles Unicode cmd.exe output consistently.
• Expanded Windows "command not found" detection to recognize localized messages, so missing CLIs are reported as unavailable instead of "installed but failed to run."
• Added regression coverage for localized Windows output and provider status handling.

Why

The Settings screen was rendering broken accented characters on Windows because localized cmd.exe output was being decoded incorrectly by the server before it reached the UI.
This also caused a second issue: when codex or claude were missing from PATH, the server could misclassify them as installed but failing to run because the "command not found" check only matched English output. Fixing this at the subprocess boundary keeps the UI simple, makes provider checks more reliable, and ensures the correct status/message is shown across localized Windows environments.

UI Changes

before:

after:

Checklist

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

---

Note

Medium Risk
Changes Windows process spawning and output decoding for provider health checks, which can affect whether codex/claude are detected as installed and how their probe commands execute (shell vs direct). Risk is mitigated by added regression tests but could still vary across Windows locales/encodings.

Overview
Fixes Windows provider health checks so codex/claude probe output is decoded correctly (including UTF-16LE cmd.exe stderr) and missing-CLI errors are recognized even when localized.

Adds shared helpers in providerSnapshot to quote Windows shell arguments, run provider commands via a Windows shell command string when needed, and collect raw output bytes before decoding; ClaudeProvider/CodexProvider now use this shared makeProviderCommand. Test coverage is expanded to validate localized “command not found” detection and UTF-16LE decoding, plus a small test helper cleanup in the web environment catalog tests.

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

Note

Fix Windows provider probe to detect localized 'command not found' stderr output

• Extends isWindowsCommandNotFound in processRunner.ts to match localized error messages (e.g. Portuguese) using a set of regex patterns instead of a single English string.
• Rewrites collectStreamAsString in providerSnapshot.ts to accumulate raw Uint8Array chunks before decoding, enabling correct UTF-16LE decoding of Windows process output across arbitrary chunk boundaries.
• Adds quoteWindowsShellArgument and updates makeProviderCommand to wrap paths with spaces in quotes and set shell: true on Windows, replacing direct ChildProcess.make calls in ClaudeProvider and CodexProvider.
• Behavioral Change: on Windows, provider probe commands now run via the shell with quoted arguments rather than direct process invocation.

^{Macroscope summarized 96b5318.}

[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: 620ebe9c-bbe3-4629-bf8a-e83908ccc45b

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: Needs human review

This PR changes runtime behavior on Windows by modifying how provider commands are spawned (new shell quoting approach) and how process output is decoded (UTF-16LE heuristic detection). While the fix for localized error messages is well-tested and scoped, the changes to command execution and output decoding patterns affect core provider functionality and warrant human review.

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

[raulpesilva]

Maybe this PR ended up a bit larger than ideal, but I think the changes are still clear and easy to follow.
Please feel free to close this PR if you'd prefer a smaller split-up version.

[cursor]

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

[raulpesilva]

#2152

[raulpesilva]

What Changed

• Fixed Windows provider health checks for codex and claude so localized shell output is decoded correctly instead of showing garbled accented characters in Settings.
• Added a shared server-side path for Windows provider probes that handles Unicode cmd.exe output consistently.
• Expanded Windows "command not found" detection to recognize localized messages, so missing CLIs are reported as unavailable instead of "installed but failed to run."
• Added regression coverage for localized Windows output and provider status handling.

Why

The Settings screen was rendering broken accented characters on Windows because localized cmd.exe output was being decoded incorrectly by the server before it reached the UI.
This also caused a second issue: when codex or claude were missing from PATH, the server could misclassify them as installed but failing to run because the "command not found" check only matched English output. Fixing this at the subprocess boundary keeps the UI simple, makes provider checks more reliable, and ensures the correct status/message is shown across localized Windows environments.

UI Changes

before:

after:

Checklist

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

---

Note

Medium Risk
Changes Windows process spawning and output decoding for provider health checks, which can affect whether codex/claude are detected as installed and how their probe commands execute (shell vs direct). Risk is mitigated by added regression tests but could still vary across Windows locales/encodings.

Overview
Fixes Windows provider health checks so codex/claude probe output is decoded correctly (including UTF-16LE cmd.exe stderr) and missing-CLI errors are recognized even when localized.

Adds shared helpers in providerSnapshot to quote Windows shell arguments, run provider commands via a Windows shell command string when needed, and collect raw output bytes before decoding; ClaudeProvider/CodexProvider now use this shared makeProviderCommand. Test coverage is expanded to validate localized “command not found” detection and UTF-16LE decoding, plus a small test helper cleanup in the web environment catalog tests.

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

Note

Fix Windows provider probe to detect localized 'command not found' stderr output

• Extends isWindowsCommandNotFound in processRunner.ts to match localized error messages (e.g. Portuguese) using a set of regex patterns instead of a single English string.
• Rewrites collectStreamAsString in providerSnapshot.ts to accumulate raw Uint8Array chunks before decoding, enabling correct UTF-16LE decoding of Windows process output across arbitrary chunk boundaries.
• Adds quoteWindowsShellArgument and updates makeProviderCommand to wrap paths with spaces in quotes and set shell: true on Windows, replacing direct ChildProcess.make calls in ClaudeProvider and CodexProvider.
• Behavioral Change: on Windows, provider probe commands now run via the shell with quoted arguments rather than direct process invocation.

^{Macroscope summarized 96b5318.}

[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: 620ebe9c-bbe3-4629-bf8a-e83908ccc45b

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: Needs human review

This PR changes runtime behavior on Windows by modifying how provider commands are spawned (new shell quoting approach) and how process output is decoded (UTF-16LE heuristic detection). While the fix for localized error messages is well-tested and scoped, the changes to command execution and output decoding patterns affect core provider functionality and warrant human review.

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

[raulpesilva]

Maybe this PR ended up a bit larger than ideal, but I think the changes are still clear and easy to follow.
Please feel free to close this PR if you'd prefer a smaller split-up version.

[cursor]

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

[raulpesilva]

#2152

[raulpesilva]

What Changed

• Fixed Windows provider health checks for codex and claude so localized shell output is decoded correctly instead of showing garbled accented characters in Settings.
• Added a shared server-side path for Windows provider probes that handles Unicode cmd.exe output consistently.
• Expanded Windows "command not found" detection to recognize localized messages, so missing CLIs are reported as unavailable instead of "installed but failed to run."
• Added regression coverage for localized Windows output and provider status handling.

Why

The Settings screen was rendering broken accented characters on Windows because localized cmd.exe output was being decoded incorrectly by the server before it reached the UI.
This also caused a second issue: when codex or claude were missing from PATH, the server could misclassify them as installed but failing to run because the "command not found" check only matched English output. Fixing this at the subprocess boundary keeps the UI simple, makes provider checks more reliable, and ensures the correct status/message is shown across localized Windows environments.

UI Changes

before:

after:

Checklist

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

---

Note

Medium Risk
Changes Windows process spawning and output decoding for provider health checks, which can affect whether codex/claude are detected as installed and how their probe commands execute (shell vs direct). Risk is mitigated by added regression tests but could still vary across Windows locales/encodings.

Overview
Fixes Windows provider health checks so codex/claude probe output is decoded correctly (including UTF-16LE cmd.exe stderr) and missing-CLI errors are recognized even when localized.

Adds shared helpers in providerSnapshot to quote Windows shell arguments, run provider commands via a Windows shell command string when needed, and collect raw output bytes before decoding; ClaudeProvider/CodexProvider now use this shared makeProviderCommand. Test coverage is expanded to validate localized “command not found” detection and UTF-16LE decoding, plus a small test helper cleanup in the web environment catalog tests.

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

Note

Fix Windows provider probe to detect localized 'command not found' stderr output

• Extends isWindowsCommandNotFound in processRunner.ts to match localized error messages (e.g. Portuguese) using a set of regex patterns instead of a single English string.
• Rewrites collectStreamAsString in providerSnapshot.ts to accumulate raw Uint8Array chunks before decoding, enabling correct UTF-16LE decoding of Windows process output across arbitrary chunk boundaries.
• Adds quoteWindowsShellArgument and updates makeProviderCommand to wrap paths with spaces in quotes and set shell: true on Windows, replacing direct ChildProcess.make calls in ClaudeProvider and CodexProvider.
• Behavioral Change: on Windows, provider probe commands now run via the shell with quoted arguments rather than direct process invocation.

^{Macroscope summarized 96b5318.}

[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: 620ebe9c-bbe3-4629-bf8a-e83908ccc45b

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: Needs human review

This PR changes runtime behavior on Windows by modifying how provider commands are spawned (new shell quoting approach) and how process output is decoded (UTF-16LE heuristic detection). While the fix for localized error messages is well-tested and scoped, the changes to command execution and output decoding patterns affect core provider functionality and warrant human review.

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

[raulpesilva]

Maybe this PR ended up a bit larger than ideal, but I think the changes are still clear and easy to follow.
Please feel free to close this PR if you'd prefer a smaller split-up version.

[cursor]

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

[raulpesilva]

#2152

[raulpesilva]

What Changed

• Fixed Windows provider health checks for codex and claude so localized shell output is decoded correctly instead of showing garbled accented characters in Settings.
• Added a shared server-side path for Windows provider probes that handles Unicode cmd.exe output consistently.
• Expanded Windows "command not found" detection to recognize localized messages, so missing CLIs are reported as unavailable instead of "installed but failed to run."
• Added regression coverage for localized Windows output and provider status handling.

Why

The Settings screen was rendering broken accented characters on Windows because localized cmd.exe output was being decoded incorrectly by the server before it reached the UI.
This also caused a second issue: when codex or claude were missing from PATH, the server could misclassify them as installed but failing to run because the "command not found" check only matched English output. Fixing this at the subprocess boundary keeps the UI simple, makes provider checks more reliable, and ensures the correct status/message is shown across localized Windows environments.

UI Changes

before:

after:

Checklist

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

---

Note

Medium Risk
Changes Windows process spawning and output decoding for provider health checks, which can affect whether codex/claude are detected as installed and how their probe commands execute (shell vs direct). Risk is mitigated by added regression tests but could still vary across Windows locales/encodings.

Overview
Fixes Windows provider health checks so codex/claude probe output is decoded correctly (including UTF-16LE cmd.exe stderr) and missing-CLI errors are recognized even when localized.

Adds shared helpers in providerSnapshot to quote Windows shell arguments, run provider commands via a Windows shell command string when needed, and collect raw output bytes before decoding; ClaudeProvider/CodexProvider now use this shared makeProviderCommand. Test coverage is expanded to validate localized “command not found” detection and UTF-16LE decoding, plus a small test helper cleanup in the web environment catalog tests.

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

Note

Fix Windows provider probe to detect localized 'command not found' stderr output

• Extends isWindowsCommandNotFound in processRunner.ts to match localized error messages (e.g. Portuguese) using a set of regex patterns instead of a single English string.
• Rewrites collectStreamAsString in providerSnapshot.ts to accumulate raw Uint8Array chunks before decoding, enabling correct UTF-16LE decoding of Windows process output across arbitrary chunk boundaries.
• Adds quoteWindowsShellArgument and updates makeProviderCommand to wrap paths with spaces in quotes and set shell: true on Windows, replacing direct ChildProcess.make calls in ClaudeProvider and CodexProvider.
• Behavioral Change: on Windows, provider probe commands now run via the shell with quoted arguments rather than direct process invocation.

^{Macroscope summarized 96b5318.}

[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: 620ebe9c-bbe3-4629-bf8a-e83908ccc45b

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: Needs human review

This PR changes runtime behavior on Windows by modifying how provider commands are spawned (new shell quoting approach) and how process output is decoded (UTF-16LE heuristic detection). While the fix for localized error messages is well-tested and scoped, the changes to command execution and output decoding patterns affect core provider functionality and warrant human review.

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

[raulpesilva]

Maybe this PR ended up a bit larger than ideal, but I think the changes are still clear and easy to follow.
Please feel free to close this PR if you'd prefer a smaller split-up version.

[cursor]

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

[raulpesilva]

#2152

[raulpesilva]

What Changed

• Fixed Windows provider health checks for codex and claude so localized shell output is decoded correctly instead of showing garbled accented characters in Settings.
• Added a shared server-side path for Windows provider probes that handles Unicode cmd.exe output consistently.
• Expanded Windows "command not found" detection to recognize localized messages, so missing CLIs are reported as unavailable instead of "installed but failed to run."
• Added regression coverage for localized Windows output and provider status handling.

Why

The Settings screen was rendering broken accented characters on Windows because localized cmd.exe output was being decoded incorrectly by the server before it reached the UI.
This also caused a second issue: when codex or claude were missing from PATH, the server could misclassify them as installed but failing to run because the "command not found" check only matched English output. Fixing this at the subprocess boundary keeps the UI simple, makes provider checks more reliable, and ensures the correct status/message is shown across localized Windows environments.

UI Changes

before:

after:

Checklist

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

---

Note

Medium Risk
Changes Windows process spawning and output decoding for provider health checks, which can affect whether codex/claude are detected as installed and how their probe commands execute (shell vs direct). Risk is mitigated by added regression tests but could still vary across Windows locales/encodings.

Overview
Fixes Windows provider health checks so codex/claude probe output is decoded correctly (including UTF-16LE cmd.exe stderr) and missing-CLI errors are recognized even when localized.

Adds shared helpers in providerSnapshot to quote Windows shell arguments, run provider commands via a Windows shell command string when needed, and collect raw output bytes before decoding; ClaudeProvider/CodexProvider now use this shared makeProviderCommand. Test coverage is expanded to validate localized “command not found” detection and UTF-16LE decoding, plus a small test helper cleanup in the web environment catalog tests.

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

Note

Fix Windows provider probe to detect localized 'command not found' stderr output

• Extends isWindowsCommandNotFound in processRunner.ts to match localized error messages (e.g. Portuguese) using a set of regex patterns instead of a single English string.
• Rewrites collectStreamAsString in providerSnapshot.ts to accumulate raw Uint8Array chunks before decoding, enabling correct UTF-16LE decoding of Windows process output across arbitrary chunk boundaries.
• Adds quoteWindowsShellArgument and updates makeProviderCommand to wrap paths with spaces in quotes and set shell: true on Windows, replacing direct ChildProcess.make calls in ClaudeProvider and CodexProvider.
• Behavioral Change: on Windows, provider probe commands now run via the shell with quoted arguments rather than direct process invocation.

^{Macroscope summarized 96b5318.}

[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: 620ebe9c-bbe3-4629-bf8a-e83908ccc45b

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: Needs human review

This PR changes runtime behavior on Windows by modifying how provider commands are spawned (new shell quoting approach) and how process output is decoded (UTF-16LE heuristic detection). While the fix for localized error messages is well-tested and scoped, the changes to command execution and output decoding patterns affect core provider functionality and warrant human review.

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

[raulpesilva]

Maybe this PR ended up a bit larger than ideal, but I think the changes are still clear and easy to follow.
Please feel free to close this PR if you'd prefer a smaller split-up version.

[cursor]

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

[raulpesilva]

#2152

[raulpesilva]

What Changed

• Fixed Windows provider health checks for codex and claude so localized shell output is decoded correctly instead of showing garbled accented characters in Settings.
• Added a shared server-side path for Windows provider probes that handles Unicode cmd.exe output consistently.
• Expanded Windows "command not found" detection to recognize localized messages, so missing CLIs are reported as unavailable instead of "installed but failed to run."
• Added regression coverage for localized Windows output and provider status handling.

Why

The Settings screen was rendering broken accented characters on Windows because localized cmd.exe output was being decoded incorrectly by the server before it reached the UI.
This also caused a second issue: when codex or claude were missing from PATH, the server could misclassify them as installed but failing to run because the "command not found" check only matched English output. Fixing this at the subprocess boundary keeps the UI simple, makes provider checks more reliable, and ensures the correct status/message is shown across localized Windows environments.

UI Changes

before:

after:

Checklist

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

---

Note

Medium Risk
Changes Windows process spawning and output decoding for provider health checks, which can affect whether codex/claude are detected as installed and how their probe commands execute (shell vs direct). Risk is mitigated by added regression tests but could still vary across Windows locales/encodings.

Overview
Fixes Windows provider health checks so codex/claude probe output is decoded correctly (including UTF-16LE cmd.exe stderr) and missing-CLI errors are recognized even when localized.

Adds shared helpers in providerSnapshot to quote Windows shell arguments, run provider commands via a Windows shell command string when needed, and collect raw output bytes before decoding; ClaudeProvider/CodexProvider now use this shared makeProviderCommand. Test coverage is expanded to validate localized “command not found” detection and UTF-16LE decoding, plus a small test helper cleanup in the web environment catalog tests.

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

Note

Fix Windows provider probe to detect localized 'command not found' stderr output

• Extends isWindowsCommandNotFound in processRunner.ts to match localized error messages (e.g. Portuguese) using a set of regex patterns instead of a single English string.
• Rewrites collectStreamAsString in providerSnapshot.ts to accumulate raw Uint8Array chunks before decoding, enabling correct UTF-16LE decoding of Windows process output across arbitrary chunk boundaries.
• Adds quoteWindowsShellArgument and updates makeProviderCommand to wrap paths with spaces in quotes and set shell: true on Windows, replacing direct ChildProcess.make calls in ClaudeProvider and CodexProvider.
• Behavioral Change: on Windows, provider probe commands now run via the shell with quoted arguments rather than direct process invocation.

^{Macroscope summarized 96b5318.}

[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: 620ebe9c-bbe3-4629-bf8a-e83908ccc45b

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: Needs human review

This PR changes runtime behavior on Windows by modifying how provider commands are spawned (new shell quoting approach) and how process output is decoded (UTF-16LE heuristic detection). While the fix for localized error messages is well-tested and scoped, the changes to command execution and output decoding patterns affect core provider functionality and warrant human review.

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

[raulpesilva]

Maybe this PR ended up a bit larger than ideal, but I think the changes are still clear and easy to follow.
Please feel free to close this PR if you'd prefer a smaller split-up version.

[cursor]

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

[raulpesilva]

#2152

[raulpesilva]

What Changed

• Fixed Windows provider health checks for codex and claude so localized shell output is decoded correctly instead of showing garbled accented characters in Settings.
• Added a shared server-side path for Windows provider probes that handles Unicode cmd.exe output consistently.
• Expanded Windows "command not found" detection to recognize localized messages, so missing CLIs are reported as unavailable instead of "installed but failed to run."
• Added regression coverage for localized Windows output and provider status handling.

Why

The Settings screen was rendering broken accented characters on Windows because localized cmd.exe output was being decoded incorrectly by the server before it reached the UI.
This also caused a second issue: when codex or claude were missing from PATH, the server could misclassify them as installed but failing to run because the "command not found" check only matched English output. Fixing this at the subprocess boundary keeps the UI simple, makes provider checks more reliable, and ensures the correct status/message is shown across localized Windows environments.

UI Changes

before:

after:

Checklist

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

---

Note

Medium Risk
Changes Windows process spawning and output decoding for provider health checks, which can affect whether codex/claude are detected as installed and how their probe commands execute (shell vs direct). Risk is mitigated by added regression tests but could still vary across Windows locales/encodings.

Overview
Fixes Windows provider health checks so codex/claude probe output is decoded correctly (including UTF-16LE cmd.exe stderr) and missing-CLI errors are recognized even when localized.

Adds shared helpers in providerSnapshot to quote Windows shell arguments, run provider commands via a Windows shell command string when needed, and collect raw output bytes before decoding; ClaudeProvider/CodexProvider now use this shared makeProviderCommand. Test coverage is expanded to validate localized “command not found” detection and UTF-16LE decoding, plus a small test helper cleanup in the web environment catalog tests.

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

Note

Fix Windows provider probe to detect localized 'command not found' stderr output

• Extends isWindowsCommandNotFound in processRunner.ts to match localized error messages (e.g. Portuguese) using a set of regex patterns instead of a single English string.
• Rewrites collectStreamAsString in providerSnapshot.ts to accumulate raw Uint8Array chunks before decoding, enabling correct UTF-16LE decoding of Windows process output across arbitrary chunk boundaries.
• Adds quoteWindowsShellArgument and updates makeProviderCommand to wrap paths with spaces in quotes and set shell: true on Windows, replacing direct ChildProcess.make calls in ClaudeProvider and CodexProvider.
• Behavioral Change: on Windows, provider probe commands now run via the shell with quoted arguments rather than direct process invocation.

^{Macroscope summarized 96b5318.}

[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: 620ebe9c-bbe3-4629-bf8a-e83908ccc45b

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: Needs human review

This PR changes runtime behavior on Windows by modifying how provider commands are spawned (new shell quoting approach) and how process output is decoded (UTF-16LE heuristic detection). While the fix for localized error messages is well-tested and scoped, the changes to command execution and output decoding patterns affect core provider functionality and warrant human review.

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

[raulpesilva]

Maybe this PR ended up a bit larger than ideal, but I think the changes are still clear and easy to follow.
Please feel free to close this PR if you'd prefer a smaller split-up version.

[cursor]

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

[raulpesilva]

#2152