windows-agent-shell

Solid

A coding agent on Windows: Git Bash path rewriting, PowerShell quoting and encoding, CRLF. Use when output comes back garbled, or it works here and breaks there.

AI & Automation 633 stars 85 forks Updated today MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
93
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Windows agent shell — traps, and the works-here-breaks-there class **When something works here and breaks there, suspect the environment you did not measure.** A Windows coding agent runs through Git Bash, PowerShell or cmd. Each splits arguments, expands characters, converts paths and decodes text differently. A command right in one can pass with a different meaning in another. **Hold the invocation constant before attributing a change to configuration.** The shell, CLI version, path spelling and line endings are part of the invocation. Every version-specific line carries its version and observation date. Vendors change these monthly; `§ Re-verify` explains how to retest. ## First, know which shell runs the command - **Claude Code's Bash tool on Windows uses Git Bash when installed.** Git Bash is MSYS2. Without Git for Windows it uses PowerShell instead (2.1.120), and with the PowerShell tool enabled PowerShell becomes primary (2.1.126; changelog, read `2026-10-24`). - **Shell-form hooks use Git Bash, or PowerShell when Git Bash is missing.** Cursor runs hook commands through PowerShell; Codex takes a separate `commandWindows`. Apply the `guardrail-hooks` skill for the hook side. - **PowerShell 7 is a separate install and is often absent.** Windows PowerShell 5.1 (`powershell.exe`) ships with Windows; PowerShell 7 uses `pwsh`. A script or instruction saying `pwsh` fails where it is absent. - **Measure the same arguments in the same shell, rather than reasoning.** Run `...

Details

Author
phuryn
Repository
phuryn/product-engineering
Created
2 weeks ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

git-bash-on-windows

Load when an AI coding agent (Claude Code, Hermes, or any other) runs shell commands on Windows through Git Bash or MSYS2, with PowerShell alongside. Triggers: Windows, Git Bash, MSYS, MSYS2, PowerShell, pwsh, path mangling, 'command not found', exit code looks wrong, command fake-succeeded, process won't die, background job died, heredoc broke, backslash disappeared.

0 Updated 2 days ago
dexteon
AI & Automation Listed

windows-agent-automation

Windows-specific traps when an agent or script drives CLIs, schedules jobs, or generates files on Windows — .cmd shims truncating multi-line input, PowerShell 5.1 missing operators, encoding defaults that corrupt output, Task Scheduler instead of cron, and path/credential locations. Use when writing any Python/Node script that shells out on Windows, scheduling a recurring job, debugging "it works when I type it but not from the script", seeing UnicodeEncodeError or garbled characters, or when a subprocess cannot find a command that is clearly on PATH. Every trap here has already cost real hours on this machine.

0 Updated 4 days ago
hellokianben-collab
AI & Automation Listed

windows-shell

Write shell commands that actually run on Windows. Use whenever the working machine is Windows and a command, script, path, or setup step is involved, and whenever a command has already failed with "not recognized", "cannot find path", "No such file or directory", a python3 or NUL problem, or CRLF warnings. Covers PowerShell, cmd, Git Bash, WSL, and the traps that differ between them.

3 Updated 3 months ago
finestructure-ai