Skip to main content
Use a local audit for an immediate, private review before connecting a machine to Failproof AI Cloud. It scans the agent histories already stored on your machine, replays tool activity through builtin policies, and opens a local results dashboard.

​
Run an interactive audit

The local audit starts from the CLI because it must discover histories on the current machine. Run failproofai audit; after the scan, Failproof AI starts the bundled dashboard and opens http://localhost:8020/audit.In the audit view, review the number of sessions, tool calls, projects, and policy hits. Start with frequent findings, then inspect the affected project and agent history before enabling enforcement.
The local audit dashboard is separate from Analyze → Audits in Failproof AI Cloud. Local audits remain on the machine and require no account or network connection.
The current audit adapters can read histories from Claude Code, Codex, GitHub Copilot CLI, Cursor, OpenCode, Pi, Hermes, OpenClaw, Factory, Devin, Antigravity, and Goose. Only locally available histories are scanned.

​
Schedule recurring local audits

Open Settings in the local dashboard, enable scheduled audits, choose the interval, and set the email address that should receive findings. The dashboard and CLI update the same machine configuration.
The daemon runs scheduled scans in the background, refreshes the cached result used by the local dashboard, and emails the configured report. Use failproofai audit when you want to run an interactive scan immediately.

​
Move from local evidence to Cloud operations

A local audit is a fast baseline. Connect the machine to Failproof AI Cloud when you need shared traces, recurring population audits, findings and issues, alerts, organization-wide policy deployment, or fleet health.

Create a Cloud audit

Define a recurring goal, population, evidence window, and response channels.

Enable a policy

Validate locally, publish deliberately, and deploy to a narrow machine group first.
Audit output is evidence for review, not proof that every flagged action is unsafe. Confirm context before turning a finding into blocking enforcement.