Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Letterbox

by dovahkiin-vversion 1.2.2i★ 0iRuns on your computerRepository ↗
Registry nameio.github.dovahkiin-v/letterbox

How to install

What it does

File-based comms protocol for AI-to-AI dialogue between terminal agents.

  • Connects Runs on your computer
  • Account or key No key needed · 3 settings to fill in (LETTERBOX_CHANNEL, LETTERBOX_SENDER, LETTERBOX_INSTANCE_ID)
  • Category Developer tools

Use together with

Skills that teach the AI this kind of work; they work alongside this one

rea

Reverse engineer anything with agents, from app behavior down to native binaries.

by morluto★ 467,2351 skills

Skill · How-to guide

andrej-karpathy-skills

A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.

by multica-ai★ 234,1251 skills

Skill · How-to guideNo license stated

graphify

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.

by Graphify-Labs★ 149,8731 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness7/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score7/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Letterbox. Follow https://mcp.popnx.com/i/dovahkiin-v-letterbox.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

3 setting(s) to fill in (LETTERBOX_CHANNEL, LETTERBOX_SENDER, LETTERBOX_INSTANCE_ID) · Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Letterbox for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "letterbox": { "command": "uvx", "args": [ "letterbox" ], "env": { "LETTERBOX_CHANNEL": "your-value", "LETTERBOX_SENDER": "your-value", "LETTERBOX_INSTANCE_ID": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For LETTERBOX_CHANNEL, LETTERBOX_SENDER, LETTERBOX_INSTANCE_ID, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Letterbox tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Fill in 3 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • LETTERBOX_CHANNEL Channel name to open. Normally set by the letterbox PTY-parent when it spawns this server; set it manually only when running the MCP server standalone.
    • LETTERBOX_SENDER This endpoint's identity on the channel — the name the peer agent sees on every message.
    • LETTERBOX_INSTANCE_ID Per-launch instance id, the watcher/own-write join key that stops an agent seeing its own messages as incoming. Must be unique per launch.

    Descriptions are as written by the maker.

  3. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  4. Paste these settings and save the file

    {
      "mcpServers": {
        "letterbox": {
          "command": "uvx",
          "args": [
            "letterbox"
          ],
          "env": {
            "LETTERBOX_CHANNEL": "your-value",
            "LETTERBOX_SENDER": "your-value",
            "LETTERBOX_INSTANCE_ID": "your-value"
          }
        }
      }
    }
  5. Quit Claude and open it again

  6. Try it

    Use Letterbox and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Letterbox or shows a Letterbox tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Letterbox yet

Letterbox runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Letterbox

  • 3 setting(s) to fill in (LETTERBOX_CHANNEL, LETTERBOX_SENDER, LETTERBOX_INSTANCE_ID) · Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • 3 setting(s) to fill in (LETTERBOX_CHANNEL, LETTERBOX_SENDER, LETTERBOX_INSTANCE_ID) · Install Python (uv) on your computer first (one time)
  • 3 setting(s) to fill in (LETTERBOX_CHANNEL, LETTERBOX_SENDER, LETTERBOX_INSTANCE_ID) · Install Python (uv) on your computer first (one time)
  • 3 setting(s) to fill in (LETTERBOX_CHANNEL, LETTERBOX_SENDER, LETTERBOX_INSTANCE_ID) · Install Python (uv) on your computer first (one time)

B · Others in Developer tools that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

3 setting(s) to fill in (LETTERBOX_CHANNEL, LETTERBOX_SENDER, LETTERBOX_INSTANCE_ID) · Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Letterbox for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user letterbox --env LETTERBOX_CHANNEL=your-value --env LETTERBOX_SENDER=your-value --env LETTERBOX_INSTANCE_ID=your-value -- uvx letterbox 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For LETTERBOX_CHANNEL, LETTERBOX_SENDER, LETTERBOX_INSTANCE_ID, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Letterbox tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Fill in 3 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • LETTERBOX_CHANNEL Channel name to open. Normally set by the letterbox PTY-parent when it spawns this server; set it manually only when running the MCP server standalone.
    • LETTERBOX_SENDER This endpoint's identity on the channel — the name the peer agent sees on every message.
    • LETTERBOX_INSTANCE_ID Per-launch instance id, the watcher/own-write join key that stops an agent seeing its own messages as incoming. Must be unique per launch.

    Descriptions are as written by the maker.

  3. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  4. Paste this command and press Enter

    claude mcp add --scope user letterbox --env LETTERBOX_CHANNEL=your-value --env LETTERBOX_SENDER=your-value --env LETTERBOX_INSTANCE_ID=your-value -- uvx letterbox
  5. Type /mcp in Claude Code

    You should see Letterbox listed as connected

  6. Try it

    Use Letterbox and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Letterbox or shows a Letterbox tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

3 setting(s) to fill in (LETTERBOX_CHANNEL, LETTERBOX_SENDER, LETTERBOX_INSTANCE_ID) · Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Letterbox for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "letterbox": { "command": "uvx", "args": [ "letterbox" ], "env": { "LETTERBOX_CHANNEL": "your-value", "LETTERBOX_SENDER": "your-value", "LETTERBOX_INSTANCE_ID": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For LETTERBOX_CHANNEL, LETTERBOX_SENDER, LETTERBOX_INSTANCE_ID, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Letterbox tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Fill in 3 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • LETTERBOX_CHANNEL Channel name to open. Normally set by the letterbox PTY-parent when it spawns this server; set it manually only when running the MCP server standalone.
    • LETTERBOX_SENDER This endpoint's identity on the channel — the name the peer agent sees on every message.
    • LETTERBOX_INSTANCE_ID Per-launch instance id, the watcher/own-write join key that stops an agent seeing its own messages as incoming. Must be unique per launch.

    Descriptions are as written by the maker.

  3. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  4. Fill in your key

    In the Letterbox settings, LETTERBOX_CHANNEL, LETTERBOX_SENDER, LETTERBOX_INSTANCE_ID is empty; add your key and save

  5. Open the AI chat in Cursor in Agent mode

  6. Try it

    Use Letterbox and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Letterbox or shows a Letterbox tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

3 setting(s) to fill in (LETTERBOX_CHANNEL, LETTERBOX_SENDER, LETTERBOX_INSTANCE_ID) · Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Letterbox for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "letterbox": { "type": "stdio", "command": "uvx", "args": [ "letterbox" ], "env": { "LETTERBOX_CHANNEL": "your-value", "LETTERBOX_SENDER": "your-value", "LETTERBOX_INSTANCE_ID": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For LETTERBOX_CHANNEL, LETTERBOX_SENDER, LETTERBOX_INSTANCE_ID, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Letterbox tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Fill in 3 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • LETTERBOX_CHANNEL Channel name to open. Normally set by the letterbox PTY-parent when it spawns this server; set it manually only when running the MCP server standalone.
    • LETTERBOX_SENDER This endpoint's identity on the channel — the name the peer agent sees on every message.
    • LETTERBOX_INSTANCE_ID Per-launch instance id, the watcher/own-write join key that stops an agent seeing its own messages as incoming. Must be unique per launch.

    Descriptions are as written by the maker.

  3. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  4. Fill in your key

    In the Letterbox settings, LETTERBOX_CHANNEL, LETTERBOX_SENDER, LETTERBOX_INSTANCE_ID is empty; add your key and save

  5. Open the AI chat in VS Code in Agent mode

  6. Try it

    Use Letterbox and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Letterbox or shows a Letterbox tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Letterbox💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user letterbox --env LETTERBOX_CHANNEL=your-value --env LETTERBOX_SENDER=your-value --env LETTERBOX_INSTANCE_ID=your-value -- uvx letterbox

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "letterbox": {
      "command": "uvx",
      "args": [
        "letterbox"
      ],
      "env": {
        "LETTERBOX_CHANNEL": "your-value",
        "LETTERBOX_SENDER": "your-value",
        "LETTERBOX_INSTANCE_ID": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "letterbox": {
      "command": "uvx",
      "args": [
        "letterbox"
      ],
      "env": {
        "LETTERBOX_CHANNEL": "your-value",
        "LETTERBOX_SENDER": "your-value",
        "LETTERBOX_INSTANCE_ID": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "letterbox": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "letterbox"
      ],
      "env": {
        "LETTERBOX_CHANNEL": "your-value",
        "LETTERBOX_SENDER": "your-value",
        "LETTERBOX_INSTANCE_ID": "your-value"
      }
    }
  }
}

Values you fill in

  • LETTERBOX_CHANNEL required env
    Channel name to open. Normally set by the letterbox PTY-parent when it spawns this server; set it manually only when running the MCP server standalone.
  • LETTERBOX_SENDER required env
    This endpoint's identity on the channel — the name the peer agent sees on every message.
  • LETTERBOX_INSTANCE_ID required env
    Per-launch instance id, the watcher/own-write join key that stops an agent seeing its own messages as incoming. Must be unique per launch.

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
23/wk
Connection
Runs on your computer
Latest versioni
1.2.2
Published to registryi
Aug 25, 2026
Code last changedi
Aug 25, 2026
Maker
dovahkiin-v
Packages
pypi: letterbox
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account dovahkiin-v, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 3 months ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for letterbox@1.2.2

Checks only this package version, not every dependency · checked Nov 16, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/dovahkiin-v-letterbox.svg)](https://mcp.popnx.com/en/servers/dovahkiin-v-letterbox)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Developer toolsi

  • More stars than 0% of the other 6116 servers in this category
  • Published to the registry more recently than 28% of the other 6116 servers in this category
  • Basic checks equal to or better than 99% of the other 6116 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Letterbox safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 3 months ago, and the latest version (1.2.2) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitDiagram

Architecture diagrams, explanations and Mermaid source for public GitHub repositories.

by ahmedkhaleel2004Widely used★ 19KUpdated 2 months ago

Runs in the cloud✓ service owner · gitdiagram.comTried by the PopNx team

Appllama

Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.

by AppllamaWidely used★ 5.2KUpdated 3 months ago

Runs in the cloud✓ service owner · appllama.io

Repowise

Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.

by repowise-devWidely used↓ 6.5K/wk★ 8.2K Stars for the whole repoUpdated 6 days ago

Computer or cloud✓ service owner · repowise.dev
Compared with similar ones
This one
Letterbox
GitDiagramAppllamaCloudflare MCPOmnaraRepowise
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installCloud or install on your computer
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoYesNoNo
Basic checks3/34/44/44/44/45/5
LicenseMITMITMITApache-2.0Apache-2.0AGPL-3.0
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Letterbox

📌 Built for internal production use. Architecture proven across months of daily AI development. Open-sourced as a reference implementation. I use it almost daily.

If you use AI coding assistants in the terminal, you normally work with one at a time — and getting two of them to collaborate means copy-pasting messages between windows yourself. Letterbox lets two assistants (say, Claude and Gemini, or Gemini and Mistral's Vibe) talk *directly* to each other and work a task together, hands-free.

The result: one agent can plan while another reviews, or the two can split the work between them — collaborating on their own while you watch, instead of relaying every message by hand.

*A small file-based comms protocol that lets two AI agents in separate terminals talk to each other in real time.*

Letterbox lets two terminal coding agents — Claude Code, Gemini CLI, Antigravity, or Mistral's Vibe — hold a real-time conversation by passing message files through a shared directory. When one agent speaks, a 📬 notification is injected into the other's terminal and wakes it to read and reply. No network, no server, no shared memory: just JSON files in a folder and the OS's atomic-rename. It's the messaging layer that was built for an internal planning loop, extracted into a standalone, versioned tool in 2026. If you've ever wanted two CLI agents to collaborate on a task without you copy-pasting between windows, this is for you. It gets the occasional update at the author's whim (the launcher tells you when a newer one is out) — but it's currently unsupported small project, not a community one.

The bridge is cross-harness: Claude on one side, Gemini on the other, talking through the same channel, has been verified live. The one wrinkle is setup — Claude wires itself automatically, while Gemini and Antigravity load letterbox from their own settings. The Setup section walks through both.

Why it exists

I work with two AI collaborators every day — Claude and Gemini — each living in whatever terminal harness it runs in (Claude Code, Gemini CLI, Antigravity CLI, and now Mistral's Vibe). Letterbox is how I get them talking to *each other* instead of through me.

That happens in two modes. Sometimes it's manual: we're brainstorming and I want to loop the other model into the conversation. Sometimes it's automated — in the planning loop, Claude drafts a plan and each plan is routed to Gemini for review as a built-in stage. Letterbox carries both the same way.

It's harness-agnostic by design — Claude Code ↔ Gemini CLI ↔ Antigravity CLI ↔ Vibe in any combination — and same-model pairs work just as well: two Claude tabs, or two Gemini tabs, talking over one channel.

What it is

Each letterbox launch runs two coordinated processes inside one terminal:

  letterbox claude --channel demo --as alice

│ ├─ PTY-Parent (the foreground letterbox process) │ • spawns the harness CLI as a PTY child │ • watches the channel directory for peer writes │ • injects 📬 notifications into the PTY on arrival │ └─ the harness spawns: └─ letterbox mcp (stdio MCP server, agent-spawned) • send_message / check_messages / acknowledge • check_latest_message / channel_info / list_channels

Both sides coordinate ONLY through the filesystem:

~/.letterbox/channels/demo/ msg-*.json ← one file per message .read/alice.json ← per-agent read markers .read/bob.json

There is no daemon, no IPC, no background service. The filesystem *is* the coordination medium — the PTY-Parent's watcher sees a new msg-*.json appear and renders a notification; the channel directory is durable, inspectable, and cat-able. Crash recovery is trivial because nothing valuable lives in memory.

How the agent gets the letterbox tools differs per harness, and it's the one thing you configure once:

  • Claude Code takes a launch flag, so letterbox wires it *automatically* — it generates a temporary MCP config and passes --mcp-config to claude. Nothing for you to set up.
  • Gemini CLI and Antigravity don't take that flag; they load MCP servers from their own settings file. You add a one-line, channel-agnostic letterbox entry there once, and the launcher hands each session its channel and identity through environment variables at launch — so you never edit settings per channel.
  • Vibe loads MCP servers from ~/.vibe/config.toml. Its MCP subprocess inherits only a trimmed environment, so a one-time bridge script is needed to relay LETTERBOX_CHANNEL / LETTERBOX_SENDER from Vibe's own process env. Once that's in place, any channel works exactly like Gemini. See the Vibe setup section.

Who it's for

  • People running terminal coding agents who want autonomous AI↔AI dialogue on one machine, without babysitting copy-paste between windows.
  • People who value files as the source of truth — auditable, greppable, no opaque protocol, no magic.

Who it's NOT for

  • Anyone wanting a hosted or networked chat service — the message protocol is filesystem-local and never touches the network. (The launcher makes one optional, best-effort version check at startup; disable it with LETTERBOX_NO_UPDATE_CHECK=1.)
  • Anyone wanting a multi-user platform — it's a point-to-point bridge between agents on one machine, not a many-user hub (see Built for two).
  • Windows-native users — v1 is POSIX-only (see What we don't support).
  • Anyone wanting a supported product — letterbox is versioned and gets the occasional update at the author's whim (the launcher tells you when a newer one is out), but there's no roadmap, no SLA, and no commitment to take feature requests or keep maintaining it. Use it as-is; pull a newer version if it helps.

Built for two

Letterbox is a two-way bridge at heart — one peer talking to one peer is what it's designed and tuned for. Three or more agents *can* share a channel: directed addressing (send_message(to=" ")) and the participants list make it workable, and same-channel broadcasts reach everyone. But a shared channel is a broadcast bus — every message wakes every participant. Without orchestration (turn-taking, a designated coordinator, or rules about who speaks when), an N-way room becomes a notification storm that can chew through a model's message/usage limits surprisingly fast. If you want three or more, bring your own conductor. The substrate is honest about who's in the room; the etiquette is on you.

Install

Available on PyPI and the MCP Registry.

pip install letterbox

Or from source:

pip install -e .          # or: pip install -e ".[dev]" for the test extras

This puts the letterbox command on your PATH. The command must resolve by name — each agent spawns letterbox mcp itself — so this is load-bearing. Confirm it:

which letterbox           # note this absolute path; Gemini/Antigravity setup needs it

You also need the harness you're launching (claude, gemini, antigravity, or vibe) installed, on your PATH, and logged in. Letterbox launches it for you.

Updating

Letterbox is versioned (letterbox.__version__, the single source of truth) and published to PyPI. On a human-facing launch the CLI makes one best-effort check (at most once a day, cached under ~/.cache/letterbox/) and prints a one-line notice if a newer version exists. To update:

pip install --upgrade letterbox

This is the only network call letterbox ever makes — the messaging protocol stays fully local. It runs with a tight timeout and is fully fail-silent: if it can't reach GitHub it simply prints nothing and never delays your launch. It is never run for letterbox mcp (the agent's stdio server). Disable it entirely with LETTERBOX_NO_UPDATE_CHECK=1.

Setup per harness

You only do this once per harness. Skip the harnesses you won't use.

Claude Code — nothing to do

Letterbox wires Claude automatically: at launch it writes a temporary MCP config (mode 0600) and passes --mcp-config to claude. The letterbox tools appear in that session and nowhere else. There is no settings file to edit.

Gemini CLI — two one-time steps

1. Register the MCP server in ~/.gemini/settings.json (create the file if it doesn't exist). Use the absolute path to your installed letterbox (from which letterbox above), and pass only ["mcp"] — no channel, no identity:

{

"mcpServers": { "letterbox": { "command": "/absolute/path/to/letterbox", "args": ["mcp"] } } }

This entry is channel-agnostic on purpose. The launcher exports LETTERBOX_CHANNEL, LETTERBOX_SENDER, and LETTERBOX_INSTANCE_ID into Gemini's environment at launch, and the MCP server reads them — so the same single entry serves every channel and you never edit it again. (This mirrors how the Forge orchestrators pass a channel via an env var.)

2. Trust the folder you launch from. Gemini refuses to run in an untrusted directory without an interactive *"do you trust this folder?"* prompt — and a blocking TUI prompt would stall the automation. Pre-trust the launch directory (or a parent) in ~/.gemini/trustedFolders.json:

{

"/home/you/projects": "TRUST_PARENT" }

TRUST_FOLDER trusts exactly that directory; TRUST_PARENT trusts it and everything beneath, so one entry covers all your project folders. (Tip: don't reach for Gemini's --skip-trust flag to dodge this — it forces a workspace-system-prompt lookup that crashes even in already-trusted directories. Trust the folder instead.)

Antigravity (agy)

Launch it as `letterbox agy …` (the long form letterbox antigravity … also works — agy is just an alias matching the binary name). Antigravity receives its per-launch channel and identity through the same environment variables as Gemini; what differs is how you register the MCP server. agy loads MCP servers from plugins, so you install letterbox as a tiny local plugin (a directory with two JSON files):

# 1. Build the plugin (one directory, two files). Use the absolute

letterbox path from which letterbox.

mkdir -p ~/.letterbox/agy-plugin/letterbox cat > ~/.letterbox/agy-plugin/letterbox/plugin.json <<'JSON' { "name": "letterbox", "version": "1.0.0", "description": "Letterbox file-based AI-to-AI comms bridge." } JSON cat > ~/.letterbox/agy-plugin/letterbox/mcp_config.json <<'JSON' { "mcpServers": { "letterbox": { "command": "/absolute/path/to/letterbox", "args": ["mcp"] } } } JSON

2. Install it (and confirm).

agy plugin install ~/.letterbox/agy-plugin/letterbox agy plugin list

The mcp_config.json is channel-agnostic for the same reason Gemini's settings entry is — the launcher passes the channel and identity by environment at launch. Like Gemini, agy

Only the beginning is shown; read the rest in the repo