Agent Lifecycle Management
Status transitions, suspending an agent, and audit trail for agent lifecycles
Status Transitions
Every agent goes through defined statuses. Each change is documented as a governance event and captured by the attestation rules.
Draft → Active → Paused → Active (reactivated)
→ Suspended → Active (after review)
→ Revoked (permanent)| Status | Meaning | Who Can Change | Next Steps |
|---|---|---|---|
| Draft | Wizard not completed or FRIA pending | Editor | Continue wizard or complete FRIA |
| Active | Agent is operational and processing requests | Admin | Pause, Suspend, or Revoke |
| Paused | Temporarily deactivated. Requests rejected (HTTP 403). | Admin | Reactivate or Revoke |
| Suspended | Locked by system or admin (e.g., incident). | System / Admin | Conduct review, then Activate or Revoke |
| Revoked | Permanently deactivated. Cannot be reactivated. | Admin | — (final state) |
Changing Status on the Detail Page
- Navigate to Agents. Click on the desired agent to open its detail page.
- The lifecycle actions are in the header, on a phone below the tabs (for example Pause agent and Suspend agent).
- Select the action you want and confirm in the dialog.
Suspend agent
To suspend one agent: open the agent, click Suspend agent, and confirm. The agent is then suspended, so every request that names it is refused. Suspending does not change the agent's API key, and answers already running finish. To stop every request that uses the project key, use the project emergency stop instead. Suspending is dispatched as a governance event and always captured by the attestation rules.
Suspension is not revocation. A suspended agent can be reactivated after review. Revocation is permanent.
Automatic Suspension
The platform suspends an agent automatically when an incident with severity Critical is reported that names this agent. There is no detection that suspends agents on its own.