[DOCS] Potentially obsolete executable/executableArgs options in TypeScript SDK

Resolved 💬 3 comments Opened Jan 25, 2026 by coygeek Closed Feb 27, 2026

Documentation Type

unclear/confusing documentation

Documentation Location

https://platform.claude.com/docs/en/agent-sdk/typescript

Section/Topic

Options type reference - executable and executableArgs properties

Current Documentation

| Property | Type | Default | Description |
| :--- | :--- | :--- | :--- |
| executable | 'bun' \| 'deno' \| 'node' | Auto-detected | JavaScript runtime to use |
| executableArgs | string[] | [] | Arguments to pass to the executable |

What's Wrong or Missing?

The SDK documentation elsewhere confirms that Claude Code is now distributed as a native binary (installed via curl/brew), not as a Node.js package. Options for configuring JavaScript runtimes (bun, deno, node) appear to be legacy artifacts from when the CLI was a Node.js package.

This creates confusion:

  1. New users may think they need to configure a JS runtime
  2. The options may not function with the native binary
  3. No documentation explains when/if these options are still relevant

Suggested Improvement

Either:

Option 1 (if deprecated): Remove executable and executableArgs from the documentation, or mark them as deprecated with a note that they only apply to legacy JS-based installations.

Option 2 (if still valid): Add clarification that these options only apply when pathToClaudeCodeExecutable points to a JavaScript script rather than the native binary.

Impact

Medium - Makes feature difficult to understand

Additional Context

  • The migration guide discusses moving from the npm package to the native binary

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