vetto 0.2.16

Daemon-less sandbox + security layer for AI coding agents (Landlock/Seatbelt, TUI statusline, post-session audit reports)
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
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65

# OpenCode Integration Guide

OpenCode is an open-source terminal coding assistant. Vetto provides zero-config kernel sandboxing and network egress allowlisting for OpenCode sessions without requiring Docker or root privileges.

---

## 1. Quick Start: Transparent Shim

The fastest and most reliable way to sandbox OpenCode is via Vetto priority shims:

```bash
vetto enable opencode
```

Once enabled, simply run OpenCode normally in any project:

```bash
opencode
# Or unattended:
opencode run --yes
```

Vetto intercepts the execution, defaults network egress to provider inference APIs (`api.openai.com`, `api.anthropic.com`, `openrouter.ai`), masks system credentials (`~/.ssh`, `~/.aws`, `.env`), and isolates disk access.

---

## 2. Configuration Runner Integration

You can also integrate Vetto directly into OpenCode's configuration runner:

```bash
vetto plugin install opencode
```

This merges the sandbox runner into `~/.config/opencode/config.json`:

```json
{
  "sandbox": {
    "command": "vetto",
    "args": [
      "--ci",
      "--"
    ]
  },
  "vetto": {
    "enabled": true,
    "version": "0.2.13"
  }
}
```

---

## 3. Direct Execution

To run OpenCode inside a specific preset or custom boundary:

```bash
# Balanced preset (recommended: workspace write, secrets masked, inference network)
vetto -- opencode

# Paranoid preset (read-only workspace, zero network)
vetto --preset paranoid -- opencode
```