railway setup agent configures Railway agent tooling

Introduced 2026-05-07 · score 0.96

HOW TO USE IT

When Railway agent tooling is not configured, run `railway setup agent -y` to configure detected tools and skip prompts. Use `--agent <name>` to target a tool or `--remote` for the CLI-authenticated hosted MCP setup; MCP can also be installed separately.

WHY THIS HELPS

Set up Railway agent tooling for a coding environment that has not been configured yet.

REQUIREMENTS AND LIMITATIONS

• Version: v4.48.0
• -y, --yes: Skip prompts and accept detected defaults; also used automatically when stdout is not a terminal.
• --agent <agent>: Select a coding tool to configure.
• --remote: Connect to `mcp.railway.com` through the CLI using the `railway login` session; documented as the default and a compatibility alias in current docs.
• Prerequisite: Install the Railway CLI before running setup.
• Prerequisite: Run `railway login` if not authenticated; setup skips the interactive login flow in non-interactive mode.
• `-y/--yes` performs detected-only, non-interactive setup.
• Non-interactive setup is auto-engaged when stdout is not a TTY.
• Codex is skipped under `--remote` because it is stdio-only.
• The interactive harness picker includes Claude Code, Cursor, OpenAI Codex, OpenCode, and the universal `.agents` fallback.
• Docs conflict: Current Railway setup documentation says `--remote` is the default compatibility alias; the v4.48.0 release note describes it as selecting remote MCP instead of local stdio. Current docs may describe newer behavior.

FIRST-PARTY EVIDENCE

• https://github.com/railwayapp/cli/releases/tag/v4.48.0
• https://github.com/railwayapp/cli/pull/872
• https://docs.railway.com/cli/setup
• https://github.com/railwayapp/cli

Check the installed version and the source before using it. Entry JSON

Report a problem with this card