nicobailon/pi-subagents: README-based editorial guide

nicobailon/pi-subagents describes itself in the README as "Pi extension for async subagent delegation with truncation, artifacts, and session sharing". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "pi-subagents", the README says: pi-subagents lets Pi delegate work to focused child agents. Use it for code review, scouting, implementation, parallel audits, saved workflows, background jobs, and anything else that benefits from a second or third set of model eyes.. That establishes the project's stated boundary, not a production test.

The README's "Clarify and launch UI" section gives a useful starting point for deciding whether the project fits: Enter runs in the foreground, or in the background if background is toggled on. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: contactsupervisor: the child contacts the parent/supervisor session that delegated the task. Use reason: "needdecision" for blocking decisions or clarification, reason: "interviewrequest" for structured input, and reason: "progressupdate". It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "Try this first". The source evidence includes: You do not need to create agents, write config, or learn slash commands. After installing, ask Pi for delegation in plain language:. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: pi install npm:pi-subagents When the README contains no runnable command, this article does not invent one. Open its "Installation" section and confirm system dependencies, default ports, and first-run initialization before using a public server.