Using Personas
Learn how to run persona tasks effectively, manage approvals, track progress, and collect deliverables.
Running a Persona Task
1. Select a Persona
Browse the persona gallery and choose one that matches your task:
2. Fill Structured Inputs
Complete the required fields:
Each persona has specific inputs tailored to its task. Fields may include:
- Text inputs for names, descriptions
- Selections for options and preferences
- Tags for topics or keywords
- File uploads for reference materials
- URLs for external resources
3. Configure Execution
Set limits for the task:
| Setting | Description | Recommendation |
|---|---|---|
| Max Duration | Maximum hours to run | Start with persona's estimate |
| Max Cost | Maximum credits to spend | 2-3x estimated cost |
| Autonomy Level | Approval requirements | approve_high_risk for new personas |
4. Connect Integrations
If the persona requires external tools, connect them:
Required connections must be set up before running. Optional connections enhance capabilities but aren't mandatory.
5. Launch
Click Start Task to begin execution.
Monitoring Progress
Progress Dashboard
Track your persona task in real-time:
The dashboard shows:
- Current step — Which SOP step is active
- Progress bar — Visual completion percentage
- Cost tracker — Credits consumed so far
- Duration — Time elapsed
- Activity log — Detailed actions taken
SOP Progress
Each SOP step has a status:
| Status | Description |
|---|---|
| Pending | Not yet started |
| In Progress | Currently executing |
| Completed | Successfully finished |
| Skipped | Bypassed (not applicable) |
Step Progress:
[x] 1. Review project requirements
[x] 2. Analyze code repository
[>] 3. Identify API endpoints <- Current step
[ ] 4. Document schemas
[ ] 5. Write authentication guide
[ ] 6. Create code examples
[ ] 7. Generate summary
[ ] 8. Final review
Activity Log
Real-time log of persona actions:
10:32:15 - Started task: Q4 Competitive Analysis
10:32:18 - Step 1: Reviewing project requirements
10:32:45 - Searched web for "Acme Corp company info"
10:33:12 - Found 15 relevant results
10:33:30 - Step 2: Analyzing public information
10:34:15 - Scraped website: acmecorp.com
10:35:02 - Extracted pricing information
10:35:30 - [APPROVAL NEEDED] Request to access LinkedIn data
Real-Time Messages
View the conversation between you and the persona:
Persona: I've completed the initial research phase. I found that Acme Corp
recently launched three new products. Should I focus on all three,
or would you like me to prioritize specific ones?
You: Focus on their enterprise product line, specifically the API offering.
Persona: Understood. I'll focus the competitive analysis on their enterprise
API products. Moving to the detailed feature comparison...
Approval Workflows
How Approvals Work
When autonomyLevel is set to approve_high_risk or approve_all, the persona pauses for certain actions:
- Persona identifies an action requiring approval
- Task pauses with status
waiting_approval - You receive a notification (email, Slack, etc.)
- You review and approve or reject
- Persona continues or adjusts based on your decision
Approval Requests
Approval requests include:
{
action: "github:create_issue",
description: "Create GitHub issue for documentation gaps",
parameters: {
repository: "acme/api-docs",
title: "Missing endpoint documentation",
body: "The following endpoints need documentation..."
},
risk: "medium",
reasoning: "This will create a visible issue in your repository"
}
Responding to Approvals
You have three options:
| Action | Description |
|---|---|
| Approve | Allow the action to proceed |
| Reject | Deny the action, persona will find alternative |
| Modify | Change parameters before approving |
Notification Channels
Configure where you receive approval requests:
{
notificationConfig: {
onApprovalNeeded: true,
onCompletion: true,
slackChannelId: "C12345678" // Optional Slack notifications
}
}
Completion
Task Status
Tasks complete with one of these statuses:
| Status | Description |
|---|---|
completed | Successfully finished with all deliverables |
max_duration | Hit time limit |
max_cost | Hit credit limit |
cancelled | Manually cancelled |
failed | Encountered unrecoverable error |
user_completed | User marked as done early |
Deliverables
When a task completes, collect your deliverables:
Each deliverable includes:
- Preview — View content inline
- Download — Save to your device
- Copy — Copy content to clipboard
- Send — Export to connected services
Deliverable Types
| Type | Format | Actions |
|---|---|---|
markdown | .md | Preview, Download, Copy |
csv | .csv | Preview, Download |
json | .json | Preview, Download, Copy |
pdf | Preview, Download | |
code | Various | Preview, Download, Copy |
image | .png/.jpg | Preview, Download |
html | .html | Preview, Download |
Cost Tracking
Credits
Persona tasks consume credits based on:
- LLM tokens (input and output)
- Tool calls (web search, integrations)
- File processing (documents, images)
Cost Breakdown
Task: Q4 Competitive Analysis
Duration: 45 minutes
Total Cost: 67 credits
Breakdown:
- LLM (Claude Sonnet): 42 credits
- Input: 125,000 tokens
- Output: 18,000 tokens
- Web Search: 12 credits (8 searches)
- Website Scraping: 8 credits (4 pages)
- Document Generation: 5 credits
Cost Controls
Prevent runaway costs with limits:
{
maxCostCredits: 100, // Hard cap
warningThreshold: 80, // Alert at 80%
pauseOnWarning: true // Pause for confirmation
}
Advanced Usage
Providing Additional Context
Beyond structured inputs, you can provide:
Knowledge Bases: Link relevant knowledge bases for the persona to reference:
{
additionalContext: {
knowledgeBases: ["kb_company_docs", "kb_competitors"];
}
}
Files: Upload reference documents:
{
additionalContext: {
files: [
{ name: "brand_guidelines.pdf", url: "..." },
{ name: "previous_analysis.md", url: "..." }
];
}
}
URLs: Provide web pages for context:
{
additionalContext: {
urls: ["https://competitor.com/pricing", "https://docs.competitor.com/api"];
}
}
Interacting During Execution
For personas with approve_high_risk or approve_all, you can:
- Provide guidance — Answer questions and clarify requirements
- Redirect focus — Adjust priorities mid-task
- Skip steps — Mark steps as not needed
- Add information — Provide additional context as needed
Early Completion
If you're satisfied with partial results:
- Click Mark as Complete
- Confirm you want to stop execution
- Deliverables generated so far are saved
This is useful when:
- You have what you need
- The task is taking longer than expected
- You want to iterate on partial results
Resuming Tasks
If a task is paused (waiting for approval or input):
- Go to Personas > My Tasks
- Find the paused task
- Provide the required input or approval
- Task resumes automatically
Best Practices
Start with Estimates
Use the persona's estimated duration and cost as a baseline, then adjust based on your specific task complexity.
Clear Inputs
Provide detailed, specific inputs:
Good: "Analyze Acme Corp's enterprise API pricing vs our $99/month plan,
focusing on feature parity and value proposition for mid-market companies"
Poor: "Compare competitors"
Iterative Approach
For complex tasks:
- Start with a shorter duration limit
- Review partial results
- Run again with refinements if needed
Monitor Actively
For important tasks:
- Watch the progress dashboard
- Respond to questions promptly
- Provide guidance when asked
Review Deliverables
Always review generated content before using:
- Check factual accuracy
- Verify calculations
- Ensure brand/style alignment
Troubleshooting
Task Stuck
If a task isn't progressing:
- Check for pending approvals
- Verify connected services are working
- Check if cost/duration limits are reached
- Review activity log for errors
Poor Quality Results
If deliverables aren't meeting expectations:
- Provide more specific inputs
- Add additional context (files, URLs)
- Use
approve_allto guide each step - Try a different persona for the task
Connection Errors
If integrations fail:
- Verify connections in Settings
- Re-authenticate if needed
- Check required permissions/scopes
- Test connection independently