railway usage adds workspace usage and limit commands
Introduced 2026-07-08 · score 0.91
HOW TO USE IT
Inspect workspace or project usage for the linked or selected workspace and billing period. Manage compute limits with `railway usage limit` commands; current docs require `--target workspace` when setting limits.
railway usage --workspace <workspace> --period <current|previous|YYYY-MM> --jsonrailway usage projects --project <project> --workspace <workspace> --period <current|previous|YYYY-MM> --jsonrailway usage limit set --target workspace --soft <dollars> --hard <dollars> --workspace <workspace> --jsonWHY THIS HELPS
Inspect usage and compute limits for a Railway workspace or project associated with the repository.
REQUIREMENTS AND LIMITATIONS
- Version: v5.25.0
- --workspace <WORKSPACE>: Workspace name or ID; defaults to the linked project's workspace, or prompts/selects when unlinked.
- --period <PERIOD>: Usage period: `current`, `previous`, or `YYYY-MM`; defaults to `current`. Only applies to summaries and project breakdowns.
- --json: Output in JSON format.
- --project <PROJECT>: Show service-level usage for one project name or ID; cannot be combined with `--limit`.
- --limit <COUNT>: Maximum projects returned; cannot be combined with `--project`.
- --target workspace (required): Selects compute usage limits for `limit set`; current docs also document `workspace` and `agent` targets for status.
- --soft <DOLLARS>: Workspace compute email alert: `0` or a whole-dollar value from $5 to $500,000. When both thresholds are nonzero, hard must be at least soft.
- --hard <DOLLARS>: Workspace compute hard limit: `0` or a whole-dollar value from $10 to $500,000. When both thresholds are nonzero, hard must be at least soft.
- --yes: Confirms limit removal; required in non-interactive sessions.
- Prerequisite: A workspace admin is required to configure usage limits.
- The period may be current, previous, or YYYY-MM.
- Docs conflict: Current docs require `--target workspace` for `limit set`, but the v5.25.0 release-note syntax omits `--target`; current docs also describe agent targets and usage limits not mentioned in the release note. Verify the installed CLI version before relying on the newer syntax.
FIRST-PARTY EVIDENCE
- https://github.com/railwayapp/cli/releases/tag/v5.25.0
- https://github.com/railwayapp/cli/pull/1001
- https://docs.railway.com/cli/usage
- https://docs.railway.com/pricing/cost-control
Check the installed version and the source before using it. Entry JSON