Files
nixfiles/docs/sites/home/slop-cannon.md
T
jackos1998andClaude Opus 5.5 a6491c7535
CI / Check, build and cache nixfiles (push) Successful in 45m39s
Update docs / update (push) Successful in 1m0s
nixos/slop-cannon: Move to a VM on palace
Give agents their own kernel, Nix daemon and disk for workloads that
need root. Put the VM on the `untrusted` VLAN with MAC spoof
checking on VF 5.

Export a dedicated partition from `cellar` and connect it on
`palace`. Give the VM its own SSH host key and age secrets for Paseo
and Gitea. Keep the agent home and Paseo identity on persistent
storage and provide `slop-pair` for pairing clients.

Retire the container, restore `sfh` to 8 cores and 32 GiB, and rekey
the shared password secret. Document the VM and its operating
procedures on the relevant box pages.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 22:02:14 +00:00

11 KiB
Raw Blame History

slop-cannon

Coding agents (Claude Code and Codex), driven from the phone or a browser through Paseo, running in a VM on palace with root inside it.

VM resources

vCPUs RAM Disk Network Other
16c × 2t (overcommitted) 48 GiB 512 GiB virtio, NVMe-oF from cellar via palace SR-IOV VF 5 (44:00.6) on VLAN 120 installer ISO

vm@slop-cannon has a low CPUWeight on palace, so cellar, river and sfh win under contention. palace has kvm_amd nested=1, so the guest has /dev/kvm.

