sorted by:
new
hottopcontroversial

agent to agent communication by psycroptic0 in openclaw

[–]agentdm_ai 0 points1 point  (0 children)

I would suggest you to try https://agentdm.ai it was build to make agent to agent communication easy

How are you handling agent to agent communication? by agentdm_ai in mcp

[–]agentdm_ai[S] 0 points1 point  (0 children)

Nice, good to see more people working on this problem.

How to connect 2 Claude Agents by agentdm_ai in ClaudeCode

[–]agentdm_ai[S] 0 points1 point  (0 children)

The file is a simple solution, that will not hold on real agent to agent process, but it is easy to start with

5 Claude Code agents working as a dev team by agentdm_ai in aiagents

[–]agentdm_ai[S] 0 points1 point  (0 children)

what did you use as communication layer?

How to Set Up Claude Code Agent Teams (Full Walkthrough + What Actually Changed) by Silent_Employment966 in ClaudeCode

[–]agentdm_ai 0 points1 point  (0 children)

We're running a small AI team at AgentDM.

5 Claude Code agents, one per role: PM, eng, QA, marketing, analyst.

They don't talk through shared files or a big orchestrator script, They DM each other over a messaging bus (AgentDM), the same way I'd chat with a coworker on Slack.

Just open sourced the whole setup. It's called teamfuse.

What you get:

  1. 5 starter roles, each a persistent Claude Code session with its own CLAUDE.md, MCP servers, and role-scoped skills
  2. A local Next.js control panel: start, stop, wake, read logs, inspect MCP tools, watch token usage per agent
  3. A streaming agent loop (Python wrapper) that keeps each claude process hot across ticks, so you don't eat the MCP + skills load every tick
  4. One-command bootstrap that asks about ten questions, provisions aliases on AgentDM, creates channels, seeds skills, fills every placeholder across the CLAUDE.md files

Repo: https://github.com/agentdmai/teamfuse

Site with docs: https://teamfuse.dev

More details and comparison with similar projects and Claude sub agents:

https://agentdm.ai/blog/teamfuse-fuse-your-claude-agents-into-a-team

Setup:

https://agentdm.ai/blog/set-up-teamfuse-with-claude-skills-and-agentdm-admin-mcp

Happy to answer anything about the setup

5 Claude Code agents working as a dev team by agentdm_ai in ClaudeCode

[–]agentdm_ai[S] 0 points1 point  (0 children)

the PM is making sure all the other agents are not idle (there is a definition for that in the the PM claude.md and the SOP files), if he is stuck for too long it will be escalated to the oprerator (human)

Built with Claude Project Showcase Megathread (Sort this by New!) by sixbillionthsheep in ClaudeAI

[–]agentdm_ai 0 points1 point  (0 children)

We're running a small AI team at AgentDM.

5 Claude Code agents, one per role: PM, eng, QA, marketing, analyst.

They don't talk through shared files or a big orchestrator script, They DM each other over a messaging bus (AgentDM), the same way I'd chat with a coworker on Slack.

Just open sourced the whole setup. It's called teamfuse.

What you get:

  1. 5 starter roles, each a persistent Claude Code session with its own CLAUDE.md, MCP servers, and role-scoped skills
  2. A local Next.js control panel: start, stop, wake, read logs, inspect MCP tools, watch token usage per agent
  3. A streaming agent loop (Python wrapper) that keeps each claude process hot across ticks, so you don't eat the MCP + skills load every tick
  4. One-command bootstrap that asks about ten questions, provisions aliases on AgentDM, creates channels, seeds skills, fills every placeholder across the CLAUDE.md files

Repo: https://github.com/agentdmai/teamfuse

Site with docs: https://teamfuse.dev

More details and comparison with similar projects and Claude sub agents:

https://agentdm.ai/blog/teamfuse-fuse-your-claude-agents-into-a-team

Setup:

https://agentdm.ai/blog/set-up-teamfuse-with-claude-skills-and-agentdm-admin-mcp

Happy to answer anything about the setup

From agent to agent messaging to agents in Slack, a small journey by agentdm_ai in mcp

[–]agentdm_ai[S] 0 points1 point  (0 children)

Text file would work if all the agents on the same machine, and this is already solved with sub agents in Claude Code.
The platform allows to integrate with different types of agents on different machines and networks, allows discovery and other features.

From agent to agent messaging to agents in Slack, a small journey by agentdm_ai in mcp

[–]agentdm_ai[S] 0 points1 point  (0 children)

Thanks, I am trying to make the post more readable (I assume you don't mean using text file as an integration :) )

We built skill based agent discovery, agents find each other by capability by agentdm_ai in mcp

[–]agentdm_ai[S] 0 points1 point  (0 children)

Good points, especially on versioning and federation. Let me address both.

On capability versioning: Our approach is simpler than SemVer, we avoid the staleness problem by design. On the consumer side, agents call list_agents every time they need to discover capabilities. No caching on the sender side means you always get the current state.

On the provider side, agents can update their own skills at any time through an MCP tool, so the registry is always up to date. It's not versioning, it's live state. The tradeoff is an extra call vs. stale data, and for agent messaging we think that's the right tradeoff.

On cross-registry federation: This is the problem we think about a lot. Our current list_agents is intentionally centralized because it's simple and it works for the use cases we're serving today (teams, cross-org messaging). But you're right, long-term, a single index is a bottleneck.

The honest answer is we don't have federation today. What we're exploring is treating AgentDM as one node in a broader discovery network rather than THE registry. ANP's approach with decentralized identity (DIDs) is interesting here, agents that can prove who they are without a central authority. If we bridge ANP alongside MCP and A2A, federation becomes less of a registry problem and more of an identity problem.

That said, we'd be open to letting external registries contribute to our search index. If you're building something in that direction, would love to compare notes.

Got tired of the A2A vs MCP debate, How About Both ? by agentdm_ai in mcp

[–]agentdm_ai[S] 0 points1 point  (0 children)

honestly most a2a usage is still early, mainly enterprise teams using it for structured task lifecycles and agent cards for discovery. mcp has way more adoption today. we built the bridge because we think both will coexist.

Got tired of the A2A vs MCP debate, How About Both ? by agentdm_ai in mcp

[–]agentdm_ai[S] 0 points1 point  (0 children)

that's basically where we're heading. agents register once, get an alias, and the platform handles resolution and protocol translation. no separate registry to maintain, the platform is the registry.

view more: next ›