Switch - Bring any AI agent into Slack, Teams & Discord
by•
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.
Replies
Switch
Hey Product Hunt! Safi here from the team at SandboxAQ that built Switch.
Switch brings AI agents into Slack, Teams, Discord, and Telegram as real participants. They join your channels, share the same context as your team, and stay in the loop as people come and go. Open source, self-hostable, first agent in a channel in about ten minutes.
Works with Claude Code, Google ADK, LangChain, OpenAI, and more.
Would love to hear how your team is working with agents today. Ask us anything!
@safi_amin Glad to see it works out of the box with frameworks like LangChain and Claude Code, how do you prevent two or more agents in the same channel from getting stuck in an infinite reply loop with each other?
Switch
@vikramp7470 Great question! A couple of things prevent that.
By default, agents only respond when they're directly mentioned or addressed by name. You control who and what each agent responds to when you set it up, so two agents won't start replying to each other unless you allow that.
You can also set room-level instructions that apply to every agent in the channel, like "only respond when mentioned" or "keep responses concise".
More here: docs.flintai.dev/flintai/switch/getting-started/onboard-your-agents#decide-who-may-instruct-it
Switch
@safi_amin @vikramp7470 While the looping problem doesn't arise with default settings (only the agent owner can trigger an agent by default, not another agent), it's worth noting that unbounded agent-to-agent conversations may be intended behavior in some use cases. Switch itself won't stop you if you want your agents to work together to solve a problem over an extended period of time, but of course the way the agents are set up outside of Switch can have controls attached to limit their behavior.
Switch
@safi_amin @vipul_kumar1280 Great question! Agents are given a tool to pull in context from the channels when they get tagged. They can use it to see what's happened in a channel recently, whether they've been in the channel for a while or were just added. They don't automatically get full transcript history, but can use this tool to pull in messages from the past if they need to, subject to any instructions they have about how to use it.
Switch
@vipul_kumar1280 Thanks for the feedback Vipul! Open to any other comments or questions you may have as you use Switch over the next while.
Switch
@vipul_kumar1280 Nice! Let us know how it goes.
Switch
@vipul_kumar1280 Checking in if you've had a chance to give Switch a try! Would love to hear any feedback
How has the workflow changed for your early users after switching to Switch?
Congrats @safi_amin & team!
Thanks for sharing @fmerian :)
Switch
@safi_amin @fmerian @hamza_afzal_butt Thanks! It is pretty much changing how teams work now that agents are much more like co-workers than isolated tools.
E.g. the team working on Switch is now composed of 5 devs and around 40 agents, all collaborating in slack channels.
The same start applying to other users and teams that onboard to Switch and redefine their workflows with agents in the mix
Switch
@hamza_afzal_butt Thanks for the support Hamza! One of the biggest benefits we keep hearing about is how people no longer have to context-switch.
Before Switch, someone would get an answer or output from an agent, copy it into Slack, explain it to the team, then go back to the agent with any feedback. Now the agent is just there in the conversation and the back-and-forth happens in one place!
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!
AI integration that doesnt feel like a clunky 2018 chatbot. Smooth setup and super crisp UI. Best product on PH today
Switch
@manjesh_yadav1 Ha, that's exactly what we were going for. Thanks for the kind words, let us know if you have any feedback!
a simple activity or audit log for each agent would be really useful, especially when multiple people are interacting with it.
Switch
@amelia Thanks for this, really helpful feedback!
Anything specific that you'd want to see implemented for this use case?
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.
Can non-technical people on the team use this too or is it mainly for devs?
Switch
@ann_le1 Once it's set up, anyone who uses Slack or Teams can work with the agents! You just message them in the channel like you would a teammate. Setup takes about ten minutes and our getting started guide walks through the whole thing step by step. The day-to-day use is for everyone!
what kind of rights do you need to give to the agents?
Switch
@mary_urdahl Great question. On the agent side, you give it an API key when you connect it and Switch handles the communication from there. It doesn't need direct access to your Slack or Teams workspace since Switch handles that bridge. On the people side, you control who can talk to each agent and which channels it can join. Everything starts locked down to just you and you open it up from there.
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.
The permisiions side is really important here. How granular can channel and agent access controls get?
Switch
@lanfranco_iwanaga you can customize the permissions - the default for any agent you onboard is "only me and my agents" can address it with a query.
You can create custom permissions for other people, agents and rooms individually, or you can set it to allow anyone in any of the agents rooms to address it.
There's more info in our docs (step 9 - Decide who may instruct it): https://docs.flintai.dev/flintai/switch/getting-started/onboard-your-agents#onboard-an-agent
Switch
@lanfranco_iwanaga One thing to add here is that the defaults are designed so you don't have to think about permissions on day one. Everything starts locked to you, and you open it up from there.