failproofai 0.0.2-beta.1 → 0.0.2-beta.3

package/.next/standalone/docs/{architecture.md → architecture.mdx}

@@ -4,7 +4,7 @@ description: "How the hook handler, config loading, and policy evaluation work i
 icon: sitemap
 ---
 
-This document explains how failproofai works internally: how the hook system processes events, how configuration is loaded and merged, how policies are evaluated, and how the dashboard fits in.
+This document explains how failproofai works internally: how the hook system intercepts agent tool calls, how configuration is loaded and merged, how policies are evaluated, and how the dashboard monitors agent activity.
 
 ---
 
@@ -12,8 +12,8 @@ This document explains how failproofai works internally: how the hook system pro
 
 failproofai has two independent subsystems:
 
-1. **Hook handler** — A fast CLI subprocess that Claude Code invokes on every tool call. Evaluates policies and returns a decision.
-2. **Dashboard** — A Next.js web application for browsing sessions and managing policies.
+1. **Hook handler** - A fast CLI subprocess that Claude Code invokes on every agent tool call. Evaluates policies and returns a decision.
+2. **Agent Monitor (Dashboard)** - A Next.js web application for monitoring agent sessions and managing policies.
 
 Both subsystems share configuration files in `~/.failproofai/` and the project's `.failproofai/` directory, but they run as separate processes and communicate only through the filesystem.
 
@@ -23,7 +23,7 @@ Both subsystems share configuration files in `~/.failproofai/` and the project's
 
 ### Integration with Claude Code
 
-When you run `failproofai --install-policies`, it writes entries like this into `~/.claude/settings.json`:
+When you run `failproofai policies --install`, it writes entries like this into `~/.claude/settings.json`:
 
 ```json
 {
@@ -60,7 +60,7 @@ Claude Code then invokes `failproofai --hook PreToolUse` as a subprocess before
 }
 ```
 
-For `PostToolUse` events, the payload additionally contains `tool_result` with the tool's output.
+For `PostToolUse` events, the payload also contains `tool_result` with the tool's output.
 
 The handler enforces a 1 MB stdin limit. Payloads exceeding this are discarded and all policies implicitly allow.
 
@@ -102,21 +102,38 @@ The handler enforces a 1 MB stdin limit. Payloads exceeding this are discarded a
 - Exit code: `0`
 - Empty stdout
 
