I've blogged about it too: https://news.ycombinator.com/item?id=48978707

To work around that limitation I came up with this https://github.com/shaftoe/sbx-template-pi

So essentially you can get latest Pi/Node pulling from that image:

`sbx run -t ghcr.io/shaftoe/sbx-template-pi:latest shell`

Like others here I'm also saddened by the login requirement but at the moment this is the best UX I could find for running sandboxed agents, the "kit/mixin" concepts are neat and I make use of them too: https://github.com/shaftoe/sbx-template-pi#stacking-the-extr...

I'm looking forward to feedback, suggestions, etc, and I'll be happy to answer any questions too.

Happy forgin'

Comments URL: https://news.ycombinator.com/item?id=48978707

Points: 9

# Comments: 2

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 same 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

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

Remote: Yes

Willing to relocate: No

Technologies: AWS, Golang, Typescript, Terraform, Docker / Kubernetes (ECS/Fargate, EKS), PostgreSQL / Redis, CloudFlare / CloudFront, CI/CDs (AWS CodePipeline, GitHub Actions)

Résumé/CV: https://cv.l3x.in/

Email: a@l3x.in

  local usbWatcher = hs.usb.watcher.new(function(device)
    if device.productName == "EMEET SmartCam C960" then
      if device.eventType == "added" then
        hs.execute("networksetup -setairportpower en0 off")
        hs.notify.new({title="Wi-Fi", informativeText="Disabled (USB device connected)"}):send()
      elseif device.eventType == "removed" then
        hs.execute("networksetup -setairportpower en0 on")
        hs.notify.new({title="Wi-Fi", informativeText="Re-enabled (USB device removed)"}):send()
      end
    end
  end)
  usbWatcher:start()

Comments URL: https://news.ycombinator.com/item?id=23177668

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=22234506

Points: 2

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=22200999

Points: 2

# Comments: 2

Comments URL: https://news.ycombinator.com/item?id=22178988

Points: 2

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=13996464

Points: 7

# Comments: 1