Deploy and Host Coshell on Railway

Coshell is a multiplayer cloud terminal for engineering teams working with AI coding agents. Several people can prompt the same live agent session inside one shared environment, with a filesystem, a command execution environment, and an integrated localhost browser. Claude Code and Codex made one person faster. Coshell makes the whole team work with the agent together, across 70+ models.

About Hosting Coshell

This template runs a Coshell drive: the persistent workspace a team's code, environment and agent sessions live in. It is one container with one volume, and no public endpoint. The drive listens only on localhost and reaches Coshell over an outbound WebSocket tunnel, so nothing about it is exposed to the internet and there is no ingress to configure.

You bring one enrollment token from your Coshell dashboard. The container exchanges it for a registered drive on first boot and connects itself, which takes a few minutes on the first build and seconds after that. Redeploying re-attaches to the same drive rather than creating another, so sessions and files survive updates. Coshell never meters a self-hosted drive; you pay Railway for the compute and nothing else.

Common Use Cases

Give a team one shared agent session instead of everyone running their own, so the codebase context is loaded once and stays warm rather than being re-paid per developer
Onboard a new engineer into a working, fully configured environment in seconds instead of a day of local setup
Keep your source on your own infrastructure while still getting multiplayer sessions, access control, attribution and audit

Dependencies for Coshell Hosting

A Coshell account, to mint the enrollment token this template asks for
A persistent volume mounted at /data (included in this template)

Deployment Dependencies

Implementation Details

Set one variable when you deploy:

Variable	Required	Notes
`COSHELL_ENROLL_TOKEN`	yes	From your Coshell dashboard: New drive → Self-hosted → Cloud provider. Single-use, and it expires 15 minutes after minting, so deploy right after you copy it.
`COSHELL_DRIVE_NAME`	no	The drive's display name in Coshell.

Two settings in this template are load-bearing and worth leaving alone:

The volume mounts at /data. Only that path persists. The drive keeps its database, the workspace, HOME, git config and every package anyone installs under it, so a volume mounted anywhere else works until the first restart and then loses everything.

Restart policy is Always, not On Failure. The drive exits with code 0 on some paths, including when it is asked to move to a new runtime version. Under On Failure a zero exit is not a failure, so the service would stay stopped.

Do not add a public domain, and do not set a health check path. The drive needs no inbound traffic, and every route on it requires Coshell-issued auth, so a health check would fail against a perfectly healthy drive.

To update, redeploy so the build re-pulls the drive image. The volume carries the drive forward and it comes back as the same drive on the newer runtime.

Why Deploy Coshell 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 Coshell 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.