microsoft/AutoSaddler

capability-patch

Selected during the capability phase — adds new tools, exposes new parameters, fixes tool implementations, or removes infrastructure limitations to expand what the agent can do

diagnose

Use to systematically diagnose why scenarios fail — identifies root causes by analyzing agent traces, codebase, and behavioral patterns

history-analysis

Use to systematically analyze the full evolution history without output truncation — produces a structured summary of what matters for the current iteration

patch-verification

Use after applying any patch to thoroughly verify the agent codebase has no bugs — checks syntax, imports, runtime behavior, docstrings, templates, hooks, and logical correctness

steering-patch

Selected during the steering phase — refines agent behavior by modifying prompts, tool descriptions, or hook reminders without changing executable code

capability-patch

Selected during the capability phase to add tools, expose parameters, fix implementations, or remove infrastructure limitations that restrict the agent.

patch-verification

Use after applying a Meta-ARE patch to check syntax, imports, integration behavior, hooks, mutation scope, and result consistency.

steering-patch

Selected during the steering phase to refine agent behavior through prompts, tool descriptions, or hook reminders without changing executable code.

causal-diagnosis

Use before proposing a mutation to diagnose measured failures from evaluator outcomes, traces, history, and the controlling candidate surfaces.

history-analysis

Use to systematically analyze the full evolution history without output truncation and produce a focused summary for selection, diagnosis, or reflection.

verification-baseline

Use after applying a candidate change to verify its diff, scope, syntax, integration behavior, and consistency before returning it.