Quick Start
1
Use the CLI flag
2
Or set the env var
How It Works
The CLI flag setsPRAISONAI_NO_PLUGINS only for the current run, then restores the prior value on return.
The @scopes_no_plugins decorator wraps each command, so suppression is restored on return and never leaks into a later in-process call. The run emits one log line: “Running without external plugins (—pure / PRAISONAI_NO_PLUGINS)”.
Configuration
Three surfaces suppress plugins. A constructordisabled=True wins; otherwise the env var decides.
The env var accepts
true, 1, or yes (case-insensitive). Pure Mode never mutates .praisonai/config.yaml or any persisted enable/disable state.
Python parity forces suppression regardless of the env var:
Common Patterns
Reproduce a CI failure without whatever plugin your machine has enabled:Best Practices
Use --pure for bug reports
Use --pure for bug reports
Attach the plugin-free reproduction alongside the normal one — it makes obvious whether a plugin is involved.
Prefer the CLI flag over the env var for one-offs
Prefer the CLI flag over the env var for one-offs
The flag’s scope is guaranteed — it always restores the prior value on return.
Keep PRAISONAI_NO_PLUGINS out of your shell rc
Keep PRAISONAI_NO_PLUGINS out of your shell rc
A persistent export defeats the one-shot contract and hides real plugin behaviour from every command.
Check plugins doctor to see which mode you're in
Check plugins doctor to see which mode you're in
praisonai plugins doctor tells you whether plugins are suppressed for the current process.Related
Plugins CLI
List, enable, disable, and diagnose plugins
Plugins
Write, load, and configure plugins

