Agent Mailbox Light
Provides a lightweight, decentralized internal mailbox system for multi-agent workspaces.
Install & Use
Copy this prompt and send it to your AI assistant (Claude / Cursor / TRAE / Codex / WorkBuddy etc.) to auto-install:
Help me install this AI Skill: Agent Mailbox Light. It is used for: Provides a lightweight, decentralized internal mailbox system for multi-agent workspaces. Full Skill content: https://321skill.com/skills/agent-mailbox-light-x-6/raw/index.md Read that page and install it.
The prompt includes a link to the full Skill content. You can also view the full content.
This Skill addresses the need for temporary, low-noise coordination between multiple AI agent workspaces without writing information to long-term memory. In practical development, developers often need to pass prompts, warnings, or context between multiple parallel agent projects but do not want these temporary messages to pollute core memory or trigger complex task scheduling. Agent Mailbox Light offers a lightweight, filesystem-based mailbox, allowing agents to view notifications from other workspaces—much like checking email—upon startup or during task intervals.
Usage is straightforward: simply install this Skill in your agent workspace and configure the path pattern to scan other workspaces (e.g., $HOME/.openclaw/workspace*). Subsequently, sender scripts will automatically write mail files to the .agent-mailbox/inbox/ directory under matching paths, while recipient agents can read the latest mail in their own inbox as part of their baseline workflow. After summarizing useful information, they can move it to the keep folder and archive processed or expired mail.
It is ideal for teams or individuals coordinating multi-agent tasks, especially developers already using multiple independent workspaces (e.g., one for front‑end development, one for data analysis, one for operations monitoring) who need a simple, dependency‑free mechanism to share temporary context, warnings, or task‑status updates without introducing complex message queues or centralized services.
We recommend integrating mailbox‑checking logic uniformly into the agent’s startup or task‑switching baseline—for instance, reading only the latest 1–3 messages per startup to control token consumption. Note that it is primarily a “best‑effort” broadcast system: it does not guarantee delivery, provides no push notifications, and mail content should be treated as “suggestions” for the local agent to evaluate, not as commands that must be executed.
Key Features
Unlike message queues that require centralized registration and management, it adopts a fully decentralized filesystem broadcast model with no need to run additional services. Compared to writing information directly into an agent’s long‑term memory, it clearly separates temporary coordination messages from persistent knowledge through the inbox/keep/archive folder structure, avoiding memory pollution.
Limitations
Only supports the local filesystem; cloud synchronization or remote delivery is not possible. It also depends on the sender being able to correctly scan the physical path of the recipient workspace.
FAQ
Is mail delivery guaranteed?
No. This is a “best‑effort” broadcast system. If the target workspace path does not exist or the write fails, the sender will silently skip it without retrying or blocking.
Will mail be automatically read and executed?
No. Mail content is purely “suggestive” context. The recipient agent must actively read and decide how to handle it within its own workflow; this is not a task‑execution bus.
Installation guide for AI assistants
If your AI coding assistant (Claude Code, Cursor, TRAE etc.) can see this page, send it this message to auto-install:
Visit https://321skill.com/skills/agent-mailbox-light-x-6/raw/index.md to read the original Skill definition (Markdown format) for Agent Mailbox Light, and install it according to the instructions.
Raw Markdown URL for AI: /skills/agent-mailbox-light-x-6/raw/index.md