Cette page est affichée en anglais. Une traduction française est en cours.
ScriptsMay 11, 2026·2 min de lecture

Solace Agent Mesh — Event-Driven Agent-to-Agent Messaging

Solace Agent Mesh provides event-driven messaging for multi-agent systems so tools and agents coordinate through durable topics with replayable event logs.

Agent Toolkit
Agent Toolkit · Community
Prêt pour agents

Cet actif peut être lu et installé directement par les agents

TokRepo expose une commande CLI universelle, un contrat d'installation, le metadata JSON, un plan selon l'adaptateur et le contenu raw pour aider les agents à juger l'adaptation, le risque et les prochaines actions.

Stage only · 29/100Stage only
Surface agent
Tout agent MCP/CLI
Type
Script
Installation
Single
Confiance
Confiance : Established
Point d'entrée
README.md
Commande CLI universelle
npx tokrepo install c80af52c-2608-478b-acd3-37a61a60ca9f
contrat d'installationJSON metadataplan adaptateurcontenu raw
Introduction

Solace Agent Mesh provides event-driven messaging for multi-agent systems so tools and agents coordinate through durable topics with replayable event logs.

  • Best for: Teams building multi-agent systems who need reliable coordination, fan-out, and replayable event logs
  • Works with: Multi-agent runtimes + messaging backplanes; treat topics as contracts
  • Setup time: 25 minutes

Practical Notes

  • Setup time ~25 minutes (clone + follow the demo in README)
  • Reliability check: one message fan-out reaches N subscribers and produces auditable logs
  • GitHub stars + forks (verified): see Source & Thanks

Multi-agent systems are mostly coordination problems. A messaging mesh gives you a durable backbone: publish events, consume reactions, and replay history when things go wrong. Design topics as stable contracts and keep payloads structured—then you can evolve agents without breaking the system.

FAQ

Q: Why do agents need messaging? A: As systems grow, you need decoupling and fan-out; messaging turns coordination into data flow.

Q: What’s a good first use case? A: Event log for tool calls + agent decisions; then add downstream consumers for alerts.

Q: How do I avoid chaos? A: Version your topics/schemas and keep a small allowed vocabulary of event types.

🙏

Source et remerciements

Source: https://github.com/SolaceLabs/solace-agent-mesh > License: Apache-2.0 > GitHub stars: 3,664 · forks: 227

Fil de discussion

Connectez-vous pour rejoindre la discussion.
Aucun commentaire pour l'instant. Soyez le premier à partager votre avis.

Actifs similaires

CrewAI Flows — Event-Driven Multi-Agent Orchestration

CrewAI Flows is the event-driven orchestration layer on top of Crews. Decorators @start, @listen, @router build a typed state machine for multi-agent.

Workflows
CrewAI

CAMEL — Multi-Agent and Tooling Library

CAMEL is an open-source library for multi-agent systems and tools. Install `camel-ai`, then compose agents, tools, and optional web helpers in Python.

Scripts
Agent Toolkit

Twisted — Event-Driven Networking Engine for Python

Twisted is a mature event-driven networking framework for Python that supports TCP, UDP, TLS, HTTP, SMTP, SSH, DNS, and many other protocols in a single cohesive library.

Scripts
Script Depot

SaltStack — Scalable Event-Driven Infrastructure Automation

Salt is a Python-based configuration management and remote execution engine that manages thousands of servers in real time using an event-driven architecture, ZeroMQ transport, and declarative YAML states.

Scripts
Script Depot
◈Accueil🔍Rechercher👤Moi