brnrd

Local agents go brr. From anywhere.

A co-maintainer that lives on your machine: survives reboots, remembers who it is, works both your Claude and Codex subscriptions, and leaves receipts — commits, pull requests, a card you can read. Not a session you reopen: a resident with continuity across runs.

Needs a machine that’s on: a laptop that doesn’t sleep, a Mac mini, a home server, or a $5 VPS (about ten minutes to set up).

Send a task from Telegram, Slack, GitHub, or the web. Watch the progress card change while the agent works. Correct course at runner boundaries. Get a branch, a pull request, or an answer back in the same thread.

brnrd is not another coding agent. It runs the CLI agents you already chose, locally and under your rules, and gives each repo a resident with continuity across runs.

Shells and doors

Shells

• Claude Code
• { }Codex

Connectors

• Telegram
• #Slack
• GitHubnotifications
• Web dashboard
• WhatsApp
• Signal

Live today: Claude Code, Codex, Telegram, Slack (self-hosted gate), GitHub, the web dashboard, WhatsApp, and Signal (self-hosted gate). GitHub here is a notification and task channel — issues and PRs in, progress and replies out — not a chat surface. This list answers “can I self-host this” — every entry ships on main (checked by tests/test_support_matrix.py, which fails the day this page and the gate code disagree, after the tags above went stale for a full day the first time). brnrd.dev’s own hosted convenience layer answers a narrower question — has this deployment been configured for a given door yet — and can legitimately show fewer doors live than this page while a gate is finalizing setup on the hosted side. Every self-hosted door still needs your own credentials regardless of this list (a bot token, a linked device, an app registration) — that per-operator cost isn’t what “live” answers here. The landing’s own shelf goes one step further for brnrd.dev’s own deployment: a door can ship and still read ready there — code done, no confirmed identity behind it yet (no Signal number, no WhatsApp Business number, no Slack app) — which is the maintainer’s setup to finish, not yours to chase for self-hosting.

The loop

you · Telegram / Slack / GitHub / dashboard
                         │
                         ▼
                    a small gate
                         │
                         ▼
          brnrd daemon · your machine · your repo
                         │
                 Claude Code · Codex
                         │
                         ▼
                progress · replies · git

Your checkout, .git, and run execution stay on your machine; with brnrd account connect, dashboard publishing continuously mirrors derived project knowledge—including any code quoted there—to brnrd.dev, but it does not read your source tree. Read Security & privacy before opening a gate.

Self-hosted gates and local execution are free, with no brnrd account required. brnrd account connect layers a managed account on top — one account across repos, continuity, and the live dashboard — without moving where runs execute. See Connect to compare the two doors.

Start here

npm install -g brnrd     # or: uv tool install brnrd · pipx install brnrd
brnrd --version

1. Check the prerequisites — terminal, GitHub, and one coding-agent CLI.
2. Install brnrd — the full picture, including what to do when there is no Python on the machine.
3. Choose a managed or self-hosted connection.
4. Send your first task.

Current posture

brnrd is alpha software, already used to build itself. The resident loop, local daemon, managed Telegram path, live dashboard, runner switching, worktree/Docker execution, and git handoff are real. Public docs, multi-project proving, managed billing/failover, and some operational polish are still release work.

If you want a quiet appliance, wait. If you want a local agent coworker with a remote door and are willing to report sharp edges, start with the install.

Source: hugimuni-labs/brnrd. Managed service information: brnrd.dev.