Personas Overview

Role-specific guidance for integrating PraisonAI recipes

Next

Role-specific docs cover building apps, operating infrastructure, and authoring recipes.

python
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.

Diagram

Personas

📋 Your Role

🧭 Match Guide

✅ Workflow

Quick Start

  1. 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.")
  2. 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

Diagram
PersonaAgentUserPersonaAgentUserDescribe your role and taskMatch to a persona guideResponsibilities + linked docsRecommended path

Choose Your Persona

Persona Collaboration

Diagram

End Users

Integration

Deployment

Distribution

Recipe Creation

creates

deploys

integrates

Recipe Author

Recipe

Recipe Registry

Platform/DevOps

Infrastructure

App Developer

Application

End Users

Quick Reference

By Task

TaskPrimary PersonaSecondary
Build app with recipesApp Developer–
Deploy recipe serverPlatform/DevOps–
Create new recipeRecipe Author–
Debug recipe failuresApp DeveloperRecipe Author
Scale infrastructurePlatform/DevOps–
Optimize performancePlatform/DevOpsApp Developer
Add new AI capabilityRecipe AuthorApp Developer

By Integration Model

ModelPrimary Persona
Embedded SDKApp Developer
CLI InvocationApp Developer, DevOps
Local HTTP SidecarApp Developer
Remote Managed RunnerPlatform/DevOps
Event-DrivenPlatform/DevOps
Plugin ModeApp Developer

By Concern

ConcernPrimary Persona
LatencyApp Developer
ReliabilityPlatform/DevOps
SecurityPlatform/DevOps
UXApp Developer
AI QualityRecipe Author
CostPlatform/DevOps

Recommended Learning Path

App Developer

  1. Start with Embedded SDK
  2. Learn CLI Invocation for scripts
  3. Explore Use Cases for patterns

Platform/DevOps

  1. Start with Local HTTP Sidecar
  2. Progress to Remote Managed Runner
  3. Learn Event-Driven for scale

Recipe Author

  1. Understand all Integration Models
  2. Study Use Cases for inspiration
  3. Review Decision Guide for recommendations

Cross-Persona Communication

Effective recipe deployment requires collaboration:

FromToKey Handoffs
Recipe AuthorApp DeveloperRecipe name, input/output schema, examples
Recipe AuthorPlatform/DevOpsResource requirements, dependencies, SLAs
Platform/DevOpsApp DeveloperEndpoint URLs, API keys, rate limits
App DeveloperRecipe AuthorBug 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: