Launching today

AgentConnect
Tag any agent, wherever work happens.
169 followers
Tag any agent, wherever work happens.
169 followers
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.









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
@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.
Ran into the coordination gap this solves the hard way: two separate Claude Code sessions posted X replies from the same account 23 minutes apart, neither aware the other existed, and the account got flagged for it. Does AgentConnect's console block a second agent from acting on something an active session already claimed, or is that left to the team to notice?
AgentConnect
@abdullah_javaid3 you should be able to control how you want agent to behave, e.g. when you create the agent, you can describe the agents like "you are..., when post, check if there already same/similar posted already within 30min, if so, don't post and alert in #xxx channel"
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