Personas Overview
Role-specific guidance for integrating PraisonAI recipes
Role-specific docs cover building apps, operating infrastructure, and authoring recipes.
from praisonaiagents import Agent
agent = Agent(
name="Role Guide",
instructions="Match the reader to app developer, platform, or author docs.",
)
agent.start("I am writing a new customer-support recipe.")The user picks a persona card to see responsibilities, checklists, and linked guides.
Quick Start
- Simple Usage
Ask the router agent which persona fits your role.
python from praisonaiagents import Agent agent = Agent(name="Role Guide", instructions="Match the reader to a persona guide.") agent.start("I am writing a new customer-support recipe.") - With Configuration
Give it your task and integration target for a sharper recommendation.
python from praisonaiagents import Agent agent = Agent( name="Role Guide", instructions="Recommend a persona and integration model from the described task.", ) agent.start("I deploy recipe infrastructure on Kubernetes for multiple tenants.")
How It Works
Choose Your Persona
Build applications that use recipes. Focus on SDK integration, error handling, and user experience.
Platform/DevOpsDeploy and operate recipe infrastructure. Focus on scaling, monitoring, security, and reliability.
Recipe AuthorCreate and maintain recipes. Focus on agent design, testing, and documentation.
Persona Collaboration
Quick Reference
By Task
| Task | Primary Persona | Secondary |
|---|---|---|
| Build app with recipes | App Developer | – |
| Deploy recipe server | Platform/DevOps | – |
| Create new recipe | Recipe Author | – |
| Debug recipe failures | App Developer | Recipe Author |
| Scale infrastructure | Platform/DevOps | – |
| Optimize performance | Platform/DevOps | App Developer |
| Add new AI capability | Recipe Author | App Developer |
By Integration Model
| Model | Primary Persona |
|---|---|
| Embedded SDK | App Developer |
| CLI Invocation | App Developer, DevOps |
| Local HTTP Sidecar | App Developer |
| Remote Managed Runner | Platform/DevOps |
| Event-Driven | Platform/DevOps |
| Plugin Mode | App Developer |
By Concern
| Concern | Primary Persona |
|---|---|
| Latency | App Developer |
| Reliability | Platform/DevOps |
| Security | Platform/DevOps |
| UX | App Developer |
| AI Quality | Recipe Author |
| Cost | Platform/DevOps |
Recommended Learning Path
App Developer
- Start with Embedded SDK
- Learn CLI Invocation for scripts
- Explore Use Cases for patterns
Platform/DevOps
- Start with Local HTTP Sidecar
- Progress to Remote Managed Runner
- Learn Event-Driven for scale
Recipe Author
- Understand all Integration Models
- Study Use Cases for inspiration
- Review Decision Guide for recommendations
Cross-Persona Communication
Effective recipe deployment requires collaboration:
| From | To | Key Handoffs |
|---|---|---|
| Recipe Author | App Developer | Recipe name, input/output schema, examples |
| Recipe Author | Platform/DevOps | Resource requirements, dependencies, SLAs |
| Platform/DevOps | App Developer | Endpoint URLs, API keys, rate limits |
| App Developer | Recipe Author | Bug reports, feature requests, usage patterns |
Best Practices
Read the persona that matches your task, not your title
A backend engineer authoring a recipe should follow the Recipe Author path for that work, even if they usually build apps.
Agree handoffs across personas early
Recipe Authors owe App Developers a clear input/output schema and owe Platform/DevOps the resource requirements. Settle these before integration starts.
Match the integration model to the persona
App Developers lean on Embedded SDK and Sidecar; Platform/DevOps own Remote Runner and Event-Driven. The Quick Reference tabs above map this out.
Next Steps
Choose your persona above to get role-specific guidance, or explore:
- Integration Models – Technical integration options
- Use Cases – Real-world implementation patterns
- Decision Guide – Choosing the right approach