How It Works
How to Debug Recipe Execution
How to Use Recipe Doctor
Review Diagnostics
The doctor command will show:
- Missing tools
- Invalid tool references
- Configuration issues
- Dependency problems
How to Debug Tool Resolution
When loading a template, PraisonAI now asks the fullToolResolver whether each referenced tool exists — not just the built-in TOOL_MAPPINGS. As of PR #2642, templates that reference tools registered via praisonai_tools, register_function, or entry-point plugins load without spurious “missing / needs install” warnings.
How to Debug with Python
Common Issues and Solutions
| Issue | Cause | Solution |
|---|---|---|
| Tool not found | Tool not available | Check praisonai tools list |
| Variable undefined | Missing variable | Pass with --var key=value |
| Recipe not found | Wrong path | Use full path |
| Permission denied | File access | Check file permissions |
Debug CLI Options
Best Practices
Validate first, then run verbose
Validate first, then run verbose
praisonai recipe validate catches structural errors cheaply; reach for --verbose only when a valid recipe still misbehaves at run time.Confirm tools resolve before blaming the recipe
Confirm tools resolve before blaming the recipe
praisonai tools list and praisonai tools resolve <name> show whether a referenced tool is actually available, which is the most common recipe failure.Reproduce failures with debug logging in Python
Reproduce failures with debug logging in Python
Set
logging.basicConfig(level=logging.DEBUG) and verbose=True on the agent to surface the exact step that fails.Related
Add Tools to Recipes
Fix tool resolution issues
Manage Recipes
Update and edit recipes

