Plugins CLI - PraisonAI

Manage the plugins that extend your agents — list them, turn them on or off, reload them without restarting, and diagnose issues.

Quick Start

See what plugins exist

praisonai plugins list

Turn one on

praisonai plugins enable pii_guardrail

Load it into the running process

praisonai plugins reload

Commands

praisonai plugins <command> [OPTIONS]

Command	Description
`list`	List every discoverable plugin with its source
`add`	Install a plugin package and verify it registered
`info`	Show details for one plugin
`enable`	Enable a plugin (writes to the config the runtime reads)
`disable`	Disable a plugin and unload its tools
`reload`	Rediscover and rewire plugins without restarting
`doctor`	Diagnose plugin issues

List Plugins

praisonai plugins list shows the real, unified registry — every plugin the runtime can load, with its source.

praisonai plugins list

Output:

                         Plugins (3 available)
┏━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Name           ┃ Source                ┃ Status   ┃ Description           ┃
┡━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━┩
│ cli_backend…   │ entry_point:praiso…   │ enabled  │ Traces CLI backend…   │
│ pii_guardrail  │ single_file           │ disabled │ Redacts PII fields    │
│ logging        │ registered            │ enabled  │ Logs lifecycle events │
└────────────────┴───────────────────────┴──────────┴───────────────────────┘

Every row’s Source is one of three real values:

Source	Where it comes from
`entry_point:<dist>`	A pip package registering in the `praisonai.plugins` group
`registered`	A `Plugin` instance held by the `PluginManager`
`single_file`	A `.py` file discovered on disk in `.praisonai/plugins/` or `~/.praisonai/plugins/`

Show only enabled plugins:

praisonai plugins list --enabled

Output as JSON (each entry has name, version, description, source, enabled, hooks):

praisonai plugins list --json

Plugin Info

Show details for one plugin by name:

praisonai plugins info pii_guardrail

Output:

pii_guardrail
ID: pii_guardrail
Source: single_file
Status: disabled
Description: Redacts PII fields

Use a real plugin name from praisonai plugins list — the argument is a single plugin name, not a category.

Enable Plugin

Enable one plugin. This writes to the config file the runtime actually reads — no separate JSON file.

praisonai plugins enable pii_guardrail

Output prints the file it wrote to:

Plugin enabled: pii_guardrail (.praisonai/config.yaml)

enable takes exactly one plugin name. To enable several, run the command once per plugin.

Where enable/disable write

Both enable and disable persist to the same file the runtime reads — the existing config, or .praisonai/config.yaml if none exists yet. Search order for the write target:

.praisonai/config.toml  →  .praisonai/config.yaml     (project-local)
praisonai.toml          →  praisonai.yaml             (project root)
~/.praisonai/config.toml → ~/.praisonai/config.yaml   (user global)
(none found)            →  .praisonai/config.yaml     (default)

Writing a .toml config requires tomli_w. Without it the CLI fails fast with a remediation hint (Install tomli-w (pip install tomli-w), or convert the config to .praisonai/config.yaml.) rather than silently writing a .yaml sidecar the runtime would ignore.

The `enabled: true` edge case

If plugins.enabled is set to a bare true (all plugins enabled):

enable <name> is a no-op — it leaves “all enabled” intact.
disable <name> raises a ValueError with the remediation: set plugins.enabled to an explicit list of plugin names first, then disable individual plugins.

Disable Plugin

Disable one plugin:

praisonai plugins disable pii_guardrail

Output:

Plugin disabled: pii_guardrail (.praisonai/config.yaml)

disable also unloads a single-file plugin’s tools via unload_plugin(module_name) — not just its hooks. After disable, the plugin’s functions are gone from the registry for the rest of the run. Unload tracks only the tools that module contributed (via a pre-exec registry snapshot), so it never removes tools owned by another plugin or the core.

Reload Plugins

Pick up a newly-added or edited plugin without restarting the process.

praisonai plugins reload

reload unloads previously-loaded single-file plugins first (so an edited file is re-executed cleanly), then rediscovers everything and rewires enabled plugins into the runtime hook registry. Output:

Reloaded plugins: 2 single-file, 1 entry-point, 3 hook(s) wired

If no single-file plugins were loaded (0 single-file), it prints a hint:

No single-file plugins were loaded. Set PRAISONAI_ALLOW_PLUGIN_DISCOVERY=true
(and PRAISONAI_ALLOW_PROJECT_PLUGINS=true for project-local plugins) to load them.

After praisonai plugins add <pkg> installs a plugin, run praisonai plugins reload to pick it up in the current process without a restart.

Add Plugin

Install a plugin package and verify it registered.

praisonai plugins add <pkg> [--dry-run] [--upgrade|-U] [--global]

Full behaviour — installer selection, exit codes, and output shape — is documented on the plugins add page.

Doctor

praisonai plugins doctor diagnoses enabled plugins and reports three issue types — it does not verify third-party dependencies.

praisonai plugins doctor

Issue	Meaning
`blocked: set PRAISONAI_ALLOW_PROJECT_PLUGINS=true`	A `single_file` plugin is enabled but the project-plugin trust gate is closed
`no hooks wired`	A `registered` plugin exposes no hooks (it may still provide tools)
`not loaded (hooks import on enable)`	An `entry_point` plugin is present but not yet loaded — its hooks import when enabled

Output is a Rich table (Plugin / Status / Issues) with a summary:

Plugin Health Check

┏━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Plugin         ┃ Status     ┃ Issues                                        ┃
┡━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ pii_guardrail  │ ✗ Issues   │ blocked: set PRAISONAI_ALLOW_PROJECT_PLUGINS…  │
│ logging        │ ✓ OK       │ -                                             │
└────────────────┴────────────┴───────────────────────────────────────────────┘

Found 1 issue(s)

When everything is healthy it prints All N plugins healthy instead.

Security: Project-Plugin Trust Gate

A single-file plugin in ./.praisonai/plugins/*.py can hook every lifecycle event and intercept every tool call, so running one from a cloned repo is gated by default.

Default: closed. A cloned repo cannot run arbitrary project plugin code.
User-global plugins in ~/.praisonai/plugins/ remain trusted.
pip / entry-point plugins remain trusted.

Open the gate with an environment variable:

export PRAISONAI_ALLOW_PROJECT_PLUGINS=true

Or in .praisonai/config.yaml:

plugins:
  allow_project_plugins: true

The gate judges a plugin by where the file is located, not where a symlink points. A repository-controlled symlink at .praisonai/plugins/evil.py -> /tmp/evil.py still counts as project-local and stays gated.

See Plugins → Security: Project-Plugin Trust Gate for the full explanation and decision diagram.

Plugins

Write, load, and configure plugins

plugins add

Install a plugin package and verify it registered

Skills CLI

Manage agent skills

Config File

Turn plugins on from [plugins] in config

​Quick Start

​Commands

​List Plugins

​Plugin Info

​Enable Plugin

​Where enable/disable write

​The enabled: true edge case

​Disable Plugin

​Reload Plugins

​Add Plugin

​Doctor

​Security: Project-Plugin Trust Gate

​Related

Plugins

plugins add

Skills CLI

Config File

Quick Start

Commands

List Plugins

Plugin Info

Enable Plugin

Where enable/disable write

The `enabled: true` edge case

Disable Plugin

Reload Plugins

Add Plugin

Doctor

Security: Project-Plugin Trust Gate

Related