3 ms·

Or pi.dev - also super fast and simple. Claude Code is sluggish, buggy, slow. Typical big enterprise garbage. The only good thing at Anthropic are the models.

orphea 4mo ago
How is text editing in it? This is what I hate about terminal coding UIs the most: all the text editing experience - the basic stuff like moving the cursor around, copying, pasting - is just broken.
- isoprophlex 4mo ago
  Both codex and claude allow editing in vi
  - 0123456789ABCDE 4mo ago
    … or whatever else you set $EDITOR to
CharlesW 4mo ago
Claude Code is notably better than Pi, although I wish them the best of luck in their efforts. As https://c-daniele.github.io/en/posts/2026-05-18-coding-harness-comparison/ https://c-daniele.github.io/en/posts/2026-05-18-coding-harne... notes, "Pi's lightness comes from a default setup that does not survive contact with reality." The same post on Claude Code: "Even though the System Prompt and tool descriptions are clearly more verbose, most of the extra tokens encode product features and rational design choices: a memory system, scheduled tasks, sub-agents, plan mode, worktree support. Whether those features are worth paying for depends on your needs. Calling the prompt 'bloated' without looking at the whole picture feels wrong to me."
- ai_slop_hater 4mo ago
  If only they could add an option to disable features you don't use
- skybrian 4mo ago
  The "guardrails" are bloat if you're using a proper sandbox. This seems like a matter of using the right harness for the environment it's running in, rather than one always being better than the other.
- mdavid626 4mo ago
  What are you talking about? Did you even use pi.dev? I used them both and I can tell you there isn’t a single feature what pi.dev misses from Claude Code.
_pdp_ 4mo ago
It is has a lot of javascript. I was forced to make my own for small projects.
JVerstry 4mo ago
I ask Claude to implement non-regression tests. It works like magic. With a couple of modules checking for code quality, more magic. Add some online performance tests if relevant, and it is close to paradise. From time to time, send it to some blog pages and articles with implementation ideas and recommendations. Look for best practices and let it do the analysis and implementation job if it makes sense... T

orphea 4mo ago

How is text editing in it? This is what I hate about terminal coding UIs the most: all the text editing experience - the basic stuff like moving the cursor around, copying, pasting - is just broken.

isoprophlex 4mo ago
Both codex and claude allow editing in vi
- 0123456789ABCDE 4mo ago
  … or whatever else you set $EDITOR to

CharlesW 4mo ago

Claude Code is notably better than Pi, although I wish them the best of luck in their efforts. As https://c-daniele.github.io/en/posts/2026-05-18-coding-harness-comparison/ https://c-daniele.github.io/en/posts/2026-05-18-coding-harne... notes, "Pi's lightness comes from a default setup that does not survive contact with reality." The same post on Claude Code: "Even though the System Prompt and tool descriptions are clearly more verbose, most of the extra tokens encode product features and rational design choices: a memory system, scheduled tasks, sub-agents, plan mode, worktree support. Whether those features are worth paying for depends on your needs. Calling the prompt 'bloated' without looking at the whole picture feels wrong to me."

ai_slop_hater 4mo ago
If only they could add an option to disable features you don't use
skybrian 4mo ago
The "guardrails" are bloat if you're using a proper sandbox. This seems like a matter of using the right harness for the environment it's running in, rather than one always being better than the other.
mdavid626 4mo ago
What are you talking about? Did you even use pi.dev? I used them both and I can tell you there isn’t a single feature what pi.dev misses from Claude Code.

_pdp_ 4mo ago

It is has a lot of javascript. I was forced to make my own for small projects.

JVerstry 4mo ago

I ask Claude to implement non-regression tests. It works like magic. With a couple of modules checking for code quality, more magic. Add some online performance tests if relevant, and it is close to paradise. From time to time, send it to some blog pages and articles with implementation ideas and recommendations. Look for best practices and let it do the analysis and implementation job if it makes sense... T