Remote Build
Use Atmos Computer and Atmos Relay to build on a remote server—without tunnel software on your client.
Remote build means your Atmos app (Desktop or Web) runs on one device, while projects, terminals, agents, and data live on another machine you added as an Atmos Computer. Everything goes through Atmos Relay, not Ngrok, Tailscale, or Cloudflare Tunnel.
Not the same as Remote Access
Atmos offers two separate remote features—do not use both for the same goal:
| Feature | Settings | What it does |
|---|---|---|
| Atmos Computer (this guide) | Atmos Computer | UI talks to a remote server via Atmos Relay; the server connects outward to Atmos |
| Remote Access (tunneling) | Remote Access (Desktop only) | Shares this machine’s Atmos through Tailscale / Cloudflare / ngrok and a Public URL in the browser |
- Building on a VPS → Atmos Computer only.
- “Let someone open my laptop’s Atmos in a browser” → Remote Access only (feature doc).
You do not need tunnel software on your laptop to Connect to an Atmos Computer.
Overview
Where your work lives
After Connect:
- Workspaces, branches, terminals, and agent history are on that Computer.
- Your laptop or browser is only the client.
- CLI tools you run locally will target the same Computer as the UI when you are connected.
On the machine you are physically using, choose Use locally to work against Atmos on that machine again.
Relay in plain terms
- The remote machine keeps a live link to Atmos Relay.
- You press Connect → Atmos gives your UI a short-lived session to that computer.
- All app actions (chat, terminals, files) go through that relay link to the remote server.
The default relay service is relay.atmos.land (your team may use a custom Atmos cloud URL).
Step 1 — Create an Access Key
- Open Settings → Atmos Computer → Access Key.
- Generate (or paste a long key you already trust).
- Save — ties the key to your Atmos account on this device.
- Copy immediately; it may not be shown again.
Treat the access key like a password.
Step 2 — Register a Computer
This machine (same device as the app)
- Make sure Atmos Server is running on this PC.
- Settings → Atmos Computer → This Computer → turn on registration.
(The UI may say “Register to Remote”—that is Atmos Relay, not Remote Access tunnels.) - Atmos registers this host; My Computers shows Online when the link is up. Use Reconnect if it drops.
Another machine (VPS / remote host)
- Save an access key on the device where you manage computers (e.g. your laptop).
- Install Atmos on the remote host (Getting started).
- In Settings → Register Computer, create a registration code (short-lived, one-time).
- On the remote host, run the install script’s
atmos computer startcommand with that code, or follow the on-screen CLI steps.
You can also pass a one-time registration token when starting the server on that host—remove it after registration succeeds.
Step 3 — Connect from Desktop or Web
- Settings → Atmos Computer → My Computers.
- For a computer that is Online, click Connect.
- The UI reconnects through Atmos Relay; all workspaces now belong to that machine.
If you are on the computer itself, use Use locally instead of Connect.
Offline remote computers stay unavailable until their relay link is active again.
Step 4 — Build remotely
After connecting, use the same workflows as on a local machine:
Security notes
| Topic | What to know |
|---|---|
| Encryption | Traffic is protected in transit by standard TLS, but Atmos does not offer end-to-end encryption where only you can read payloads on the relay today. |
| Who can connect | Anyone with your access key can manage and connect to your computers—guard it like a password. |
| Registration codes | Short-lived and single-use; generate a new one if it expires. |
| Sessions | Connect sessions last about a day; connect again if needed. |
| Revoke | Remove or revoke a computer in My Computers to cut off access. |
Related
- Atmos Computer — feature overview
- Cross-Platform & Remote Access — tunneling for this machine only