cgl-interagentmail 1.1.0

File-backed local mail, MCP tools, and push delivery for Codex project agents

InterAgentMail

InterAgentMail gives local Codex project agents durable mailboxes, MCP tools, and automatic wake-up delivery. Messages are stored as JSON on disk, so they remain queued while Codex or the receiving agent is offline.

One shared Codex app-server and one background InterAgentMail supervisor manage every registered project. Users do not need a bridge terminal, a port per agent, or copied Codex session IDs.

Requirements

• Python 3.10 or newer
• The OpenAI Codex CLI installed, available on PATH, and signed in
• Windows, macOS, or Linux; background operation is tested most heavily on Windows

Install

Install the isolated command-line application with pipx:

pipx install cgl-interagentmail

Register one or more Codex projects, then start delivery:

iam setup "C:\Projects\MainApp" "C:\Projects\SecurityReviewer" "C:\Projects\UXReviewer"
iam start

Open the correct agent from any registered project:

cd C:\Projects\SecurityReviewer
iam open

The complete Windows, macOS, Linux, upgrade, troubleshooting, and uninstall instructions are in docs/INSTALL.md.

Source code, releases, and issue tracking are hosted at https://github.com/cerberusgamelabs/cgl-interagentmail.

Everyday commands

iam status
iam open [PROJECT]
iam restart
iam stop
iam stop --all
iam unregister [PROJECT ...]

• iam status shows services, projects, and pinned thread IDs.
• iam open resumes the exact thread owned by the current or named project.
• iam stop stops mail delivery but leaves the shared app-server running.
• iam stop --all stops both IAM-managed background services.
• iam unregister removes IAM's managed MCP block and project registration while preserving mailbox data.

Setup behavior

iam setup is safe to run again. It:

1. Initializes the project's durable mailbox.
2. Records its project directory and safety policy.
3. Adds a clearly marked mcp_servers.interagentmail block to .codex/config.toml.
4. Establishes the existing-inbox baseline so old mail does not unexpectedly trigger work.

Use iam setup --process-existing when existing inbox messages should be delivered immediately.

Installed releases keep data under %LOCALAPPDATA%\InterAgentMail on Windows or ~/.local/share/interagentmail on macOS/Linux. Set INTERAGENTMAIL_HOME before setup to use another shared data directory.

Safety

New agents use workspace-write with on-request approvals. The unattended supervisor rejects interactive approval requests instead of granting them. A task that needs approval remains uncompleted until a person opens that agent.

Only for a trusted project that genuinely requires unrestricted filesystem and network access:

iam setup "C:\Projects\SecurityReviewer" --full-access

InterAgentMail is a local coordination mechanism, not an authentication boundary. Any local process that can write to its data directory can inject or modify mail. Do not share that directory with untrusted users or accept untrusted message content as instructions.

Sending mail

Agents normally use the project-bound InterAgentMail MCP tools. People and fallback workflows can use the CLI:

interagentmail send --project-root "C:\Projects\MainApp" --to SecurityReviewer --subject "Security review" --body "Review the current release and send back actionable findings."

The receiving supervisor wakes the correct Codex thread. The agent reads the message through MCP, performs the work, sends a substantive reply when appropriate, and archives the message only after it is handled.

Protocol and low-level bridge details are in SYSTEM.md. Release history is in CHANGELOG.md.

License

InterAgentMail is open-source software released under the MIT License. Use it, modify it, distribute it, and build on it. Copyright 2026 Cerberus Game Labs.

Contributions are welcome; see CONTRIBUTING.md.