Railway shell installer uses a user-owned install directory
Introduced 2026-05-08 · score 0.96
HOW TO USE IT
When elevated permissions are unavailable, install the Railway CLI with the shell installer; it targets `~/.railway/bin` by default or `$RAILWAY_HOME/bin` when `RAILWAY_HOME` is set. The installer also makes the user-owned binary eligible for its self-update behavior. [Official v4.57.0 installer](https://github.com/railwayapp/cli/blob/v4.57.0/install.sh)
curl -fsSL https://railway.com/install.sh | shWHY THIS HELPS
Install the Railway CLI in an agent environment where elevated permissions are unavailable.
BEFORE THIS CHANGE
The `cli.new` flow installed to `/usr/local/bin`, which often required elevated permissions. The release note says shell installs could then fall back to notification-only update behavior.
REQUIREMENTS AND LIMITATIONS
- Version: v4.57.0
- Requires Shell installer (`install.sh`)
- RAILWAY_HOME: When set, the installer uses `$RAILWAY_HOME/bin` as its default binary directory; otherwise it defaults to `$HOME/.railway/bin`.
- When `RAILWAY_HOME` is set, the install path is `$RAILWAY_HOME/bin/railway`.
- The release span links a PR description that is truncated after `## What changed`; additional details are unavailable.
FIRST-PARTY EVIDENCE
- https://github.com/railwayapp/cli/releases/tag/v4.57.0
- https://github.com/railwayapp/cli/pull/888
- https://github.com/railwayapp/cli/blob/v4.57.0/install.sh
Check the installed version and the source before using it. Entry JSON