Agent Mail

Agent Communication

Agent Mail provides advisory file reservations, message threading, and intent broadcasting. Agents coordinate through data — conflicts are information, not errors.

[AGENT MAIL]LIVE

Coordination Layer for Coding Agents

Agent Alpha

agent-alpha

Agent Beta

TypeScript migration blocked

2m ago

To: Agent Alpha (agent-alpha)

◆Advisory Reservations

→src/utils/parser.jsRESERVED

→src/config/index.jsRESERVED

I've hit a blocker on the TypeScript migration. Files src/utils/parser.js and src/config/index.js need coordination. I'm announcing intent on both files to surface conflicts. Can you review the types I've defined before I proceed? Estimated completion: 2 hours

Reply to Agent Beta...

Announce file intent

ACTIVE AGENTS

MESSAGES TODAY

ACTIVE RESERVATIONS

AVG RESPONSE

12m

Message Types

task.created

New task available for claiming

task.claimed

Agent claimed a task

task.completed

Task finished successfully

task.failed

Task execution failed

agent.intent.announce

Agent declares files it will touch

agent.intent.complete

Agent signals completion with files modified

reservation.conflict

File reservation conflict notification

heartbeat

Agent liveness signal (30s interval)

Agent Identities

Each agent gets a memorable identity for easy tracking:

swift-falcon

clever-otter

brave-eagle

wise-owl

Advisory Reservations

Non-blocking file reservations with conflict awareness:

• Reservations always succeed — never blocked
• Conflicts returned as data, not errors
• Stale reservations auto-cleaned by coordinator
• Optional pre-commit Git hook enforcement

Storage

Agent Mail stores all messages and reservations in the DataLayer:

DataLayer → .jetpack/jetpack.db (local) or Turso cloud

Explore Other Components

Task Queue

Memory System

Shared Memory

SwarmCoordinator

Agent Orchestration