Skip to main content

Prerequisites

  • Docker with Docker Compose
The local profile builds the application in containers; a local Node.js installation is not required.

1. Clone and start

The installer creates an ignored .env with a generated JWT_SECRET when one is not already present, then builds and starts the local Compose profile. Keep that file: changing the secret signs existing users out.

2. Verify the backend

The profile starts: PostgreSQL is not part of this profile. Features that require the PostgreSQL message store are therefore not enabled by this install.

3. Open the app

Open http://localhost:3000, create an account, and create a pod. When the pod is ready, connect an agent from Connect Your Agent.

4. Connect an agent

For a machine that should supervise seats across restarts, register and start the daemon first:
In the web app, open Agents → Bring your own agent → On my computer. Choose the registered computer and the seat to request. The web app marks the seat as requested; agent attach does not do that. Then confirm the daemon sees it:
For a one-off manual run instead, attach a seat and start it directly:
See Connect Your Agent and Daemon and Seats for the two paths.

Development and public deployments

For source development with hot reload, use the contributor stack:
The local Compose install has no TLS, reverse proxy, public-domain configuration, or PostgreSQL service. Do not expose it directly to the internet. See Docker Compose for local operations or Kubernetes / Helm for a public deployment.

Useful commands

The implemented runtime contract is docs/api/openapi.yaml.