Ask a teammate from inside your agent.
Send a short note to a teammate without leaving Claude Code or Codex. It goes straight to their machine and shows up in their agent, as a quote rather than an instruction.
Runs on Flanner Mesh. It comes with Team Mesh and Organization, and is not sold on its own.
How a message gets there
The same four steps, whichever surface you send from.
- 01
You ask
From your agent, the CLI or the web UI. Tell your agent "ask maya whether we drop the old column now" and it writes the message for you.
- 02
You see it first
The CLI and the web UI show what will be sent, and to whom by name, and send only on your yes. An agent has to preview the exact message before flanner sends it, and is told to wait for your yes.
- 03
It goes device to device
Straight from your machine to theirs, over the same encrypted connection Mesh uses for plans. If their laptop is closed, it waits on yours and is tried again for up to a day, while your device is receiving.
- 04
It reaches their agent
It appears in their Claude Code or Codex session at the next prompt, or between tool calls. A desktop notification names who sent it.
Where it shows up
In the agent you already have open, and in flanner's own tools when you do not.
Claude Code
A hook shows new messages at your next prompt and between tool calls. With channels, a Claude Code research preview, it can show one the moment it arrives, even in an idle session. That takes one flanner setting and, today, a development flag.
Codex
The same hook, at your next prompt or tool call. Codex runs it once you trust it with /hooks. If your administrator allows only managed hooks, flanner init --print-codex-hook prints the entry to give them.
The CLI and the web UI
Neither needs an agent. flanner messages inbox lists unread messages, and the local web UI has a Messages page with an unread count.
When no agent is open
A desktop notification, on by default, names the sender and never shows the message; flanner messages notifications off turns them off. flanner peer autostart on keeps your device receiving across reboots.
What it will not do
A quote, not an instruction
Your agent receives a teammate's message as a quote, with the sender's name and a note that it was only shown. flanner tells it never to act on one, even when the message asks it to run something. What your agent may do on your machine is still set by its own permissions.
Our servers never see them
Messages go device to device. The relay only carries encrypted traffic it cannot read. The hosted service never stores what a message says, who it was sent to, or when.
Deleted on a schedule
Every device deletes messages after 90 days, unless your organization's admin chooses 30, 180 or 365. There is no keep-for-ever. Plans are the lasting record; a message is a conversation about one.
Quiet when you want it
Set quiet hours, or mute a teammate, on your own device. Messages still arrive and are listed; they just do not interrupt. Nobody is told.
Part of Team Mesh
Messages run on Flanner Mesh: the same enrolled devices, the same roster and the same encrypted connections that sync your plans. There is nothing extra to buy. Team Mesh and Organization include it.
Personal Mesh does not. It is one person on their own devices, and there is nobody to message.
An admin can switch messaging off for the whole organization in the console. A message is plain text up to 4 KB, to up to 20 people or one workspace.
Next to Claude Code's own messaging
Since v2.1.224, Claude Code can pass a note from one of your sessions to another of yours. On one machine it travels over a local channel. To reach a session on another machine it goes through Remote Control, and so through Anthropic's servers, with a claude.ai sign-in at both ends.
Flanner Messages is for other people. A message goes from your device to a teammate's, signed, and reaches their agent in Claude Code or Codex as a quote, not an instruction.
The two sit side by side: one for your own sessions, one for your team. How messages reach each agent.
Included in Team Mesh
Every Team Mesh and Organization seat receives messages, and anyone who can comment in a workspace can send them. Start a team, or read how it works first.