Skip to content

phuryn/product-engineering / agent-harness/skills/windows-agent-shell

windows-agent-shell

Unverified

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.

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 python <skill dir>/scripts/probe_argv.py <the same arguments>. It prints exactly what the program receives and which encodings its pipes use.

Paths

  1. Forward slashes, always, in anything a bash shell will read. Bash treats \ as an escape. Write C:/Python313/python.exe; Windows accepts it. Backslashes also fed Claude Code's Windows command analyser and caused permission prompts (observed 2026-08-16).
  2. Uppercase the drive letter for any tool that takes its root from the working directory. Use C:/work/app rather than c:/work/app with npm --prefix. On Vitest, a lowercase drive can give No test suite found, zero tests and exit 1 (observed 2026-08-22). Keep the command shape constant when comparing runs: changed shapes can look like a worker-count cliff or a broken suite.
  3. Prevent Git Bash from rewriting leading-slash arguments passed to native programs. It rewrites any argument starting with / into a Windows path before the program sees it. gh api /repos/owner/name fails with invalid API endpoint: "C:/Program Files/Git/repos/owner/name". --flag=/etc/x arrives as --flag=C:/Program Files/Git/etc/x (verified and observed 2026-10-24, Git 2.49.0, gh 2.100.0). Drop the leading slash (gh api repos/owner/name) or set MSYS_NO_PATHCONV=1 for that command.
  4. Convert Git Bash's /c/x paths before Windows programs open them. Git Bash spells C:/x as /c/x, which Windows programs can't open. Convert paths read from commands (/c/x → C:/x). Claude Code hook-input file paths arrive with backslashes even under Git Bash (docs, read 2026-10-24); normalize before comparing.
  5. A generated file written with the host's separators must not be tracked. Untrack it, don't commit one OS's copy. A sync-generated package manifest can use native separators that the other platform's compiler rejects as invalid escapes. The trap is tracking the generated file at all.
  6. A junction makes a delete reach somewhere else. npm --prefix <worktree> install can create a package junction to another checkout when run from a checkout supplying a package the worktree depends on. Recursive deletion of node_modules, or git worktree remove --force, goes through that junction. Run installs with the target as the process's working directory. List node_modules for junctions before deleting; remove the junction itself first. rmdir on the link doesn't follow it. Then run git worktree remove without --force.

Arguments and quoting

  1. Backticks inside git commit -m "..." are command substitution. Backticked words execute and are replaced by their output, usually nothing, without warning. See § Commit messages for the safe spelling.
  2. PowerShell splits a bare -c.foo=bar token in two. Windows PowerShell 5.1 does this too (reproduced and observed 2026-10-24, 5.1.26100): ["-c", ".a.b=c"] bare, ["-c.a.b=c"] quoted. Quote it, and pin the quoted spelling with a test. A matrix can half-break and look finished: check the assets, not the run. A flag that has never been passed before has never been tested.
  3. Judge native PowerShell calls by $LASTEXITCODE, with stderr non-fatal around them. Under $ErrorActionPreference = "Stop", Windows PowerShell 5.1 turns redirected native stderr into a terminating error. Reproduced 2026-10-24 (5.1.26100): an exit-0 program writing one warning, called with 2>&1, ended the script with NativeCommandError.
  4. In PowerShell, an environment variable set to an empty string is deleted. $env:DATABASE_URL = "" removes it, so a loader such as dotenv fills it back in from .env; a supposedly database-free run reaches the configured database. Bash's DATABASE_URL= cmd passes an empty value instead (reproduced and observed 2026-10-25, 5.1.26100). Set a single space when the code trims values to absent, or pass an explicit flag. When an attempt may have touched a real system, say so in the handoff.
  5. Long PowerShell scripts: launch them from the Bash tool. Claude Code's PowerShell tool capped a call at 10 minutes (observed 2026-09-25), which can kill a release between the tag and the installers. Use powershell.exe -NoProfile -ExecutionPolicy Bypass -File <script> from the Bash tool with a long timeout. This has carried 16-minute runs without interruption.

