Skip to main content
Run validation and verbose recipe commands when a template fails in production.
The user enables verbose mode, validates the recipe folder, and fixes configuration before re-running.

How It Works


How to Debug Recipe Execution

1

Enable Verbose Mode

2

Check Recipe Validation

3

View Recipe Info

4

Check Tool Resolution

How to Use Recipe Doctor

1

Run Doctor Command

2

Review Diagnostics

The doctor command will show:
  • Missing tools
  • Invalid tool references
  • Configuration issues
  • Dependency problems
3

Fix Issues

Based on doctor output, fix the identified issues in your recipe files.

How to Debug Tool Resolution

When loading a template, PraisonAI now asks the full ToolResolver 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.
1

List Available Tools

2

Resolve Specific Tool

How to Debug with Python

1

Enable Debug Logging

2

Test Agent Execution

Common Issues and Solutions

Debug CLI Options

Best Practices

praisonai recipe validate catches structural errors cheaply; reach for --verbose only when a valid recipe still misbehaves at run time.
praisonai tools list and praisonai tools resolve <name> show whether a referenced tool is actually available, which is the most common recipe failure.
Set logging.basicConfig(level=logging.DEBUG) and verbose=True on the agent to surface the exact step that fails.

Add Tools to Recipes

Fix tool resolution issues

Manage Recipes

Update and edit recipes