Skip to main content
The default framework changed from crewai to praisonai when running YAML files without specifying an explicit framework.
The user runs a YAML file without framework:; agents execute on the praisonai adapter by default.

Quick Start

1

Before (v0.x)

Running praisonai agents.yaml would fail with error:
2

After (v1.0.0+)

Running praisonai agents.yaml works out of the box using the praisonai framework:

Agent-Centric Example

Equivalent CLI command:
Both produce the same result with no --framework flag required.

Framework Precedence

PraisonAI resolves the framework in this order: The set of valid framework names is discovered dynamically from the adapter registry — see Framework Adapter Plugins.

How to Keep CrewAI as Default

If you want to continue using CrewAI as your default framework, you have two options:

Option 1: YAML Configuration

Option 2: CLI Flag


User Interaction Flow


Best Practices

Add framework: crewai (or your preferred adapter) to shared YAML so every teammate gets the same runtime without passing CLI flags.
Keep YAML portable and pass --framework crewai only when experimenting with a different adapter.
Run praisonai --list-frameworks in CI to confirm the expected adapter is installed before kicking off agent workflows.
During upgrades, set framework: praisonai explicitly in YAML so behaviour stays predictable even if defaults change again.

CrewAI Framework

CrewAI framework integration guide

PraisonAI Agents

PraisonAI native agents framework