Role

  • Runs the Paseo daemon and the agents it starts, as the user slop-cannon. Agents have root in the VM (wheel, passwordless doas): nested VMs, kernel modules, system services.
  • A normal deploy node (deploy .#slop-cannon, ssh-machine slop-cannon).
  • Everything inside the guest is treated as agent-controlled. The boundaries are outside it: the untrusted filter on the routers, the VLAN tag on the NIC and the disk connection on palace. Credentials for deploying or logging into other boxes stay outside the VM.

Network assignments

See the consolidated network assignments table (this box: slop-cannon).

Network

  • The only interface, lan-untrusted, is SR-IOV VF 5 on palace. The NIC tags and filters VLAN 120 and enforces MAC spoof checking on the host side. The guest loads mlx5_core at boot. See the VF attachment table.
  • A static untrusted address (outside both routers' DHCP pools), MTU 1500. DNS is Cloudflare, as untrusted's DHCP and RAs hand out; the routers' resolvers aren't reachable from untrusted.
  • The routers keep untrusted to the Internet (see Untrusted clients). git.nul.ie and paseo-relay.nul.ie resolve to colony IPv6 addresses, which are rejected, so Gitea SSH and the Paseo relay fall back to IPv4 immediately.
  • SSH from hi and lo works through the routers. The VM shares layer 2 with other clients on the untrusted VLAN.
  • Builds use the guest's own Nix daemon and store, behind the same filter.

Storage

  • One virtio disk: GPT with a 2 GiB ESP (partition label esp) and an LVM PV in VG main.
  • slop-cannon-nix, slop-cannon-persist and slop-cannon-tmp are thin LVs in main/tpool, overcommitted, so space goes to whichever needs it. The pool takes 90% of the VG; LVM grows it into the rest at 80% full (thin_pool_autoextend_threshold). Watch lvs if it gets close.
  • The root is tmproot; /tmp is its own LV, cleaned on boot and mounted with discard, so agents' scratch files don't use RAM and freed space returns to the pool.
  • The disk is nqn.2016-06.io.spdk:slop-cannon on cellar, connected by palace (see palace's disk notes). The guest never speaks NVMe-oF.

Users and secrets

User Purpose
slop-cannon Runs Paseo and the agents; wheel and kvm; locked password, Dev's SSH key; home persisted; UID/GID pinned in lib.my.c.ids
dev Administration; locked password, Dev's SSH key
  • No user-passwd.txt (my.user.passwordSecret = null): root belongs to the agents, so the box gets no shared secrets. Recovery is through the installer ISO.
  • The VM's SSH host key is the age identity for slop-cannon/paseo.env and slop-cannon/gitea-key. Agents can read the host key and decrypt anything encrypted to it.

Paseo

A daemon (paseo-server) that starts and manages agents and serves a WebSocket API to the Paseo app, the web UI and the paseo CLI. Claude Code runs through the Claude Agent SDK, using the installed claude and its claude.ai login; Codex runs through codex app-server.

Service

  • The upstream services.paseo module (flake input paseo, pinned to a release, imported in nixos/modules/common.nix), with a package override for the web UI bug getpaseo/paseo#7673.
  • Runs as slop-cannon, so agents use that user's logins and settings, with ~/.paseo as PASEO_HOME.
  • The daemon password comes from the age secret slop-cannon/paseo.env. To read it for a new client, follow Pair a Paseo client.
  • The service is not restarted on deploy, so running agents aren't interrupted. Restart it by hand (doas systemctl restart paseo) to pick up a new config; stopping it stops its agents.
  • Startup takes about a minute and a half while bundled plugins load; the daemon answers 503 until it is ready.

Settings

services.paseo.settings is rewritten into ~/.paseo/config.json on every start, so changes made from the app don't survive a restart. It:

  • disables the tools Paseo injects into agents (daemon.mcp.injectIntoAgents = false), which would let an agent change its own mode, answer its own permission prompts or open terminals;
  • requires relay replay protection;
  • turns off dictation and voice, which would otherwise download a large local speech model;
  • hides providers other than Claude and Codex;
  • adds a "Claude, accept edits" agent profile. Each provider's default mode is hardcoded upstream (Claude auto, Codex auto-review), and profiles are the only way to preset one.

Connectivity

  • The daemon listens on 127.0.0.1:6767 only. The phone app and the browser reach it through our relay on middleman (paseo-relay.nul.ie).
  • Traffic through the relay is end-to-end encrypted between the app and the daemon; the relay sees only addresses, timing and sizes. The pairing QR code or link is the trust anchor; treat it like a password. Switching relays means re-pairing.
  • Push notifications go from the daemon to Expo's push service (exp.host), one outbound request per notification carrying its text.
  • middleman serves the static web app on paseo.nul.ie. The daemon's own web UI stays off.

State

The agent home is backed by /persist/home/slop-cannon. It holds the provider logins and sessions, repos, and ~/.paseo, which contains the daemon keypair, agent records, projects, workspaces and Paseo-managed Git worktrees. Paired clients trust that daemon keypair. Claude sessions live under ~/.claude/projects/ and Codex sessions under ~/.codex/sessions/.

Repos, worktrees and jj

Repos live under ~/src as colocated jj clones (see slop-clone below). Paseo only calls git:

  • A local workspace runs the agent in the checkout itself; jj and Paseo's git views see the same changes. Use it for work you want to steer with jj.
  • A worktree workspace is a git worktree under ~/.paseo/worktrees on its own branch. Use it for unattended agents. Archiving it removes the worktree with --force, losing uncommitted work.
  • Archiving a local workspace removes only Paseo's record; the folder is kept.
  • Only one colocated working copy per repo is possible, so parallel jj-driven work needs separate clones.
  • Don't run jj in a folder while an agent is mid-turn there: jj snapshots its partial edits.

Terminal access

  • The paseo CLI talks to the running daemon: paseo ls, paseo logs -f <id>, paseo send <id> "…", paseo permit ls|allow|deny. It is command-line only, not a chat interface.
  • A session can be taken over in the provider's own TUI by its ID: claude --resume <session> in the agent's folder, or codex resume <session>. paseo import goes the other way. This is a hand-off, not a shared view: stop the agent in Paseo first and don't type in both.

Agent permissions

Paseo has the full rights of slop-cannon, and slop-cannon has root: anyone with the daemon password or a pairing controls the VM.

  • Claude Code and Codex come from the shared my.agents home-manager module.
  • Claude's user settings deny raw deploy, ssh-machine and .keys/, and ask before slop-deploy / slop-ssh. Claude's managed settings (/etc/claude-code/managed-settings.json) repeat the deny rules and disable bypass mode. All of these match command text and live inside the guest, so they steer agents rather than enforce anything.
  • Codex stores its credentials in a file and uses its standard Linux sandbox.
  • Deployments and administrative SSH to other boxes are handled by an operator outside the VM.

SSH and first login

ssh slop-cannon (agent user) and ssh slop-cannon-dev (dev) are the shared aliases, both with ForwardAgent=no. Never forward your SSH agent into the box: agents could use it while you're logged in. For recovery, use the VM serial console for slop-cannon on palace.

The VM uses a Gitea deploy key from the age secret slop-cannon/gitea-key. As slop-cannon, run ssh-keygen -y -f /run/secrets/slop-cannon/gitea-key to get its public key. Add that public key in Gitea as a write-enabled deploy key on each repo agents may use. Commits are authored as Dev through the shared Git config.

To set up provider logins and repos on a fresh agent home, connect with ssh slop-cannon:

  1. claude auth login (a full login; setup-token tokens are not enough for every feature).
  2. codex login --device-auth.
  3. Pair a Paseo client.
  4. slop-clone <owner>/<repo> for each repo. It clones a colocated jj repo into ~/src/<repo>, registers it with Paseo as a local workspace, and prints the box's public key if Gitea refuses the clone.

Pair a Paseo client

  1. On the VM, run slop-pair as slop-cannon. It prints the QR code, pairing link and PASEO_PASSWORD. Keep its output private.

  2. If you only need the QR code and link, run paseo daemon pair as slop-cannon. To look up the password separately, run doas cat /run/secrets/slop-cannon/paseo.env on the VM. You can also decrypt it from a repo checkout with access to the dev age key:

    rage --decrypt -i .keys/dev.key secrets/slop-cannon/paseo.env.age
    
  3. On a phone, scan the QR code from the Paseo app. In a browser, open https://paseo.nul.ie and use the app's paste-pairing-link option. Enter the value after PASEO_PASSWORD= when prompted and open the paired host. If the browser shows “Password required” after opening the link in the address bar, remove that host entry and pair again using the paste dialog.

Notable config files