Greptile Summary

Adds "claude" to the cmdCommands allowlist in resolveWindowsCommandShim, fixing ENOENT errors when spawning the claude-cli provider on Windows. The function is a no-op on non-Windows platforms, so this change has no cross-platform impact.

Confidence Score: 5/5

Safe to merge — minimal, targeted fix with no cross-platform side effects.

Single-line addition to an allowlist with a well-understood, deterministic function. Non-Windows behavior is unchanged. No logic issues or security concerns.

No files require special attention.

_{Reviews (1): Last reviewed commit: "fix: add "claude" to Windows cmdCommands..." | Re-trigger Greptile}

Related work from PRtags group patient-piglet-45hj

Title: Open PR duplicate: Windows claude cmd shim spawning

* This PR

Closing this as duplicate or superseded after Codex automated review.

PR #68849 is a narrow allowlist-only duplicate for the Windows Claude CLI shim bug. Current main still has the bug, but open PR #68819 supersedes this PR by tracking the full supervisor .cmd shim fix plus regression coverage.

Best possible solution:

Close PR #68849 as superseded and keep the remaining review on #68819, or an equivalent full core patch that handles supervisor Windows .cmd shim resolution and regression tests rather than only adding claude to the allowlist.

What I checked:

• Current main still omits claude from supervisor shim allowlist: resolveCommand in the child supervisor still passes only npm, pnpm, yarn, and npx to resolveWindowsCommandShim. (src/process/supervisor/adapters/child.ts:12, c7a0d9b1889c)
• Claude CLI backend uses the bare claude command: The bundled Anthropic CLI backend registers config.command: "claude", matching the failing Windows command path. (extensions/anthropic/cli-backend.ts:29, c7a0d9b1889c)
• CLI runner sends backend command through supervisor child spawn: CLI execution calls supervisor.spawn({ mode: "child", argv: [backend.command, ...args] }), so claude reaches the child adapter. (src/agents/cli-runner/execute.ts:409, c7a0d9b1889c)
• Existing .cmd workaround is not on the supervisor child path: exec.ts documents the Node 18.20.2+ .cmd direct-spawn EINVAL issue and wraps batch commands for runExec/runCommandWithTimeout, but that helper is local to exec.ts and is not used by createChildAdapter. (src/process/exec.ts:44, c7a0d9b1889c)
• PR fix: add "claude" to Windows cmdCommands shim allowlist #68849 is allowlist-only: The target PR changes only src/process/supervisor/adapters/child.ts, adding "claude" to the cmdCommands array, with no regression test or .cmd target resolution. (src/process/supervisor/adapters/child.ts:15, e4201210fad6)
• PR fix: resolve Windows .cmd shims to underlying .exe before spawn #68819 supersedes with the broader fix: Open PR fix: resolve Windows .cmd shims to underlying .exe before spawn #68819 changes the child adapter to call resolveWindowsCmdShimArgv, adds Windows PATH/shim helpers in src/process/windows-command.ts, and adds extensive regression coverage in src/process/windows-command.test.ts. (src/process/windows-command.ts, 192c46a80262)

So I’m closing this here and keeping the remaining discussion on the canonical linked item.

Codex Review notes: model gpt-5.5, reasoning high; reviewed against c7a0d9b1889c.