praisonai dashboard --aiui, and interacts with the agent in the browser.
Quick Start
1
Install
2
Run integrated mode
Pattern B — In-process host
PraisonAISessionDataStore, PraisonAIProvider, and L1 bridges before create_app().
Pattern C — Gateway + static SPA
AIUIGateway.start() from praisonaiui.integration (calls the same bootstrap).
Legacy rollback
SetPRAISONAI_HOST_LEGACY=1 to skip provider wiring and use callback-only @aiui.reply handlers.
Backend injection
The wrapper callspraisonaiui.backends.set_backend() for hooks, workflows, usage, and approvals. Standalone aiui uses SDK defaults when no backend is injected.
See also: backend-integration in the praisonaiui repo.
Best Practices
Use Pattern B for in-process hosting
Use Pattern B for in-process hosting
Pattern B (in-process host) is simpler to deploy and works well for most use cases.
Use Pattern C for microservices
Use Pattern C for microservices
Pattern C (Gateway + static SPA) scales better and enables independent UI and backend deployments.
Configure allowed origins
Configure allowed origins
Always configure
allowed_origins when deploying to non-localhost to prevent unauthorized access.Use the onboarding wizard
Use the onboarding wizard
Run
praisonai onboard for guided setup — it handles credentials, ports, and daemon configuration.Related
PraisonAIUI
Frontend UI for PraisonAI agents
Gateway
Gateway configuration and setup

