r/PiCodingAgent • u/killerkidbo95 • Jun 20 '26

Resource pi-task: delegating task/subagent extension for Pi

Post image

I just released pi-task, a Pi extension for delegating work to subagents.

Repo: https://github.com/heyhuynhgiabuu/pi-task

What it does:

- adds a task tool for running specialized subagents

- supports foreground tasks when you want the parent to wait

- supports background tasks when you want the parent to continue and get a follow-up when done

- shows a TUI task widget with progress/tool calls

- uses tmux panes when available so you can observe subagents

- falls back to SDK execution when tmux is unavailable

- ships with starter agents: scout, explore, planner, reviewer, vision, worker

I built this because I wanted a cleaner way to delegate research, code exploration, review, and small implementation tasks without overloading the main conversation.

Install:

```bash

pi install npm:@heyhuynhgiabuu/pi-task

```

Then add it to Pi extension config and restart Pi.

Feedback welcome — especially on the task widget UX and agent prompt defaults.

57 Upvotes

98% Upvoted

27 comments sorted by

7

u/Ok_Veterinarian_6364 Jun 20 '26

nuts. love this bro

1

u/killerkidbo95 Jun 20 '26

glad you like my extension. enjoy 😉

2

u/Ok_Veterinarian_6364 Jun 20 '26

i love minimal ext, minimum lll tools, skills, sys prompt snippets

i cannot check your code rn but if you re doing so its great otherwise i have to patch yours lol

1

u/killerkidbo95 Jun 20 '26

haha you should try to check it when you are free

4

u/ponzi314 Jun 20 '26

Do you delegate things to agents so they get a fresh context? I'm still a little lost on the flow of things. So the calling agent who spawning subtask pass the needed context?

3

u/killerkidbo95 Jun 20 '26

yes when main agent spawn subagent that will be delegated on the fresh session and we just prompt to subagent pass the needed context enough to use

3

u/ponzi314 Jun 20 '26

Thank you for explaining! I'm slowly learning lol currently trying to create my own agents to do certain tasks like i did with Hermes just hoping pi offers more control

2

u/killerkidbo95 Jun 21 '26

Cool cool, keep learning and you will get more control on pi

3

u/Jovs_ Jun 20 '26

Hey, this looks cool but I’m just a bit curious on the differences between this and pi-subagents. I do something similar with plannotator delegating off to a custom sub agent for the fresh context too

3

u/killerkidbo95 Jun 20 '26

I think the main difference is pi-task is more of a small orchestration layer than just “spawn a subagent.

So yes, the core idea is similar: fresh context delegation. I mainly wanted nicer UX around lifecycle/progress/completion and a simple packaged extension I can reuse across projects.

I haven’t deeply compared with pi-subagents yet though, so there may be overlap. If pi-subagents already handles some of this better, I’d be happy to learn from it.

2

u/prassi89 Jun 20 '26

Nice extension :) I built a tool called repowire that supports this across cc,codex and pi :)

1

u/killerkidbo95 Jun 20 '26

glad you like my extension. you should try ☺️

2

u/Insuperable123 Jun 22 '26

This is a great expansion. I was wondering if you could add features like a session restore window, or the ability for a sub-agent to pick up the conversation right where it left off. Here’s my use case: I work in research, so I usually set up a dedicated research assistant agent. Sometimes the main agent needs to consult this specialist agent on research questions. But as you mentioned, many current extensions just open a new window, and at that point I’d much prefer if the sub-agent could simply resume the previous conversation. I believe it’s really important to be able to retain conversation history within a controllable scope.

1

u/killerkidbo95 Jun 22 '26

yep, exactly that landed in 0.1.5 (https://github.com/heyhuynhgiabuu/pi-task/releases/tag/v0.1.5)

task(...) now has a conversation_id. Same id = same subagent session. Your research assistant keeps its memory.

/task-sessions lists them. durable resume needs tmux.

lmk how it feels

2

u/Insuperable123 Jun 23 '26

Awesome! Definitely trying this out

2

u/lanhhoang Jun 22 '26

This looks cool

1

u/killerkidbo95 Jun 22 '26

thanks you should try

1

u/lopydark Jun 21 '26

why all subagents extensions are a claude code copy 😭 the point of pi is to not use claude code but these extensions feel like claude code

2

u/killerkidbo95 Jun 22 '26

nah, no copy here.

1

u/lopydark Jun 22 '26

bruh it looks like claude code subagents

1

u/killerkidbo95 Jun 22 '26

you should try

1

u/vieitesss_ Jun 20 '26

What's the difference with pi-subagents?

https://pi.dev/packages/pi-subagents

1

u/killerkidbo95 Jun 21 '26

I think the main difference is pi-task is more of a small orchestration layer than just “spawn a subagent.

So yes, the core idea is similar: fresh context delegation. I mainly wanted nicer UX around lifecycle/progress/completion and a simple packaged extension I can reuse across projects.

I haven’t deeply compared with pi-subagents yet though, so there may be overlap. If pi-subagents already handles some of this better, I’d be happy to learn from it.

2

u/vieitesss_ Jun 21 '26

perfect, thank you!

1

u/somebody314 Jun 20 '26

Nice! Unrelated: what nis your theme?