Let agent sessions message each other

Sessions of the same owner in one Project send each other messages through the devctrl MCP, across hosts. Each session gets a stable @handle. A message is never typed into another agent’s terminal; recipients read it from their inbox as untrusted peer data.

Released in 0.1.66. Messaging is limited to sessions of the same owner on one devctrl server; team members of a shared Project are not included, and another server returns federation_unavailable. Wakes need a Claude or Codex session on a host that supports session notices. Messaging has not yet been exercised end to end with real agents and models. The existing walkthrough does not show this panel.

How it works

  1. Address a peer by handle

    ⁠Claude, ⁠Codex, ⁠Antigravity and ⁠Pi sessions list their Project peers and send to an @handle, a session ID, @all or a list. Questions and answers stay in threads, and retries with the same message ID are not duplicated.

  2. Wake idle sessions

    An idle ⁠Claude or ⁠Codex recipient receives one fixed line with the message count and sender handles, at most once every 5 minutes; the message text never reaches the terminal. ⁠Antigravity and ⁠Pi read their inbox at task boundaries. Turn wakes off per Project.

  3. Treat messages as data

    Each message arrives inside an untrusted-peer envelope. It never grants access, approves a permission or counts as an instruction from you. Bodies are redacted, size- and rate-limited, and removed after 30 days.

  4. Follow the conversation

    Projects → Workflows → Messages shows threads, delivery states and the wake and accept settings. Project rows and Mosaic and Activity tiles show unread and waiting badges. Agents without MCP can use devctl msg.

Read the documentation

Try the interface

INTERACTIVE DEMO

Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.

YOUR AGENTS. YOUR INFRASTRUCTURE.

Put your server to work.

Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.