Skip to content

fix(install): wire ~/.bashrc on Windows for Git Bash / Claude Code#46

Open
MasonStation wants to merge 1 commit intomainfrom
fix/install-bashrc-path
Open

fix(install): wire ~/.bashrc on Windows for Git Bash / Claude Code#46
MasonStation wants to merge 1 commit intomainfrom
fix/install-bashrc-path

Conversation

@MasonStation
Copy link
Copy Markdown
Contributor

Summary

  • Mirrors the bashrc-PATH fix already shipped in ashlr-stack's installer.
  • After wiring Windows User PATH, append an idempotent export PATH=... to ~/.bashrc with the unix-style path so Git Bash picks phantom up on next session-start instead of requiring a full terminal + Claude Code restart.
  • Updates the verify message: 'restart your terminal -- and your Claude Code session, if any -- then try: phantom --help'.
  • Both scripts/install.ps1 and apps/web/public/install.ps1 updated; copies are byte-identical.

Why now

Running irm https://phm.dev/install.ps1 | iex from inside Claude Code on Windows installs phantom successfully, but the Claude Code bash session (and any open Git Bash) keeps reporting 'phantom not on PATH' until restart. The bashrc mirror eliminates that friction for the common case.

Test plan

  • PowerShell parse check: both copies OK
  • Run irm https://phm.dev/install.ps1 | iex in a fresh Windows VM, verify ~/.bashrc block appended
  • Open a new Git Bash, verify which phantom resolves without User PATH propagation race

🤖 Generated with Claude Code

Windows User PATH is only inherited by Git Bash at shell-start time, so
already-running bash sessions (Claude Code on Windows shells out through
Git Bash) don't see the new ~/.phantom-secrets/bin entry until restart.

After updating Windows User PATH, also append an idempotent
`export PATH=...` to ~/.bashrc with the unix-style path, so a fresh
Git Bash session picks phantom up without restart-and-restart-again.

Mirrors the same fix already shipped in ashlr-stack's installer.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 27, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
web Ready Ready Preview, Comment Apr 27, 2026 6:21pm

Request Review

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.

1 participant