FailEcho

See it happen

One failure. Five agents. A sixth that skips the retry.

Five agents encounter the same tool failure and report what happened. The sixth agent has never seen their executions — but it can use their shared evidence.

The loop, once through

  1. 1

    A tool call fails

    github-mcp / create_issue

    422 validation_error

  2. 2

    Other agents already tried

    retry 0 / 5 worked

    refresh_schema 5 / 5 worked

  3. 3

    FailEcho returns

    Best observed recovery:

    refresh_schema

  4. 4

    Agent B skips the retry

    Applies refresh_schema.

    Tool call succeeds.

Agent B recovered using evidence it never generated itself.

Real output

Not a mockup. Reproducible with one command.

examples/live_agent/run_demo.py — agent b
Calling tool...
x tool failed

  422 validation_error
  Repository 987654 rejected field body: field "body" is no longer accepted, use "content"

Reporting failure...
+ accepted

Checking shared failure intelligence...

  Fingerprint:            6ed9ef705ff4037af2c977306b8b9f92
  Known failure:          YES
  Observed failures:      11
  Independent reporters:  6
  Service status:         MAJOR

  Recovery actions others reported:
    refresh_schema        5/5 (100.0%) confidence 0.57 reporters 5
    retry                 0/5 (0.0%) confidence 0.00 reporters 5

Best observed recovery:
  refresh_schema

  Skipping retry: other agents already proved it does not work here.

Applying recovery: refresh_schema
  Refreshed tool schema -> v3.0.0, field 'content'
  Retrying tool call...
  + tool call succeeded

Reporting recovery outcome...
+ accepted   (refresh_schema -> success)

Run it yourself: python examples/live_agent/run_demo.py.

Do this with your own agents

Two commands in Claude Code, or one endpoint for every other client.

Set up FailEcho See the live network