Field bulletin · Install the beta
Install on one machine. Or all of them.
Potluck is a desktop app that runs open models on hardware you own. Chat with them, give your coding agents a persistent memory over MCP, and join your machines into one private network with the WireGuard mesh built into the app. Every request routes where you say: this machine, your other machines, a trusted circle, or the open pool. Local is the default, and everything else is opt-in per request.
Before you start
| Item | Requirement |
|---|---|
| Mac | macOS 12+, Apple Silicon or Intel. Beta builds are not yet notarized, so the first open is right-click, then Open. Signed and notarized installers are a launch gate. |
| Windows | Windows 10+. The installer is unsigned, so SmartScreen warns once (More info, then Run anyway). We publish a SHA-256 for every build so you can verify it yourself. |
| Linux | Packaged .AppImage/.deb/.rpm builds are in the release pipeline. During the private beta the Linux path is a source install from the repo; ask us for access. |
| Cross-machine | Nothing extra. The WireGuard mesh is embedded in the app, and machines pair from inside the app. No VPN account, no config files, no terminal. |
| Disk | Models are the bulk of it: a few GB for a starter model, more if you pick larger ones. The app shows the download size before it fetches anything, and every download is SHA-256 verified. |
| Access | Private beta. Join the waitlist and we will send a download link. |
Install
One installer per platform. The app carries everything it needs: the inference engine, the memory store, the MCP server, and the mesh. There is no step two where you install something else.
macOS
- Download the DMG for your chip (Apple Silicon or Intel) from the link we send you.
- Double-click. Drag the app to Applications. Eject.
- Right-click the app and choose Open the first time (beta builds are not yet notarized). First launch unpacks the bundled engine (~10-20 seconds).
Windows
- Download the installer .exe from the link we send you.
- On the SmartScreen warning, click "More info" then "Run anyway." Windows builds are unsigned; the same binaries run on our own machines, and you can match the published SHA-256 before you run it.
- After install, Potluck appears in the Start menu.
Linux
Packaged builds have not shipped yet. If you are in the private beta and want the source-install path, reply to your invite and we will send the runbook. Signed .AppImage, .deb, and .rpm packages ship at launch.
First run
The app walks you through setup in four short steps. No account is required to run locally; sign-in exists for membership things (the network, billing when it opens) and nothing else gates on it.
- Hardware check. The app reads your RAM and GPU and tells you what it can run well on this machine.
- Pick a starter model. It downloads with a visible size and progress, hash-verified before it loads.
- Pair your other machines (optional). Machines on the same network find each other; a short pairing code confirms it is really yours.
- Readiness check. Real probes, not a green dot: can this machine actually run inference, is a VPN fighting the mesh, is the mesh port reachable.
Bring your coding agents
Any agent that speaks MCP (Claude Code, Cursor, Zed, Cline, Continue) can use Potluck as its persistent memory: project facts, decisions, and multi-session tasks that survive across sessions and across machines.
You do not hand-write the config. Open Settings, then Connect tools, pick your agent, and the app generates the exact MCP entry pointing at its bundled server. Paste it where your agent expects MCP servers and restart the agent. It will see memory_search, memory_save, task_create, and the rest of the Potluck tools.
The fastest proof it works: ask the agent to remember something, then find it in Potluck's memory browser. The /agents view shows every connected session live, with tool-call metadata only; argument contents stay out of the observability surface by design.
Your machines, one network
Pairing happens inside the app. Machines on the same network discover each other; you confirm with a short pairing code. Under the hood this builds a private WireGuard mesh between machines you own, with no third-party VPN account and no config to edit.
Once paired, the routing scope selector in chat decides where each request runs: this machine, My Machines (a gaming PC with a real GPU answering from the couch laptop), a trusted circle of invited people, or the open pool. Each message carries a receipt of what left your machine and where it ran, honest per route.
Memory works across the mesh too, if you opt in per machine: your agent on the laptop can search memories saved on the desktop. Peers only ever reach the narrow peer endpoints; your full memory store, tasks, conversations, and settings stay loopback-only. Peer reads are read-only; writes stay local.
Honest limits
- Windows installers are unsigned. Gatekeeper on Mac and SmartScreen on Windows both warn during the beta. The Mac build is notarized for the public launch so Gatekeeper opens it normally; Windows stays unsigned, and we publish a SHA-256 for every build so you can verify integrity without a signature.
- Public membership is not open. This page documents the private beta. The waitlist is the way in.
- The open pool is quiet pre-launch. Routing to the open contributor pool works, but there are few contributors before launch. Your own machines and a trusted circle are the scopes that earn their keep today.
- Peer memory sharing is per-machine, all or nothing. When you opt a machine in, paired peers can search that whole store. Per-project sharing flags are on the roadmap.
- Mesh membership is the trust boundary. Any machine paired into your mesh can call the peer endpoints you opted into. A signed-nonce peer credential replacing reachability-as-trust is planned hardening.
Where to go next
- /how-it-works · the routing scopes, the mesh, and what a contributor can and cannot see.
- /benchmarks · measured numbers across memory retrieval, inference, and cross-machine latency on Mac/Linux/Windows.
- /manifesto · why Potluck is built as a member-operated network and a founder-led company.
- /roadmap · what is shipped, in flight, designed, and to be decided.
Not in the beta yet?
Join the waitlist