safe-chains 0.133.2

Auto-allow safe, read-only bash commands in agentic coding tools
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

# Safety Levels

Every allowed command is classified into one of three safety levels:

| Level | Description | Examples |
|-------|-------------|----------|
| `inert` | Pure read/display, no code execution | `cat`, `grep`, `ls`, `git log` |
| `safe-read` | Executes code but read-only | `cargo test`, `rspec`, `npm test` |
| `safe-write` | May modify files but considered safe | `cargo build`, `go build` |

Use `--level` to set a threshold. Only commands at or below the threshold pass:

```bash
safe-chains --level inert "cat foo"          # exit 0 (inert <= inert)
safe-chains --level inert "cargo test"       # exit 1 (safe-read > inert)
safe-chains --level safe-read "cargo test"   # exit 0 (safe-read <= safe-read)
safe-chains --level safe-read "cargo build"  # exit 1 (safe-write > safe-read)
```

Without `--level`, the default threshold is `safe-write` (all allowed commands pass).

`--help` and `--version` on any command are always `inert`.

Levels propagate through pipelines, wrappers, and substitutions — a pipeline's level is the maximum of its components.