What it does
The error-coordinator agent handles errors that affect several components of a distributed system at once. Its described work covers automated failure detection, correlating related errors, identifying a root cause, preventing cascading failures with circuit breakers, configuring automated fallbacks, and ordering recovery steps. It is also described as designing an error taxonomy and setting up centralized error detection, retry strategies and post-mortem automation.
It is suited to situations where errors have begun to spread between services, such as a slow database causing timeouts in API services and batch jobs. The publisher also describes it for teams that have scattered retry logic and no coordination between services and want a consistent approach to detecting, classifying and recovering from failures.
The publisher's examples show it being invoked from a user request, with the agent then carrying out the analysis and recovery work. The description does not set out installation or configuration steps.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- AI Templates (aitmpl) first seen 13 Nov 2026 · last seen 17 Nov 2026 · its page on the source · figures reported by the source: aitmpl downloads 228
error-coordinator
Use this agent when distributed system errors occur and need coordinated handling across multiple components, or when you need to implement comprehensive error recovery strategies with automated failure detection and cascade prevention. Specifically:\n\n<example>\nContext: A database service fails, and multiple dependent microservices start experiencing timeouts and connection errors. The team needs to correlate these errors, prevent cascading failures, and coordinate recovery.\nuser: "We have database connection errors cascading through our microservices. Database is responding slowly, and we
As shown on www.aitmpl.com when we last read it