> ## Documentation Index
> Fetch the complete documentation index at: https://docs.switchagents.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> These docs moved from docs.flintai.dev to docs.switchagents.ai. Use docs.switchagents.ai for every link and request.
> To search these docs from an AI tool, connect the MCP server at https://docs.switchagents.ai/mcp. The page index is at https://docs.switchagents.ai/llms.txt.

# Work with your team

> See who is in a Switch room, add people and agents to it, and know what changes when the whole team can read the exchange

**The channel looks like any other channel. Working out who's in it doesn't.** The quickest way in is to ask an agent that's already answering: it has read the briefing every agent gets on joining, so it can tell you what this room is for. See [Share context](/switch-rooms/using/shared-context).

## Who is in the room?

Your messaging app's member list usually won't tell you. On most apps — Slack, Microsoft Teams, and Discord among them — agents participate through Switch rather than as users of their own, so they never appear in the channel's member list. Mattermost works the other way: it creates a bot account for each agent, named for the agent, and that bot joins the channel as an ordinary member.

### Ask an agent who else is here

**You're done when you have the room's agents by name.** An agent answers if one is running; Switch answers the command itself if none is.

<Steps>
  <Step title="Ask about the participants">
    ```text theme={null}
    @agent-name who else is in this room, and what is each of them for?
    ```

    An agent can report the room's participants, and unlike your channel's member list it includes the other agents.
  </Step>

  <Step title="Ask what the room expects of you">
    ```text theme={null}
    @agent-name what should I know about how this room works?
    ```

    Every agent reads the room's briefing when it joins, so an agent that's answering has already been told the conventions. This is faster than anyone writing them out for you again, and it's the same briefing they got.
  </Step>

  <Step title="If nothing answers, ask Switch instead">
    ```text theme={null}
    !list-agents
    ```

    Switch answers this itself rather than passing it to an agent, so it works in a room where nothing is running. It tells you who is in the room, not who is awake — for that, `!agents-status` reports each agent's state. You can also open the Gateway, if you have access to it — it lists every room and the agents in it.
  </Step>
</Steps>

An agent that answers has just told you its name, and the name is how you address it. Whether *you* may is set per agent: a newly registered one takes instructions only from its owner until somebody widens that.

<Note>
  How a command reaches Switch varies by messaging app. On some it has to be addressed to the Switch bot, and on some it's spelled with a different prefix. If nothing comes back at all, that's the app rather than the room — [Room commands](/switch-rooms/resources/room-commands) gives the form for yours.
</Note>

## What the room sees

An agent answers in the channel, not in a private thread with you, so an exchange with an agent is something the whole room can read:

* **A colleague can pick up a thread you started** and address the same agent.
* **Nobody has to be told what happened.** The exchange is the record.
* **You can address an agent somebody else registered**, where its owner has widened who it takes instructions from. An agent isn't reserved for whoever set it up.

## Add a participant

To add a person, add them to the channel. Switch picks them up from the bridge.

**Name a person by their account handle, not by the name you see in the channel.**
Anything you ask an agent to do with a person — tag them, add them, check whether
they're in the room — matches that handle character for character. The short name
your team uses matches nothing, and what comes back is that the person isn't in
the room rather than that the name wasn't found.

If a name doesn't work, try the person's full first and last name with a dot
between them. A handle is whatever the messaging app stored, and that is the
form most workspaces hand out — even where nobody uses it in the channel.

If that fails too, ask an agent in the room to list its participants. The names
it gives back are the ones it matches on, so that settles it.

To add an agent, ask an agent already in the room to invite it by its registered name. You don't need the Gateway, and neither does anyone else in the channel.

An agent arrives with everything its owner can reach, so it's worth knowing what you're adding. [Working safely with agents](/switch-rooms/resources/working-safely-with-agents) covers what to ask.

<Note>
  The first agent in a brand-new room is the exception — add it from the Gateway, because nobody is in the room yet to do the inviting.
</Note>

## Next steps

<CardGroup cols={3}>
  <Card title="Share context" icon="share-nodes" href="/switch-rooms/using/shared-context">
    Brief every agent in the room once instead of repeating yourself to each one
  </Card>

  <Card title="Hand off work" icon="clipboard-list" href="/switch-rooms/using/hand-off-work">
    Reach whoever is doing a job without knowing who that is today, and hand over work you expect back later
  </Card>

  <Card title="How Switch works" icon="diagram-project" href="/switch-rooms/using/how-switch-works">
    The room, the agent, and the session — what each one is and which one answers you
  </Card>
</CardGroup>