There's a number floating around that i cannot stop thinking about. Grok 4 Fast went from 6.7% to 68.3% on coding edits. No new model release. No training data dump.
Just a better tool format. The creator of oh-my-pi built something called Hashline. Every line of code gets a short content hash, and the model references the hash instead of reproducing the entire line. Tenfold improvement in an afternoon.
This is the hashline effect. And it tells you everything about why the coding agent space is so weird right now.
oh-my-pi is a fork of Mario Zechner's Pi project, extended by a developer called can1357. It is a terminal-based AI coding agent that runs on Bun, with a Rust core clocking around 27k lines.
It supports 40+ model providers, 32 built-in tools, 13 LSP operations, and 27 DAP operations. A lot of people are talking about it. And the reactions are all over the place.
So what is actually happening here.
The hype is real but nobody agrees on why
Some people see oh-my-pi as the LazyVim of coding agents. Batteries included, works out of the box. You don't have to spend your weekend configuring tools.
Others call it bloated and say the real way is pure Pi, building your own setup, composing your own distro.
AkitaOnRails tested it and said: "It works. It is not bad. It also did not make me say how did I live without this." That is a pretty honest take from someone who has used a lot of these tools.
On Reddit, a user called it "really nice in that it feels like a polished product, but the initial token count is 22k, which hurts." And that is a real problem. Every conversation starts with a 22k token overhead before you even say hello to the model.
But then you have can1357's numbers. Grok Code Fast jumping from 6.7% to 68.3%. Gemini improving by 8 percentage points. Grok 4 Fast spending 61% fewer output tokens.
These are not small wins.
What makes oh-my-pi different
The tool surface is the actual product here. Most coding agents give the model a Python sandbox and call it done. oh-my-pi runs a persistent Python kernel and a Bun worker, both of which can call back into the agent's own tools over a loopback bridge. So the agent can load a CSV with the read tool from inside Python, chart it from JavaScript, and never leave the cell.
The LSP integration is serious too. Ask for a rename and it goes through workspace/willRenameFiles. Re-exports, barrel files, and aliased imports all update before the file moves. That is the kind of thing you only get if someone actually shipped a product, not just a script.
And the DAP support is wild. A C binary segfaults. The agent attaches lldb, steps to the bad pointer, reads the frame. A Go service hangs. DlV, walk the goroutines.
A Python process is wedged. Debugpy, pause, inspect, evaluate. Most agents are still sprinkling print statements.
i used to think the model was everything. Pick the biggest one, throw tokens at it, get results. oh-my-pi is making me rethink that.
The difference between a 6.7% pass rate and a 68.3% pass rate is not a bigger brain. It is a better interface.
Here is a question people always ask: is oh-my-pi better than Claude Code? And the answer is it depends on what you value. Claude Code has the best context management and compaction in the game. The subscription pricing is unbeatable if you use it all day.
oh-my-pi gives you flexibility. 40+ providers. Custom tools. Debugger integration. Things Claude Code does not let you touch.
But honesty requires saying this: oh-my-pi feels like a lab project in some places. The default verbosity is annoying. The configuration surface is deep and not always documented well.
Akita put it best when he said he did not want to spend an afternoon tuning prompts and panel sizes.
the model is the moat. the harness is the bridge. burning bridges just means fewer people bother to cross.
That quote from can1357 is the key insight. Models are getting better every quarter. The gap between them is shrinking. What actually determines whether an agent helps you or not is the harness around it.
Here's what broke for one HN user who migrated from Pi to oh-my-pi:
- the Rust tools using NAPI caused tool confusion after updates
- models needed 11 iterations just to edit a single file
- the agent then gave up and rewrote the whole file from memory
- fixing it meant wiping all agent memory and starting fresh
The integrations with search, LSP, syntax highlighting, and custom tools work like a charm, they said. But the upgrade path is not smooth.
And this is the tension. oh-my-pi adds so much. But every layer you add is another thing that can break when you pull from upstream.
Here is something related but off topic. The naming situation is hilarious. Pi is already a famously overloaded name. Raspberry Pi, the math constant, and now a coding agent.
And oh-my-pi adds another layer. Type "oh my pi" into Google and you get a mixture of coding agent docs and confused home assistant users. Every time someone talks about their "Pi setup" in a coding context, they have to clarify which Pi.
i have been in conversations where three different people assumed three different things. It is the namespace collision of 2026 and nobody has fixed it yet.
But really this reminds me of NeoVim. Some people want LazyVim. Some people want to build from scratch. Neither is wrong.
The problem is when people on either side pretend their choice is the only right one.
And the irony is that this debate over batteries included versus minimal keeps happening with every new tool. It happened with text editors, with frameworks, with package managers.
Every time the community splits into two camps that spend more energy fighting each other than building. oh-my-pi is just the latest frontier for this.
Who should actually use oh-my-pi
Here is the blunt version. If you use Claude Code all day and it works fine for you, oh-my-pi probably is not worth switching to. The subscription pricing from Anthropic changes the math completely. Why pay per token when you can pay per month.
But if you want to use models outside the big two. If you want to run local models. If you want the full tool surface including LSP, DAP, persistent kernels, subagent orchestration, and hash-anchored edits.
If you care about the harness as much as the model. Then oh-my-pi is probably the most complete open option right now.
The hashline thing still bothers me
i keep going back to that number. 6.7% to 68.3%. Not a better model. Not more training compute.
Just a better way to say "edit this line." The old approach was: the model guesses the exact text around the change, repeats it, and hopes for the best. Line numbers shift, whitespace mismatches happen.
The edit fails, the model retries, the context grows, your token bill doubles.
The Reddit thread said it best
On r/PiCodingAgent, someone asked "Is oh-my-pi the best batteries-included Pi mod, or does it diverge from Pi's minimalist philosophy too much?" The top comment: "The main goal of pi is not to be minimalistic but to be customized by the end-user with no built-in trash."
That is a very specific philosophy. And oh-my-pi violates it on purpose. It adds everything. It is the opposite of minimalist.
Hashline: every line has a hash. The model says "edit this hash." The tool finds it. Done.
This is the kind of improvement that changes how you think about the whole space. Maybe the next 10x is not a bigger model. Maybe it is a smarter way to talk to the one you already have.
i still think about that HN comment comparing Pi to llama-cpp. "The former gets all the hype, while the latter is actually the more impressive part."
It is true for oh-my-pi too. The hype cycle is pointing at the model. The real work is happening in the harness. And the numbers say it matters more than most people are willing to admit.