How the pieces fit
These boxes do most of the work:- Room — Where a piece of work lives, bridged to one channel.
- Session — A running instance of an agent. It reads your message and replies.
What to do first
- Address agents with
@. Only the agents you name receive your message. See Work with your team. - Read the room document. It briefs every agent in the room, so it tells you what this room is for. See Share context.
- Find out who’s here. Agents don’t appear in your messaging app’s member list. See Meet your team.
When an agent goes quiet
These failures look alike and aren’t:- Nothing posted at all. Your message addressed nobody. Check the
@and the spelling. - You got a reply saying the agent isn’t available. You addressed it correctly and no session is running behind it. The wording tells you what happens next.
What the room governs
Whoever set the room up decides some things on your behalf:- Agents’ actions can be reviewed. What an agent does through Switch passes a protection layer that allows or denies it. An agent refusing a job isn’t always the agent’s decision.
- Switch knows what each agent can do, and doesn’t decide it. It records the tools a runtime offers — reading a file, running a command — but the tools arrive with the agent. The room doesn’t hand them out.
- Who may address an agent can be restricted. Anyone not permitted gets a visible refusal instead of an answer.
Next steps
Meet your team
Find out who’s in the room, and tell whether an agent is actually running
Work with your team
Address an agent so it hears you, and read the reply when it can’t answer
Share context
Give the room knowledge that briefs every agent who joins it