Encoding and line endings

  1. Never edit a UTF-8 file through Windows PowerShell 5.1's Get-Content. It decodes with the ANSI code page. (Get-Content f -Raw) -replace 'a','b' | Set-Content f -Encoding utf8 gives each § a stray Â. It turns every — into â € ”; -Encoding utf8 makes the write look safe, but the damage is on the read. Reproduced and observed 2026-10-24 (5.1.26100): the write also adds a UTF-8 BOM and trailing CRLF.
    • Edit with the agent's own tool and pass CLI text as a file. Use --body-file or -F body=@file, which reads bytes.
    • Detect encoding damage and line endings with check_text.py. Run python <skill dir>/scripts/check_text.py <files> to flag mojibake, BOM, CRLF and invalid UTF-8.
    • Restore the last good version and redo the edit. Use git checkout <good-ref> -- <file>. Don't reverse double encoding: CP1252's 0x80–0x9F range doesn't round-trip, so reversal loses characters.
  2. Configure Python's piped text as UTF-8 explicitly on Windows. Python otherwise reads and writes pipes in locale-dependent cp1250 or cp1252. PYTHONUTF8=1 uses utf-8 (observed 2026-10-24, Python 3.13.1). In piped scripts, reconfigure stdout and stderr to UTF-8 and decode stdin as UTF-8 bytes, or set PYTHONUTF8=1.
  3. A tool or a delegate can rewrite line endings behind a clean diff. core.autocrlf can normalize CRLF on commit while leaving the working tree wrong despite .gitattributes specifying eol=lf. Source-anchored tests can fail in a file the batch never touched, misleading a delegate into blaming the checkout.
    • Check tracked working copies with git ls-files --eol | grep w/crlf. It lists endings differing from the index. Use check_text.py for untracked files; grep -c $'\r' is not reliable under Git Bash.
    • Fix CRLF with check_text.py --fix-crlf <files>, which changes nothing else.

Claude Code auto mode on Windows Git Bash: version-specific, with an expiry

The rule under the cheat sheet: the analyser must never have to infer anything. Every path, directory and write target appears literally in the command. Retest before carrying these workarounds to a newer version.

Auto mode became native Windows' default in 2.1.233; 2.1.232 added a Windows-only static analyser for Git Bash commands. From observed 2026-08-14, ordinary read-only commands stopped for a manual click. The analyser ran after permission decisions and downgraded allow to ask; neither permissions.allow nor an autoMode entry could clear it.

Two upstream issues were closed on 2026-08-20 as fixed in 2.1.233. Its changelog says cd <dir> && <command> > file no longer stops. The 2.1.232 changes for Cygwin-style symlinks and < file were reverted. Measured on 2.1.233, 2026-08-16, chains without a redirect still prompted. This cheat sheet was measured on 2.1.232/2.1.233, 2026-08-16:

Don'tDo instead
cd <dir> && <cmd>absolute paths, or the tool's own directory flag (below)
S="<path>"; ... > "$S/out.log"the literal path inline
a loop writing "$S/f$i.log"the loop in a script, invoked by its literal path
(, ) or = inside quoted prose (echo "=== check (x) ===")plain words
a heredoc (git commit -F - <<'EOF')the text in a file, passed by path (§ Commit messages)
backslashed pathsforward slashes
one command naming more than 8 paths, or over ~10,000 charactersseveral calls; long briefs in a file
grep, cat, ls through Bashthe agent's own search, glob and read tools, which skip the analyser

Keep independent steps separate and use one command per call. Use ; instead of && when steps are independent. Every extra &&, pipe, glob and quoted regex raised the odds.

Use directory flags for commands resolving configuration from their working directory. Use npm --prefix <dir> run <script>, git -C <dir>, node <absolute script path>, and --cwd <dir> for delegate CLIs. npm --prefix was verified to set the script's own working directory and survive nested npm run. A standalone cd leaving the session's project root was bounced next call with Shell cwd was reset to ... (observed 2026-08-16).

Move loops into scripts without concealing safety-relevant flags from the classifier. A script is fine for moving a loop out of the command. Never use it to hide a safety-relevant flag. It stays on disk and gets read.

Retest the cheat sheet and delete workarounds whose cause is gone. In an auto-mode Windows 11 session on 2.1.310 (observed 2026-10-24), compound commands and heredocs ran without stopping. These included cd <dir> && ls && git log ..., mkdir ... && cd ... && curl -o <file> ..., and heredocs fed to python -. The intervening changelog has heredoc and compound-command fixes in several releases.

Run cd <dir> && sed -n '1,5p' <file> in auto mode on your version. If clean, drop the workaround half: keeping it past its cause uglifies commands for nothing. Keep directory flags, briefs in a file, and dedicated read and search tools regardless; they are correct for other reasons. --cwd keeps a delegate from working in, or resuming a thread from, the wrong repository.

Read auto-mode settings and denial reasons from their effective sources. These facts are not Windows-specific (observed 2026-08-16):

  • autoMode is read only from user settings, never project .claude/settings*.json. Since 2.1.207, a checked-in repository cannot grant itself rules.
  • Include literal "$defaults" when extending an autoMode array. Without it, the array replaces the built-in list. For soft_deny, that silently drops force-push and production-deploy protection. claude auto-mode config shows the result.
  • Read /permissions → Recently denied for a classifier block's real reason. Since 2.1.208, the agent sees only Blocked by classifier.

