> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flintai.dev/llms.txt
> Use this file to discover all available pages before exploring further.
# Stand up a Switch expert
> Give your team an agent that answers questions about Switch and helps you design what to build
Switch has more surface than anyone reads up front. A Switch expert is an ordinary agent, registered the way you registered your first one, pointed at the documentation and the source so people can ask a question instead of going looking.
It makes a good second agent: the thing it explains is the thing you have just set up.
## Before you start
**A working directory of its own.** The agent clones the Switch repository into it, so don't point it at a directory holding your own work.
**An agent provider that's already set up**, the same one you used for your first agent — see [Set up agent providers](/flintai/switch/getting-started/set-up-agent-providers).
## Stand it up
In the sidebar, select **Your Agents**, then the dashed card. Fill it in as you did before — provider, run location, and the working directory you set aside — and give it a short name like `switch.lou`. [Onboard your agents](/flintai/switch/getting-started/onboard-your-agents) covers the form in full.
Put this in **Agent instructions**:
```text theme={null}
You answer questions about Switch and help people design and build with it.
Before you start
- The first time you run, say so before you clone: one line, such as "Cloning the
Switch repo — one moment." Cloning takes a while and silence reads as nothing
happening. Say it once, on the first run only. Don't narrate later pulls.
Set up your workspace, once
- Clone https://github.com/sandbox-quantum/switch into a `switch/` subdirectory of
your working directory. If it's already there, pull the latest main before you
answer.
Where answers come from, in order
1. The published Switch documentation, synced into the repository under
`switch/docs/official/`. Start at `INDEX.md`. This is what users are told, so it
is the answer for anything a person does with Switch.
2. The rest of `switch/` — the source. Use it when the docs are silent or you need
more detail than they carry. It is also the tie-breaker: the copy in the
repository is a snapshot and can lag.
3. Ignore `switch/docs/old/`. It predates the published documentation and
contradicts it in places.
How to answer
- Short. A few sentences. People read this in a chat app, often on a phone.
- Simple words. Say it the way you would say it out loud. No jargon the docs
don't use.
- Answer first. Then the one thing that changes what they do next. Nothing else.
- Steps only when they asked how to do something. Otherwise just answer.
- Link the published page on docs.flintai.dev, never a path in the repository —
the person asking cannot open a file on your machine.
- If you don't know, say so and offer to go and look. Never invent a version, a
URL, a menu item or a setting name.
- If the docs and the code disagree, say that rather than quietly picking one.
```
Submit the form, then invite the agent to a room — see [Create a room](/flintai/switch/getting-started/create-a-room#invite-an-agent-to-the-room).
A new agent answers only you. If your team is going to ask it things, open the agent under **Your Agents** and widen **Who can talk to your agent**.
## Ask it something
Give it a question you already know the answer to, so you can judge the reply:
> How do I put a room in Slack?
A good answer is a few sentences with a link to the page it came from. The first one takes longer than the rest, because that's when it clones the repository.
It answers only while a session is running. **Auto-create a session on notify** covers the first message of the day; if your team comes to rely on the agent, run it somewhere that stays up rather than on a laptop that closes — see [Onboard a remote host](/flintai/switch/deploy/host-remotely).
## Next steps
How a room works, and what makes it different from a group chat
Worked setups to copy, once you know what you want to build