Agent rules turn the signals you watch in Agent Radar into automatic responses. A rule pairs a condition — an agent changing state — with one non-destructive action, so Quorum Terminal can focus a terminal, feed in a saved prompt, or log the change the moment something happens.
What a rule is
A rule reacts to an agent status transition and fires exactly one whitelisted action. The trigger is a move between two statuses: idle, busy, and waiting. You set a target status (the to) and, optionally, the from status and scope filters — ownership (self, external, ambiguous), kind (interactive, background), a project directory, or a specific session id.
The action is one of three, and none of them change your files or run shell commands:
| Action | What it does |
|---|---|
focus | Focuses the agent's owned terminal |
open-saved-prompt | Sends a global saved prompt into that terminal |
log | Records the transition to the rule-fire audit log only |
Rules are off by default and each new rule starts disabled. Nothing fires until you both enable automation and switch the rule on.
Global vs per-project rules
Scope is decided by where a rule lives, not by a field. Global rules apply across every project. Per-project rules belong to one project and are automatically scoped to that project's folder, so they only fire for agents running there. Per-project rules need an authorized project open; otherwise the editor shows the global list and asks you to open one.
The visual editor
Open the editor from the Agent Radar panel header. The list view groups your global and per-project rules, each with an ON/OFF switch, an Edit button, and a Delete button. The form lets you set the name, from/to statuses, scope filters, action, and a debounce window in milliseconds, with a live "When …" preview and inline validation. A debounce keeps a rule from firing more than once per window.
How it connects to Agent Radar
The rules engine subscribes to the same status transitions Agent Radar already tracks. On each poll it folds fresh transitions against your enabled rules and dispatches matching actions. It deduplicates so a transition never fires twice, debounces per rule, and suppresses replays — enabling a rule never re-runs past history. Agent context passed to an action is a strict allowlist that never includes your working directory or process id.
Something off on this page? Tell us.