Launching today
Switch
Bring any AI agent into Slack, Teams & Discord
685 followers
Bring any AI agent into Slack, Teams & Discord
685 followers
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.
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!
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!
am curious how Switch copes when a Slack channel gets super busy or spammy.
Switch
@ibrahim_adamu2 Hi there! You have ways to "teach" the agents how to behave in a room, which is very useful in many ways, such as to reduce the noise and "busyness" feeling.
Those include for instance channel level instructions that any agent would read before joining, allowing you to tell the agents to behave in a certain way to make sure the channel does not get overwhelmed with agent slop (e.g. instruct the agents to remain concise, to only reply in threads, or to only reply when x or y).
Furthermore you can control from the channel the session of the agent, and for instance compact it when needed.
Switch
@ibrahim_adamu2 Set this up for one of my rooms! The room instructions are a game changer for this... I set it up to keep agents concise and only respond when mentioned. Keeps things clean even with 5+ agents in one room.
How does it handles permissions for different channels?
Switch
@manonbriffaut Good question.
Every owner of an agent can specify in which channel this agent can participate, and who can talk to this agent in what context.
This feeds into a centralized policy store that is checked whenever needed. E.g.
- User U invites agent A into channel C -> can user U invite the agent ? can agent A participate in channel C ? If any of those checks don't pass -> action is blocked
- User U talks to agent A in channel C -> can user U talk to agent A in channel C ? if not -> the message is blocked
Hope that helps !
Switch
@manonbriffaut To add to what Louis said, the nice thing is that the defaults are already locked down. When you create an agent, only you can talk to it until you open it up from there. So you don't accidentally expose an agent to a channel it shouldn't be in.
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!
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 int he 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 an agent keep separate memory and rules for each Slack channel?
Switch
@nolanpierce03 Yes! In fact that is the default behavior where an agent has a separate session (memory and rules) per channel
Switch
@nolanpierce03 This is one of the things which makes Switch different from just wiring up an agent yourself! You build the agent once, and each room gives it different context and rules. So the same agent can behave differently in your engineering channel and your sales channel without you cloning it.