@anh-chu/pi-subagents

A pi extension extension that brings smart Claude Code-style autonomous sub-agents to pi.

Packages

Package details

extension

Install @anh-chu/pi-subagents from npm and Pi will load the resources declared by the package manifest.

npm repo home report

$ pi install npm:@anh-chu/pi-subagents

Package: @anh-chu/pi-subagents
Version: 0.7.6
Published: May 8, 2026
Downloads: 300/mo · 32/wk
Author: anh-chu
License: MIT
Types: extension
Size: 674.2 KB
Dependencies: 4 dependencies · 0 peers

Pi manifest JSON

{
  "extensions": [
    "./src/index.ts"
  ],
  "video": "https://github.com/anh-chu/pi-subagents/raw/master/media/demo.mp4",
  "image": "https://github.com/anh-chu/pi-subagents/raw/master/media/screenshot.png"
}

Security note

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

README

@anh-chu/pi-subagents — DEPRECATED

Use @tintinweb/pi-subagents instead.

This fork is no longer maintained. Upstream has outpaced us — token tracking, persistent settings, scheduled subagents, proper context isolation, and active maintenance from a broader contributor base. We can't keep up.

What we've done

Our unique features have been submitted upstream as PRs:

Chain mode — sequential agent execution with {previous} placeholder (#53)
Dynamic routing guidelines — Agent tool description auto-generated from agent configs (#52)
Card grid widget — card-grid layout for /agents with /agents-view toggle (#54)

Once these land upstream (or are rejected with finality), there is zero reason to use this fork.

Migrating

# In your pi settings.json, replace:
#   "@anh-chu/pi-subagents"  →  "@tintinweb/pi-subagents"
npm uninstall -g @anh-chu/pi-subagents
npm install -g @tintinweb/pi-subagents

Your custom agents (.pi/agents/*.md) and settings continue to work. The parent-bridge tools (message_parent, ask_parent, reply_to_subagent) were never used in practice — if you relied on them, open an issue upstream.

Why

We aggregated four forks (tintinweb, yzlin, Evizero, elidickinson) into one. That was useful in March 2026 when each fork had a different piece of the puzzle. By May 2026, upstream absorbed most of the ecosystem's improvements and added its own. Maintaining a 71-commit fork that can't clean-merge upstream is self-defeating. We're shutting it down.