Using a CLI coding agent in your IDE's terminal is a terrible way to view conversation history and works poorly for organizing multiple conversations.

It only fits a hands-on, merely AI-assisted development approach, on one feature at a time, that is not typically productive compared to agentic development.

You might disagree, but you'll find that the proponents of the hands-on approach are losing ground every month as AI gets better at working autonomously.

I'm expecting IDEs to adapt to new workflows, albeit very slowly.

There is potential to build a better UI than what's constrained within a CLI's grid of characters.

I'll admit I'm currently not up to speed on having multiple features worked at the same time, with git worktrees etc.

Except surrendering cognitive control over the system being built makes things worse.

Claude constantly makes poor architectural decisions, adds unnecessary and costly checks, makes wrong assumptions, etc.

Doesn't take the value out of LLMs writing code, but they need to be properly steered and reasoned with. How will you do so if you don't even browse the code it generates.

I always suspect that the people all in fully agentic codig like this are mostly creating prototypes, half-assed copies of existing products, etc.

I am glad to not work in such an environment.