railway status accepts explicit project and environment targeting
Introduced 2026-06-24 · score 0.95
HOW TO USE IT
When checking a specific Railway project without relying on the repository’s local link, pass both the project and environment. Add `--json` for JSON output scoped to that environment.
railway status --project <project-id-or-name> --environment <environment>railway status --project <project-id-or-name> --environment <environment> --jsonWHY THIS HELPS
Check a Railway project's status from a coding workflow without relying on the repository's local link state.
REQUIREMENTS AND LIMITATIONS
- Version: v5.23.0
- --project, -p <PROJECT_ID>: Project ID or name to inspect; defaults to the linked project. Requires `--environment` when provided.
- --environment, -e <ENV> (required): Environment to inspect; required when `--project` is used.
- --json: Output in JSON format; with explicit project and environment, output is scoped to that environment.
- Prerequisite: Authenticate with a Railway account before using the CLI (`railway login`).
- `--environment` is required whenever `--project` is used, including JSON output.
FIRST-PARTY EVIDENCE
- https://github.com/railwayapp/cli/releases/tag/v5.23.0
- https://github.com/railwayapp/cli/pull/988
- https://github.com/railwayapp/cli/blob/v5.23.0/src/commands/status.rs
- https://docs.railway.com/cli
Check the installed version and the source before using it. Entry JSON