Creating a Brix

A Brix is defined by its responsibility — the standing brief you write once and it keeps. Creating one takes a few sentences, not a workflow.

What you set

Setting	What it decides
Instructions (up to 4,000 characters)	Who this Brix is for you and the standard it should hold. "You keep the API service healthy for the platform team. Prefer small, reviewable changes."
Repository	The one repository this Brix may work on, as owner/name. Its self-scheduled work can never point anywhere else.
The wake brief (up to 2,000 characters)	What each run should do — concrete enough to act on. "Summarise what changed on main in the last 24 hours: merged PRs, notable commits, anything risky. Under 300 words."
Mode	Write (delivers a branch + pull request) or monitor (read-only; the report is the deliverable).
Schedule	How often it wakes: every 15 minutes up to every 7 days (default: daily). The first run can also be delayed.

A good first responsibility is a monitor: it is read-only by construction, and its output — a report — arrives in full in the notification. The recipe below creates exactly that.

What happens after you create it

• By default the first run starts right away — Brix gets to work as soon as the responsibility exists. You can delay it instead (up to 7 days).
• Every recurring run books its successor before it starts, so one bad run never breaks the schedule.
• When a run finishes you get a notification with the summary — and the chain continues from the schedule you set, refined by Brix's own notes.

During the beta: via the API

Brix is enabled per account while it rolls out, and the API is the surface available today (app and CLI surfaces are on the way). Requests are authenticated the usual way — Authorization: Bearer <token>, see Authentication. If Brix isn't enabled for your account yet, every request refuses with a sentence saying so.

See your Brix — the agent, its upcoming wakes and recent runs:

curl https://api.nexrall.com/api/code/brix \
  -H "Authorization: Bearer $NEXRALL_TOKEN"

Create the responsibility (one Brix per account during the beta):

curl -X POST https://api.nexrall.com/api/code/brix/responsibilities \
  -H "Authorization: Bearer $NEXRALL_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "instructions": "You watch the acme/api repository for the platform team. Be concise and concrete; name PRs and commits by number.",
    "repo": "acme/api",
    "prompt": "Summarise what changed on main in the last 24 hours: merged pull requests, notable commits, and anything that looks risky. Keep it under 300 words.",
    "monitor": true,
    "interval_minutes": 1440,
    "start_in_minutes": 0
  }'

The response is { agent, wake } — the responsibility and its first scheduled wake. For a write responsibility, drop monitor: each run then delivers a branch and a pull request instead of a report.

Cancel a scheduled wake — allowed any time before it fires:

curl -X POST https://api.nexrall.com/api/code/brix/wakes/<wake-id>/cancel \
  -H "Authorization: Bearer $NEXRALL_TOKEN"

TIP

The first run of a new responsibility is the best end-to-end check: the notification that lands when it settles tells you the whole loop works.

Next

• Wakes, runs & activity — how schedules, self-wakes and runs behave once Brix is working.
• Safety, limits & billing — the caps behind all of this, and how runs are billed.