Homepage
Not present in the local metadata.
brew package intelligence
railway
Automic Vault tracks railway because plain text railway cli tokens matters when AI agents run command-line tools on macOS.
overview
What Automic Vault knows about railway
Develop and deploy code with zero configuration
Commands and aliases
No executable aliases were found in the local package database.
radioisotope
Plain Text Railway CLI Tokens
Railway CLI stores login state in JSON config files under ~/.railway, including legacy tokens and OAuth access/refresh tokens. Our isotope stores the Railway configs in the macOS keychain and injects them through a temporary HOME while `railway` runs.
Local README excerpt
Railway Radioisotope
Railway CLI stores login state in JSON config files under ~/.railway, including legacy token values and OAuth accessToken / refreshToken values. The radioisotope moves those configs into the macOS keychain and runs railway with a temporary home directory containing the injected configs.
Caveats
- The production, staging, and development config files are migrated:
config.json, config-staging.json, and config-dev.json.
- Login, logout, token refresh, and project link changes happen in temporary
runtime state and are not persisted back to the keychain.
- Direct execution of the original binary will not receive credentials.
Source: data/radioisotopes/railway/README.md
Coverage source
Caveats
- Runtime login/logout/token refresh changes are not persisted back to keychain.
- Direct execution of the original binary will not receive credentials.
install metadata
Resolver facts
| Package key | brew:railway |
|---|---|
| Last updated | 2026-05-22T10:06:25Z |
| Pulse | updated |
source trail
Generated from repository data
This page is regenerated by scripts/generate-pkg-pages.py. Deployments refuse to publish if www/pkg/ is stale relative to local package data.
Used sources
- Nucleus package database
- local isotope README
- radioisotope security manifest