My AI coding flow was burning tokens to do things code should do
The author discusses their transition from complex AI coding flows to a simpler, more deterministic approach using Pi Agent. They highlight the inefficiencies of relying on commands and agents, which often led to unnecessary token consumption. By adopting a modular system, they have improved the reliability of their coding processes and reduced costs.
- ▪The author moved from using opencode to Pi Agent for a more streamlined coding flow.
- ▪They emphasize the importance of determinism in coding processes to avoid unnecessary token usage.
- ▪The author created extensions for Pi that allow for more reliable execution of tasks like code reviews and report generation.
Opening excerpt (first ~120 words) tap to expand
My AI coding flow was burning tokens to do things code should doHow Pi Agent and a few deterministic extensions fixed my flowGeert TheysMay 25, 2026ShareMost AI coding flows are getting more elaborate. Mine got simpler.If you spend most of your day in a coding agent and have started wondering whether some of it should just be a script, this is for you. I am not going to cover MCP servers, skill authoring, or how Pi compares feature by feature to Claude Code. Plenty of other posts do that.Credit where it is due: Robert Douglass built Spec Kitty and it is a good tool. It sits on top of a coding harness, follows Spec-Driven Development, and gives you governance and auditability. It will work for plenty of teams. I went the other way.I started with an open source harness called opencode.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Hacker News (Newest).
Discussion
0 commentsMore from Hacker News (Newest)
