Switch brings AI agents into the collaboration tools your team already uses. Agents join as named participants in your Slack, Teams, Discord, or Telegram channels, sharing the same context and history as your team. Connect an agent once and use it across projects. Each room carries its own context, participants, and rules. Works with Claude Code, OpenAI, Google ADK, LangChain, and more. Open source, self-hostable, running in minutes.
The named participant approach is interesting. Can admins control which agents are allowed to join specific channels?
Switch
@eriberto_puppypound Yes! Admins can decide which rooms each agent can access, and an agent that hasn't been added to a channel can't see it or post in it.
Would love to hear about your use cases and how you might be thinking of setting up Switch!
Are these plans for custom agent permissions so companies can limit what each agent can access?
Switch
@jeankang Yes and its possible today! Each agent has its own policy for which rooms it can work in and who can direct it there.
Would love to hear more about what use cases you're thinking of!
Bababot
How does Switch handle permission controls when multiple AI agents are in the same Slack channel?
Switch
@adams_parker Good question.
Each agent has an owner (human). The default permissions is that only that owner can speak to the agent in any context (channel, etc.). You can tweak this to be much more permissive, e.g. any agents or humans in any context can speak to this agent, or something more granular, e.g. my agent can be spoken to by agents x,y,z and humans u,v in channels a,b.
Behind the scenes, on every message sent to your agent in a channel, we have a gate that checks the policy of that agent can block that message if needed.
Switch
@adams_parker One thing worth adding here is that as each agent has its own policy, you can have 5 agents in the same channel with completely different access rules. One might respond to anyone, another only to its owner. The agents and their permissions dictate that, rather than the room itself.
louis says each agent has one human owner and only they can change it. does that hold in telegram too or is it slack and teams first?
Switch
@niveditha_patluri1 Applies to every supported messaging app :)
Switch
@niveditha_patluri1 Worth adding that this is handled by Switch itself, not by the individual chat apps. So your permissions don't break if you add a new connector or chat app later.
My co founder sent me the github link yesterday. We have been trying to figure out how to get claude into our team trelegram chats and Switch does exactly that.
Switch
@andrew_dale2 Sweet ! Glad you found a good use-case!
Let us know if you have any further feedback (good and bad)!
Switch
@andrew_dale2 That's awesome to hear!! Telegram is one of our most requested connectors. Any feedback welcome. :)
Switch
@andrew_dale2 Let us know if you were able to get Claude into your Telegram group. Would love to hear what you have it doing and any improvements that we should be thinking of!
Context switching is the worst so staying natively in Teams is a big plus. really interesting nice work @Switch team👏
Switch
@priya_kushwaha1 Thanks Priya, appreciate the support. If the team already lives in Teams, they shouldn't have to go somewhere else to work with their agents!
@safi_amin exactly, keeping the workflow uninterrupted is so valuable. i hope it will be the product of the day🙌
Switch
@priya_kushwaha1 Thank you Priya, fingers crossed!
Having one environment that keeps the organizational context and workflows consistent while allowing for the other tools (Claude, Slack, etc) is a big unlock for making human x agentic collab work durably. Will be testing this out soon
Switch
@luca_ferrara2 Yep 100% That's the vision -> provide the underlying infrastructure and framework that allows for true human x agentic collaboration.
Switch
@luca_ferrara2 Would love to hear how it goes!