velaclaw 0.3.0

Protocol-driven autonomous AI agent runtime with intelligent model selection and multi-model negotiation.
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
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128

# VelaClaw Operations Runbook

This runbook is for operators who maintain availability, security posture, and incident response.

Last verified: **February 18, 2026**.

## Scope

Use this document for day-2 operations:

- starting and supervising runtime
- health checks and diagnostics
- safe rollout and rollback
- incident triage and recovery

For first-time installation, start from [one-click-bootstrap.md](one-click-bootstrap.md).

## Runtime Modes

| Mode | Command | When to use |
|---|---|---|
| Foreground runtime | `velaclaw daemon` | local debugging, short-lived sessions |
| Foreground gateway only | `velaclaw gateway` | webhook endpoint testing |
| User service | `velaclaw service install && velaclaw service start` | persistent operator-managed runtime |

## Baseline Operator Checklist

1. Validate configuration:

```bash
velaclaw status
```

2. Verify diagnostics:

```bash
velaclaw doctor
velaclaw channel doctor
```

3. Start runtime:

```bash
velaclaw daemon
```

4. For persistent user session service:

```bash
velaclaw service install
velaclaw service start
velaclaw service status
```

## Health and State Signals

| Signal | Command / File | Expected |
|---|---|---|
| Config validity | `velaclaw doctor` | no critical errors |
| Channel connectivity | `velaclaw channel doctor` | configured channels healthy |
| Runtime summary | `velaclaw status` | expected provider/model/channels |
| Daemon heartbeat/state | `~/.velaclaw/daemon_state.json` | file updates periodically |

## Logs and Diagnostics

### macOS / Windows (service wrapper logs)

- `~/.velaclaw/logs/daemon.stdout.log`
- `~/.velaclaw/logs/daemon.stderr.log`

### Linux (systemd user service)

```bash
journalctl --user -u velaclaw.service -f
```

## Incident Triage Flow (Fast Path)

1. Snapshot system state:

```bash
velaclaw status
velaclaw doctor
velaclaw channel doctor
```

2. Check service state:

```bash
velaclaw service status
```

3. If service is unhealthy, restart cleanly:

```bash
velaclaw service stop
velaclaw service start
```

4. If channels still fail, verify allowlists and credentials in `~/.velaclaw/config.toml`.

5. If gateway is involved, verify bind/auth settings (`[gateway]`) and local reachability.

## Safe Change Procedure

Before applying config changes:

1. backup `~/.velaclaw/config.toml`
2. apply one logical change at a time
3. run `velaclaw doctor`
4. restart daemon/service
5. verify with `status` + `channel doctor`

## Rollback Procedure

If a rollout regresses behavior:

1. restore previous `config.toml`
2. restart runtime (`daemon` or `service`)
3. confirm recovery via `doctor` and channel health checks
4. document incident root cause and mitigation

## Related Docs

- [one-click-bootstrap.md](one-click-bootstrap.md)
- [troubleshooting.md](troubleshooting.md)
- [config-reference.md](config-reference.md)
- [commands-reference.md](commands-reference.md)