Skip to content

windows: stop Git Bash expanding '*' in the CLI's arguments (#1369) - #1370

Merged
swapnilpaliwal-sd merged 1 commit into
devfrom
fix/1369-windows-noglob
Sep 26, 2026
Merged

swapnilpaliwal-sd merged 1 commit into
devfrom
fix/1369-windows-noglob

Conversation

@swapnilpaliwal-sd

Copy link
Copy Markdown
Contributor

On Windows, Git Bash expanded * in the arguments the npm launcher and the MCP server hand it, so axiomcode path '*' X reached the CLI as file names. This PR adds noglob to MSYS in the shared launcher environment (withPython), keeping any options the user set.

Verified on Windows Server 2022: axiomcode path * square answered for the file names before this change and for * after. The v0.1.2 release e2e (path '*' leaf) failed on win32-x64 for this reason; linux-x64, linux-arm64, darwin-arm64 and darwin-x64 passed.

Closes #1369

Git Bash's runtime globs the arguments a native Windows process passes
it, since no shell did. The npm launcher and the MCP server start bash
with `*` unquoted, so `axiomcode path '*' X` reached the CLI as the
working directory's file names. The release e2e caught it on its first
Windows run.

withPython, the environment every launcher (CLI, MCP, hooks) hands to
bash, now adds noglob to MSYS on Windows, keeping any MSYS options the
user set. Verified on Windows Server 2022: `axiomcode path * square`
answered for file names before and for `*` after.
@swapnilpaliwal-sd
swapnilpaliwal-sd merged commit ed9c5e5 into dev Sep 26, 2026
8 checks passed
@swapnilpaliwal-sd
swapnilpaliwal-sd deleted the fix/1369-windows-noglob branch September 26, 2026 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

windows: path '*' fails through the npm launcher; Git Bash expands the wildcard into file names

1 participant