Personas & categories

Reusable agent identities injected as system prompts, and the optional folders that organize both libraries.

A persona is a reusable identity for a step's agent — a name, an icon and color, and above all a system prompt. Bind one to a step and the transcript shows who is working; the same reviewer identity, spec writer, or security auditor serves every workflow in the project.

Defining one

Personas live in the Personas library — editor, dashboard, or phone — one YAML per persona in your project's host-stored config:

# persona/security-reviewer.yaml
id: security-reviewer
name: Security Reviewer
icon: shield
color: red
description: Reviews changes for security implications.
prompt: |
  You are a security reviewer. Focus on authentication, authorization,
  injection, and secrets handling. Prefer the smallest safe change.

name and prompt are required; icon defaults to person, color to gray. The editor includes an AI "improve prompt" helper, and the setup wizard offers a starter roster — Engineer, Spec Writer, QA Engineer, Security Reviewer, Technical Writer, and friends — you can adopt and edit.

Using one

- type: prompt
  prompt: Review the diff for security issues and fix what you find.
  persona: security-reviewer

The persona's prompt is injected as the step's system prompt. The full layering, outermost first: project system prompt → workflow basePrompt → the step's persona. A persona is deliberately not a model choice — pick models per step or workflow in Agents & models.

Categories

Both libraries — workflows and personas — can be organized into per-library categories. They're optional and invisible until you create one: no headers, no "Uncategorized" bucket, nothing to configure in a fresh project.

• Create / rename / delete from the library's header (the folder, pencil, and trash buttons). Deleting a category leaves its members in place, just unfiled.
• Filing is drag-and-drop — drop a row on a group header to file it, drag past the last group to unfile. On the phone, use the row's "Move to category…" menu instead.
• Pickers follow along: anywhere you choose a workflow or persona, categories render as submenus, with unfiled items last.
• Searching flattens the list (a category's name matches all its members); each item belongs to at most one category.