Paseo PlaybooksMulti-step agent playbooks for Paseo
One Paseo agent, the Playbook Manager, runs a playbook. Each step runs as one of its subagents in the same worktree, and the run stops at human gates that you approve in Paseo.
⌄
Pull request.paseo/playbooks/pr.yaml
▷ Start⌄
Definition7f3k2 · running⌄
▷ Start request, base_branch
✓ InvestigateInvestigator · ro
✓ ImplementImplementer · #1 #2
◌ ReviewReviewer · ro
✓ Local_qaLocal QA · ro
○ BabysitPR Babysitter · ro
ready
⚑ End pr_url, pr_number
changes_requested · 1/3
Playbooks are YAML files in your repository. Steps declare what they needs, so steps that are ready together run in parallel. Loops are explicit goto steps back with a limit. Inputs and outputs are typed and matched by name.
The plugin owns the rules: it validates playbooks, refuses any step or transition a playbook does not allow, keeps run state on the daemon so runs survive a restart, and wakes the manager when a step finishes. The manager makes the judgment calls: it briefs each step, reads its result and chooses the outcome.
Getting startedInstall the plugin, write a first playbook, press Start.
Playbook referenceFolder layout, every field, variables, loops, gates and validation rules.
ExamplesA pull-request playbook and a docs check, with their roles, ready to copy.
How it worksThe manager, the tools, run state, wake-ups and the Playbooks panel.