opencode VS pi-mono

Dax, the creator of OpenCode — an open-source coding agent, of all the people one might expect to disagree — put the case for hand-coding cleanly in a recent interview about Spec-Driven Development:

Pipa is our agent for studio operations at Lunch Pail Labs. She lives in Slack, is powered by E2B sandboxes, and uses OpenCode for the harness.

One reason I liked OpenSpec more than others, such as Kiro and SpecKit, is that OpenSpec is highly portable between coding assistants, codebases and stages of development. I've plugged OpenSpec into all sorts of projects, from infrastructure to Python libraries. I also work on diverse codebases, with a variety of AI friends that OpenSpec supports: OpenCode, Codex and Claude Code.

Beyond the big names, I would also keep an eye on OpenCode and T3 Code. OpenCode is a solid open-source, terminal-first option if you want a model-agnostic agent and bring your own provider setup. T3 Code is interesting for the opposite reason: it gives you an open-source GUI on top of the agents you may already pay for, like Claude Code, Codex CLI, OpenCode, or Cursor.

Brought to you by the infamous creator of OpenCode, who will exfiltrate all your data, then feign ignorance:

https://github.com/anomalyco/opencode/issues/10416

47k stars

Their secret? A very rigorous contribution policy. Essentially, issues and PRs are autoclosed, and reviewed daily by the team. If its not slop, they whitelist either the issue/PR or the contributor (so their stuff isn't autoclosed next time).

https://github.com/badlogic/pi-mono/blob/main/CONTRIBUTING.m...

GitHub needs an issue / PR approval flow.

Their process is outlined here: https://github.com/badlogic/pi-mono/blob/main/CONTRIBUTING.m...

> Maintainers review auto-closed issues daily and reopen worthwhile ones. Issues that do not meet the quality bar below will not be reopened or receive a reply.

Seems like not an unreasonable way to deal with the problem of large numbers of low quality issues being submitted.

pi-mono: tool calling and state management

A couple other major open source harnesses:

- https://github.com/badlogic/pi-mono/

https://github.com/badlogic/pi-mono/tree/main/packages/codin...

you already could! just install Termux, npm install your favourite agent harness (pi for one has explicit Termux support, but its AGENTS.md works just fine with Claude Code for example - https://github.com/badlogic/pi-mono/blob/main/packages/codin...), and say you want an android app. It problem solves for a bit, then spits out an apk out to your Downloads folder.

Reluctantly, the dev seems to have a stinky attitude.

He went on an "OSS vacation", which is perfectly reasonable and said he'd be back on a certain date. I had a PR open for a trivial fix, someone asked when it would land. I shared he was still away. After his return I politely asked, "@badlogic hey, what can we do to progress this? Thanks x"

I then got what I would consider an abusive reply, because he confused me with someone else. In the meantime he extended his vacation. Didn't even think his shitty attitude was worthy of an apology, that HE confused me with someone else.

https://github.com/badlogic/pi-mono/discussions/1475#discuss...

And another other thing I fixed with no attribution, just landed it himself separately.

My point is pi-coding-agent [1] is a very well designed and implemented open source project that we all can learn from as software engineers. His blog post about his decision making [2] is also very well written.

I should've given original links instead of noisy HN threads.

[1] https://github.com/badlogic/pi-mono/blob/main/packages/codin...

[2] https://mariozechner.at/posts/2025-11-30-pi-coding-agent/

pi-conding-agent itself is not a product yet and it won't have much value to end users other than those using the products built on top of it.

badlogic/pi-mono/packages/mom/README.md

Oh, you should have a look at Pi then.

https://github.com/badlogic/pi-mono/tree/main/packages/codin...