Check service status, rename services, change service icons, link services, or create services with Docker images. For creating services with local code, prefer railway-new skill. For GitHub repo sources, use railway-new skill to create empty service then railway-environment skill to configure source.
Check status, update properties, and advanced service creation.
Note: For creating services with local code (the common case), prefer the railway-new skill which handles project setup, scaffolding, and service creation together.
For GitHub repo sources: Use railway-new skill to create empty service, then railway-environment skill to configure source.repo via staged changes API.
Create a new service via GraphQL API. There is no CLI command for this.
railway status --json
Extract:
project.id - for creating the serviceenvironment.id - for staging the instance configmutation serviceCreate($input: ServiceCreateInput!) {
serviceCreate(input: $input) {
id
name
}
}
| Field | Type | Description |
|-------|------|-------------|
| projectId | String! | Project ID (required) |
| name | String | Service name (auto-generated if omitted) |
| source.image | String | Docker image (e.g., nginx:latest) |
| source.repo | String | GitHub repo (e.g., user/repo) |
| branch | String | Git branch for repo source |
| environmentId | String | If set and is a fork, only creates in that env |
bash <<'SCRIPT'
${CLAUDE_PLUGIN_ROOT}/skills/lib/railway-api.sh \
'mutation createService($input: ServiceCreateInput!) {
serviceCreate(input: $input) { id name }
}' \
'{"input": {"projectId": "PROJECT_ID"}}'
SCRIPT
bash <<'SCRIPT'
${CLAUDE_PLUGIN_ROOT}/skills/lib/railway-api.sh \
'mutation createService($input: ServiceCreateInput!) {
serviceCreate(input: $input) { id name }
}' \
'{"input": {"projectId": "PROJECT_ID", "name": "my-service", "source": {"image": "nginx:latest"}}}'
SCRIPT
Do NOT use serviceCreate with source.repo - use staged changes API instead.
Flow:
serviceCreate(input: {projectId: "...", name: "my-service"})Use railway-environment skill to configure the service instance:
{
"services": {
"<serviceId>": {
"isCreated": true,
"source": { "image": "nginx:latest" },
"variables": {
"PORT": { "value": "8080" }
}
}
}
}
Critical: Always include isCreated: true for new service instances.
Then use railway-environment skill to apply and deploy.
railway service status --json
Returns current deployment status for the linked service.
railway deployment list --json --limit 5
Show:
| Status | Meaning | |--------|---------| | SUCCESS | Deployed and running | | FAILED | Build or deploy failed | | DEPLOYING | Currently deploying | | BUILDING | Build in progress | | CRASHED | Runtime crash | | REMOVED | Deployment removed |
Update service name or icon via GraphQL API.
railway status --json
Extract service.id from the response.
bash <<'SCRIPT'
${CLAUDE_PLUGIN_ROOT}/skills/lib/railway-api.sh \
'mutation updateService($id: String!, $input: ServiceUpdateInput!) {
serviceUpdate(id: $id, input: $input) { id name }
}' \
'{"id": "SERVICE_ID", "input": {"name": "new-name"}}'
SCRIPT
Icons can be image URLs or animated GIFs.
| Type | Example |
|------|---------|
| Image URL | "icon": "https://example.com/logo.png" |
| Animated GIF | "icon": "https://example.com/animated.gif" |
| Devicons | "icon": "https://devicons.railway.app/github" |
Railway Devicons: Query https://devicons.railway.app/{query} for common developer icons (e.g., github, postgres, redis, nodejs). Browse all at https://devicons.railway.app
bash <<'SCRIPT'
${CLAUDE_PLUGIN_ROOT}/skills/lib/railway-api.sh \
'mutation updateService($id: String!, $input: ServiceUpdateInput!) {
serviceUpdate(id: $id, input: $input) { id icon }
}' \
'{"id": "SERVICE_ID", "input": {"icon": "https://devicons.railway.app/github"}}'
SCRIPT
| Field | Type | Description |
|-------|------|-------------|
| name | String | Service name |
| icon | String | Emoji or image URL (including animated GIFs) |
Switch the linked service for the current directory:
railway service link
Or specify directly:
railway service link <service-name>
isDeleted: trueNo service linked. Run `railway service link` to link a service.
Service exists but has no deployments yet. Deploy with `railway up`.
Service "foo" not found. Check available services with `railway status`.
User may not be in a linked project. Check railway status.
User needs at least DEVELOPER role to create services.
Docker image must be accessible (public or with registry credentials).
Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
Search and analyze your own session logs (older/parent conversations) using jq.
ElevenLabs text-to-speech with mac-style say UX.
Notion API for creating and managing pages, databases, and blocks.
Transcribe audio via OpenAI Audio Transcriptions API (Whisper).
Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Claude Code: use --print --permission-mode bypassPermissions (no PTY). Codex/Pi/OpenCode: pty:true required.
Category:developer
Tags:Railway, Service, Status, Docker, Container, Infrastructure, Management