io.github.parasxos/postbag

Registre officiel Outils de développement

Local Claude Code and Codex sessions on one machine exchange letters through native inputs.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

PYPI package postbag
Claude Code
claude mcp add postbag -e 'POSTBAG_CODEX=<POSTBAG_CODEX>' -- uvx postbag==2.3.0 mcp
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "postbag": {
            "command": "uvx",
            "args": [
                "postbag==2.3.0",
                "mcp"
            ],
            "env": {
                "POSTBAG_CODEX": "<POSTBAG_CODEX>"
            }
        }
    }
}

Variables d'environnement

  • POSTBAG_CODEX Path to the codex executable for Codex delivery when several are installed.

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. postbag
  2. Install
  3. Quick start
  4. What to use it for
  5. Tools
  6. How it works
  7. Security

postbag

Let Codex and Claude Code talk to each other.

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.

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.

pipx install 'postbag[mcp]'
claude mcp add --scope user postbag -- "$(command -v postbag-mcp)"
codex mcp add postbag -- "$(command -v postbag-mcp)"

Start a new session in each app, then run /mcp. postbag should list five tools. For uvx and other setups, see MCP setup.

Or ask your agent: Install postbag using llms-install.md.

Quick start

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.

  1. In Codex:

    Join postbag bag "review" as codex.

  2. 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.

ToolWhat it does
postbag_joinRegisters this session under a name in a bag, creating the bag if needed.
postbag_sendSends a letter to a name in the bag. final: true asks for no reply.
postbag_readPages through the bag's history.
postbag_bagsLists local bags with letter counts and registered names.
postbag_leaveWithdraws 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.

See SECURITY.md.

MCP setup · Concept · Changelog · Contributing · MIT

Questions fréquentes

Qu'est-ce que io.github.parasxos/postbag ?

Local Claude Code and Codex sessions on one machine exchange letters through native inputs.

Comment installer io.github.parasxos/postbag ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add postbag -e 'POSTBAG_CODEX=<POSTBAG_CODEX>' -- uvx postbag==2.3.0 mcp. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.parasxos/postbag ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

io.github.parasxos/postbag est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient io.github.parasxos/postbag ?

Il est publié par parasxos. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.