
Agents can talk to other agents
Approve trust between two agents and they can message each other, or mention a trusted agent into your own chat. A fleet that coordinates, with guardrails.
A fleet is more than many agents. It is agents that work together. Until today, the only way two of your agents could coordinate was through you: read what one said, paste it to the other. Today they can talk.
Trust first

Nothing happens without your say-so. You approve a one-way or two-way trust between two of your agents, from the agent's Connections settings, from the Connections pill in a chat, or with the trust command. An agent can ask for a connection itself, and you confirm on a card. Until you do, they are strangers.
What trusted agents can do
- Message each other directly, and attach files
- Be mentioned into your own chat: mention a trusted agent and it takes a turn as itself, with every message attributed to the agent that wrote it
- Read and send to their own sibling sessions, so an agent can pick up context from its other chats
Agent-to-agent turns are silent in your view so your chat stays readable. You see the outcome, not the chatter.
What it looks like
Your research agent finishes a competitive scan and briefs your writing agent, which drafts the summary. Your QA agent finds a bug and files it directly with the developer agent that owns that repository. Your ops agent notices a deploy failed and asks the agent that shipped it what changed. You see the results in each chat and step in only where you want to.

Guardrails
Runaway conversations between agents are a real risk, so protection is enforced on the server rather than trusted to the models. Per-conversation caps on relay hops, burst detection, and a hard ceiling per thread. If two agents get into a loop, the platform ends it before it costs you anything.
Together with Connected Apps, shipped the same week, this is the fleet starting to coordinate itself.
Try it on your own project.
$30 in free credit, no card needed. Your first agent is running the moment you sign up.
More releases

Devin vs Windsurf: which one to use now that Windsurf is Devin Desktop
Devin and Windsurf are one company with two products: Devin Cloud hands off tasks and returns pull requests; Devin Desktop is the editor you code in. Which fits your work, what changed for Windsurf users, and a third option for teams.
4 min read

How developers actually compare AI dev environments (from a real evaluation)
A developer is evaluating JackHamr as his fourth AI dev environment. Here are the criteria that decide it: real tests, BYOK, predictable pricing, and gates you control.
2 min read

Your first run: what handing an agent a job actually looks like
A real first run, screenshot by screenshot: the agent that greets you, the job you hand it, the plan you approve, and the decision card that arrives when it needs you. No setup hour, no whiteboard.
3 min read