Why does this makes more sense over OpenCode?
The memory footprint of Opencode is prohibitive to run 10+ copies at once.
Opinionated and easy Pi.dev configuration
21–30 of 78 posts
Re: Opinionated and easy Pi.dev configuration
#22I 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.
ironically (?) i prefer to improve Pi by connecting MCP servers instead of native extensions in part due to this (process-level sandboxing is trivial; anything more granular -- as would be required for in-process plugins -- is far more intimidating).
Re: Opinionated and easy Pi.dev configuration
#23This seems to be like the antithesis of pi, it's supposed to be this minimal thing you customise
I guess it's the same kinda friction with vanilla vim/neovim vs vim 'distributions' that provide a bunch of stuff out of the box.
Re: Opinionated and easy Pi.dev configuration
#24What 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 tooling, idiomatic Go, well designed initial test harnesses, GitHub actions that enforce some linting.
I think that works better than any markdown instructions ever will.
Re: Opinionated and easy Pi.dev configuration
#25I like peeping at other people's skills but it is unclear to me what/where the claimed 60+ skills are actually located. Compound Engineering conveys a few but nowhere near 60.
Re: Opinionated and easy Pi.dev configuration
#26"One command installs 60+ community skills, 67 themes, MCP support, sub-agent support, Claude Code CLI provider support, memory, and more."
What, no kitchen sink?
Re: Opinionated and easy Pi.dev configuration
#27This thing defeats the whole purpose of Pi.
I use lazyvim for all my neovim config. Does it fly in the face of the configurability or minimalism of vim? I'd argue no, but rather it is an expected outcome of a highly configurable system. Some people don't want to think about this kind of thing, they just want something that works.
> Does it fly in the face of the configurability
Probably not.
> or minimalism of vim?
I'd have to say at least a bit? Which is totally fine if it works for you, but there's gotta be some amount of extra features added after which "minimal" stops being a good description.
Edit: Although, we should also acknowledge that minimalism is a sliding scale. Compared to plain vi, vim is bloated. Compared to a full blown traditional IDE, lazyvim probably is minimal.
Re: Opinionated and easy Pi.dev configuration
#28Currently 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?
Re: Opinionated and easy Pi.dev configuration
#29What 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…
Nothing in (AGENTS|CLAUDE).md, no Cursor style rules. Just some skills for Jira/Confluence, CI, and Playwright.
Haven't bothered doing any extra customisation in Claude Code or Codex as I don't really trust those things to apply consistently. And if you can run your CI steps locally before you push you don't need to tell an agent to remember it.
That said I've been playing with pi today and given how stripped down it is I've used it as a sandbox for customisation. Still, I haven't gone quite as far as laying down project level instructions. More that Claude Code in particular is quite heavy, and so it its prompt, and adding stuff like rich integration with GitHub and SourceHut (CI status, active branch or PR) seems comparatively trivial in pi.
Only thing left to do is switch out ghostty for the time being as it's misbehaving. Laptop hot to the touch even after idling overnight.
Re: Opinionated and easy Pi.dev configuration
#30I 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.
> Pi is meant for people who know what they are doing
How many people genuinely know what they're doing when the value prop of Pi is basically to vibe code it to your taste? The entire point of vibe coding being that you don't actually have to know what you're doing?