$ cat ~/map/pi-flows.md

pi-flows

Delegate work to isolated, budgeted pi sub-agents — recon, review, decomposition — with cost caps, OpenInference tracing, and contract validation.

extensions✓ Oct 16

Facts

repository: github.com/Thulr/pi-flows ↗
GitHub Stars: ★ 2
Forks: 0
license: MIT
npm / mo: —
last push: Sep 26, 2026

install

pi install npm:pi-flows

## TL;DR

pi extension that adds a flow tool for delegating work to separate, budgeted pi subprocesses — nine bundled agents and fifteen delegation modes cover scouting, parallel investigation, gated implementation, and large-task decomposition.

## Key points

$The flow tool runs separate, disposable pi subprocesses and returns compact findings, keeping the parent session focused on the decision instead of every file the children opened.
$Nine bundled agents ship in agents/ (recon, strategist, overwatch, operator, analyst, redteam, controller, commander, debrief) plus three workflow presets in presets/ (scout, map-codebase, code-review).
$Fifteen delegation modes behind one interface, from single/parallel/chain through evaluate, vote, route, orchestrate, graph, loop, search, workflow, worktree, debate, dossier, and monitor.
$Prerequisites: Node.js >=24, npm >=11, and the pi CLI >=0.82.0 on PATH; verify the install with /flows version and flow list showing all nine agents.
$Budgets and tracing compose with any mode: maxCostUsd, maxTokens, and maxGeneratedTokens ceilings, OpenInference-shaped JSONL traces, and /flows report, with every ceiling disclosed before work starts.
$Custom agents and presets need no code — one markdown file each, user-scoped or project-scoped; project files are trust-gated and shadowing shows visible diagnostics.
$Safety model: read-only agents (recon, analyst) ship without a shell, bash-ro gives read-only shell access enforced inside the child, returned content is redacted by default, and handoffs between children are scanned for injected instructions.

## FAQ

Q How do I verify the extension is installed correctly?

Install with pi install npm:pi-flows, reload pi with /reload, then run /flows version or flow list — the list output must show all nine bundled agents from recon to debrief.

Q Does it work without provider credentials?

The no-model calls still work: /flows help, /flows status, and flow calls with list:true or showConfig:true answer without spawning a child or contacting a model.

Q Are project-local agents safe to run?

They are repo-controlled prompts, so interactive sessions ask before using them and headless runs fail closed — review the files, then pass confirmProjectAgents:false to open them.

pi-flows

## TL;DR

## Key points

## FAQ

## References

## Related entries

## Guides