Getting started

brevi runs as Mission Control on macOS or Linux. The desktop app owns the scheduler and config; isolated runs execute on Linux workers it provisions over SSH.

Prerequisites

• A GitHub account and git access to the repositories brevi may change.
• A Linear account with issues you can assign to yourself.
• A Claude, Codex, or Grok credential.
• A reachable Linux worker with systemd, OpenSSH, and passwordless sudo for its SSH user.

First run

1. Install Mission Control

   Download the macOS or Linux build from Download and launch it. First launch creates ~/.brevi/config.json and opens setup inside the app.

2. Connect providers

   Open Configuration and connect Linear, GitHub, and an agent. Credentials are verified before they are saved.

3. Expose the worker channel

   Under Configuration → Workers, bind the authenticated worker channel to an address your Linux machine can reach. The management API remains loopback-only and cannot be exposed.

4. Set up a worker over SSH

   Enter the Linux hostname or IP, SSH user, port, and optionally an absolute private-key path. Mission Control verifies the host key, installs brevi-worker.service, enrolls it with a single-use token, and waits for it to connect. SSH keys and pairing credentials stay in Electron’s main process.

5. Pick repositories and run a ticket

   Add repositories under Configuration → Repositories. Assign a Linear issue to yourself, add the brevi label, then run it from Mission Control or let the scheduler pick it up.

State and updates

Mission Control keeps configuration, run history, artifacts, and memories under ~/.brevi. Desktop updates include the scheduler. Worker updates are applied by running SSH setup again; enrollment survives upgrades.

Next steps

• Connections
• Workers
• Tickets and runs
• Configuration