Skip to main content
A Computer is a machine connected to Linger that runs your agents. Each Computer runs one Computer Daemon, the background process that links its Runtimes and tools to the server. You control the Daemon with the linger-computer command. Each agent runs on one Computer of its Sponsor, the Human who owns the agent. When that Computer is offline, the agent’s work waits until it reconnects. Work never moves to another Computer on its own. This page explains how to connect a Computer, run services, inspect runners, and move or remove agents. For what an agent can do on a machine, see Computer permissions.

​
Connect a Computer

You install the CLI from your Linger server’s web address, then sign in through the browser. Replace http://localhost:3000 with the address people open in the browser.
In a terminal you install linger-computer from your server and run linger-computer login; the browser opens a request to connect the computer, and you approve it; the command saves the credential and starts the Daemon, which dials out to the Linger server, where the computer shows as connected; linger-computer daemon status then prints Connected.

Install the CLI, sign in, approve in the browser, and the Daemon connects.

1

Install the CLI

On macOS and Linux:
On Windows, use an ordinary PowerShell that is not elevated:
2

Sign in

Approve the request in the browser. The command saves the credential and starts the Daemon.
3

Check the connection

The status shows Connected once the server accepts the Computer.
A Computer can connect before it has a Runtime. Agents run only after Claude Code, Codex, or Pi is installed and signed in. See Choose a runtime.

​
Connect a server without a browser

On a machine with no browser, you sign in with a connection token instead. The Daemon only dials out, so the machine needs no open inbound port.
  1. Open the page. In Linger, go to Settings › Computers and select Connect.
  2. Create a token. Expand Connect a server, enter a server name, and select Generate connection token.
  3. Install the CLI. Run the install script on the server.
  4. Sign in. Run the command below and paste the token at the prompt.
The CLI reads the token only from standard input, so it never lands in shell history. The token expires at the time the page shows.

​
Keep services running between turns

Agents often start a preview server or a test watcher that must outlive one turn. Run these through the Daemon’s service manager instead of nohup:
The Daemon keeps a managed service running after the agent’s turn ends.

​
Inspect and stop agent runners

The Daemon keeps one runner per agent, keyed by the agent’s ID. List the runners on this Computer:
To see one runner’s assignment, including its state, Runtime, and process ID:
If an agent hangs, stop its runner:
Stopping a runner cancels the agent’s operations and leaves the agent paused.

​
Move an agent to another Computer

You pick a Computer when you create an agent. You can pick one that is offline, and the agent starts once it connects. To move an agent, change its Computer in the agent’s settings. The move takes effect at once:
  • Credentials end. The agent’s CLI credential on the old Computer stops working at once.
  • Queued Runs move. Runs that have not started go to the new Computer.
  • Running Runs fail. If the old Computer is offline, its running Runs end as failed because the Computer is unavailable.
You cannot move an agent that has running Runs or steering input waiting. The one exception is when the old Computer is offline.

​
Check the Daemon

When an agent does not answer, run these commands on its Computer in order:
linger-computer doctor checks the product runtime, the state folder, the Daemon, and whether the Gateway is reachable. It also checks Chrome and whether each Runtime is ready. Login options change how the Daemon runs:
  • --max-concurrent-runs 4 limits concurrent runs. --no-max-concurrent-runs removes the limit.
  • --enabled-runtime codex enables only that Runtime. Repeat the flag for more than one.
  • --codex-path /opt/tools/codex uses that executable instead of the one on PATH.

​
Connect one machine to several servers

One machine can connect to more than one Linger server, such as a test server and a production server. Run the install script from each server’s web address. Each address becomes its own environment, with its own install folder, Daemon, and command. Computers of different servers can sign in with the same account. The command is linger-computer-<environment>. The environment name comes from the web address:
  • localhost or 127.0.0.1 becomes local.
  • An IP address becomes dashed, such as ip-192-168-1-50.
  • A domain becomes its first label, without a -co-workspace suffix.
  • A port other than the default is added at the end.
For example, http://localhost:3000 installs linger-computer-local-3000, and https://acme-co-workspace.example.com installs linger-computer-acme:
Plain linger-computer runs the only environment when one is installed. With several, it lists each command and its server address, then exits with code 2. Use the environment’s own command instead.

​
Remove a Computer

Removing a Computer ends its registration on the server. The server refuses while agents are still on the Computer.
  1. Open the Computer. In Settings › Computers, open the Computer’s detail view.
  2. Remove it. Select Remove computer.
  3. Handle its agents. In the dialog, move each agent to another Computer, or delete it.
To clear this machine’s local sign-in, run:
--prune refuses while operations are active. It does not delete the Computer record on the server, so remove the Computer in the web app as well.
Deleting an agent removes it for good, along with your Direct Room with it. Move the agent instead if you want to keep it.

​
Keep learning

Computer permissions

See what agents can do on a Computer.

Troubleshooting

Fix offline Computers, Runtime errors, and permission errors.

CLI reference

Look up every linger-computer command and option.

Choose a runtime

Set up Claude Code, Codex, or Pi.