[Bug] Fails to execute on Windows due to hardcoded shell paths and invalid command syntax

[gdumoulin]

Description

The claude-commit extension is currently unusable on a native Windows environment due to two related issues:

1. Default execution fails: By default, the extension attempts to execute the claude command via /bin/bash, a path that does not exist on Windows. This results in a spawn /bin/bash ENOENT error.
2. Custom path execution fails: Attempting to work around this by providing a direct, valid Windows path to the claude executable in the settings also fails. The extension wraps the provided path in single quotes ('...') when validating it with the --version command. This syntax is invalid for the Windows shell (cmd.exe or PowerShell), causing a file syntax error.

My local installation of claude-cli is correct and fully functional, as I can run it manually from the command line without any issues.

Steps to Reproduce

This bug manifests in two ways:

Scenario 1: Using the default (empty) path

1. Install the claude-commit extension in VS Code on a Windows machine.
2. Ensure claude-cli is installed and accessible in the system's PATH.
3. Leave the "Claude CLI Path" setting empty.
4. Stage changes in a Git repository and click the "Claude Commit" icon.
5. Result: The following error appears:

   Error: Failed to generate commit message: Claude CLI execution failed: spawn /bin/bash ENOENT
   

Scenario 2: Providing a custom Windows path

1. In the extension settings, set the "Claude CLI Path" to a valid Windows path (e.g., C:\Users\g_dum.A15GDM2023\scoop\apps\nodejs-lts\current\bin\claude).
2. Stage changes and click the "Claude Commit" icon.
3. Result: A different error appears, related to command syntax:

   Error: Failed to generate commit message: Custom Claude CLI path not valid: C:\\Users\\g_dum.A15GDM2023\\scoop\\apps\\nodejs-lts\\current\\bin\\claude - Command failed: 'C:\\Users\\g_dum.A15GDM2023\\scoop\\apps\\nodejs-lts\\current\\bin\\claude' --version
   La syntaxe du nom de fichier, de répertoire ou de volume est incorrecte.
   

Proof of Correct Local Installation

To confirm the issue is not with my local environment, I can execute the command successfully directly in my terminal:

PS C:\Users\g_dum.A15GDM2023\scoop\apps\nodejs-lts\current\bin> .\claude --version
1.0.102 (Claude Code)

Environment

• Operating System: Windows 11
• VS Code Version: 1.103.2
• Extension Version: 1.0.0

[juanlb]

Ok, I'll review this and try to fix it.
Thanks for the feedback.

[rossanodr]

same problem here

[DawidGrzejek]

Claude Commit Extension - Windows Compatibility Fix

Overview

Modified the Claude Commit VS Code extension to support Windows by detecting the platform and using PowerShell instead of bash.

Changes Made to extension.js

1. Added Platform Detection (Line 291)

// Detect platform
const isWindows = process.platform === 'win32';

2. Updated Base64 Decoding Command (Lines 296-304)

Before:

let command = `echo "${base64Prompt}" | base64 -d | ${this.claudePath}`;

After:

let command;
if (isWindows) {
    // PowerShell command for Windows
    command = `[System.Text.Encoding]::UTF8.GetString([System.Convert]::FromBase64String('${base64Prompt}')) | ${this.claudePath}`;
} else {
    // Bash command for Linux/macOS
    command = `echo "${base64Prompt}" | base64 -d | ${this.claudePath}`;
}

3. Updated Shell Selection (Line 322)

Before:

shell: '/bin/bash',

After:

shell: isWindows ? 'powershell.exe' : '/bin/bash',

4. Updated PATH Environment Variable (Lines 324-326)

Before:

PATH: `/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:${process.env.PATH}:${process.env.HOME}/.nvm/versions/node/*/bin`

After:

PATH: isWindows ? process.env.PATH : `/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:${process.env.PATH}:${process.env.HOME}/.nvm/versions/node/*/bin`

5. Skip Unix Shell Detection on Windows (Lines 120 & 147)

Wrapped bash and zsh shell detection in platform checks:

// Try using bash shell (skip on Windows)
if (process.platform !== 'win32') {
    // ... bash detection code ...
}

// Try zsh shell (skip on Windows)
if (process.platform !== 'win32') {
    // ... zsh detection code ...
}

Technical Details

Windows PowerShell Base64 Decoding

The extension now uses .NET's System.Convert.FromBase64String() method available in PowerShell:

[System.Text.Encoding]::UTF8.GetString([System.Convert]::FromBase64String('base64string'))

Cross-Platform Shell Selection

• Windows: powershell.exe
• Linux/macOS: /bin/bash

Testing

After making these changes:

1. Reload VS Code window (Ctrl+Shift+P → "Reload Window")
2. Test the Claude Commit extension on staged or unstaged changes
3. The extension should now successfully execute Claude CLI via PowerShell on

extension.js

Root Cause
The extension was hardcoded to use /bin/bash, which doesn't exist on Windows systems (unless WSL or Git Bash is configured). The fix detects the platform and uses the appropriate shell and commands for each OS.

#3