nixos/sfh: Add slop-cannon container for agents

A container on `sfh` for coding agents driven remotely through Paseo,
using our relay on `middleman`. Agents run as the unprivileged
`slop-cannon` user; Claude managed settings disable bypass mode and
deny raw deploy and `ssh-machine` access.

Move the Claude Code and Codex configuration out of `gui` into a
shared `my.agents` home-manager module.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-16 00:39:48 +00:00
co-authored by Claude Opus 5.5
parent 5af71ea231
commit a62b8351fa
17 changed files with 599 additions and 116 deletions
+3
View File
@@ -24,6 +24,8 @@ from `river` and runs its root off NVMe-oF from `cellar`.
`/var/lib/frigate`.
- USB: two host ports are passed to the VM (qemu flags) for the Zigbee coordinator and webcam used
by `hass`; the nspawn unit gets `DeviceAllow` for `char-ttyUSB` and `char-video4linux`.
- `slop-cannon`'s nspawn unit gets a low `CPUWeight` and a `MemoryMax`, so agent builds can't starve
`hass` and `unifi`, and a larger `/tmp` tmpfs than nspawn's default (10% of RAM).
## Network assignments
@@ -53,6 +55,7 @@ back through the VM handoffs to the physical switch connections.
|---|---|
| [`hass`](containers/hass.md) | Home Assistant + Frigate + MQTT |
| [`unifi`](containers/unifi.md) | UniFi controller |
| [`slop-cannon`](containers/slop-cannon.md) | Coding agents, driven remotely through Paseo |
## Notable config files