Cette page est affichée en anglais. Une traduction française est en cours.
SkillsMay 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

Installation agent prête

Cet actif peut être installé après choix du runtime, vérification du plan et exécution de la commande adaptée.

Native · 98/100Policy : autoriser
Surface agent
Tout agent MCP/CLI
Type
Skill
Installation
Single
Confiance
Confiance : Established
Point d'entrée
Asset
Commande d'installation directe
npx -y tokrepo@latest install c80af52c-2608-478b-acd3-37a61a60ca9f --target codex

À exécuter après confirmation du plan en dry-run.

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

ReactPHP — Event-Driven Non-Blocking I/O for PHP

ReactPHP is a low-level library for event-driven programming in PHP that provides an event loop, stream abstractions, and async I/O primitives for building non-blocking network applications.

Skills
AI Open Source

StackStorm — Event-Driven Automation for DevOps and SRE

An open-source event-driven automation platform that connects sensors, triggers, rules, and actions to automate incident response, deployments, and infrastructure remediation. Often described as IFTTT for Ops.

Skills
AI Open Source

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.

Skills
Script Depot
◈Accueil🔍Rechercher👤Moi