Brix — Overview
Brix is Nexrall's always-on agent. Every other agent on the platform works while you watch: a chat, a build, a coding session. Brix works between conversations — you hand it a standing responsibility, it wakes up on its own schedule, does the work in the cloud, and reports back when there's something to say.
The flagship pattern is small to describe and big in effect: "watch this repository and summarise the action every morning." Create that responsibility once, and every morning a short report is waiting — merged pull requests, notable commits, anything that needs attention.
The loop: wake, work, settle, report
- Wake — Brix goes to work on schedule, or at a moment it chose for itself. Every wake is a fresh task under the standing responsibility.
- Work — the wake becomes a run on an isolated pod in Nexrall's cloud: the repository is cloned, and the agent works headless — the same executor
nex clouduses. Your machine is not involved and can be closed. - Settle — when the pod finishes, Brix reads the outcome, writes notes for itself, and decides when it should next check in.
- Report — you get a notification (push, email, in-app) with the summary. Nothing else is required of you.
Two ways to run: write and monitor
| Mode | What the run does | What you get |
|---|---|---|
| Write (default) | Works on the repository and delivers the change as a branch + pull request. Nothing merges on its own. | A reviewable PR — a fix, a dependency bump, a regenerated doc |
| Monitor | Read-only. Brix reads the repository through the GitHub API; whatever it writes in the pod is discarded on purpose. | The report itself — a digest, a status check, a "nothing moved" |
Vocabulary
| Term | Meaning |
|---|---|
| Responsibility | The standing brief: instructions, one repository, what each run should do, how often it wakes, and which mode it runs in. |
| Wake | A scheduled moment Brix goes to work — a recurring time, or one Brix set for itself. |
| Run | One wake's work: a cloud pod, a status, a summary and a recorded cost. |
| Notes | What Brix carries between runs — decisions, open threads, what to check next. Not a transcript. |
What people use it for
- Watch a repository — a morning digest of merged PRs, commits and issues that need attention (monitor).
- Keep a routine — a recurring maintenance task where each run produces a small, reviewable pull request (write): dependency bumps, doc regeneration, flaky-test cleanup, a weekly report.
- Check back on its own work — after opening a PR, Brix can schedule its own next wake to see how review went.
What Brix is not
Brix is a coordinator: it owns the responsibility and books the work, but the heavy lifting happens on the existing cloud-session executor. The beta is deliberately narrow — exactly what it may do is on Safety, limits & billing.
Brix is in beta
Brix is enabled per account while it rolls out — until your account is enabled, every request refuses with a sentence saying so. Creating and managing a Brix is done through the Nexrall API today; see Creating a Brix.
Where to go next
- Creating a Brix — set up your first responsibility.
- Wakes, runs & activity — schedules, self-wakes, watching a run live, and the notifications that come back.
- Notes & memory — the continuity that makes an always-on agent useful.
- Safety, limits & billing — what Brix may do, the caps it runs under, and how it's billed.