@cr1ms0n/pi-subagent

Community fork of Luke Parke's pi-subagent with Jev model/tool routing and verified Pi child capabilities

Packages

Package details

extensionskill

Install @cr1ms0n/pi-subagent from npm and Pi will load the resources declared by the package manifest.

npm repo home report

$ pi install npm:@cr1ms0n/pi-subagent

Package: @cr1ms0n/pi-subagent
Version: 0.11.6
Published: Sep 30, 2026
Downloads: 2,522/mo · 831/wk
Author: cr1ms0n
License: MIT
Types: extension, skill
Size: 850.8 KB
Dependencies: 0 dependencies · 4 peers

Pi manifest JSON

{
  "skills": [
    "./skills"
  ],
  "extensions": [
    "./extensions/subagent.ts"
  ]
}

Security note

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

README

Pi Smart Subagents

English | 简体中文

Run isolated child agents in Pi, with Jev selecting a model and tools for each task.

An independent community fork of Luke Parke's @parke.dev/pi-subagent from LukasParke/pi-extensions. It retains the upstream engine's named agents, parallel and background tasks, worktrees and usage accounting, and adds Jev routing with child capability verification.

Installation

pi install npm:@cr1ms0n/pi-subagent

Usage

Before your first task, configure your TypeSafe API key and candidate models in ~/.pi/subagent.json. See the configuration example.

Then ask Pi, for example:

Use a read-only subagent to review this project's directory structure and summarize the main modules.

Jev chooses the model and tools. The optional jevRouting.baseUrl setting can point to a trusted complete https:// SystemOne request URL; when omitted, the official https://api.typesafe.ai/v1/systemone endpoint remains the exact default. The value is strictly validated, and changing it changes the destination receiving the minimal routing disclosure. See the configuration reference for the full contract.

Optional infrastructure tools can be preserved outside Jev's ordinary tool choices with the top-level passthroughTools string array in the same config file (default []). Use exact registered names; there are no built-in presets. This is your explicit approval of trusted non-project-writing infrastructure, including in read-only profiles—not automatic proof of a custom tool's effects. Known write/unsafe builtin and nested-dispatch tools cannot use this exception. Startup requires every listed definition to be registered, while letting its host control whether it is active. See passthrough tools.

Open /subagents to inspect tasks and /subagent-cost to view usage.

See the usage reference for parallel tasks, background work, worktrees and structured results, or the TUI guide for keyboard controls.

License

Thanks to Linux.do.