Skip to content

Fix global install: direct symlink and command detection#27

Merged
jonathonbyrdziak merged 1 commit intomasterfrom
feature/fix-global-install
Mar 18, 2026
Merged

Fix global install: direct symlink and command detection#27
jonathonbyrdziak merged 1 commit intomasterfrom
feature/fix-global-install

Conversation

@jonathonbyrdziak
Copy link
Copy Markdown
Contributor

Summary

  • Install script now creates /usr/local/bin/protocol symlink directly instead of delegating to self:global — fixes the chicken-and-egg issue where protocol isn't in PATH yet
  • self:global uses command -v instead of whichwhich on some systems outputs error text like which: no protocol in (...) which was treated as a found command
  • Shell completion message detects the user's actual shell (~/.bashrc vs ~/.zshrc) instead of hardcoding zsh

Test plan

  • Run install script on EC2 (bash) — should create symlink and show .bashrc in message
  • Run protocol self:global when no existing command — should succeed without false conflict
  • Run protocol self:global when symlink exists — should report conflict correctly

🤖 Generated with Claude Code

- Install script: create /usr/local/bin/protocol symlink directly instead
  of delegating to self:global (avoids chicken-and-egg PATH issue)
- self:global: use `command -v` instead of `which` to avoid false
  positives from error messages like "which: no protocol in (...)"
- Detect user's actual shell for the "source ~/.xxxrc" message

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@jonathonbyrdziak jonathonbyrdziak merged commit 8e24542 into master Mar 18, 2026
8 checks passed
@jonathonbyrdziak jonathonbyrdziak deleted the feature/fix-global-install branch March 18, 2026 18:04
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