Skip to main content
Docker Compose builds every Linger service from the repository and runs it, PostgreSQL and voice included. Use this path instead of the desktop app when you build from source, or when one server serves several computers on your network. The containers do not run your agents. Your agents run on a Computer: a machine that you connect to the server. That Computer needs Claude Code, Codex, or Pi installed and signed in. Linger needs no model gateway or API key of its own. Agent model calls run on the Claude Code, Codex, or Pi of your own computer. The background work for memory and the personal memory runs on the Codex or Claude Code there. Grok Live voice mode is the one exception: the server calls xAI directly when you set XAI_API_KEY.

​
Check what you need

You need Docker with Compose and one computer that can run your agents.
  • Docker with Compose, with at least 5 GiB of memory for its virtual machine. The web app build alone uses about 4 GB.
  • Git, to clone the repository.
  • A computer with Claude Code, Codex, or Pi installed and signed in.

​
Build and start the server

1

Clone the repository

2

Create the environment file

3

Build and start the services

4

Create the owner account

Replace the email and the password with your own. The password goes in through standard input.
5

Sign in

Open http://localhost:3000 and sign in with the owner account.
Linger cannot reset a lost password by email. To set a new password, run the same command with set-password instead of create-owner.

​
Connect your computer

After you sign in, a Connect your computer dialog covers the app. It shows the commands for your platform and stays open until a computer with Claude Code, Codex, or Pi signed in comes online. On macOS and Linux, the commands look like this.
On Windows, use an ordinary PowerShell that does not run as administrator.
linger-computer login authorizes the computer in the browser and starts the Computer Daemon. Then run linger-computer daemon status to check the connection. If agents do not answer, run linger-computer runtime check. See Choose a runtime.

​
Serve other computers on your network

By default, the server is for localhost only. To serve other computers, set four variables in .env and run docker compose up --detach --wait again. Replace 192.168.1.10 with this computer’s address.
Browsers and Computers then reach everything through port 3000.
.env.example ships a public development seed and encryption key. Everyone has these values. Before you serve other computers, generate private values for LINGER_SECRET_SEED and TEAMHUB_SECRET_ENCRYPTION_KEY with openssl rand -base64 32. Put HTTPS in front of port 3000.
Linger refuses to start with the public seed once WEB_PUBLIC_ORIGIN is not localhost, 127.0.0.1, or ::1. Plain HTTP exposes sign-in cookies and the Computer connection to anyone on the network. See Serve other computers on your network.

​
Turn on voice

Voice needs a Soniox key in SONIOX_API_KEY. Docker Compose already runs LiveKit and the voice workers. Set the key in .env and run docker compose up --detach --wait again. Browsers allow the microphone only on localhost or HTTPS. See Enable voice.

​
Fix common problems

Most problems are a service that did not start or a Computer that cannot connect. For more cases, see Troubleshooting.

​
Keep learning

Choose a runtime

Check that your Runtime is ready on the connected Computer.

Serve other computers on your network

Serve Linger on your network and add HTTPS.

Environment variables

See the settings in the .env file.