+**Allow with message (beta):**
+
+Since v0.0.2-beta.3, `allow(message)` lets a policy send informational context back to Claude even when the operation is permitted. The hook handler writes the following JSON to **stdout** (not a config file — this is the handler's response to Claude Code, just like deny and instruct responses above):
+
+```json
+// Written to stdout by the hook handler process
+{
+  "hookSpecificOutput": {
+    "additionalContext": "All CI checks passed on branch 'feat/my-feature'."
+  }
+}
+```
+- Exit code: `0` (operation is allowed)
+- When multiple policies return `allow` with a message, their messages are joined with newlines into a single `additionalContext` string
+- If no policy provides a message, stdout is empty (same as before)
+
 ### Processing pipeline
 
 `src/hooks/handler.ts` implements the full pipeline:
 
-```
+```text
 stdin JSON
   → parse payload (max 1 MB)
   → extract session metadata (session_id, cwd, tool_name, tool_input, etc.)
   → readMergedHooksConfig(cwd)    ← merges project + local + global config
   → register enabled builtin policies with resolved params
-  → load custom hooks from customPoliciesPath (if set)
-  → register custom hooks into policy registry
+  → load custom policies from customPoliciesPath (if set)
+  → register custom policies into policy registry
   → evaluate all policies (builtins first, then custom)
       → first deny short-circuits
       → instruct decisions accumulate
+      → allow messages accumulate
   → write JSON decision to stdout
   → persist event to ~/.failproofai/hook-activity.jsonl
   → exit
@@ -130,17 +147,17 @@ The entire process runs in under 100ms for typical payloads with no LLM calls.
 
 `src/hooks/hooks-config.ts` implements three-scope config loading.
 
-```
+```text
 [1] {cwd}/.failproofai/policies-config.json        ← project  (highest priority)
 [2] {cwd}/.failproofai/policies-config.local.json  ← local
 [3] ~/.failproofai/policies-config.json             ← global   (lowest priority)
 ```
 
 Merge logic:
-- `enabledPolicies` — deduplicated union across all three files
-- `policyParams` — per-policy key, first file that defines it wins entirely
-- `customPoliciesPath` — first file that defines it wins
-- `llm` — first file that defines it wins
+- `enabledPolicies` - deduplicated union across all three files
+- `policyParams` - per-policy key, first file that defines it wins entirely
+- `customPoliciesPath` - first file that defines it wins
+- `llm` - first file that defines it wins
 
 The web dashboard uses `readHooksConfig()` (global only) for reading and writing, since it is not invoked with a project cwd.
 
@@ -169,7 +186,7 @@ After all policies run:
 
 ## Builtin policies
 
-`src/hooks/builtin-policies.ts` defines all 35+ built-in policies as `BuiltinPolicyDefinition` objects:
+`src/hooks/builtin-policies.ts` defines all 26 built-in policies as `BuiltinPolicyDefinition` objects:
 
 ```typescript
 interface BuiltinPolicyDefinition {
@@ -193,7 +210,7 @@ Pattern matching inside policies uses parsed command tokens (argv), not raw stri
 
 ---
 
-## Custom hooks
+## Custom policies
 
 `src/hooks/custom-hooks-registry.ts` implements a `globalThis`-backed registry:
 
@@ -208,7 +225,7 @@ export function getCustomHooks(): CustomHook[] { ... }
 export function clearCustomHooks(): void { ... }  // used in tests
 ```
 
-`src/hooks/custom-hooks-loader.ts` loads the user's hooks file:
+`src/hooks/custom-hooks-loader.ts` loads the user's policy file:
 
 1. Read `customPoliciesPath` from config; skip if absent.
 2. Resolve to absolute path; check file exists.
@@ -220,7 +237,7 @@ export function clearCustomHooks(): void { ... }  // used in tests
 
 On any error (file not found, syntax error, import failure), the error is logged to `~/.failproofai/hook.log` and the loader returns an empty array. Built-in policies are unaffected.
 
-Custom hooks are evaluated after all built-in policies. A custom hook `deny` still short-circuits further custom hooks (but all built-ins have already run by that point).
+Custom policies are evaluated after all built-in policies. A custom policy `deny` still short-circuits further custom policies (but all built-ins have already run by that point).
 
 ---
 
@@ -249,7 +266,7 @@ One line per policy that made a non-allow decision. Allow decisions are not logg
 
 The dashboard is a **Next.js 16** application using the App Router with React Server Components and Server Actions.
 
-```
+```text
 app/
   layout.tsx                  ← Root layout (theme, telemetry, nav)
   projects/page.tsx           ← Server component: list all Claude projects
@@ -275,22 +292,22 @@ app/
 
 **Key design decisions:**
 
-- No database — all persistent state is in plain files (`~/.failproofai/`, `~/.claude/projects/`).
-- Server Actions for mutations — no REST API needed for CRUD operations.
-- React Server Components for read pages — faster initial load, no client bundle for data fetching.
+- No database - all persistent state is in plain files (`~/.failproofai/`, `~/.claude/projects/`).
+- Server Actions for mutations - no REST API needed for CRUD operations.
+- React Server Components for read pages - faster initial load, no client bundle for data fetching.
 - Client components only where interactivity is needed (policy toggles, activity search, log viewer).
 
 ---
 
 ## File layout
 
-```
+```text
 failproofai/
 ├── bin/
 │   └── failproofai.mjs           # CLI router (hook / dashboard / install / etc.)
 ├── src/hooks/
 │   ├── handler.ts                # Hook event pipeline
-│   ├── builtin-policies.ts       # 35+ policy definitions
+│   ├── builtin-policies.ts       # 26 policy definitions
 │   ├── policy-evaluator.ts       # Policy execution engine
 │   ├── policy-registry.ts        # Policy registration and lookup
 │   ├── policy-types.ts           # TypeScript interfaces

package/.next/standalone/docs/{built-in-policies.md → built-in-policies.mdx}

@@ -1,10 +1,10 @@
 ---
 title: Built-in Policies
-description: "All 35+ security policies with descriptions and parameters"
+description: "All 30 built-in policies that catch common agent failure modes"
 icon: shield
 ---
 
-failproofai ships with 35+ built-in security policies. Each policy fires on a specific hook event type and tool name. Eight policies accept parameters that let you tune their behavior without writing code.
+failproofai ships with 30 built-in policies that catch common agent failure modes. Each policy fires on a specific hook event type and tool name. Nine policies accept parameters that let you tune their behavior without writing code. Four beta workflow policies enforce a commit → push → PR → CI pipeline before Claude stops.
 
 ---
 
@@ -21,13 +21,19 @@ Policies are grouped into categories:
 | [Git](#git) | block-push-master, block-work-on-main, block-force-push, warn-git-amend, warn-git-stash-drop, warn-all-files-staged | PreToolUse |
 | [Database](#database) | warn-destructive-sql, warn-schema-alteration | PreToolUse |
 | [Warnings](#warnings) | warn-large-file-write, warn-package-publish, warn-background-process, warn-global-package-install | PreToolUse |
+| [Workflow (beta)](#workflow-beta) | require-commit-before-stop, require-push-before-stop, require-pr-before-stop, require-ci-green-before-stop | Stop |
 
-Policies that start with `block-` return a **deny** decision (Claude cannot proceed). Policies that start with `warn-` return an **instruct** decision (Claude gets extra context but can proceed). Policies that start with `sanitize-` also return deny but fire after tool execution to redact secrets from output before Claude sees it.
+- **`block-`** — stop the agent from proceeding.
+- **`warn-`** — give the agent additional context so it can self-correct.
+- **`sanitize-`** — scrub sensitive data from tool output before the agent sees it.
+- **`require-`** — block the Stop event until conditions are met.
 
 ---
 
 ## Dangerous commands
 
+Prevent agents from running operations that are hard to undo or that could damage the host system.
+
 ### `block-sudo`
 
 **Event:** PreToolUse (Bash)  
@@ -55,7 +61,9 @@ Blocks invocations that include the `sudo` keyword. Pattern matching is done on
 
 With this config, `sudo systemctl status nginx` is allowed, but `sudo rm /etc/hosts` is denied.
 
-> **Security note:** Patterns are matched against parsed tokens, not the raw command string. This prevents bypass via appended shell operators (e.g. `sudo systemctl status x; rm -rf /` does not match `sudo systemctl status *`).
+<Note>
+Patterns are matched against parsed tokens, not the raw command string. This prevents bypass via appended shell operators (e.g. `sudo systemctl status x; rm -rf /` does not match `sudo systemctl status *`).
+</Note>
 
 ---
 
@@ -96,7 +104,7 @@ No parameters.
 ### `block-failproofai-commands`
 
 **Event:** PreToolUse (Bash)  
-**Default:** Denies commands that would uninstall or disable failproofai itself (e.g. `npm uninstall failproofai`, `failproofai --remove-policies`).
+**Default:** Denies commands that would uninstall or disable failproofai itself (e.g. `npm uninstall failproofai`, `failproofai policies --uninstall`).
 
 No parameters.
 
@@ -104,7 +112,7 @@ No parameters.
 
 ## Secrets (sanitizers)
 
-Sanitizer policies fire on **PostToolUse** events. When Claude runs a Bash command, reads a file, or calls any tool, these policies inspect the output before it is returned to Claude. If a secret pattern is detected, the policy returns a deny decision that prevents the output from being passed back.
+Stop agents from leaking credentials into their context or output. Sanitizer policies fire on **PostToolUse** events. When Claude runs a Bash command, reads a file, or calls any tool, these policies inspect the output before it is returned to Claude. If a secret pattern is detected, the policy returns a deny decision that prevents the output from being passed back.
 
 ### `sanitize-jwt`
 
@@ -172,12 +180,14 @@ No parameters.
 
 ## Environment
 
+Protect sensitive environment configuration from being read or exposed by agents.
+
 ### `block-env-files`
 
 **Event:** PreToolUse (Bash, Read)  
 **Default:** Denies reading `.env` files via `cat .env`, `Read` tool calls with `.env` as the file path, etc.
 
-Does not block `.envrc` or other environment-adjacent files — only files named exactly `.env`.
+Does not block `.envrc` or other environment-adjacent files - only files named exactly `.env`.
 
 No parameters.
 
@@ -194,6 +204,8 @@ No parameters.
 
 ## File access
 
+Keep agents working inside project boundaries and away from sensitive files.
+
 ### `block-read-outside-cwd`
 
 **Event:** PreToolUse (Read, Bash)  
@@ -246,6 +258,8 @@ No parameters.
 
 ## Git
 
+Prevent accidental pushes, force-pushes, and branch mistakes that are hard to undo.
+
 ### `block-push-master`
 
 **Event:** PreToolUse (Bash)  
@@ -269,7 +283,9 @@ No parameters.
 }
 ```
 
-> To allow pushing to all branches (effectively disabling this policy without removing it from `enabledPolicies`), set `protectedBranches: []`.
+<Tip>
+To allow pushing to all branches (effectively disabling this policy without removing it from `enabledPolicies`), set `protectedBranches: []`.
+</Tip>
 
 ---
 
@@ -324,6 +340,8 @@ No parameters.
 
 ## Database
 
+Catch destructive SQL operations before they execute against your database.
+
 ### `warn-destructive-sql`
 
 **Event:** PreToolUse (Bash)  
@@ -344,6 +362,8 @@ No parameters.
 
 ## Warnings
 
+Give agents extra context before potentially risky but non-destructive operations.
+
 ### `warn-large-file-write`
 
 **Event:** PreToolUse (Write)  
@@ -367,7 +387,9 @@ No parameters.
 }
 ```
 
-> **Note:** The hook handler enforces a 1 MB stdin limit on payloads. To test this policy with small content, set `thresholdKb` to a value well below 1024.
+<Note>
+The hook handler enforces a 1 MB stdin limit on payloads. To test this policy with small content, set `thresholdKb` to a value well below 1024.
+</Note>
 
 ---
 
@@ -398,15 +420,115 @@ No parameters.
 
 ---
 
+## AI behavior
+
+Detect when agents get stuck or behave unexpectedly.
+
+### `warn-repeated-tool-calls`
+
+**Event:** PreToolUse (all tools)  
+**Default:** Instructs Claude to reconsider when the same tool is called 3+ times with identical parameters - a common sign the agent is stuck in a loop.
+
+No parameters.
+
+---
+
+## Workflow (beta)
+
+Enforce a disciplined end-of-session workflow. These policies fire on the **Stop** event and deny Claude from stopping until each condition is met. They follow a natural dependency chain: commit → push → PR → CI. If a policy denies, later policies in the chain are skipped (deny short-circuits).
+
+All workflow policies are **fail-open**: if the required tool is not available (e.g. `gh` not installed, no git remote), the policy allows with an informational message explaining why the check was skipped.
+
+### `require-commit-before-stop`
+
+**Event:** Stop  
+**Default:** Denies stopping when there are uncommitted changes (modified, staged, or untracked files). Returns an informational message when the working directory is clean.
+
+No parameters.
+
+---
+
+### `require-push-before-stop`
+
+**Event:** Stop  
+**Default:** Denies stopping when there are unpushed commits or when the current branch has no remote tracking branch. Suggests `git push -u` to create a tracking branch if needed. Fails open if no remote is configured.
+
+**Parameters:**
+
+| Param | Type | Default | Description |
+|-------|------|---------|-------------|
+| `remote` | `string` | `"origin"` | Remote name to push to. |
+
+**Example:**
+
+```json
+{
+  "policyParams": {
+    "require-push-before-stop": {
+      "remote": "upstream"
+    }
+  }
+}
+```
+
+---
+
+### `require-pr-before-stop`
+
+**Event:** Stop  
+**Default:** Denies stopping when no pull request exists for the current branch, or when the existing PR is closed/merged. Instructs Claude to create a PR with `gh pr create`.
+
+No parameters.
+
+<Note>
+This policy requires [GitHub CLI](https://cli.github.com/) (`gh`) to be installed and authenticated.
+Run `gh auth login` with a personal access token that has `repo` scope for read access to
+pull requests. If `gh` is not installed or not authenticated, the policy fails open and reports the reason to Claude.
+</Note>
+
+---
+
+### `require-ci-green-before-stop`
+
+**Event:** Stop  
+**Default:** Denies stopping when CI checks are failing or still running on the current branch. Treats `skipped` conclusions as success. Returns an informational message when all checks pass.
+
+No parameters.
+
+<Note>
+This policy requires [GitHub CLI](https://cli.github.com/) (`gh`) to be installed and authenticated.
+Run `gh auth login` with a personal access token that has `repo` scope for read access to
+Actions workflow runs. If `gh` is not installed or not authenticated, the policy fails open and reports the reason to Claude.
+</Note>
+
+---
+
 ## Beta policies
 
-Some policies are marked `beta` and are not installed by default. To include them:
+Some policies are marked `beta` and are not installed by default. Beta policies may have rough edges or generate false positives. They graduate to stable in future releases.
+
+**Current beta policies:**
+
+- `require-commit-before-stop` — commit all changes before stopping
+- `require-push-before-stop` — push all commits to remote
+- `require-pr-before-stop` — ensure a PR exists for the branch
+- `require-ci-green-before-stop` — all CI checks must pass
+
+Together, these enforce a **commit → push → PR → CI** workflow.
+
+To install all beta policies:
+
+```bash
+failproofai policies --install --beta
+```
+
+Or install specific workflow policies:
 
 ```bash
-failproofai --install-policies --beta
+failproofai policies --install require-commit-before-stop require-push-before-stop require-pr-before-stop require-ci-green-before-stop
 ```
 
-Beta policies may have rough edges or generate false positives. Use `failproofai --list-policies` to see which policies carry the beta flag.
+Run `failproofai policies` to see which policies carry the beta flag.
 
 ---
 

package/.next/standalone/docs/cli/dashboard.mdx

@@ -0,0 +1,28 @@
+---
+title: View sessions
+description: "Launch the dashboard to browse agent sessions and manage policies"
+---
+
+```bash
+failproofai
+```
+
+Starts the web dashboard at `http://localhost:8020`.
+
+## Options
+
+| Flag | Description |
+|------|-------------|
+| `--port <number>` | Port to listen on (default: `8020`) |
+| `--projects-path <path>` | Override where Claude Code project folders are found |
+| `--allowed-origins <origins>` | Comma-separated hosts/IPs allowed to access dev resources |
+
+## Examples
+
+```bash
+# Launch on a different port
+failproofai --port 9000
+
+# Use a custom projects path
+failproofai --projects-path ~/my-claude-projects
+```

package/.next/standalone/docs/cli/environment-variables.mdx

@@ -0,0 +1,34 @@
+---
+title: Environment variables
+description: "Configure failproofai behavior with environment variables"
+---
+
+## Dashboard
+
+| Variable | Description |
+|----------|-------------|
+| `PORT` | Dashboard port (default: `8020`) |
+| `CLAUDE_PROJECTS_PATH` | Override where Claude Code project folders are found |
+| `FAILPROOFAI_DISABLE_PAGES=policies,projects` | Comma-separated dashboard pages to hide |
+| `FAILPROOFAI_ALLOWED_DEV_ORIGINS` | Hosts/IPs allowed to access dev resources. Same as `--allowed-origins`. |
+
+## Logging
+
+| Variable | Description |
+|----------|-------------|
+| `FAILPROOFAI_LOG_LEVEL=info\|warn\|error` | Server log level (default: `warn`) |
+| `FAILPROOFAI_HOOK_LOG_FILE` | Custom hook log file path, or `true` for default (`~/.failproofai/logs/hooks.log`) |
+
+## Telemetry
+
+| Variable | Description |
+|----------|-------------|
+| `FAILPROOFAI_TELEMETRY_DISABLED=1` | Disable anonymous usage telemetry |
+
+## LLM (for policy evaluation)
+
+| Variable | Description |
+|----------|-------------|
+| `FAILPROOFAI_LLM_BASE_URL` | LLM API endpoint (default: `https://api.openai.com/v1`) |
+| `FAILPROOFAI_LLM_API_KEY` | API key for LLM-powered policies |
+| `FAILPROOFAI_LLM_MODEL` | Model name (default: `gpt-4o-mini`) |

package/.next/standalone/docs/cli/hook.mdx

@@ -0,0 +1,30 @@
+---
+title: Hook handler (internal)
+description: "The subprocess Claude Code calls on each tool event"
+---
+
+```bash
+failproofai --hook <EventType>
+```
+
+This is the command registered in Claude Code's `settings.json` by `failproofai policies --install`. You don't normally call this directly.
+
+Reads a JSON payload from stdin, evaluates all enabled policies, and exits with a code indicating the decision:
+
+| Exit code | Decision | Effect |
+|-----------|----------|--------|
+| `0` | `allow` | Permit the action |
+| `1` | `deny` | Block the action - Claude sees the denial reason |
+| `2` | `instruct` | Inject guidance into Claude's context |
+
+### Supported event types
+
+| Category | Events |
+|----------|--------|
+| **Tool execution** | `PreToolUse`, `PostToolUse`, `PostToolUseFailure`, `PermissionRequest`, `PermissionDenied` |
+| **Session lifecycle** | `SessionStart`, `SessionEnd`, `Stop`, `StopFailure` |
+| **User interaction** | `UserPromptSubmit`, `Notification`, `Elicitation`, `ElicitationResult` |
+| **Subagents & tasks** | `SubagentStart`, `SubagentStop`, `TaskCreated`, `TaskCompleted`, `TeammateIdle` |
+| **Configuration** | `InstructionsLoaded`, `ConfigChange`, `CwdChanged` |
+| **File system** | `FileChanged`, `WorktreeCreate`, `WorktreeRemove` |
+| **Context** | `PreCompact`, `PostCompact` |

package/.next/standalone/docs/cli/install-policies.mdx

@@ -0,0 +1,48 @@
+---
+title: Install policies
+description: "Enable policies so they run on every agent tool call"
+---
+
+```bash
+failproofai policies --install [policy-names...] [options]
+```
+
+Writes hook entries into Claude Code's `settings.json` so failproofai intercepts tool calls.
+
+Aliases: `failproofai p -i`
+
+## Options
+
+| Flag | Description |
+|------|-------------|
+| `--scope user` | Install into `~/.claude/settings.json` (default - all sessions) |
+| `--scope project` | Install into `.claude/settings.json` in the current directory |
+| `--scope local` | Install into `.claude/settings.local.json` in the current directory |
+| `--custom <path>` / `-c` | Path to a JS file containing custom hook policies |
+| `--beta` | Include beta policies |
+
+## Behavior
+
+- **No policy names** - opens an interactive prompt to select policies
+- **Specific names** - enables those policies (added to any already enabled)
+- **`all`** - enables every available policy
+
+Installation is additive: running `--install` again adds new policies without removing existing ones.
+
+## Examples
+
+```bash
+# Install all default policies globally (interactive)
+failproofai policies --install
+
+# Install specific policies for the current project
+failproofai policies --install block-sudo sanitize-api-keys --scope project
+
+# Enable all policies at once
+failproofai policies --install all
+
+# Install with a custom policies file
+failproofai policies --install --custom ./my-policies.js
+```
+
+When `--custom <path>` is provided, the file is validated immediately - it must call `customPolicies.add()` at least once. The resolved path is saved to `policies-config.json` as `customPoliciesPath`.

package/.next/standalone/docs/cli/list-policies.mdx

@@ -0,0 +1,31 @@
+---
+title: List policies
+description: "See which policies are enabled, their parameters, and custom policies"
+---
+
+```bash
+failproofai policies
+```
+
+Shows all policies with their status, configured parameters, and custom policies.
+
+## Sample output
+
+```text
+Failproof AI Hook Policies (user)
+
+  Status  Name                          Description
+  ──────  ──────────────────────────────────────────────────────────────
+  ✓       block-sudo                    Block sudo commands
+            allowPatterns: ["sudo systemctl status"]
+  ✓       block-rm-rf                   Block recursive deletions
+  ✗       block-curl-pipe-sh            Block curl|bash patterns
+  ✓       sanitize-api-keys             Redact API keys from output
+            additionalPatterns: [{ regex: "MY_TOKEN_...", label: "..." }]
+
+  ── Custom Policies (/home/alice/myproject/my-policies.js) ──────────────
+  ✓       require-jira-ticket           Block commits without ticket
+  ✓       approval-gate                 Approval gate for destructive ops
+```
+
+Unknown keys in `policyParams` are flagged here so you can catch typos early.

package/.next/standalone/docs/cli/remove-policies.mdx

@@ -0,0 +1,44 @@
+---
+title: Uninstall policies
+description: "Remove hook entries from Claude Code's settings"
+---
+
+```bash
+failproofai policies --uninstall [policy-names...] [options]
+```
+
+Removes failproofai hook entries from Claude Code's `settings.json`.
+
+Aliases: `failproofai p -u`
+
+## Options
+
+| Flag | Description |
+|------|-------------|
+| `--scope user` | Remove from global settings (default) |
+| `--scope project` | Remove from project settings |
+| `--scope local` | Remove from local settings |
+| `--scope all` | Remove from all scopes at once |
+| `--custom` / `-c` | Clear the `customPoliciesPath` from config |
+| `--beta` | Remove only beta policies from config |
+
+## Behavior
+
+- **No policy names** - removes all failproofai hook entries from the settings file
+- **Specific names** - disables those policies but keeps hooks installed
+
+## Examples
+
+```bash
+# Remove all hooks globally
+failproofai policies --uninstall
+
+# Disable a specific policy (keeps hooks installed)
+failproofai policies --uninstall block-sudo
+
+# Remove hooks from every scope
+failproofai policies --uninstall --scope all
+
+# Clear custom policies path
+failproofai policies --uninstall --custom
+```

package/.next/standalone/docs/cli/version.mdx

@@ -0,0 +1,12 @@
+---
+title: Check version
+description: "Print the installed failproofai version"
+---
+
+```bash
+failproofai --version
+# or
+failproofai -v
+```
+
+Prints the installed version number.