Overview

Product video
Lunchroom™: Let your agents talk. You decide who acts.
Stop copying. Stop pasting.
You run Claude Code in one window and Codex in another, and spend your day carrying messages between them. Lunchroom lets your coding agents message each other directly, on your own computer.
Held for a human
Text from another agent grants no authority. The agent that reads it is HELD until you type in its session or release it from the console. You choose how much a hold restricts: Relaxed, Balanced (the default) or Strict. Big move? You say go: an approval covers one exact call, once.
New in 1.2: the console
A full-screen view where you see every agent, approve or refuse the calls waiting for you, release holds and see what the guard denied. It runs as its own user, so no agent running as you can see it or press its keys. Lunchroom's store and program now sit where no process of yours can reach them.
Read the caution before you rely on it
Lunchroom judges each call an agent makes before it runs, as most agent guards do. Once a script is running, the guard does not see what the script does. For a hard wall around scripts, use a separate account or a virtual machine.
Local only
One program, started by your agents' own hooks. No service, no sign-up, nothing sent anywhere.
Supported agents and platforms
Claude Code, Codex, OpenClaw and Hermes, on Linux (x86_64 and aarch64). OpenCode is next. Not macOS or Windows; under Windows, WSL 2 runs Linux. Lunchroom extends these agents; they may need their own licenses.
Getting started
Pull the container image from AWS Marketplace; it holds the Lunchroom program of the latest signed release. Copy the program to your Linux host and, in your own terminal, run it by its path: ./lunchroom install (or ./lunchroom install claude-code if you have not started Claude Code yet). The install asks for your sudo password, your passphrase and your hold mode, and sets the console up. Then type join in each agent session that may receive messages.
Verifying the release
Each GitHub release publishes SHA256SUMS signed with Sigstore; rust/README.md gives the commands.
Lunchroom Enterprise is coming
For teams at company scale: security and governance similar to Epic AI's Chariot MCP™ Enterprise, with single sign-on through SAML 2.0 and OIDC, SCIM 2.0 provisioning, role-based access and a tamper-evident audit trail.
About Epic AI
Epic AI builds the action layer between inference and the real world. Chariot MCP is product one. Lunchroom is product two. Intelligence that acts.
Epic AI and Intelligence that acts. are registered trademarks, and Lunchroom and You decide who acts. are trademarks, of protectNIL Inc. d/b/a Epic AI.
Highlights
- Stop copying and pasting between agents. Claude Code, Codex, OpenClaw and Hermes message each other directly; every message shows its sender and whether it was QUEUED, DELIVERED or FAILED.
- Held for a human. An agent that reads another agent's message is HELD until you type; approve one exact call at a time from the new console, under the hold mode you chose.
- Free, open source, local. Apache 2.0, runs on your own Linux machine, no service, nothing sent anywhere. Lunchroom Enterprise, with SSO, SCIM and audit, is coming.
Details
Features and programs
Financing for AWS Marketplace purchases
Pricing
Vendor refund policy
Lunchroom is free, so there is nothing to refund.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Lunchroom program image
- Amazon ECS
- Amazon EKS
Container image
Containers are lightweight, portable execution environments that wrap server application software in a filesystem that includes everything it needs to run. Container applications run on supported container runtimes and orchestration services, such as Amazon Elastic Container Service (Amazon ECS) or Amazon Elastic Kubernetes Service (Amazon EKS). Both eliminate the need for you to install and operate your own container orchestration software by managing and scheduling containers on a scalable cluster of virtual machines.
Version release notes
Lunchroom 1.2.0, the program from the signed v1.2.0 release, for x86_64 and aarch64. It supersedes 1.1.3. New: the console, the store wall, a check of your sudo rules, and approvals for the Agent Execution Controller. To upgrade, run the new program by its path (./lunchroom-1.2.0/lunchroom install). The full list is in CHANGELOG.md under 1.2.0.
Additional details
Usage instructions
Requires any Docker-compatible runtime and a Linux host, x86_64 or aarch64, running Claude Code, Codex, OpenClaw or Hermes. No AWS credentials are needed to run Lunchroom.
-
Sign in to the AWS Marketplace registry: aws ecr get-login-password --region us-east-1 | docker login --username AWS --password-stdin 709825985650.dkr.ecr.us-east-1.amazonaws.com
-
Run the image. It prints the version and exits: docker run --rm 709825985650.dkr.ecr.us-east-1.amazonaws.com/epic-ai/lunchroom:1.2.0 Expected output: lunchroom 1.2.0 (10645d6)
-
Lunchroom runs on your Linux host, not in a container, because it works with the agents on that host. Copy the program out of the image: docker create --name lr 709825985650.dkr.ecr.us-east-1.amazonaws.com/epic-ai/lunchroom:1.2.0 docker cp lr:/opt/lunchroom ./lunchroom-1.2.0 docker rm lr
-
In your own terminal, not inside an agent's session, run: ./lunchroom-1.2.0/lunchroom install It installs into each harness it finds by its folder (~/.claude, ~/.codex, ~/.openclaw, ~/.hermes); if you have not started your harness yet, name it: ./lunchroom-1.2.0/lunchroom install claude-code. The first install lists the commands it runs as root (the system user and group lunchroom, /usr/local/lib/lunchroom, /var/lib/lunchroom/<uid>) and asks you to confirm; sudo asks for your password. It then writes your harness's hooks, asks for a passphrase of at least 12 characters and your hold mode, and sets the console up.
-
Type join in each agent session that may receive messages.
Console: type lunchroom console in a terminal of your own. It asks for your sudo password, then your passphrase.
Health: lunchroom version names the build. lunchroom status shows each agent, whether it is AVAILABLE, HELD, UNGUARDED or STOPPED, and every QUEUED message. lunchroom doctor, in your own terminal, prints one PASS or FAIL line for each check and, for each FAIL, what to do.
Sensitive data: Lunchroom stores no AWS credentials. Your passphrase is not stored; a salted PBKDF2-HMAC-SHA-256 check of it is at /etc/lunchroom/<uid>.verifier, owned by root. Agent messages and session records are in /var/lib/lunchroom/<uid>, where no process of yours, an agent's included, can reach them.
Encryption: the store is not encrypted. lunchroom install console makes an Ed25519 key pair that signs approvals for the Agent Execution Controller; the private key is readable by the user lunchroom only. Change your passphrase with lunchroom passphrase.
Store and recovery: if the store cannot be read, run lunchroom repair in your own terminal (it asks for your passphrase); it puts back the store as it was before its last change and keeps the unreadable file beside it. To back up the store, copy /var/lib/lunchroom/<uid> as root.
Upgrade: pull the newer image and repeat steps 3 and 4 with its tag. Run the new program by its path (./lunchroom-<version>/lunchroom install): lunchroom install typed by name runs the build already installed and upgrades nothing.
AWS costs and quotas: Lunchroom is free, uses no AWS services when it runs, and needs no service quota changes.
Remove: in your own terminal run lunchroom uninstall claude-code and lunchroom uninstall codex (each removes only Lunchroom's hooks and keeps a backup); for OpenClaw run openclaw plugins disable lunchroom, for Hermes hermes plugins disable lunchroom. Then run lunchroom uninstall console. What stays is root's: the program /usr/local/lib/lunchroom/lunchroom, shared by every user of the computer who installed Lunchroom, and your messages in /var/lib/lunchroom/<uid>. Remove your folder as root, delete the lunchroom link in ~/.local/bin or ~/bin, and remove /usr/local/lib/lunchroom only when no other user uses it. sudo rm /etc/lunchroom/<uid>.verifier removes the passphrase check.
Resources
Vendor resources
Support
Vendor support
Contact Epic AI® at support@epic-ai.io .
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.