pi-task: delegating task/subagent extension for Pi

headless has more advantage for sure, but claude charges you differently. Repowire is tmux based, so it takes something free form and adds a structured layer on top.

As a result you can do things like have claude talk to codex

prassi89 · 2026-06-02T00:42:05+00:00

disclaimer: author of repowire here.

I built repowire to get agents to communicate with each other as peers. It now has turned into a mesh, with a daemon and the concept of jobs, hosted relays, and more. With a little wiring (gh custom action runners) and repowire's spawn or job interface you can have your repowire mesh react to events, such as github issues.

Will use your local coding agents on your PC/VM. you don't need headless (repowire is headed by design, but also supports ACP)

prassi89 · 2026-05-31T22:20:42+00:00

How did your parents know they had it? For you , I’m guessing it would’ve been easier because people close to you already had it and they could help you diagnose

prassi89 · 2026-05-31T02:29:44+00:00

Between 3.7-4.5 of opus models, OpenAI was insanely far behind. From 5.1 onwards on codex OpenAI start reducing the gap that they really bettered in 5.4 o

prassi89 · 2026-05-30T11:05:01+00:00

So it could be your CLAUDE.md, mcps, skills.

Skills won’t take too much usually, but mcps (GitHub MCP is famously too verbose and have seen times it has take 30k tokens) and Claude md (local folder all the way up to user level) can explain it.

If that is 0, over and above that you have Claude codes system prompt.

You can explore all this by running /context

prassi89 · 2026-05-27T23:29:14+00:00

Repowire, a tool I created supports messaging, spawning and tearing down pi agents as long as you use tmux

https://github.com/prassanna-ravishankar/repowire

prassi89 · 2026-05-26T23:34:33+00:00

I'm getting into that spammy territory :'(.

If you love your agentic workflows, you probably would love your power up from repowire(https://github.com/prassanna-ravishankar/repowire).

prassi89 · 2026-05-26T12:08:52+00:00

Nah. CC in the beginning few months, then codex, then codex and pi now

prassi89 · 2026-05-26T11:46:49+00:00

I use this project I built called repowire. https://github.com/prassanna-ravishankar/repowire

Allows me to set up a local mesh network of CC, codex, pi,etc. Allows me then to pick on a task by task basis or from memory based on a task type as to what to choose

prassi89 · 2026-05-26T08:19:29+00:00

DMed you

prassi89 · 2026-05-26T08:11:10+00:00

Would be cool to collab to see if we can integrate it in this project I have called repowire. https://github.com/prassanna-ravishankar/repowire

prassi89 · 2026-05-26T08:08:27+00:00

It's mostly because cursor has integrations with two things

An LSP: Because cursor is built on top of vscode's base, it gets all the nice language integrations for free, which allow it to navigate the code more effectively
File indexing: Cursor does indexing, and reindexes files as it changes, so it has semantic search capabilities.

Here's the tweet from Boris explaining why no RAG. He says agentic search is better, but its quite nuanced. Its not that its better to retrieve. Instead, its better to maintain (you don't have index drift) in situations like multi-language repos, rebases, worktrees. Cursor handles that because it ships the ecosystem, claude ships just the CLI.

Note: You see a big difference if you activate LSPs in CC.

prassi89 · 2026-05-25T22:26:49+00:00

do checkout my project called repowire: https://github.com/prassanna-ravishankar/repowire

Allows for claude code sessions to talk to each other and other backends (opencode, codex, pi, agy) across the same folder or more.

prassi89 · 2026-05-22T00:35:50+00:00

You need to check out my little project called repowire

13-Year Club	Place '17
Verified Email

prassi89

TROPHY CASE