Deploy Gas Town

Multi-agent coding workspace: a Mayor coordinating Claude Code agents

Deploy Gas Town

Just deployed

Deploy and Host Gas Town on Railway

Gas Town is a multi-agent workspace for coding agents. A Mayor agent breaks work into beads (issues) and convoys, and dispatches worker agents (polecats, crew, witnesses, a refinery) that run Claude Code in tmux sessions against your git repositories, with state tracked in a Dolt database.

About Hosting Gas Town

This template builds the official Gas Town image (Dockerfile, based on Docker's Claude Code sandbox image with Go, Dolt, beads and tmux) and runs it as an always-on workspace:

  • The Gas Town HQ at /gt and the agent home folder (Claude Code login, git and gh credentials) on a persistent volume
  • The gt dashboard web UI on your public domain, behind HTTP Basic auth with a generated password
  • gt install runs on every start, like the upstream Docker setup, and the beads database is migrated to the installed bd version
  • Agents run as the unprivileged agent user

The first build takes several minutes.

After deploy:

  1. Open https://YOUR-RAILWAY-DOMAIN and sign in as GASTOWN_DASHBOARD_USER with GASTOWN_DASHBOARD_PASSWORD from the service Variables tab.
  2. Open a shell in the container with the Railway CLI: railway ssh, then cd /gt.
  3. Sign in to Claude Code once: run claude and follow the login. The session is stored on the volume.
  4. Optional: gh auth login for private GitHub repositories.
  5. Add a project and start the town: gt rig add myproject https://github.com/you/repo.git, gt enable, gt up --restore, then gt mayor attach to talk to the Mayor.
  6. Watch agents, convoys and merge queues in the dashboard.

Common Use Cases

  • Run a fleet of Claude Code agents on a repository around the clock
  • Break a large change into tracked beads and convoys handled in parallel
  • Keep long agent sessions running away from your laptop
  • Monitor agents, queues and escalations from a browser

Dependencies for Gas Town Hosting

Deployment Dependencies

Implementation Details

  • Upstream treats the dashboard as a trusted local surface (it can run gt commands). Here it listens on loopback only, and a small Node proxy (GASTOWN_AUTH_PROXY) in front of it requires the password on every request; /healthz is the only open path.
  • Railway allows one volume per service, so GASTOWN_BOOT keeps both /gt and /home/agent under /data with symlinks. The home folder is copied from the image on first boot, the same as the upstream agent-home volume.
  • The image installs the latest bd release, whose schema is newer than the database gt install creates, so the start script runs bd migrate schema before starting the dashboard.
  • Agents can run many processes; give the service enough memory for the number of workers you start.

Why Deploy Gas Town on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Gas Town on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.


Template Content

More templates in this category

View Template
Chat Chat
Chat Chat, your own unified chat and search to AI platform.

okisdev
117
View Template
Weaviate
Vector database with hybrid search and an API key-protected API

GitHub Locker
1
View Template
Möbius Personal AI OS
Self-hosted AI agent that builds and runs apps for you, with memory.

bento
1