brevi

What brevi does

You connect your machine to Linear and GitHub, then add the brevi label to a ticket and assign it to yourself. brevi polls Linear, picks the ticket up, and runs a coding agent against a checkout of the mapped repository inside a sandbox. A branch brevi/<ticket-id> is force-pushed and a pull request is opened; the demo the agent captured (screenshots or a recording) stays with the run in the dashboard.

Everything runs locally. All state lives under ~/.brevi/: config, run history, artifacts, and workspaces.

One-click connections

brevi finds credentials that are already on your machine (the gh CLI, your Claude Code login, a Codex/ChatGPT login), verifies them live, and stores them. No copying keys, no environment variables.

Real isolation

On Linux each run executes inside a bubblewrap sandbox. A host that cannot run bwrap schedules work onto a Linux worker.

Demos, not just diffs

Runs are required to produce evidence under .brevi/demo/ (real screenshots or a recording), kept with the run and viewable in the dashboard.

A live dashboard

brevi serves a dashboard on localhost:4400: the eligible ticket queue, streaming agent output per run, artifacts, and the Configuration page.

Start here

Getting startedInstall brevi, connect your accounts, and run your first ticket.

DownloadMission Control, the self-updating desktop app for macOS and Linux, no terminal required.

ConnectionsHow each Connect button acquires a credential, and where credentials are stored.

Tickets and runsEligibility rules, repository routing, what a run produces, and when a ticket runs again.

Configuration referenceEvery field in ~/.brevi/config.json.