2026-09-03 12:46:14 +00:00
# LazyBoy
Create a bot in the browser, give it a Team or Private computer, and let it drive a Linux desktop.
2026-09-04 05:41:09 +00:00
## Run (full Docker, recommended)
Everything (postgres, desktop image build, supervisor, API + web UI) runs in
Docker Compose, driven by the Makefile:
```bash
make env # creates .env with two generated 64-hex tokens (no-op if .env exists)
# then set XAI_API_KEY in .env
make up # builds all images and starts the stack
make health
```
Open `http://127.0.0.1:3101` and sign in with `LAZYBOY_APP_TOKEN` .
Useful targets (see `make help` ):
| target | what it does |
| --- | --- |
| `make up` / `make down` / `make purge` | start / stop (keep data) / stop + delete postgres volume |
| `make logs` , `make ps` , `make health` | observe the stack |
| `make computer` | build only the heavy desktop image `lazyboy/computer:local` |
| `make postgres` , `make postgres-down` | start/stop just the database on `127.0.0.1:5434` |
| `make build` , `make fmt` , `make clippy` , `make test` | cargo workspace tasks |
| `make web` | build `apps/web` with npm (needs node) |
| `make dev` , `make dev-supervisor` , `make dev-api` | local dev: postgres in Docker, Rust services on the host in two terminals |
Without make, the full-stack equivalent is:
```bash
cp .env.example .env # fill in the two tokens + XAI_API_KEY
docker compose up -d --build
```
2026-09-03 12:46:14 +00:00
## Run (local)
Postgres is on `127.0.0.1:5434` so it does not collide with other stacks.
```bash
2026-09-03 23:43:37 +00:00
cp .env.example .env
# Set XAI_API_KEY, then generate two different secrets:
# openssl rand -hex 32
# openssl rand -hex 32
# Put them in LAZYBOY_APP_TOKEN and SANDBOX_SUPERVISOR_TOKEN.
2026-09-03 12:46:14 +00:00
docker compose up -d postgres
./scripts/build-computer-image.sh
2026-09-03 23:43:37 +00:00
SANDBOX_SUPERVISOR_TOKEN=< same-strong-supervisor-token > \
2026-09-03 12:46:14 +00:00
DATA_DIR=/root/LazyBoy/data cargo run -p lazyboy-supervisor
DATABASE_URL=postgres://lazyboy:lazyboy@127.0.0.1:5434/lazyboy \
SANDBOX_PROVIDER=docker \
SANDBOX_SUPERVISOR_URL=http://127.0.0.1:7091 \
2026-09-03 23:43:37 +00:00
SANDBOX_SUPERVISOR_TOKEN=< same-strong-supervisor-token > \
LAZYBOY_APP_TOKEN=< strong-app-token > \
2026-09-03 12:46:14 +00:00
DATA_DIR=/root/LazyBoy/data \
LAZYBOY_WEB_DIR=apps/web \
API_BIND=0.0.0.0:3101 \
cargo run -p lazyboy-api
```
2026-09-03 23:43:37 +00:00
Open `http://<host>:3101` and sign in with `LAZYBOY_APP_TOKEN` . The computer is a real Debian container: fluxbox toolbar, Chromium with tabs and URL bar, and xterm. The display is proxied through the authenticated API; the supervisor is internal-only in Docker Compose and must not be published to the LAN.
For LAN use, put LazyBoy behind HTTPS whenever possible. A shared token sent over plain HTTP can be observed by other devices on an untrusted network. Set `LAZYBOY_SECURE_COOKIE=true` when HTTPS terminates at LazyBoy or a trusted reverse proxy. The API refuses a non-loopback bind unless `LAZYBOY_APP_TOKEN` is at least 32 characters; the supervisor likewise rejects missing, short, or default tokens.
2026-09-03 12:46:14 +00:00
2026-09-03 16:16:34 +00:00
For frontend development, run `npm install && npm run dev` in `apps/web` , then open
`http://127.0.0.1:5173` . Vite proxies API and computer-screen traffic to the Rust API on port 3101.
2026-09-03 23:43:37 +00:00
The standalone supervisor listens on `127.0.0.1:7091` by default. Docker Compose reaches it internally as `supervisor:7091` ; there is intentionally no host port `7092` .
2026-09-03 12:46:14 +00:00
Model providers: v1 talks to xAI (`XAI_API_KEY`). `openai` / `anthropic` / `openrouter` are reserved on the factory and return `unsupported_provider` .
