Caleb moved from Claude Code to Pi, another coding-agent harness: the software that connects a model to tools, files and an interface. He wanted a more predictable setup that he could adapt to how he reviews code.
- In his VS Code workflow, only one Claude Code terminal session could receive editor selections at a time. He says he built a Pi extension for multiple tabs.
- He found the official graphical extension better at handling tabs, but missed commands and a custom status line.
- Frequent changes to the default instructions and tool descriptions disrupted his setup, he says. He also questions how much the built-in instructions add to the model’s context.
Pi needed some initial configuration, but Caleb says its minimal approach has worked well for him. This is one developer’s experience, not a controlled comparison; the essay dates to September, and features may have changed.
The 274-comment thread on Hacker News adds several tradeoffs:
What the thread adds
- B4uler5 — Configured Pi as a tutor that advises while they make the edits themselves.
- giladd — Asks about blocking dangerous actions and raises concerns about vetting third-party extensions. mpern prefers wrapping an agent in an external sandbox.
- bottlepalm — Prefers a desktop interface for managing many sessions across projects, a counterexample to the terminal-first preference.
- medochi48 and commandersaki — Ask about API costs and subscription compatibility, which the essay doesn’t settle.
HN handles are pseudonymous, per-comment scores aren’t public, and ordering follows HN’s ranking. This is a slice of the thread, not a consensus.