Your project can say no to an agent

• A project can refuse things outright, not just ask. Until now every risky thing an agent did arrived as the same question waiting on a click — which cannot say “nobody here does that”, and only works if somebody happens to be watching at the moment it lands. A new Authority section in your project settings answers three questions once, in writing: deleting something other code may be calling, editing a file a teammate is holding, and sending work off to another machine. Each can be allowed, asked about, or refused, and a refusal cannot be clicked past.
• The rules live in the project, in writing. They sit in the settings file that goes into your history alongside the code, so a change to what an agent may do turns up in a review like any other change.
• A typo makes an agent do less, never more. An unreadable rule, a missing section or a missing file all fall back to asking, so getting the spelling wrong can never quietly grant something.
• Saying yes once means once. These three prompts no longer offer “always allow” — “yes, delete this function” must never quietly become “yes, delete anything”. A standing yes is a rule you write down, where it can be read.
• The wall of red “unexplained change” rows is gone. A build or a formatter touching a lot of files at once could fill the screen with things to accept or revert, because Aura briefly stopped recording reasons while it waited out a cooldown. Recording never pauses now, and working out why something changed is Aura’s job rather than a question that interrupts you — the reasons still land in your history, and the check that runs when you commit is unchanged.
• Nothing changes until you write a rule. The starting point is exactly what it was.