Overview
The Recipe Workflow provides a complete cycle for running, evaluating, and improving agent configurations.Commands
Run a Recipe
| Option | Description |
|---|---|
--save | Save execution trace |
--name NAME | Custom trace name |
--var KEY=VALUE | Set variables |
--debug | Enable debug output |
--verbose | Verbose output |
Judge a Trace
| Option | Description |
|---|---|
--yaml FILE | YAML for context-aware evaluation |
--output FILE | Output plan file |
--model MODEL | Judge model (default: gpt-4o-mini) |
Apply Improvements
| Option | Description |
|---|---|
--confirm / -c | Apply without confirmation |
--dry-run | Preview only |
--fix-ids IDS | Apply specific fixes |
--no-backup | Skip backup |
Complete Workflow
Evaluation Metrics
The judge evaluates each agent on 6 criteria:| Metric | Description |
|---|---|
| Task Achievement | Did the agent complete its goal? |
| Context Utilization | Was context effectively used? |
| Output Quality | Is output high quality? |
| Instruction Following | Did agent follow instructions? |
| Hallucination | 10=accurate, 1=fabricated |
| Error Handling | How well were errors handled? |
Fix Types
The judge generates actionable fixes:| Type | Description |
|---|---|
append_instruction | Add guidance to instructions |
add_expected_output | Specify output format |
modify_context_config | Adjust context settings |
suggestion | General improvement |
Example Output
Judge Report
Plan Preview
Best Practices
Save All Runs
Always use
--save to capture traces for analysisName Your Traces
Use
--name for easy identificationPreview First
Always
--dry-run before applyingIterate
Run → Judge → Apply → Repeat
Viewing Traces
Use the replay commands to inspect traces:Related
- Context Replay - Trace capture and viewing
- LLM as Judge - Evaluation details

