Open-source AI teammates in Slack, Teams, Discord, Telegram and Mattermost. Self-host it, with any agent harness and any model.
Python agent-orchestrationaiai-agentschatopsdiscordlangchainmcpmicrosoft-teamsmulti-agentopen-sourceopenaiself-hostedslack
Before you build anything
Last checked against: 2026-08-20.
Settle these before creating a single room. Skipping them is how people end up with six rooms they do not need and three agents that do the same thing.
Work through them in conversation, a couple at a time. Do not send someone a numbered battery of twelve questions.
The goal
- What does done look like? Not "an agent that helps with X" — what specifically will be different when it works. If this cannot be answered, stop; there is nothing to build yet.
- Who is it for? One person, a team, anyone who wanders into a channel. This decides almost everything else.
- Does it already exist? Check
RECIPES.md. Adapting the nearest recipe beats designing from nothing.
The people and the channels
- Where do these people already talk? Build there. A new channel nobody visits is a dead setup. If they live in Slack, the room is that Slack channel.
- Which chat platform, and is it already connected to Switch? Platforms differ in ways
that will affect your design — see
GOTCHAS.md. Do not assume the instance's default bridge is where the humans are; it very often is not. - Is this one-to-one or one-to-many? One person repeatedly needing help is a room per person. A team with a shared queue is a hub.
The agents
- How many agents, really? Default to one. Add a second only when it does a genuinely different job — the usual honest split is doer versus coordinator. Two agents that both "help with the project" is one agent.
- When should each one be awake? Idle until someone addresses it is the right default. Anything else needs a reason.
- Where does each one run? On whose machine, in which directory, with which credentials. Remember it is not your machine — ask what they have rather than prescribing. If the work wants a GPU or a big dataset, ask whether they have a box they reach over SSH.
- Who provisions them? Not you — say so early, so nobody sits waiting on you to create something you cannot create. Point them at Switch Console: it creates the agent, gives it its identity and credentials, and holds its instructions. An agent set up outside it does not connect to Switch properly.
- Where does each agent's brief live, and what does it point at? The instructions go in Switch Console. They should point at material — a repository it clones, files in its working directory, documents on its room — rather than containing everything, so it stays current instead of frozen at the moment it was written.
Where the facts live
- What is portable and what is specific to this instance? Portable how-to goes in the agent's instructions. Ids, keys, channel names, people to notify, lookup tables go in the room's instructions. If you are about to hard-code an id into a prompt, stop.
- Will this ever run in a second place? If yes, no server-specific value may appear in any prompt — it goes in a table the agent looks its own row up in.
- Does anything need to be remembered between conversations? If yes, that is a file the agent owns and updates as it goes, not something it holds in its head. Decide where it lives and who else can read it.
Roles
- Do you actually need a role? Only if the holder varies, or you need exactly one holder at a time, or you want to address the job rather than the agent. If one known agent will always do it, put the procedure in the agent and skip the role.
The failure cases
- What happens when the agent is wrong? Where does the correction go, and who applies it? "Someone will notice" is not an answer.
- What happens when it does not know? It should say so plainly. Design that in rather than hoping.
- What is the blast radius? If the agent can do something irreversible, put it behind an explicit human yes and confine it to one room.
- If its access runs through a person's account, what else can it reach that it should not? Confine it to an allow-list before you build, not after.
Before you call it done
- Has the person seen the design and said yes? Room topology, what each agent does, what goes where. Propose it in the room and wait. Never start creating off your own judgement.
- Can they change it themselves? If every adjustment needs you, it is not finished. The things they will want to tweak — wording, who gets notified, which sources — should be in room instructions or a file they can edit, not buried in a prompt.