Skip to main content
Agent context tells audits what each agent exists to do, what it must produce, and what it must never do. Failproof AI stores this context as one agent contract per agent. Agent context belongs to the organization, not to one audit. You write it once per agent, and every model-backed audit whose scope includes that agent uses it.

Add agent context

  1. Go to Analyze → audits, select agents, and choose the agent ID reported by its sessions.
  2. Select add content or edit.
  3. Describe what the agent is for, what it must produce, what “done” means, how often it should run, and what it must never do.
  4. Save the context, then return to the audit form and confirm the selected agent is shown as covered. The audit Agents drawer used to add purpose, cadence, outputs, completion conditions, and prohibited behavior for an agent.
You can also add or edit agent context from the agents drawer while creating or editing an audit. It saves independently and is immediately available to every applicable audit.

Write useful context

Keep the context under 5,000 characters and make it testable. Useful context normally contains:
  • Purpose: why the agent exists
  • Outputs: artifacts or actions it must produce
  • Done when: the condition that makes a run successful
  • Cadence: how often or when it should run
  • Must not: actions and outcomes that are always unacceptable
Agent context states expected behavior; it cannot tell the analysis what conclusion to reach or restrict which evidence it examines. Agents without context are audited normally, but Failproof AI cannot judge their behavior against organization-specific intent.

Pause or change agent context

  • Pause agent context when audits should temporarily ignore it. Pausing is reversible.
  • Edit the context when the agent’s responsibility changes. The new text applies to future runs.
  • Check last matched when a running agent never appears to use its context. This usually means its agent ID does not match telemetry.
  • Delete through the API only when the text must be permanently destroyed. The dashboard intentionally offers pause instead of delete.
Every audit run stores the exact agent-context snapshot it used. Editing, pausing, or deleting the current contract resource does not rewrite the basis of earlier findings.
Reading contracts requires audits:read. Creating, editing, pausing, or deleting them requires audits:write.