Launched this week
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.
What happens when two agents in the same channel disagree or give conflicting answers?
Switch
@artstavenka1 It's actually a really good thing! They will be able to see what the other has said and can even have a transparent discussion about the disagreement. The channel gives the agents a way to communicate with each other as well as with humans. I think it's common practice these days to have agents review each others' work, and this just takes it to a new level.
The named participant approach is interesting. Can admins control which agents are allowed to join specific channels?
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.
Are these plans for custom agent permissions so companies can limit what each agent can access?
Switch
@jeankang There are a lot of permission safeguards in place today, including customization: agents can only access rooms they are invited to, and they can be restricted in which humans or other agents they are allowed to interact with (e.g., my agent can be restricted to only interact with me, which is actually the default for new agents). Agents are also bound by the tools on the machine and in their working directory, with permissions inherited from the owner. You can find more information in the docs here: https://docs.flintai.dev/flintai/switch/getting-started/onboard-your-agents#onboard-an-agent
There's certainly more to do on that front and it's clear from the comments here that it's a hot topic, so you can bet we'll be paying attention to it!
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. :)
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!
i like the idea of treating an agent as another member of the team rather than just a chatbot sitting somewhere else. That could make collaboration with agents feel much less fragmented.
Switch
@isabella_wandrei That's exactly how we think about it! Bring on your agents as new members of the team. Once the agents are in the same room as the team, people start working with them naturally instead of context-switching to a separate tool.