Local Claude Code and Codex sessions on one machine exchange letters through native inputs.
MCP Server: io.github.parasxos/postbag
The MCP server “io.github.parasxos/postbag” enables local Claude Code and Codex sessions on a single machine to exchange “letters” using native input mechanisms. Its description specifies that the interaction occurs between those sessions, coordinated through local, shared input channels rather than external networking details.
🛠️ Key Features
Supports local Claude Code and Codex sessions
Exchanges letters through native inputs
🚀 Use Cases
Coordinating information flow between Claude Code and Codex on the same machine
Managing letter-based communication for local workflows
⚡ Developer Benefits
Simple setup centered on native input exchange for local session interaction
⚠️ Limitations
Described scope is limited to local sessions on one machine
No additional tooling, capabilities, or configuration details are provided
A local MCP server. Ask Codex to review what Claude Code just wrote, or the
other way round. The answer arrives as a new turn. No copying text between
windows.
A real recorded run, edited and sped up. Codex joins bag review. Claude Code joins and asks Codex to review the last commit, and the request arrives in Codex as letter 1. Codex reads the diff, runs a test showing a failing job reported as None, and sends two findings back as a final letter. Claude Code checks them against the diff and agrees.
Install
Needs Python 3.10 or later, Claude Code and a recent Codex CLI with
codex queue. Run both sessions on one machine with the same postbag version.
Delivery is tested on macOS.
A bag is a named conversation. Both agents join the same one. Open Codex and
Claude Code in the same repository, so both see the same code.
In Codex:
Join postbag bag "review" as codex.
In Claude Code:
Join postbag bag "review" as claude, then ask codex to review my last commit.
Codex joins first so Claude Code has someone to write to. Approve the postbag
tools when asked. Codex gets the request as a new turn, and its reply lands in
Claude Code the same way. Either side can end with a final letter, which asks
for no reply.
What to use it for
Cross review. Claude Code finishes a change and asks Codex to review the diff before you commit.
Split work. Codex writes the tests while Claude Code writes the implementation. They compare notes by letter.
Second opinion. When one agent is stuck on a bug, it asks the other for a fresh read.
Tools
Your agents call these. You just ask in plain words.
Tool
What it does
postbag_join
Registers this session under a name in a bag, creating the bag if needed.
postbag_send
Sends a letter to a name in the bag. final: true asks for no reply.
postbag_read
Pages through the bag's history.
postbag_bags
Lists local bags with letter counts and registered names.
postbag_leave
Withdraws this session from the bag. History stays.
How it works
Native delivery. Accepted letters become a new turn in the other session,
through its own input. postbag adds no delivery daemon, polling or hooks.
No setup prompts. Every letter ends with how to reply, or asks for no reply.
One shared history. Each bag keeps a local log that either agent can page
through with postbag_read.
A successful send confirms submission and recording. Neither the receipt nor
the log proves that the recipient accepted, read or acted on the letter.
Security
Each letter names its peer and asks the recipient to stay within the human's
existing authorization. This is model guidance, not a security boundary.
Connect only sessions you trust with the task.
There is no letter limit. To confirm every MCP send, configure the host to ask
before each postbag_send call.
Ledgers under ~/.postbag/ hold Claude Code inbox tokens. New files use
mode 0600. Never commit or share them.