| ▲ | hippycruncher22 7 hours ago | |
I'm a https://pi.dev man myself. | ||
| ▲ | 6ak74rfy 4 hours ago | parent | next [-] | |
Same. Pi is refreshingly minimal in terms of system prompts, but still works really well and that makes me wonder whether other harnesses are overdoing. Look at OpenCode's prompts, for instance - long, mostly based on feels and IMO unnecessary. I would've liked to just overwrite OC's system prompts with Pi's (to get other features that Pi doesn't have) but that isn't possible today (without maintaining a custom fork) | ||
| ▲ | Richard_Jiang 4 hours ago | parent | prev | next [-] | |
Pi is a great project, and the lightweight Agent development is really recommended to refer to Pi's implementation method. | ||
| ▲ | wyre 5 hours ago | parent | prev | next [-] | |
Same. I’m sure there’s a more elegant way to say this, but OpenCode feels like an open source Claude Code, while pi feels like an open source coding agent. | ||
| ▲ | cmrdporcupine 4 hours ago | parent | prev [-] | |
Pi is good stuff and refreshingly simple and malleable. I used it recently inside a CI workflow in GitLab to automatically create ChangeLog.md entries for commits. That + Qwen 3.5 has been pretty successful. The job starts up Pi programatically, points it at the commits in question, and tells it to explore and get all the context it needs within 600 seconds... and it works. I love that this is possible. | ||