Commit messages and other text passed to a CLI

Write CLI text to a file and pass it by path. Use git commit -F <file>, gh ... --body-file <file>, or gh api ... -F body=@<file>. The shell expands nothing in the file, and an analyser has nothing to infer.

Use a quoted heredoc where your version accepts it. The usual fix is git commit -F -, never -m "...", because backticks execute and vanish silently (§ Arguments 1). A quoted delimiter (<<'EOF') passes text without expansion. Native Windows auto mode in Claude Code 2.1.232/2.1.233 read heredocs as “expansion obfuscation” and prompted (observed 2026-08-16). On 2.1.310 (observed 2026-10-24), they ran without stopping. Where accepted, git commit -F - <<'EOF' is equally safe.

Never -m with backticks · never text that came through PowerShell 5.1's Get-Content (§ Encoding 1).

Works here, breaks there

When you shell out to someone else's CLI, its version on the target machine is the contract. Local tests and review can pass against tools different from the target's.

  1. Probe the target before building on a third-party binary. Probe the real machine, not the dev box; one command costs a minute.
    • Prefer the oldest surface that answers the question. For example: gh api user --jq .login, which every plausible version has.
    • Branch on the exit code, never on stdout. An error can itself be JSON; treating it as success can report a user called {.
    • Encode the older contract in the test fake. Reject --json the way the old gh auth status version does.
  2. A new value on an existing message is not additive. A new message type is additive: an old receiver doesn't recognise it and drops it. A new value on an existing field reaches the old handler's default branch. Read what it does with an unrecognised value: reject it (safe), map to a default, or half-handle it. The last two need a capability flag, exactly as a new type does.
  3. The dev box's tools are part of what a review can see. Tell the reviewer when the target differs, and explicitly reproduce the target's behaviour in the test. GNU coreutils 9.2 and later exit 1 when mv -n declines to overwrite; Git Bash's mv exits 0 (observed 2026-09-25).

Re-verify

Retest each version-specific fact and replace any line whose behaviour changed. Correct its date too. Delete a workaround whose cause is gone rather than keeping it beside the new fact.

FactObservedRe-test
auto-mode analyser stops cd && cmd, heredocs, variablesobserved on 2.1.232/2.1.233, 2026-08-16; not stopping on 2.1.310, observed 2026-10-24in auto mode on your version: cd <dir> && sed -n '1,5p' <file>, then a heredoc
Git Bash converts /path argumentsobserved on Git 2.49.0, gh 2.100.0, 2026-10-24python <skill dir>/scripts/probe_argv.py /x
PowerShell splits bare -c.a.b=cobserved on PowerShell 7, 2026-08-24; 5.1.26100, observed 2026-10-24probe_argv.py -c.a.b=c from each PowerShell
PS 5.1 Get-Content reads ANSI; Set-Content -Encoding utf8 adds a BOMobserved on 5.1, 2026-07-31; 5.1.26100, observed 2026-10-24round-trip a UTF-8 file, then check_text.py on it
PS 5.1 redirected native stderr is terminating under Stopobserved 2026-08-17; 5.1.26100, observed 2026-10-24a native call that warns on stderr, with 2>&1
PowerShell deletes an env var set to ""observed on 5.1.26100, 2026-10-25$env:X = "x"; $env:X = ""; Test-Path Env:X
Python pipes use the ANSI code pageobserved on Python 3.13.1, 2026-10-24python -c "import sys; print(sys.stdout.encoding)" | cat
PowerShell tool caps a call at 10 minutesobserved 2026-09-25the tools reference, or a long Start-Sleep
Bash tool falls back to PowerShell without Git Bash; PowerShell primary when enabled2.1.120, 2.1.126 (changelog, read 2026-10-24)the changelog
mv -n exit code: GNU 9.2+ exits 1, Git Bash exits 0observed 2026-09-25mv -n a b where b exists, echo $?, on each machine

Each rule's origin, the case that taught it, is in receipts.md beside this file; read it when a rule's edge is unclear.

How you can tell it worked

A probe shows the program received the arguments, paths and text you meant. The command means the same thing in the shell that actually runs it.

Files

FileDoes
scripts/check_text.pyflags mojibake (UTF-8 decoded as CP1252 or CP1250), a UTF-8 BOM, CRLF and invalid UTF-8 in files, directories or a repository's changed and untracked files (--changed); --fix-crlf normalises line endings and nothing else; --self-test checks the checker
scripts/probe_argv.pyprints the arguments a program actually received, its working directory and its pipe encodings, for measuring what a shell did to a command
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).Stars: 195kUpdated Claude CodeCodexVerifiedInstall