[DOCS] [VSCode] `claudeProcessWrapper` docs do not explain how to handle extension builds missing a bundled Claude binary

Documentation Type

Other

Documentation Location

https://code.claude.com/docs/en/vs-code

Section/Topic

"Extension settings" table — claudeProcessWrapper row (line 321)

Current Documentation

The claudeProcessWrapper setting is documented as:

Executable path used to launch the Claude process

This description does not explain:

• That VS Code extension builds may not bundle a Claude binary on all platforms
• What happens when the extension activates without a bundled binary (e.g., "Unsupported platform" error)
• That this setting exists precisely so users can point the extension to a separately installed claude binary when the bundled binary is unavailable

What's Wrong or Missing?

A. No documentation of the "bundled binary may be absent" scenario

VS Code extension builds ship a bundled Claude binary for a fixed set of platforms. On platforms outside that set, the extension fails to activate with an "Unsupported platform" error. The docs do not mention this limitation.

B. claudeProcessWrapper purpose is underspecified

The setting's only description is "Executable path used to launch the Claude process." It does not explain that it is the escape hatch for when the extension build does not include a bundled binary, or that users building custom extension bundles can use it to inject a Claude binary path directly.

C. No cross-reference to "Unsupported platform" troubleshooting

The troubleshooting guide mentions "Unsupported platform" in the context of CLI installs (troubleshoot-install.md line 690), but the VS Code extension settings docs do not cross-reference this setting to that troubleshooting path.

Suggested Improvement

Update the claudeProcessWrapper description in the Extension settings table to:

Executable path used to launch the Claude process. Use this when your VS Code extension
build does not bundle a Claude binary for your platform (the extension will fail to
activate with "Unsupported platform"). Point this to a separately installed `claude`
binary to work around the missing bundled binary.

Add a cross-reference note linking to the "Unsupported platform" entry in the troubleshooting guide for further detail on supported platforms.

Impact

Medium - Makes feature difficult to understand

Additional Context

Changelog entry (v2.1.133):

[VSCode] Fixed claudeProcessWrapper failing with Unsupported platform when the extension build doesn't bundle a Claude binary

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/vs-code | 321 | claudeProcessWrapper row in Extension settings table |
| https://code.claude.com/docs/en/troubleshoot-install | 690 | "Unsupported platform" entry (CLI-focused; extension not mentioned) |

Total scope: 2 pages affected