Live data from Hacker News

Opinionated and easy Pi.dev configuration

lazypi.org

61–70 of 78 posts

Re: Opinionated and easy Pi.dev configuration

#61

I can understand someone being overwhelmed and not wanting to configure and "build your own pi" which is really one of the beautiful points of pi, but like with vim, I do recommend that after playing with this for a while you go back to pure pi and then decide what do you really need and incrementally add it. The power of the incremental in control approach is huge. It allows you to keep moving in whatever direction…

Pi is perfectly usable in its "raw" state (except perhaps an extension for your specific provider, if not built in).

Configuring it isn't really overwhelming: you use it for a while and then find that you'd want to extend it with some particular functionality.

Re: Opinionated and easy Pi.dev configuration

#62

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.

I made my own subagent implementation in a couple of hours using Pi itself. It aligns with my needs better than any existing plugin, none of which seems to be what I was looking for.

You don't _need_ to use someone else's plugin if you don't want to, and for simple functionality, you can get pretty good resulting rolling your own.

Re: Opinionated and easy Pi.dev configuration

#63
post #56
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…

My first thought when reading about this was, why does Pi with 8 custom skills and one extension work so well for me, and apparently so poorly for others that they are compelled to go to these lengths?

people use different models. I use small local ones for instance

Re: Opinionated and easy Pi.dev configuration

#64
post #36

Earlier quoted context omitted.

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.

Oh-my-pi seems to like robo coding, while pi itself is entirely against vibe coding for production. (The clanker is a tool, not a free wheeling agent.)

And I see that tonight pi has had their regular devs ship (https://github.com/earendil-works/pi/tags) new releases with modified thinking levels for GPT-5.6 while roboomp is discussing this back and forth with some contributors in oh-my-pi's repo.

Re: Opinionated and easy Pi.dev configuration

#65
> One command. Everything configured. Nothing to research.

Being talked at by someone's AI copypasta feels like being in the Truman Show.

"Why don't you let me fix you some of this new Mococo drink? All natural cocoa beans from the upper slopes of Mount Nicaragua, no artificial sweeteners!"

"What the hell are you talking about? Who're you talking to?"

Re: Opinionated and easy Pi.dev configuration

#66
post #56
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…

My first thought when reading about this was, why does Pi with 8 custom skills and one extension work so well for me, and apparently so poorly for others that they are compelled to go to these lengths?

Also if anyone wants opinionated and easy pi, oh-my-pi has been that choice for ages

Re: Opinionated and easy Pi.dev configuration

#67
post #56

Earlier quoted context omitted.

My first thought when reading about this was, why does Pi with 8 custom skills and one extension work so well for me, and apparently so poorly for others that they are compelled to go to these lengths?

people use different models. I use small local ones for instance

Can this perform "agentic tasks" while using a local ollama instance

Re: Opinionated and easy Pi.dev configuration

#69
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…

> The new models are quite smart, so suffocating their context with dozens of MCPs and skills isn’t necessary like it used to be. Genuinely curious, how MCPs can suffocate the context? And what exactly do you mean by this? I have probably more than a dozen of MCPs enabled in my Claude Code (slack, jira, github, many internal ones), and I have never seen model calling into them unnecessarily unless it’s explicitly nee…

Tip: You can see the token usage of MCPs/plugins/skills by using `/context`.

For example, the M$ 365 MCP occupies several thousands of tokens, and there's currently no way to disable it entirely in Claude Code...

Re: Opinionated and easy Pi.dev configuration

#70
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…

> The new models are quite smart, so suffocating their context with dozens of MCPs and skills isn’t necessary like it used to be. Genuinely curious, how MCPs can suffocate the context? And what exactly do you mean by this? I have probably more than a dozen of MCPs enabled in my Claude Code (slack, jira, github, many internal ones), and I have never seen model calling into them unnecessarily unless it’s explicitly nee…

superpowers front-load 22k tokens before you even hit send and their context inflation balloons after 500k
Post reply on HN