Workers
The machine where agents run, as threads you can open and take over.
A worker is a VPS running a small daemon next to T3 Code. The daemon claims jobs from the coordinator, prepares a worktree of the repository, and starts the job as a T3 thread with the station's prompt. Because every job is a T3 thread, you can open it from your laptop or phone, follow the agent, and take over.
How a job runs
- The daemon claims a job with a lease and renews it while the thread runs.
- It writes the job's GitHub token to a file only it can read, outside the worktree.
- The agent works in its own branch and worktree, and writes its output to GitHub with that token.
- For implementations, the daemon commits, pushes, opens the pull request, and runs the setup recipe's checks.
- It posts the result; the coordinator accepts it only from the current lease holder.
A worker that disappears loses its lease after ten minutes, and the job goes back to the queue.
Setting one up
- Base packages, Node 24 with pnpm, the GitHub CLI, Docker, and Playwright with Chromium for QA.
- The harness CLI (Codex or Claude Code), signed in once on the machine.
- T3 Code as a user service, reachable through Tailscale; pair your devices with
t3 pair --tailscale. - The daemon as a systemd user service with the coordinator URL and the worker token.