Developers are divided between migrating to third-party harnesses like Pi for their customizability and control, versus staying with native tools like Claude Code due to concerns about stability, security, and vendor restrictions. The strongest disagreement centers on whether the flexibility of open-source harnesses outweighs the operational risks of manual configuration and potential Terms of Service violations.
493 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4shaftoe
pi-coding-agent-action
TypeScript2026–2026
shaftoe / pi-coding-agent-action
pi-coding-agent-action
GitHub action to integrate https://pi.dev/ coding agent with GitHub-compatible CI/CD, issues and PRs
2Distinct people
4Mentions
0Explicit recommenders
80GitHub stars
What to know before exploring
What it is
GitHub action to integrate https://pi.dev/ coding agent with GitHub-compatible CI/CD, issues and PRs
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:03:16 PM UTC.
Mentions over time
HN mentions by week4 dated mentions
Observed mentions: 2026-06-04 03:26:37 UTC to 2026-10-02 09:17:49 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jun 1 | 2026-06-01 00:00:00 UTC | 2026-06-08 00:00:00 UTC | 1 | 1 | 0 |
| Jun 8 | 2026-06-08 00:00:00 UTC | 2026-06-15 00:00:00 UTC | 0 | 0 | 0 |
| Jun 15 | 2026-06-15 00:00:00 UTC | 2026-06-22 00:00:00 UTC | 0 | 0 | 0 |
| Jun 22 | 2026-06-22 00:00:00 UTC | 2026-06-29 00:00:00 UTC | 0 | 0 | 0 |
| Jun 29 | 2026-06-29 00:00:00 UTC | 2026-07-06 00:00:00 UTC | 2 | 0 | 2 |
| Jul 6 | 2026-07-06 00:00:00 UTC | 2026-07-13 00:00:00 UTC | 0 | 0 | 0 |
| Jul 13 | 2026-07-13 00:00:00 UTC | 2026-07-20 00:00:00 UTC | 0 | 0 | 0 |
| Jul 20 | 2026-07-20 00:00:00 UTC | 2026-07-27 00:00:00 UTC | 0 | 0 | 0 |
| Jul 27 | 2026-07-27 00:00:00 UTC | 2026-08-03 00:00:00 UTC | 0 | 0 | 0 |
| Aug 3 | 2026-08-03 00:00:00 UTC | 2026-08-10 00:00:00 UTC | 0 | 0 | 0 |
| Aug 10 | 2026-08-10 00:00:00 UTC | 2026-08-17 00:00:00 UTC | 0 | 0 | 0 |
| Aug 17 | 2026-08-17 00:00:00 UTC | 2026-08-24 00:00:00 UTC | 0 | 0 | 0 |
| Aug 24 | 2026-08-24 00:00:00 UTC | 2026-08-31 00:00:00 UTC | 0 | 0 | 0 |
| Aug 31 | 2026-08-31 00:00:00 UTC | 2026-09-07 00:00:00 UTC | 0 | 0 | 0 |
| Sep 7 | 2026-09-07 00:00:00 UTC | 2026-09-14 00:00:00 UTC | 0 | 0 | 0 |
| Sep 14 | 2026-09-14 00:00:00 UTC | 2026-09-21 00:00:00 UTC | 0 | 0 | 0 |
| Sep 21 | 2026-09-21 00:00:00 UTC | 2026-09-28 00:00:00 UTC | 0 | 0 | 0 |
| Sep 28 | 2026-09-28 00:00:00 UTC | 2026-10-05 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
4 sourcesALalexfortin·Oct 2, 2026
I've been using Pi almost exclusively as coding agent in various forms since more or less January this year (I think). I settled quickly for a short list of extensions (which I wrote and I maintain) and a few skills/shared AGENTS.md, also installable as extension: https://forge.l3x.in/alex/pi-shared
For one thing I've re-built my personal website with it (mostly via GH issues from GH iOS app) and also added a section to talk about how I use AI in general: https://a.l3x.in/ai
I also maintain a couple of other Pi-related projects:
- https://awesome-pi.site/
- https://github.com/shaftoe/pi-coding-agent-action
So yeah, I still love the tool and use it pretty much every day, either as TUI sessions or inside CI/CD workflows.
Long live Pi!
In Pi 1.0Thanks to being unemployed, the last few months I've been experimenting a lot with coding agents, harnesses and most importantly, the workflows around them.
Currently I'm refining what I think works best for me, which I'd call something like "issues/PR based LLM workflow", powered mainly by this action I'm building on top of the Pi coding agent SDK: https://github.com/shaftoe/pi-coding-agent-action
Essentially I issue prompts swapping between the terminal and the git forge web app (GitHub and my own Forgejo instance) and it currently looks something like this:
- create an issue with detail/quality of spec based on how the task or the project is important
- trigger a Pi session prepending a comment in the forge with "/pi " to work on it, either to produce a report or to e.g. implement the change in a new PR
- trigger more sessions in the s
Read the rest
ame thread, be it an issue or a PR, to steer or to add more requests like fork out a new PR or similar. This works also for reviews so I just add comments and the submit a review with "/pi follow the comments instructions" or similar
- if I want more fine graded control and I am at the workstation I use the bridging Pi extension to pick up the work locally: https://github.com/shaftoe/pi-coding-agent-action/tree/devel...
- rinse and repeat until I'm either happy with the change or the PR is so bloated that I get rid of it and start anew
I know it's probably something Claude / Codex / Cursor offer with their web app but I want the freedom and the flexibility to use the LL provider/model I want, and Pi as a harness does that plus all the rests egregiously. Another advantage is that I can fit the LLM action in any pipeline I want and take care of chores like automated changelog generation and what not.
As I said it's still mostly work in progress but in general I think there's lot of potential with this kind of workflow, it forces me to keep the scope of the changes small (I still want to review the PR content after all) and gives me a memory for free just leveraging the ticketing system. I also like the fact the harness is running most of the time in the ci/cd sandbox which, in the case of Forgejo, I control fully.
PS I try to keep my work with/on AI tools on my website at https://a.l3x.in/ai
If you haven't yet you should give a chance to https://pi.dev
I've been using it exclusively (and extending it, see https://a.l3x.in/ai) for months with mainly GLM-4.7 then 5.1 and now 5.2 and I could hardly be any happier.
I'm still working on a "Github/Forgejo first" based workflow but also quite happy with it already, basically most of my sessions run as a ci/cd job (triggered by "/pi" comments) and generate PRs or push commits to PRs, see https://github.com/shaftoe/pi-coding-agent-action
In ZCode – Harness for GLM-5.2Beware of infinite loops when using AI
1 points · Open discussion