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
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?
@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
@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.
@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.
@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.
@vipul_kumar1280 Nice! Let us know how it goes.
@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 :)
@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
@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!
Can non-technical people on the team use this too or is it mainly for devs?
@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!
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?
@niveditha_patluri1 Applies to every supported messaging app :)
@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.
Hey @safi_amin and team, congrats on the launch! Bringing AI into the tools people already use makes a lot of sense. Getting closer to feeling like Iron Man talking to Jarvis 😂
How much setup would someone nontechnical need before they could start using an agent in their team’s channels?
Looking forward to trying this out! 👍
@safi_amin @kpwdev hi ! Thanks for this!
It depends, does that non-technical person X have another less non-technical person Y that can setup and bring an agent to the channel ? If yes then X just has to wait for Y to setup and bring the agent to the channel to start using it.
If not, full transparency warning, the road might be a bit bumpy. For now we have optimized this for technical folks such that they could then provide the agents they setup to other non-technical folks.
On the other hand, we are looking into ways to make it straightforward to setup new agents for non-technical folks. Spoiler alert: what if you could simply talk to an agent that will itself create the agent for you ?
But that will come later :)
@kpwdev Hahaha love the Jarvis comparison! 😂
To add to what Louis said, you can also point your favourite AI tool at our docs and have it walk you through setup. Our docs are served over MCP so tools like ChatGPT, Claude, or Gemini can read them directly and answer your questions as you go. Link: https://docs.flintai.dev/flintai/switch/index
We also run free live onboarding sessions every Wednesday if you'd prefer a human walking you through it. Takes about 10mins and they leave time for questions & discussion. Link: flintai.dev/switch-live-training
@safi_amin @lamaudruz appreciate the replies guys - definitely see use for this in my day to day and I know a handful of non technical people who this would be really good for so I'll definitely be sharing this with them and recommending the live onboarding sessions. Excited to see where you guys take this!
@kpwdev Appreciate the kind words Kevin! Open to any feedback or questions along the way. :)
@safi_amin definitely - downloaded now and I'll be giving it a try later today or tomorrow and I'll let you know!
@rukhsar_amjad Personally I think this is something that's always evolving. If you're curious about how the team developed Switch during its own AI journey check out our lead eng Louis's blog post about building Switch with Switch: https://www.flintai.dev/blog-posts/our-team-is-now-composed-of-5-devs-and-45-agents-all-in-slack
@rukhsar_amjad Thanks! It took a lot of iteration, but once we figured out the room should hold the context instead of the agent, everything else fell into place. You build an agent once and each room gives it different rules and context. We typically start a new room for each focus area, initiative, or deliverable depending on the size and scope of the item of work. That's what makes switching between tasks feel natural instead of having to reconfigure or catch up agents every time!
Context switching is the worst so staying natively in Teams is a big plus. really interesting nice work @Switch team👏
@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🙌
@priya_kushwaha1 Thank you Priya, fingers crossed!
What happens when two agents in the same channel disagree or give conflicting answers?
@artstavenka1 This actually happens! And I think it's one of the key benefits of having agents in a shared room... when two agents give different answers, the team can see both in real time and make a call. It's the same thing that happens when two teammates disagree in a thread. The difference with isolated agents is that you wouldn't even know they disagreed because nobody sees both answers side by side.
@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.
Can an agent carry context from slack into teams and vice versa? I see that as being the most useful element, where context from a slack channel with engineers can answer questions on a teams channel with execs.
@safi_amin congrats on the launch, looking forward to testing this out.
@safi_amin @umier Hey ! Yep that is possible, the session of an agent that is connected to let's say a slack channel can jump to another channel in another connected messaging like teams, back and forth, and therefore carry the require context!
@umier Thank you Umier! That's one of the most exciting use cases we're seeing. Engineering works in Slack, leadership is in Teams, and the agent carries the context between both without anyone having to copy-paste or re-explain. Let us know how it goes when you try it out!
@safi_amin @umier You can bridge between rooms if needed (even on different messaging apps), or you can get agents from each room to write to a common resource outside of it (eg confluence, a word doc, a wiki) to ensure context is carried.
This is the correct vision of the future of work.