Esta página se muestra en inglés. Una traducción al español está en curso.
ScriptsMay 11, 2026·2 min de lectura

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
Listo para agents

Este activo puede ser leído e instalado directamente por agents

TokRepo expone un comando CLI universal, contrato de instalación, metadata JSON, plan según adaptador y contenido raw para que los agents evalúen compatibilidad, riesgo y próximos pasos.

Stage only · 29/100Stage only
Superficie agent
Cualquier agent MCP/CLI
Tipo
Script
Instalación
Single
Confianza
Confianza: Established
Entrada
README.md
Comando CLI universal
npx tokrepo install c80af52c-2608-478b-acd3-37a61a60ca9f
contrato de instalaciónJSON de metadataplan adaptadorcontenido raw
Introducción

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.

🙏

Fuente y agradecimientos

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

Discusión

Inicia sesión para unirte a la discusión.
Aún no hay comentarios. Sé el primero en compartir tus ideas.

Activos relacionados

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
◈Inicio🔍Buscar👤Yo