Route a group or direct message
A workspace group chat is shared. A direct chat is one-to-one. The address you use decides who receives the message and which conversation holds the resulting work.
Before you start
- A workspace has at least one member and a leader.
- Read Conversations and routing for the routing grammar and conversation channels.
Steps
Select the workspace in the rail and press
ito focus the composer.Type a message with no
$Nameand pressEnter. The leader receives the message and either answers or coordinates the work.To address one agent in the group, type
$, choose the agent, and finish the message. PressEnter. That agent receives a peer turn. The leader does not receive the command. A bare name without$is only a reference.!Nameis an accepted alias.To address several agents, include each
$Namein one message. Each unique named agent receives one work item. Duplicate mentions collapse.To reference a workspace file, type
@and choose the file from the workspace index. Finish the message and pressEnter. The composer inserts the escaped workspace-relative path, such as@docs/notes.md, and the reference is appended to the instruction.@is for files only; it never addresses an agent or a skill.To write a literal dollar sign, type
\$. To talk about an agent without creating work, write the bare name or put it in code formatting.To work with one agent privately, select that agent in the rail and send the message from its direct chat. Only that agent answers. A
$Namein a direct chat creates no work and shows a notice that direct chat stays one-to-one.
Expected result
- A group message without a mention creates a leader turn and a work item for the leader.
- A group message with mentions creates one work item per named member.
- A direct message creates work only in that direct chat. Its Work history is separate from the workspace group.
- Agent references inside fenced code, inline code, URLs, and file paths do not route. This lets agents discuss names without assigning work.
Troubleshooting
- Your draft stays and an unknown agent is named. The message was rejected before a transcript line or work item existed. Pick an existing workspace member.
- A bare name created no work. That is a reference, not a route. Add
$. - A direct chat ignores
$Name. Open the workspace group chat or the named agent's own direct chat instead. - A file reference is missing. Check that the file is inside the workspace and the index has refreshed. The picker indexes workspace files, not files outside the workspace directory.
Next
- Use skills: route reusable guidance to its owner.
- Use the Work pane: follow the work you created.
- Conversations and routing: read why code and URLs never route.
- Keyboard reference: exact chat and composer bindings.