See every ticket-loop workflow, its agents, and the teams running now.
From the plugin's README
.claude/ticket-loop.json manifest and run state folders
of the ticket-loop skill. Without them, the Workflows, Agents and runs views are empty.npmjs · Paseo 0.9+
paseo plugin add npm:paseo-crew-flows@0.1.0GitHub · Paseo 0.8 fallback
paseo plugin add maxwell-01/maxs-paseo-plugins --ref 18e65e93b7b075e50d620db65e149a5d56aa112e --path crew-flowsGit security status and fallback installation are pinned to commit 18e65e93b7b0.
From the plugin's README
paseo plugin install https://github.com/maxwell-01/maxs-paseo-plugins.git:crew-flows
Update with paseo plugin update crew-flows.
README
A Paseo plugin that shows your agent teams in one screen: the ticket-loop workflow each repo declares, the agent roles in it, and the runs and FirstMate crew working now. Requires Paseo 0.10.3 or newer.
Open it from Crew & Flows in the sidebar, or Open Crew & Flows in the Command Center.
Each ticket-loop run, from its state folder: every stage with its latest verdict and live agent, what the current agent last said, and the run log. Below that, the FirstMate first mate and its crew, each with the status line its last turn ended with. Open jumps to an agent; Send a note… posts a follow-up to it. The tab refreshes every 5 seconds.
Each repo's loop as a diagram: the stages in order, which agents persist and which start fresh, the review gates, the stages that always run, and each FAIL loop-back with its round limit.
Each stage role compared across the repos that run it: model, thinking level, the goal line of its brief, and whether it persists or gates. Pick a repo's stage to see how the loop runs it.
paseo plugin install https://github.com/maxwell-01/maxs-paseo-plugins.git:crew-flows
Update with paseo plugin update crew-flows.
The plugin reads the machine of the daemon it is installed on. Change its folders in Settings → Plugins → crew-flows → Crew & Flows. A change applies the next time a tab refreshes.
| Setting | Default | What it is |
|---|---|---|
| Repo folders | /workspace |
Comma-separated. Every git repo directly inside is checked for a loop. |
| Run state folder | /workspace/.ticket-loop |
Where the loop writes each run's *-state folder. |
| ticket-loop skill | ~/.claude/plugins/marketplaces/max-personal/claudeConfig/skills/ticket-loop |
Holds skill: briefs and the shared craft.md. |
origin/main has .claude/ticket-loop.json. The
plugin reads origin/main, not the working tree, so a stale checkout does not hide a loop. It
never fetches, so the view is as fresh as your last git fetch.origin/main. A skill: brief, and craft.md,
come from the ticket-loop skill folder.*-state folder in the run state folder. A run finds its agents by their
ticket-loop.run label, or by the agent map in its beacon.firstmate.role=first-mate, and its crew. A crewmate's state is the
<state>: <line> its last turn ended with.A manifest that does not parse, a brief that is missing, or a folder that cannot be read shows as a problem. The rest of the screen still shows.
.claude/ticket-loop.json manifest and run state folders
of the ticket-loop skill. Without them, the Workflows, Agents and runs views are empty.npm install
npm run typecheck
npm test
MIT. See LICENSE.
Scanned 21 Oct 2026, 14:40 UTC from maxwell-01/maxs-paseo-plugins/crew-flows.