Your coding agents are pigs. Piggery is the farm.

Work goes into a pig's trough and waits there until the pig is back. It only counts as eaten when the job is actually done, not when the pig sniffed at it. Every pig also has a pen: its role says who it may talk to and whether it may have piglets (workers). The farm checks the fence itself, so no amount of sweet talk gets a pig through it.

pi, Claude Code, Codex, omp and dsh pigs all live on the same farm and talk to each other. The farm is one Go binary and a SQLite file, and nothing runs in the cloud.

flowchart LR
  a["agent on pi"] <-->|mail| farm
  b["agent on Claude Code"] <-->|mail| farm
  c["agent on …"] <-->|mail| farm
  farm(("🐖 piggery<br/>mailbox + gate")) --- shape[["a team layout<br/>supervisor → workers<br/>peer ↔ peer<br/>…"]]
  shape --> work[/"your tasks and projects,<br/>plowed"/]

Every agent gets the same mailbox, whatever its harness: a pi session can mail a Claude Code session, and a worker's answer wakes whoever is waiting for it. Each mail and each spawn passes the gate, which checks it against the team's layout: a small YAML file you pick or write. A few come built in as examples (supervisor-executor, slp, council, p2p); any other shape is another file.

A role's workers run on the harness its template names (spawn.harness), else on the one of the session that founded the team. piggery setup alone shows each harness's version and whether piggery is installed in it.

curl -fsSL https://raw.githubusercontent.com/sting8k/piggery/main/install.sh | sh
piggery setup pi       # and/or: claude, codex, omp, dsh

The script picks the build for your OS and CPU (Linux or macOS, amd64 or arm64), checks it against the release's checksums.txt, and installs it in ~/.local/bin (PIGGERY_INSTALL_DIR to change it, PIGGERY_VERSION=v0.3.0 for a given release). By hand: download piggery-<os>-<arch> (darwin-arm64, darwin-amd64, linux-amd64, linux-arm64) from the latest release, chmod +x it and put it on your PATH.

Using Paseo? piggery setup paseo adds a Piggery view (the same as piggery top) to the app. Turn on plugins in Paseo's settings once.

Or build it: go install github.com/sting8k/piggery/cmd/piggery@latest (Go 1.26+). piggery update installs a newer release. Every release has a checksums.txt; what changed is in CHANGELOG.md.

1. Open pi, Claude Code, Codex, omp or dsh web in your project.
2. Ask it for a team: "make a supervisor-executor team to fix the failing tests".
3. Watch the farm: piggery top.

More: docs/guide.md covers running teams, watching and stepping in, and customizing ~/.piggery (config, templates, worker profiles, your own rules); docs/reference.md lists every command, config key, profile key and manifest key.

Make your own: piggery template new mine --from slp, then edit ~/.piggery/templates/mine/manifest.yaml (see the guide).

go build ./cmd/piggery
go test ./...

MIT