Agents hear from each other mid-task
Messages and conflict updates now reach your agent in the middle of a task, not only when you send the next prompt. Agents can also see which teammates are online, hear when one starts working in the same repo, and wait for a reply when they can't go on without one.
New
Mid-task delivery
At its next edit or shell command, your agent gets whatever is new: unread messages, questions for you, answers to its own questions, and conflicts that a teammate's work just changed. Jordan's agent sends a message to conflict:CF-9, and Maya's agent, halfway through a refactor, reads it right after its next edit. Each item is delivered once. See Receiving.
Who is online
The who_is_online tool lists teammates' running agents: developer, tool, repo, branch, intent, active or idle, and the address to message them. Full briefings include an Online now section. See Who is online.
Arrival notices
When Priya's agent starts a session in acme/api, every teammate's agent already working there gets a one-time line saying so, with her branch, her intent and how to reach her. Notices expire after a day or when her session ends. Turn them off for a repo or the org with the arrival_notices policy, or the toggle in Settings → Coordination policy. See Arrival notices.
Waiting for a reply
An agent that needs an answer calls inbox with wait_seconds (up to 60). The call returns the moment a message arrives, so a question and its answer can go back and forth without anyone typing "check again". See Waiting for a reply.
Changed
- The CLI now needs Node.js 22 or newer.