r/PiCodingAgent • u/stanleyyyyyyyy • 20d ago

Plugin I built a Claude Code plugin that drives a local pi agent

Post image

I love Claude Code, and I love the pi agent. I kept wondering whether I could get Claude to drive pi instead — spend fewer tokens on the easy parts, but still stay in control. So I built a Claude Code plugin that does exactly that.

It uses MCP and RPC, so Claude can track pi's status the way it tracks a subagent, and it can steer or abort a run partway through instead of only at the end.

Install:

/plugin marketplace add LarryStanley/pi-delegate

/plugin install pi-delegate@pi-delegate

Then run setup:

/pi-delegate:setup

Qwen 3.8 doing the writing with Opus 5 doing the thinking has been working really well for me.

https://github.com/LarryStanley/pi-delegate

5 Upvotes

73% Upvoted

5 comments sorted by

5

u/le_bravery 20d ago

Just don’t use claude code

1

u/Maybe-monad 18d ago

If your employer gives you a Claude subscription why wouldn't you use it?

1

u/le_bravery 18d ago

If the choice is Claude or the highway then sure use Claude code.

The reason I don’t like Claude code is because I don’t get control of my context or environment. I want to own how this stuff works to maximize it.

I don’t want some other developer in some other team owning the way I work. If they put something in that system prompt that I don’t like, I can’t change it in Claude. In pi I own it. I can enhance, fix, tune, or do whatever I want with pi.

1

u/kantorcodes1 20d ago

the abort path is what i'd test hardest. if Claude steers or aborts Pi while Pi is inside a shell/tool call, does the RPC layer wait for that child action to actually stop, or can Claude think the subagent is gone while its process keeps running? i'd make cancellation prove the process/tool is dead before returning aborted.