TL;DR
Get business pricing on tech for your team
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
A developer writing on caleb.software says he has stopped using Claude Code as his main coding harness and moved to Pi, an open-source alternative. His reasons include workflow limits, concerns about stability and product direction, and a preference for Pi’s minimalism and customization. The account is one user’s experience, not evidence of a broader migration.
A longtime Claude Code user says he has replaced Anthropic’s coding harness with Pi as his main development tool, citing workflow limitations, frequent changes and a preference for a more customizable, minimal setup. In a September 21 post on caleb.software, the developer described the move as a personal decision after frustrations accumulated over time—not as a recommendation based on a formal comparison or a wider user trend.
The author said he had used Claude Code since it became available through the Claude Pro subscription more than a year earlier. He credited it with making it possible to generate code from a prompt and called the software an important contribution to a new era of development. But he said the tool’s shortcomings had led him to retire it as his primary coding harness.
Among the problems he described was a limitation in Claude Code’s connection to Visual Studio Code: according to the post, only one session at a time can receive text selections from the IDE. He also criticized the official VS Code extension, saying some slash commands did not work in its interface, it lacked a custom status line, and output from multiple subagents could become difficult to read in a single chat thread.
The author also objected to maintaining separate CLAUDE.md and AGENTS.md instruction files across projects. He said Anthropic announced Claude Code support for AGENTS.md one day after he had decided to switch, but that the change came too late for him. His post reports 244 Claude Code releases during 2026 at the time he wrote it, with more than three-quarters changing the system prompt or tool descriptions. Those counts and his assessments are the author’s own; the post does not provide an independent release audit.
Why One Developer Chose Pi
The account highlights a practical tension in AI coding tools: adding capabilities does not necessarily improve the day-to-day experience for every developer. For this user, session handling, readable output and stable behavior mattered more than an expanding set of features he said he did not need.
The choice also illustrates that developers can respond to frustrations by changing the software layer around a model, not necessarily abandoning AI-assisted coding. The author described Pi as an open-source harness and said he had written extensions for his own needs. That may appeal to people who want to customize their tools, though it also means they may have to spend time configuring or maintaining them.
The post does not establish that Pi is generally more reliable or suitable than Claude Code. It records one developer’s experience and preferences. Its value is as a specific account of trade-offs in a fast-changing category, rather than a market-wide verdict.
Products Worth Considering
Logitech MX Mechanical Wireless Illuminated Full-Size Keyboard, Clicky
Apple MacBook Air 13.6-inch Laptop with M5 Chip, 24GB Memory, 1TB SSD, Midnight
Samsung 49-Inch Odyssey OLED G9 (G91SD) Dual QHD Curved Gaming Monitor
As an affiliate, we earn on qualifying purchases.
From Claude Code to Pi
The author’s criticism focused on the product around the models as much as on the models themselves. He argued that Claude Code’s system prompt and tool descriptions added more overhead than he wanted, including a Bash tool description he estimated at nearly 3,000 tokens. He also questioned whether detailed Git and GitHub instructions were necessary. These are his judgments about design and efficiency; the post does not report measured performance or cost comparisons between the two tools.
He described Pi’s approach as minimal and customizable, saying the first few days required some setup before the experience became smooth. He reported writing an extension to support a workflow across multiple open tabs in about 20 minutes. That example is specific to his use case and does not establish how much setup Pi would require for other developers.
The author framed Claude Code’s rapid development as understandable for a young product category, while arguing that the addition of features can make a product less coherent if teams do not account for their effects on existing workflows. He said he was not claiming he could have built a better product, and acknowledged that tools such as Pi benefit from hindsight.
““I’ve finally decided to retire it as my main coding harness and migrate my development setup to use Pi instead.””
— The author of the caleb.software report
Limits of a Single User’s Account
The post documents one person’s experience. It does not show how common the reported IDE and extension problems are, whether other users encounter them, or how Anthropic would respond to the criticisms. The author’s release count and estimates about prompt overhead are not independently verified in the source material.
It is also unclear whether the author’s extensions will be published: he said he hoped to share them after cleaning them up. The post does not provide a controlled comparison of Pi and Claude Code for performance, cost, coding quality or reliability, and it does not say that he has stopped using Anthropic’s models or services.
The author said he intends to continue using Pi and hopes to share a couple of extensions after cleaning them up. He also encouraged readers experiencing similar frustrations to try an open-source harness, while acknowledging that his experience may not match theirs.
No broader product response or follow-up from Anthropic is included in the source report. The next concrete development described is whether the author publishes his extensions and whether his new setup continues to fit his workflow over time.
Key Questions
What does “Goodbye Claude, Hello Pi” describe?
It is a September 21, 2026, post in which a longtime Claude Code user says he has switched his main coding harness to Pi after accumulating frustrations with Claude Code.
Why did the developer leave Claude Code?
He cited limits in its VS Code workflow, problems he said he encountered in the official extension, the burden of maintaining different instruction-file formats, and frequent changes to prompts and tool descriptions.
What did the author say he likes about Pi?
He described Pi as stable, minimalist and highly customizable. He also said he wrote extensions to support his own workflows, though those assessments reflect his personal experience.
Did the author say Claude Code added AGENTS.md support?
Yes. He said Anthropic announced support for AGENTS.md one day after he had decided to move to Pi. He considered the update too late to change his decision.
Does this show that developers are broadly leaving Claude Code?
No. The source is an individual account and provides no user surveys, adoption figures or other evidence of a wider migration from Claude Code to Pi.
Source: caleb.software
