MAmathaix·Sep 21, 2026
Thank you, will checkout https://github.com/jakelevirne/pi-relay
I want to extend this. Support other harness like PI and models like Kimi
In Show HN: Self Improving AgentOrchestrator Skilljakelevirne
pi-relay
Shell2026–2026
jakelevirne / pi-relay
pi-relay
Fan Claude Code workflow steps out to any pi-supported model (Kimi K3 by default) via a relay subagent
2Distinct people
2Mentions
0Explicit recommenders
0GitHub stars
What to know before exploring
What it is
Fan Claude Code workflow steps out to any pi-supported model (Kimi K3 by default) via a relay subagent
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by hour2 dated mentions
Observed mentions: 2026-09-21 14:47:10 UTC to 2026-09-21 14:52:52 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC. One observed period does not establish a trend.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Sep 21, 14:00 | 2026-09-21 14:00:00 UTC | 2026-09-21 15:00:00 UTC | 2 | 0 | 2 |
What Hacker News says
2 sourcesThis is great to see. I've now fully embraced long-running agentic workflows with separate plan->generate->evaluate steps, all coordinated by an orchestrator. I've done this using Claude Code alone, which is very easy but costly using Fable alone. I've done this in a team-visible way using Linear and Cyrus https://specstory.com/tutorials/team-based-loop-engineering.
And lately, for cost savings I've been doing this via Claude Code orchestrated workflows that fan out to lower cost Pi.dev Kimi agents https://github.com/jakelevirne/pi-relay.
I think there's a lot to be said for having orchestrated goal-oriented workflows (loops/harnesses) that have their choice of agents. So it's nice to see that principle in play here. And strong goal/outcome definition is critical for success with these long running workflows, so helpful to see SpecFlow me
Read the rest
thodology baked in to the skill.
I think the biggest thing I've seen over and over as teams try to adopt this type of approach is weak testing/verification. Using agentic development it's very easy to have automated unit and integration testing. But what this approach really demands is acceptance testing and intent verification. Most people I know still do this part by hand, which means the loops can't be as long-running as they ideally would be. Have you thought about a deeper (more deterministic) verification approach, in addition to adversarial review from another agent?
(Note: I'm a SpecStory maintainer but didn't have anything to do with this Claramap Builder project)