> ## Documentation Index
> Fetch the complete documentation index at: https://docs.befailproof.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Make your agent failproof

> Observability and enforcement for every harness your agents run in — coding CLIs, chat gateways, self-hosted assistants, and your own instrumented agents.

Failproof AI helps teams understand what agents did, find where they failed, and deploy safeguards before the same behavior happens again.

A **harness** is whatever your agent actually runs inside. Failproof AI hooks 12 of them — coding CLIs like Claude Code and Codex, chat gateways like Hermes, self-hosted assistants like OpenClaw — and the same events, the same policies, and the same session history apply to every one. Agents with no harness report in through the [Python SDK](/reference/python-sdk), which traces and audits them; enforcing a policy there needs a hook in your own runtime.

<Columns cols={2}>
  <Card title="Set Failproof up" icon="wand-sparkles" href="/start/quickstart">
    Use the skill to instrument your project, connect it, and verify that agent logs arrive.
  </Card>

  <Card title="Ask the Failproof Assistant" icon="message-square-text" href="/sessions/assistant">
    Analyze, query, build dashboards, and run audits in natural language on your agent logs.
  </Card>
</Columns>

<Columns cols={3}>
  <Card title="See what the agent did" icon="route" href="/sessions/overview">
    Follow model calls, tools, errors, human input, latency, and policy decisions in one session.
  </Card>

  <Card title="Find failures systematically" icon="scan-search" href="/audits/overview">
    Audit a defined set of sessions, review evidence-backed findings, and track remediation as issues.
  </Card>

  <Card title="Prevent recurrence" icon="shield-check" href="/policies/overview">
    Turn a known failure mode into a policy, observe its impact, and deploy it across your fleet.
  </Card>
</Columns>

> **Session → Audit → Finding → Issue → Policy**<br />
> Trace what happened, find the failure, manage the response, then prevent the same behavior in future runs.

## Start here

If you are deploying your first instrumented agent, start with the [quickstart](/start/quickstart). If data is already arriving, open [Sessions](/sessions/overview) and inspect a real run before configuring audits or policies.

<Card title="Find and prevent one failure" icon="arrow-right" href="/start/quickstart">
  Complete the end-to-end workflow from capture to a safely deployed policy.
</Card>