Persistence CLI
Command-line interface for database persistence management.Installation
Commands
Help
Doctor
Validate database connectivity.
Example:
Backend Auto-Detection
praisonai persistence doctor inspects each --*-url and picks the matching store client automatically — the same rules the live persistence path uses.
Detection delegates to the canonical resolver PraisonAIDB._detect_backend, so the doctor recognises the same schemes as the live path.
Recognised schemes:
The serverless PostgreSQL family (
.neon.tech, .cockroachlabs.cloud, .cockroachlabs.com, .xata.sh, .supabase.com) resolves to postgres when passed with a postgresql:// / postgres:// scheme. A Supabase host over http(s):// (.supabase.co / .supabase.com) resolves to the supabase REST backend instead.Backend detection was aligned with the live persistence path in PraisonAI PR #4524 (release ≥ the merge date, 2026-08-28). On older releases
libsql:// defaulted to sqlite, .supabase.co defaulted to sqlite, and Weaviate URLs defaulted to qdrant.Run
Run an agent with persistence.
Example:
Resume
Resume an existing session.
Example:
Environment Variables
Troubleshooting
Connection refused:- Check Docker containers are running
- Verify URL format and credentials
- Set
OPENAI_API_KEYenvironment variable

