Failproofai

Translations: 简体中文 · 日本語 · 한국어 · Español · Português · Deutsch · Français · Русский · हिन्दी · Türkçe · Tiếng Việt · Italiano · العربية · עברית

Observability and enforcement for every harness your agents run in.
Wherever your agents run, we see it — and we can say no. Failproof hooks 12 agent
harnesses — coding CLIs like Claude Code and Codex, chat gateways like Hermes,
self-hosted assistants like OpenClaw — capturing every run and blocking dangerous
tool calls before they execute. 40 built-in policies. Zero latency. Runs locally.

Supported harnesses

Twelve harnesses in two classes — ten coding CLIs, and two chat and assistant
gateways (Hermes, OpenClaw). One policy API and one session history across all
of them. What a policy can *block* is per-harness: stopping a tool call before
it runs is verified on all twelve, turn-end gates on eight. The
per-harness matrix
lists the events each one honours.

Agents that run in none of them report through the Python SDK,
which gives you tracing, sessions and audits. Enforcement there needs a hook in
your own runtime — talk to us and we'll map it.

Install

Setup wires the hooks and picks no policies — that second command is what
puts guardrails on the machine, and any pack is typed the same way
(failproofai policies add /; policies show / reads
one first). Run failproofai config with no terminal — CI, a container, an
agent driving it — and it applies rather than asking. On a machine that has
never been set up, any other command runs the same wizard first; disable that
with FAILPROOFAI_NO_FIRST_RUN=1.

Until a pack arrives, the only thing enforcing is block-failproofai-commands,
which is always on and cannot be switched off or paused: an agent that can pause
enforcement can switch off every other policy.

What it stops

Every…