alexei-led

Pi Subagents Bridge — Development skill for Claude Code

Development community

Protocol adapter that lets @tintinweb/pi-tasks TaskExecute spawn nicobailon/pi-subagents.

How to install Pi Subagents Bridge

This entry records only its repository, not the path inside it, so there is no exact command to give. Open alexei-led/pi-subagents-bridge and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Pi Subagents Bridge does

Protocol adapter that lets @tintinweb/pi-tasks TaskExecute spawn nicobailon/pi-subagents.

Alternatives in Development

Happy Coder — by GrocerPublishAgent - Spawn and control multiple Claude Codes in parallel from your phone or desktop 15.7k ★
Call Me — Minimal plugin that lets Claude Code call you on the phone 2.5k ★
Hermes Paperclip Adapter — Paperclip adapter for Hermes Agent — run Hermes as a managed employee in a Paperclip company 1.8k ★

README

pi-subagents-bridge

[![npm version](https://img.shields.io/npm/v/%40alexeiled%2Fpi-subagents-bridge?style=flat-square&logo=npm&logoColor=white)](https://www.npmjs.com/package/@alexeiled/pi-subagents-bridge) [![CI](https://img.shields.io/github/actions/workflow/status/alexei-led/pi-subagents-bridge/ci.yml?branch=main&style=flat-square&label=ci)](https://github.com/alexei-led/pi-subagents-bridge/actions/workflows/ci.yml?query=branch%3Amain) [![node](https://img.shields.io/badge/node-%3E%3D22.19.0-5fa04e?style=flat-square&logo=node.js&logoColor=white)](https://nodejs.org/) [![license](https://img.shields.io/badge/license-MIT-blue?style=flat-square)](./LICENSE)

`pi-subagents-bridge` is a protocol adapter between two Pi extensions:

It makes `TaskExecute` work with `pi-subagents` by translating the `pi-tasks` subagent RPC into the RPC and completion events that `pi-subagents` exposes. It also exposes a separate, generic plan-exec RPC for direct execution clients.

What it does

`@tintinweb/pi-tasks` expects a v2 subagent protocol. `pi-subagents` exposes a v1 RPC plus async completion events. This bridge sits between them and handles the mismatch.

Specifically, it:

answers the pi-tasks v2 ping handshake
forwards spawn and stop requests to pi-subagents
translates pi-subagents completion events back into pi-tasks task updates
falls back to polling pi-subagents run status if an async completion event is missed
keeps the generic plan-exec RPC separate from all pi-tasks channels

Request and completion flow

sequenceDiagram
  autonumber
  participant Tasks as @tintinweb/pi-tasks
  participant Bridge as pi-subagents-bridge
  participant Subs as pi-subagents

  Tasks->>Bridge: ping (v2)
  Bridge-->>Tasks: version 2

  Tasks->>Bridge: spawn(type, prompt, options)
  Bridge->>Subs: spawn(work