The computer
A teammate can have a computer: a Linux desktop in a container on your machine, with a browser and a window manager. The teammate works it through tools that look at the screen, type, click, and run commands. You can open the same screen, watch, and take the keyboard when the teammate asks you to. A teammate without one browses with its desk browser.
What you need
Section titled “What you need”One container runtime:
| Runtime | Where |
|---|---|
| Docker (Docker Desktop, or OrbStack on macOS) | macOS, Linux and Windows |
| Podman | macOS, Linux and Windows |
Apple container |
macOS only |
Settings → Computer → Teammate computers → Runs on lists every runtime, whether it is installed and running, and what to do if it is not. Leave it on automatic and Hotline takes the first one that is ready, preferring one that runs rootless.
The desktop image is ghcr.io/1broseidon/hotline-computer. Image, in
the same place, chooses its release: Newest follows each new release of
the image, or pick one to pin it, or a custom image of your own. Check now
looks for a newer release. A teammate can use a different image, under
Desktop in its pane. The image lives in its own repository,
hotline-computer.
Turn it on
Section titled “Turn it on”In the teammate’s pane, under Computer, switch on A computer of its own, or turn on Computer under Abilities when you add the teammate.
The first start downloads the image. A ring fills where the computer’s button will sit in the conversation’s header. The teammate does not wait for it: it answers straight away without its computer, can ask how the download is going, and gets the computer once the image is down. If the computer cannot start at all, for example because Docker is not running, the teammate still answers and says why.
From then on the container wakes with the teammate and stops with it. Stopping keeps the container for the next start; removing it starts over. Thirty minutes idle stops it; seven days idle removes it.
Inside
Section titled “Inside”The teammate’s working directory is mounted at /home/agent/workspace, and
its extra folders under
/home/agent/folders. Under Desktop in the pane:
- Memory and CPU limits, on sliders that stop at what this machine has (memory is 4 GB unless you set it; CPU is unlimited unless you set it);
- Processes, the most processes the container may run (1024 when blank,
0 for no limit; a parallel build needs more). Apple
containerhas no process limit, so this does nothing there; - Mount a folder adds another folder of yours, read-only if you like;
- Updates says which release the computer runs, and offers Update
when a newer one is out. Updating recreates the container. On Docker and
Podman the workspace, prepared environments and the browser profile come
back with it, while anything installed into the container outside them is
gone. On Apple
containeronly the workspace and the folders you mounted come back; the browser profile and everything else start over.
Sign the teammate in
Section titled “Sign the teammate in”Logins, variables, passkeys and your shared cookies are under Secrets in the teammate’s pane, not under Computer: they belong to the teammate, and follow it when its computer is turned on or off. Variables become environment variables in the computer’s shell. See Sign-ins.
Watch and take over
Section titled “Watch and take over”While the computer is running, the computer button in the conversation’s header (Open the teammate’s computer) opens the desktop in a window of its own. When the teammate needs you for a login or a tap the agent cannot do, its Needs you card has Open the screen. What you type goes to the desktop, never through the agent. Mark the card Done and the desktop is the agent’s again.
In the viewer, Ctrl + Alt + V (⌥ + ⌘ + V on a Mac) pastes this computer’s clipboard into the desktop.
A teammate can also send you a screenshot of its screen, or a file from its computer, in the conversation.
What the container can do
Section titled “What the container can do”Nothing in the image runs as root. Hotline creates the container with every
capability dropped, a memory limit, a CPU limit if you set one, and its one
port on loopback only. On Docker and Podman it also forbids gaining new
privileges, applies the process limit, and keeps the container’s home, its
source and its installed packages in named volumes between starts. Apple
container supports neither of those flags nor named volumes: it gets only
the folders mounted from your machine, and anything else lives in the
container itself.
Work threads and side threads on the same teammate take turns on its computer. One that finds it busy is told which thread has it.