Live data from Hacker News

Opinionated and easy Pi.dev configuration

lazypi.org

31–40 of 78 posts

Re: Opinionated and easy Pi.dev configuration

#31

What AGENTS.md and skills are people relying on these days? I have little to none and am successful building full stack Go apps Claude Code, Codex, and Shelley which covers the spectrum of crazy black box to simple `bash` clanker. It makes me think the models are continually improving in knowing what to do on their own. I do put some major work into the classic "Developer Experience" (DX) of my code base. Standard Go…

I’ve tried quite a few, from oh-my-openagent’s gargantuan hooks+plugin system to minimal add-i like wozcode, and I’ve been most impressed by that (wozcode) and oh-my-pi. I get that pi is supposed to be roll-your-own but I think OMP’s config is a great starting point; pi removed all the fluff and OMP added just enough orchestration and tooling back in to take things to the next level. Wozcode is great if you like CC because it doesn’t mess with the fundamentals, it just adds things like batching for efficiency—CC’s system prompt alone is absurd.

Caveat: I’m a data scientist/researcher, not a professional SWE, so take my experiences with a grain of salt. I’m just a python monkey most of the time

Re: Opinionated and easy Pi.dev configuration

#32
post #6

Pi makes you think about what you’re doing with it on purpose. This defeats that, as the Mario quote on the page says, and therefore isn’t worth using. People really need to try out “less is more”. The new models are quite smart, so suffocating their context with dozens of MCPs and skills isn’t necessary like it used to be. A cli tool with good built in help and good errors is amazingly easy for the model to figure o…

I like the Pi approach, but I think I didn't "hold it correctly" so to say. I would like to migrate away from Claude Code and use Pi as my "peimary" harness. I really like in particular how it manages conversation trees and branches. But I think I didn't do a good job in customizing it for my work. While nothing dramatic, I think the LLM I was using did a better job on Claude Code than on Pi a couple of time when I t…

That’s why I like things like oh-my-pi and lazypi, nothing’s stopping you from modifying it after you install; I find that when I’m working on my own sometimes I brick myself into a corner and it’s nice to see someone else’s starting point for reference.

Re: Opinionated and easy Pi.dev configuration

#33

I think the developers of Pi made a supply chain mistake by stripping down the core agent and requiring features like subagents to load plugins written by some random person.

Pi is meant for people who know what they are doing. If you dont fall into that category use OpenCode, etc. The whole idea is that you customize Pi to your own needs by asking it to modify itself through extensions. That said, sometimes it is really easy to leverage existing extensions. You run the risk of supply chain attack though. I installed one extension that was useful, modified it to my needs and pinned it.

That’s why Mario said “YOLO” is enabled by default from what I remember—something like, I want you to think about what you’re doing.

Re: Opinionated and easy Pi.dev configuration

#34
post #6

Pi makes you think about what you’re doing with it on purpose. This defeats that, as the Mario quote on the page says, and therefore isn’t worth using. People really need to try out “less is more”. The new models are quite smart, so suffocating their context with dozens of MCPs and skills isn’t necessary like it used to be. A cli tool with good built in help and good errors is amazingly easy for the model to figure o…

I like the Pi approach, but I think I didn't "hold it correctly" so to say. I would like to migrate away from Claude Code and use Pi as my "peimary" harness. I really like in particular how it manages conversation trees and branches. But I think I didn't do a good job in customizing it for my work. While nothing dramatic, I think the LLM I was using did a better job on Claude Code than on Pi a couple of time when I t…

What was lacking? This is self promotional but I am working on

https://github.com/gitsense/pi-brains

which is designed around the Pi philosophy of less is better by focusing on ondemand context/guidance. I won't bloat the context unless the LLM needs to do something I know it will need better guidance with. I have a demo repo for this at https://github.com/gitsense/gsc-rules-demos

One of the examples is, if I know the agent is reading a specific file, I will inject additional context. So if the agent never needs to do something in a certain file or directory, I don't need to pollute the context with "what it may need to know".

Re: Opinionated and easy Pi.dev configuration

#35
post #18

Currently using Oh My Pi ( https://github.com/can1357/oh-my-pi ) and appreciate the batteries included approach. From my limited time using pure Pi, I found quite a few of the plugins lacking and had no desire to upgrade/fix and maintain them myself. I know others feel differently though. I like the idea of keep Pi minimal but having “official”, high quality optional plugins to make it more usable.

As AI outsider, can you speak to how you draw the line here? Like doesn't the agential blahblah make upgrades/maintenance trivial? When do you get it to make you the thing versus choosing to vendor something out like back in the day?

Making the upgrades or maintaining or crafting from scratch a plugin isn't free, it costs tokens and time and attention. And you're almost assuredly reinventing a wheel that someone else already did and probably did better. I like have the ability, but I prefer not needing it.

Re: Opinionated and easy Pi.dev configuration

#36
post #18

Currently using Oh My Pi ( https://github.com/can1357/oh-my-pi ) and appreciate the batteries included approach. From my limited time using pure Pi, I found quite a few of the plugins lacking and had no desire to upgrade/fix and maintain them myself. I know others feel differently though. I like the idea of keep Pi minimal but having “official”, high quality optional plugins to make it more usable.

As AI outsider, can you speak to how you draw the line here? Like doesn't the agential blahblah make upgrades/maintenance trivial? When do you get it to make you the thing versus choosing to vendor something out like back in the day?

Funny you mention that because the OMP GitHub issues (https://github.com/can1357/oh-my-pi/issues) is almost exclusively attended to by a very efficient bot. I routinely submit issues and they’re replicated and resolved (via PRs) in ~30 mins.

To your question: it’s the difference between one person and an agent working on something vs an experienced dev and the entire community.

Time and tokens too of course.

Re: Opinionated and easy Pi.dev configuration

#38
60+ ! oh my, while this is cool it seems that is overkill. I want to know all my skills back and forth.

But I like this kind of projects where I can peak of what extensions other people use. Is like .vimrc file back in the day. Do not clone blindly, but peak, learn and copy what is needed.

Re: Opinionated and easy Pi.dev configuration

#39

What AGENTS.md and skills are people relying on these days? I have little to none and am successful building full stack Go apps Claude Code, Codex, and Shelley which covers the spectrum of crazy black box to simple `bash` clanker. It makes me think the models are continually improving in knowing what to do on their own. I do put some major work into the classic "Developer Experience" (DX) of my code base. Standard Go…

My Claude.md is a maybe 30 lines. I only adid something if it repeatedly does something that annoys me.

It still tends to do those things, but maybe 40% less.

Post reply on HN