Use machines the network lends you, lend one of yours, or just tell the Hotline what you want done. They are the same platform seen from three sides, and one account covers all three.
You bring the work; the network brings the hardware. A consumer account starts coding-agent sessions — Claude Code, Codex, Antigravity — on machines other people have donated, or on your own Outposts. Each session is a real shell on a real machine: you watch the terminal live, you can take the keyboard at any time, and what it builds can be published straight to a URL.
Enable the consumer role and download the packA zip on Windows, a tar.gz elsewhere, with your credentials already inside it.
Run it onceIt opens one outbound connection to your region node. No public IP, no inbound firewall rule.
Start a sessionThe node matches you to a free machine that runs the agent you asked for and bridges the two.
Watch, take over, publishLive terminal, shared net-disk, and one-step publishing of anything the agent builds.
Nothing runs on the node itself — it relays. Sessions are scoped to a pool, and a pool can be shared with a teammate as use, manage or delegate.
贡献者
For anyone with a machine that is on anyway
A donor lends one machine and the agent subscription already installed on it. When a consumer needs that agent, the session lands on your box, runs inside a dedicated workspace, and you are paid for it. You keep the machine: the donor program only accepts work while it is running, and stopping it takes you out of rotation.
Ask for the donor roleAn administrator approves it, and picks which agent configurations you may serve.
Download the pack for that configurationOne per agent — Codex, Claude Code or Antigravity — with the launcher for your platform.
Run it and leave it runningIt dials home, reports health, and updates itself when the node ships a new build.
Serve sessions and earnA patrol probes you regularly; a good reliability score means more sessions routed your way.
Sessions are confined to a workspace directory the pack creates. Going offline is a supported action, not a failure: the node stops routing to you and the sessions you were serving end cleanly.
amerc-dialog
For anyone who would rather ask than click
The box at the bottom of the front page is not a search field. It is an agent with hands on your account: it registers machines, builds an Outpost with your credentials already baked in, publishes artifacts and reads back what happened. Anonymous visitors can talk to it too — it simply has fewer tools until you sign in. The same engine can be embedded in your own site as a reception desk.
Ask it somethingType or speak into the dock on the front page. No setup, no install.
It calls tools, not just wordsServer-side tools act on your account; browser-side tools reach the Outpost on your own laptop.
Sign in to widen the toolsetMachines, packages, deployments and artifacts all become things it can do rather than describe.
Put it on your own siteOne script tag with an embed key; your reception pool answers, and traffic is metered by bytes.