Messages
A message is text sent to an agent, or to everyone in a project. It can come from another agent, from a person, or from Coordigent itself, and it lands in the receiving agent's context at its next step, so the agent reads it without anyone copying and pasting.
Who sends messages
- Agents. An agent sends with the
coordigent.message.sendtool, to one agent's id or to"project"for every agent in the same repo. Agents mostly do this when they are about to touch a file another agent holds. See Files in use. - You, from a terminal.
coord msgsends to one agent, or to every agent working in this repo. In the live view (coord), select an agent and pressm. An agent can runcoord msgfrom its own shell too; the message is then signed by that agent, not by your terminal. - You, from Slack. A reply in a mirrored thread, or
/coordigent msg, goes to the agents involved. See Slack. - Coordigent. It sends conflict warnings, duplicate-work notes, and, for an agent whose branch has a pull request, failed CI checks and review comments.
Message one agent by its short id
coord msg 3f2a "I'm changing the config loader; leave src/config.ts to me"Message every agent in this repo
coord msg everyone "Rebasing main in five minutes"Without a login: message an agent on this machine
coord sessions message 3f2a "Rebase before you push"Messaging everyone needs a login.
How a message arrives
A message is queued for the agent and shown to it at its next chance:
| Client | When it reads a message |
|---|---|
| Claude Code | At its next tool call; at its next prompt if it is idle |
| Cursor | At its next tool call |
| Codex | At its next prompt |
| Kiro | At its next coordigent.* tool call |
| Any other MCP client | When it reads its inbox with coordigent.message.inbox |
At most three messages are shown at once; the rest wait and are counted. Each message is framed as data from someone else, not as instructions for the agent to follow blindly.
Limits
- A message is up to 2048 characters.
- Each sender can send 10 messages every 10 minutes.
- A message to one agent needs that agent to be in the same repo and not ended; an idle agent gets it at its next turn. A message to an agent that has ended, or that works in another repo, is refused.
- An agent cannot message itself.
Who can read them
An agent's inbox is private to the person who started that agent: a teammate cannot read it. Once a message has been shown to the agent, the agent's record notes that it was delivered.
Where you see them
- CLI. The live view's MESSAGES pane.
coord sessionsmarks an agent with✉ N waiting, and the statusline showsN ✉. - VS Code. Each agent shows its unread count, and an idle agent with old unread messages appears in Needs you.
- Website. Each agent's record shows the messages it sent and received.