refactor: drop the Windows PowerShell launcher in favor of Git Bash#192
Merged
Conversation
The PowerShell launcher (scripts/windows/agmsg.ps1 + install-agmsg.ps1) was a thin shim that located Git Bash and forwarded to the Bash scripts. Codex on Windows runs commands through PowerShell, so agents can call the scripts directly via Git Bash (`bash -lc 'scripts/*.sh'`), and delivery hooks are already wrapped for Git Bash by windows_wrap() in delivery.sh. The separate PowerShell reimplementation is now redundant. Removed: - scripts/windows/agmsg.ps1, scripts/windows/install-agmsg.ps1 - docs/windows.md - tests/smoke_windows_powershell.ps1, tests/test_windows_powershell.bats - the PowerShell launcher install step in install.sh - the README "Native Windows / PowerShell" section (replaced with a Git Bash note) Kept (general Windows support): the Bash dispatcher (dispatch.sh), the delivery hook Git Bash wrapping (delivery.sh windows_wrap), the sqlite3 shim, and install.sh's legacy-helper cleanup. BREAKING CHANGE: the `agmsg` PowerShell command is no longer installed. On Windows, call the scripts through Git Bash, e.g. `bash -lc 'scripts/whoami.sh "$(pwd)" codex'`. If a bare `bash` resolves to the WSL shim, pin Git Bash in your PowerShell profile: Set-Alias bash 'C:\Program Files\Git\bin\bash.exe'. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XpJ8VvSV1hNdJWy875V5tm
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rebases #186 by @lucianlamp onto current
mainand resolves the conflicts with the 1.1.0 restructure. Commit authorship is preserved (a8b2795, authored by @lucianlamp).What
Drops the Windows PowerShell launcher in favor of Git Bash:
scripts/windows/agmsg.ps1,install-agmsg.ps1, the PowerShell smoke test, andtests/test_windows_powershell.batsscripts/windows/), deliverycommandWindowswrapping, and legacy helper cleanupdocs/windows.md, README, andllms.txtto make Git Bash the explicit execution pathWhy
PowerShell can't execute bare
.shfiles, and a barebashcan resolve to the WSL shim (separate$HOME/SQLite DB). Pinning the execution path to Git Bash removes that ambiguity.Notes
Supersedes #186 — the fork branch couldn't be force-updated cleanly, so this proxy branch carries @lucianlamp's commit unchanged. #186 will be closed with credit once this lands. Full suite green (the 2 failures are the known load-dependent
test_watchflake, unrelated).