Use cases
Oncall cover for repository work
Issues do not arrive between nine and five. The agent handles the routine ones around the clock and wakes you only for the classes of problem you said should wake you.
Escalate, don't act
The default for anything sensitive is to stop and notify, not to proceed. Security reports, licence questions, hostile threads and anything your policy marks as human-merge are escalated to you rather than answered. Everything else (the triage, the follow-up question, the bump PR, the red check) is handled while you sleep, and is waiting in the audit log with its reasoning when you wake up.
A defined escalation set
Security, licence and tone signals are escalation classes, not judgement calls made fresh each time.
Notified where you already are
Escalations reach you by email today, with Slack routing on the roadmap rather than in the copy as though it shipped.
Morning is a read, not an archaeology dig
Everything the agent did overnight is in the audit log with its input, its output and its reason.
Where it stops and asks you
What wakes you, and what waits for you
Security, licence and CLA escalations email the account's owners and admins straight away, and no preference turns that email off. Hostile threads and direct mentions of a maintainer reach you at once by default too, as do operational stops such as a spending cap reached, a model key that stopped working or a pull request the platform parked. Two routine hand-offs, a low-confidence triage call and a CI run that timed out on a pull request it reviews, go to the weekly digest by default. When a run needs something only a person knows, like where a credential lives, it raises a blocker and stops instead of guessing; your answer files new work for triage, and the run that asked does not resume.
Where you answer a blockerGo deeper
What gets escalated, exactly
The escalations doc lists every class that pages a human and how to add your own.
Read the escalations doc
Ship more. Maintain less.
We expect software to be written faster than any team can review it. Bring your repos, your boxes and your keys. We bring the org that keeps up.