I might not be the best person to ask. I use Pi harness in tmux and just ask my current agent to spawn interactive pi instances in new tmux windows, create a sentinel file for each of them, and monitor the sentinel files for signals every 2 seconds.
replyCurrently have auto compaction turned off. When the orchestrator's context is getting close to full, I have it write a handoff markdown file and point a fresh agent at it.
I do feel like I'm getting close to the point where I might be ready for something more sophisticated, especially wrt to subagents communicating with the orchestrator.
That limitation is what stops me from using Pi for anything serious. I may have to configure it and then configure it and it will eventually become a codex, a claude code or so. I recently heard the maintainers added mcp to it (in stock, not via plugin), I wonder what stopped them from adding subagent function, and decent loop capacity to it.
reply> Currently have auto compaction turned off. When the orchestrator's context is getting close to full, I have it write a handoff markdown file and point a fresh agent at it.
replyIn a good harness that should be how auto compaction works anyway
Yes, and I'll probably trust it eventually. But currently I always want to know when compaction is happening, so I can correlate any drops in quality or weird behavior.
replyMany orchestrator harnesses exist.
replyCheck: https://agentmgmt.dev/ and find the one that works for you.
I quite like Paseo (been maining it for a week), but Orca also looks good.