The snapshot is a hook, not a habit

The agent is about to run a migration. It calls bash. Before the command executes, a PreToolUse hook fires: a shell command you registered once, matched on the tool name, that curls POST /api/v1/containers/{id}/snapshots with an alias. The snapshot lands. Then the migration runs.

The agent didn't decide to snapshot. It doesn't know the hook exists. The care sits in the lifecycle, as an entry in .hoody/settings.json, and it fires whether the model is having a good day or not.

Prompting the agent to snapshot before risky steps works until the one turn it forgets. A hook doesn't forget. Every destructive tool call is preceded by a restore point, and a bad migration costs one restore.

Safety that lives in the prompt is a suggestion. Safety that lives in a hook is a guarantee.