AgentConnect is an open-source platform where teams and AI agents work together across Slack, Telegram, Discord, and GitHub. Connect Claude Code, Codex, Grok Build, DeepSeek, Pi, or any ACP-compatible runtime. Give each agent a role and choose its model, workspace, memory, tools, skills, and permissions. Start work from conversations, pull requests, issues, webhooks, or schedules. Agents can call one another while your team follows the work they are allowed to see from one console.
Hey Product Hunt 👋
We started like most teams: everyone running Claude Code or Codex in their own terminal. As agents took on more — triaging errors, reviewing PRs, answering support — they became real teammates, except nobody else could see a session, take it over, or reuse its context. So we all wrote our own glue, then realized we'd built nearly the same thing.
We looked at what existed: great personal tools with no team model, team tools that require migrating into a brand-new chat app, and closed-source tools tied to one provider.
So we built AgentConnect — open-source, provider-neutral (Claude Code, Codex, any ACP runtime), living inside Slack/Discord/Telegram plus GitHub, fully self-hosted. Agents run on your machines; we never see your code or messages.
Would love your feedback — happy to answer anything!
Report
My worry with multi-agent setups has always been visibility, who approved what and why. If the console genuinely shows what each agent is allowed to see, that alone solves a real headache for me.
@david_grunwald1 yes, we are making this specific for team, following a screenshot in the console showing the agent visibilities. Sandbox options are also also available for agents so they can't access each other's data physically
Report
This is awesome! Is it painful to go through all the OAuth with each platform?
I’ve tried a few multi-agent setups, and the agents often just keep replying to each other without actually converging. How does AgentConnect behave in those situation?
@sidraarifali In short, AgentConnect agents behave more like thoughtful teammates: they do not speak unless they have something useful to add.
Multi-agent conversations usually become chatty for two reasons:
Unnecessary model output. Many models produce a response even when they have nothing meaningful to add. We can tune an agent to return an explicit no-op signal in that situation, allowing AgentConnect to safely filter the message before it reaches the conversation.
Responding to stale context. Two agents may begin working from the same conversation state and publish their answers without seeing what the other has said. In a counting game, for example, both agents may say “1,” then both say “2”—producing four messages instead of two. Before an agent publishes its response, AgentConnect tells it whether new context has arrived, giving it a chance to update or suppress its output.
The result is deliberate turn-taking instead of an open-ended conversation between bots.
Report
I like that it's runtime-agnostic. Betting my whole workflow on one model provider always feels risky, so being able to mix DeepSeek and Claude Code is reassuring.
Tagging an agent where work already happens, instead of asking the team to move into yet another chat app — that's the right call, and it's the part most competitors get wrong.
Provider-neutral, self-hosted, Apache 2.0 is a strong combination for anyone who doesn't want their agent layer locked to whichever runtime happens to be ahead this quarter.
Will be watching how the cross-surface session and memory model shakes out. Congrats to the team!
AgentConnect
My worry with multi-agent setups has always been visibility, who approved what and why. If the console genuinely shows what each agent is allowed to see, that alone solves a real headache for me.
AgentConnect
@david_grunwald1 yes, we are making this specific for team, following a screenshot in the console showing the agent visibilities. Sandbox options are also also available for agents so they can't access each other's data physically
AgentConnect
@claire_santiago we made it as easy as possible
e.g. for slack, you could add slack app with one click with configure token or builtin slack app:
https://docs.agentconnect.md/docs/slack
AgentConnect
@sidraarifali In short, AgentConnect agents behave more like thoughtful teammates: they do not speak unless they have something useful to add.
Multi-agent conversations usually become chatty for two reasons:
Unnecessary model output. Many models produce a response even when they have nothing meaningful to add. We can tune an agent to return an explicit no-op signal in that situation, allowing AgentConnect to safely filter the message before it reaches the conversation.
Responding to stale context. Two agents may begin working from the same conversation state and publish their answers without seeing what the other has said. In a counting game, for example, both agents may say “1,” then both say “2”—producing four messages instead of two. Before an agent publishes its response, AgentConnect tells it whether new context has arrived, giving it a chance to update or suppress its output.
The result is deliberate turn-taking instead of an open-ended conversation between bots.
I like that it's runtime-agnostic. Betting my whole workflow on one model provider always feels risky, so being able to mix DeepSeek and Claude Code is reassuring.
AgentConnect
@charlos_brat yeah that's our major motivation indeed, give it a try and let us know what you think
Macaly
tagging agents across slack + github is smart 🔥 open source is the right call here
AdAnt AI
Tagging an agent where work already happens, instead of asking the team to move into yet another chat app — that's the right call, and it's the part most competitors get wrong.
Provider-neutral, self-hosted, Apache 2.0 is a strong combination for anyone who doesn't want their agent layer locked to whichever runtime happens to be ahead this quarter.
Will be watching how the cross-surface session and memory model shakes out. Congrats to the team!