I've been really curious about pi and have been following it but haven't seen a reason to switch yet outside anecdotes. What makes it a better daily driver out of the box compared to Claude or Codex? What did you end up needing to add to get your workflow to be "now capable to write its own extensions"? Just trying to see what the benefit would be if I hop into a new tool.

Why don’t you try it, it’s 2 minutes to setup (or tell Claude to do it), and it uses your CC Max sub if you want.

Some advantages:

- Faster because it does no extra Haiku inference for every prompt (Anthropic does this for safety it seems)

- Extensions & skills can be hot reloaded. Pi is aware of its own docs so you just tell it „build an extension that does this and that“. Things like sub agents or chains of sub agents are easily doable. You could probably make a Ralph workflow extension in a few minutes if you think that’s a good idea.

- Tree based history rewind (no code rewind but you could make an extension for that easily)

- Readable session format (jsonl) - you can actually DO things with your session files like analysis or submit it along with a PR. People have workflows around this already. Armin Ronacher liked asking pi about other user’s sessions to judge quality.

- No flicker because Mario knows his TUI stuff. He sometimes tells the CC engs on X how they could fix their flicker but they don’t seem to listen. The TUI is published separately as well (pi-tui) and I‘ve been implementing a tailing log reader based on it - works well.