Safety, limits & billing
Brix runs while you're not watching, so the boundaries are the product. In the beta everything below is enforced server-side, not just documented.
What a Brix may do (beta)
- Create cloud sessions for its own responsibility, inside every cap below.
- Write its own notes and schedule its own wakes, within the clamp windows.
- Notify you.
That's the whole list. A Brix cannot reach outside its configured repository, cannot use other executors (no browser agent, no other work types), cannot merge anything, and cannot spend beyond the per-run budget.
Scope by construction
- The deliverable is reviewable git. Write runs end in a branch and a pull request against your base branch; nothing merges on its own. A run that produced no commits reports exactly that.
- Monitor runs cannot write. The read-only mode reads the repository through the GitHub API, and its edits are discarded on purpose — no branch, no pull request, ever.
- One repository. The responsibility names a single repository (
owner/name); Brix's self-scheduled work is refused if it points anywhere else. - Credentials stay server-side. Brix works through a platform-held, fine-grained GitHub credential. You never paste a token into a responsibility; the pod fetches it per use and never writes it to disk.
The caps
Brix's runs draw from the same session limits as every cloud run on your account — with Brix's own daily cap on top:
| Limit | Value |
|---|---|
| Sessions running at once | 1 per account |
| Sessions queued | up to 3 |
| Sessions per rolling 24 hours | 10 |
| Wall clock per run | 90 minutes |
| Budget per run | $3 |
| Turns per run | 120 |
| Brix wakes per day | 24 (default) |
| Self-wake window | 5 minutes – 30 days ahead |
Where two limits disagree, the tighter one wins. If a wake can't start inside these limits, you get told: the wake records the failure and a notification lands — nothing fails invisibly.
Billing
- Model spend is charged to your wallet (or team) like any other usage — the same account everything else on Nexrall uses.
- Each run records its own cost; the settle summary is a small completion, billed the same way.
- Cost honesty: a run that couldn't report its cost records no number — never
$0.
Beta status
Brix is enabled per account while it rolls out, behind a server-side switch. Until your account is enabled, every request refuses with a sentence saying so. The scope above is the beta's promise: expansion (more executors, connectors, shared team Brix) is future work, not a hidden setting.
Related
- Wakes, runs & activity — where these limits show up in practice.
- Nexrall CLI — cloud sessions — the same caps and the same executor, at your command.