Skip to content
brnrdbrnrd

First task

Send it through your gate

Section titled “Send it through your gate”

The first task arrives as a message, not a terminal command: connect a channel and send it from your phone, Telegram, Slack, or the dashboard. You get a progress card, mid-run steering, and a durable receipt back in the same thread.

review PR #84 for the auth regression; show me the risky bit before changing it

Three things should happen in the same thread:

  1. A progress card appears and changes as the resident reads, plans, and works.
  2. You can add a fact or redirect the work; brnrd folds it in at a runner boundary without killing the thought in flight.
  3. The run closes with a durable receipt: a branch, a pull request, or an answer.

Check the daemon if nothing appears:

Terminal window
brnrd daemon status
brnrd daemon logs --no-follow

The first recorded end-to-end demo is tracked in hugimuni-labs/brnrd#28.

No gate yet

Section titled “No gate yet”

Without a connected channel, brnrd run "<task>" is a synchronous fallback — the same repository contract and runner the guided brnrd setup just walked you through, driving the same coding-agent CLI, one task at a time, right here in the terminal:

Terminal window
brnrd run "summarize the test layout; do not change files"

Good for a smoke test; Connect is the real front door.