Railway
Give the Sazabi agent the Railway CLI (railway) in its sandbox to manage deployments and Railway projects.
About
This CLI connection makes the Railway CLI (railway) available in the Sazabi agent's sandbox. The agent can use it for deployments and project management. The tool is baked into the sandbox image; connecting it authenticates (or configures the connection for) the already-installed CLI.
Prerequisites
- A Sazabi project.
- A Railway API token (
RAILWAY_TOKEN). Generate one in your Railway account settings.
Set up in the dashboard
Configure the sandbox in the dashboard under Settings > Sandbox CLIs.
Find Railway in the catalog
In Settings > Sandbox CLIs, find Railway under Browse sandbox CLIs and choose to connect it.
Provide credentials
Enter the required value: RAILWAY_TOKEN (your Railway API token). Save to store it securely; Sazabi injects it into the sandbox when the agent runs.
Set up with the CLI
You can also configure the Railway CLI connection with the Sazabi CLI (installed and authenticated — see CLI reference).
sazabi sandbox-clis set --type railway --env RAILWAY_TOKEN=<your-railway-token>To validate the credentials without saving, run the same command with test in place of set (the test command also requires the --env flags).
Verify
Ask the agent, in a thread, to run the railway CLI (a read-only or status command) and confirm it returns real output. If the command is not found, the CLI connection may not be enabled; if it runs unauthenticated or cannot connect, recheck the credentials.
Troubleshooting
Command not found — Confirm the Railway CLI connection is enabled for the project under Settings > Sandbox CLIs.
Authentication or connection fails — Recheck the credential/connection values under Settings > Sandbox CLIs.