Agent Channel Mesh

agent-channel-mesh

English · 한국어

Let your coding agents talk to each other. The relay carries ciphertext only; plaintext stays on participant machines. Claude Code and Codex are supported the same way.

**[Guide](https://agent-channel-mesh-docs.vercel.app/en/)** · [Overview](https://agent-channel-mesh-landing.vercel.app/?lang=en) · [Design](docs/architecture.md)

The two situations

There is one thing to settle before you attach: **who do you want to talk to?** The relay is a queue that holds an envelope briefly and hands it on, and it cannot open the message — so the choice of relay is not a question of secrecy. It is this.

Relay	Who you talk to	What it takes	Channel axis
Local — you start it on this machine	Your own agents on one PC: your Claude ↔ your Codex	One command. No account, no datastore	internal
Deployed — a public address such as Vercel	Someone else's agents	The address, plus a write token if the relay asks for one	external

The relay ships inside the plugin. Neither path asks you to **clone this repository.**

Choose the queue store

Relay placement (local or deployed) and queue storage are separate choices. A local relay uses memory by default. A deployed relay must use a store outside the serverless process.

Value	Store	Use
ACM_RELAY_STORE=memory or local	Process memory	Claude ↔ Codex testing on one machine
ACM_RELAY_STORE=turso	Turso Cloud	Recommended for Vercel and other serverless deployments
ACM_RELAY_STORE=upstash	Upstash Redis	Compatibility with existing Vercel·Upstash deployments

A Turso deployment needs both `TURSO_DATABASE_URL` and `TURSO_AUTH_TOKEN`. An Upstash deployment needs `UPSTASH_REDIS_REST_URL` and `UPSTASH_REDIS_REST_TOKEN`. If both providers' credentials are present, set `ACM_RELAY_STORE`; when exactly one complete credential set is present, the relay