Local configuration - Failproof AI

Failproof AI separates policy selection from machine and daemon settings. This keeps repository policy choices reviewable while credentials and daemon state stay outside the repository.

Choose a policy scope

Dashboard
CLI

Run failproofai without arguments to open the local policy dashboard. Choose the user, project, or local scope before enabling a policy so the change is written to the intended configuration file.

User applies across projects on this machine.
Project belongs to the repository and can be committed.
Local overrides one project for one user and should remain gitignored.

failproofai policy add block-rm-rf --scope user
failproofai policy add block-force-push --scope project
failproofai policy add warn-large-file-write --scope local
failproofai policies

Not every harness supports local scope. The CLI rejects a scope that the selected harness cannot represent.

Scope	Policy configuration file
Project	`<project>/.failproofai/policies-config.json`
Local	`<project>/.failproofai/policies-config.local.json`
User	`~/.failproofai/policies-config.json`

Enabled policies are merged as a union. Policy parameters use the first scope that defines parameters for that policy, in project → local → user order. Explicit custom policy paths use the first scope that defines them.

Configure policy parameters

Dashboard
CLI

Open the policy in the local dashboard, edit its supported parameters, and save in the selected scope. Run a matching and non-matching agent action, then inspect the decision in Observe → policy.

Edit the selected scope’s policies-config.json, then run failproofai policies to surface unknown policy names or parameter keys.

{
  "enabledPolicies": ["block-rm-rf", "block-force-push"],
  "policyParams": {
    "block-rm-rf": {
      "allowPaths": ["/tmp/build-output"]
    }
  }
}

failproofai policies

Understand the machine files

~/.failproofai contains separate files for separate trust boundaries:

Path	Purpose
`config.json`	Non-secret daemon, audit, and telemetry settings
`credentials.json`	Cloud credentials; stored with owner-only permissions
`policies-config.json`	User-scope builtin selection, parameters, and explicit custom paths
`policies/`	User convention policies and Cloud-managed policy artifacts
`hook-activity/`	Local policy decision log
`state/`	Daemon spool, health, pause, and runtime state

Use FAILPROOFAI_HOME to relocate the complete machine layout for a container or isolated test. Do not relocate individual state directories independently.

Never commit credentials.json. Commit project policy configuration and project convention policies only after reviewing them as enforcement code.

​Choose a policy scope

​Configure policy parameters

​Understand the machine files

Choose a policy scope

Configure policy parameters

Understand the machine files