Potluck blog
Guides and notes on running GitHub Actions jobs and coding agents on your team's idle machines, from the people who make Potluck. Atom feed
-
Give your AI agent a sandbox over MCP, on a machine you own
Add one line of MCP configuration and a coding agent gets throwaway VMs and sandboxes on your team's idle Macs and Linux boxes to run its commands in. What it can do and what it keeps away.
-
Use the E2B SDK on your own machines
potluck-e2b answers the calls the E2B Python and TypeScript SDKs make, so code written for E2B sandboxes runs on your team's idle Macs and Linux boxes with only its environment changed. What it covers and how to set it up.
-
How to pool your team's spare Macs and Linux boxes for builds and coding agents
How a pool of a team's or friends' spare computers works: who can use whose machine, what a machine owner shares, and how a Mac owner takes it back.
-
How to run Claude Code and Codex in a sandbox on your own machines instead of a hosted sandbox service
Give Claude Code, Codex or another coding agent a throwaway sandbox on a Mac or Linux box you own. What a sandbox must isolate, and how Potluck sets it up.
-
How to run a self-hosted GitHub Actions runner on your own Mac, with a fresh VM for each job
Run GitHub Actions jobs on your own Mac or Mac mini, each in a fresh throwaway VM, so one job never touches your files or the next job.