pi-chef-subagents

Optional pi-chef add-on: shows the chef's cooks as external jobs in the pi-subagents FleetView.

Packages

Package details

extension

Install pi-chef-subagents from npm and Pi will load the resources declared by the package manifest.

$ pi install npm:pi-chef-subagents
Package
pi-chef-subagents
Version
0.2.1
Published
Oct 12, 2026
Downloads
408/mo · 18/wk
Author
b_pauli
License
MIT
Types
extension
Size
13.8 KB
Dependencies
0 dependencies · 2 peers
Pi manifest JSON
{
  "extensions": [
    "./index.ts"
  ]
}

Security note

Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.

README

pi-chef-subagents

An optional add-on for pi-chef. It shows the chef's cooks in the FleetView of pi-subagents, next to the subagents of the same Pi session. Each open task is one external job, labeled <task id> <title>:

Task FleetView state Current action Preview
queued queued queued
cooking running the cook's activity, for example bash: npm test
idle, done completed done: <summary> the summary
idle, failed failed failed: <reason> the reason
idle, needs decision or blocked stopped needs decision: <question> or blocked: <reason> the question or reason
idle, stopped stopped stopped

The job also names the transcript path of the current or last run. FleetView jobs from another extension are display-only: steer, answer, and stop cooks through the chef. A closed task leaves FleetView, and so do all cooks when chef mode turns off.

Install

Install pi-chef and pi-subagents first. Then install this add-on:

pi install npm:pi-chef-subagents

To use the add-on from main, install its directory as a local package, because Pi git sources take no subdirectory. When you installed pi-chef from git, the checkout is under your Pi agent directory, for example ~/.pi/agent/git/github.com/bpauli/pi-chef/addons/subagents.

How it works

The add-on reads the cooks snapshot that pi-chef emits on pi.events (pi-chef:cooks:v1, see docs/design.md, "Integration events"), in owner and read-only chef sessions. It finds pi-subagents in <project>/.pi/npm/node_modules or <Pi agent dir>/npm/node_modules, and calls registerExternalRun, updateExternalRun, and unregisterExternalRun from pi-subagents/external-runs. Without pi-subagents it does nothing and says so once.