Darwin
Contact Us
Customer Stories

Axolotl finds another path when an agent workflow fails


Find a replacement for a failed tool, then check whether it completed the original task.

Developer project · Proposed Act workflow.

The build.

Axolotl is a TypeScript and Next.js app with its own Darwin Search and Act client. It can also call verified agent MCP endpoints directly. Simulated agents are the default demo mode; OpenAI-based output review is optional.

The brief

When an assistant’s tool call fails, Axolotl identifies the unfinished work and looks for another capability that can complete it.

Finding the right capabilities

Darwin finds alternatives using the original goal and completion criteria. Axolotl compares their inputs, access requirements, and expected output.

Coordinating the work

A selected replacement could retry the unfinished work. The retry would preserve completed actions and stop if it needed more access or spending.

What comes back

A result checked against the original task, with partial work and failures recorded. The operator can accept the recovery or choose another route.

The plan, step by step

  1. 1

    Find another route.

    Editorial illustration of Gautam Sudarshan Anand Viruthagiri at work on his project.

    Search. Find an alternative for the unfinished goal, using the original completion criteria.

    Act. Check the replacement’s inputs, access needs, cost, and expected output before retrying.

    Outcome. Replacement options with the differences that matter to the recovery decision.

  2. 2

    Retry the unfinished work.

    Axolotl’s original dashboard showing recovered accessibility, performance, and SEO tasks with an activity log of replacement tools.

    Search. Choose a replacement that covers the unfinished work and accepts the approved inputs.

    Act. Retry the unfinished work while tracking completed actions so an earlier successful side effect is not repeated.

    Outcome. The retry result or failure, with completed actions and remaining work recorded.

  3. 3

    Check whether recovery worked.

    Axolotl’s original Agent reliability screen, with example rankings across crawl, accessibility, performance, and other capabilities.

    Search. Compare the retry result with the original completion criteria.

    Act. Request missing evidence or a correction before accepting recovery.

    Outcome. A check of which criteria passed, what remains incomplete, and whether another attempt is needed.

Recovery checks.

Keep the original request, the retry record, and the acceptance checks together so recovery can be verified.

Recovery proposal

Deliverable: Replacement options with the differences that matter to the recovery decision.

Review criteria: Keep the original goal intact. Show changes in access, cost, or output format before proceeding.

Original prototype by Gautam Sudarshan Anand Viruthagiri and Swarchis and Devesh Aggarwal. Axolotl shows where an audit got stuck and which alternative tools continued the run.

Watch the original demoView the project source
Retry record

Deliverable: The retry result or failure, with completed actions and remaining work recorded.

Review criteria: Do not repeat completed actions. Stop if the replacement needs additional access or spending.

Recovery checks

Deliverable: A check of which criteria passed, what remains incomplete, and whether another attempt is needed.

Review criteria: Keep partial results marked as partial. Return another recovery proposal if the original criteria are not met.

Similar articles

All customer stories
TechnologyCharlotteTechnologyPrecedentTechnologyAegis-Context