Hi HN, we built agentconnect. It is an open source project for team working with multiple agents. It gives teams one place to manage all agents.
Claude Tag showed a shared agent can be useful in a team channel. We want to support a different setup. A team can run agents on different runtime. It can assign each agent to a different codebase or other part of business. Each agent has its own workspace and context.
Agents can ask each other for help, and both sides must allow the request. Receiving agent works in a separate session with its own permissions. Then it sends the result back to the original thread. Its credentials and direct access to resources are never shared with the calling agent.
Agentconnect supports several acp runtimes and can be self hosted. I’ll be reading the comments and would love to see your feedback.
Hi HN, we built agentconnect. It is an open source project for team working with multiple agents. It gives teams one place to manage all agents.
Claude Tag showed a shared agent can be useful in a team channel. We want to support a different setup. A team can run agents on different runtime. It can assign each agent to a different codebase or other part of business. Each agent has its own workspace and context.
Agents can ask each other for help, and both sides must allow the request. Receiving agent works in a separate session with its own permissions. Then it sends the result back to the original thread. Its credentials and direct access to resources are never shared with the calling agent.
Agentconnect supports several acp runtimes and can be self hosted. I’ll be reading the comments and would love to see your feedback.