[cookiengineer]

Most problems you described come from using LLMs with high temperatures and long lifecycles.

The point behind agentic environments and an orchestrator/planner architecture is that you can delegate defined and specified tasks to short living and low tempered agents. Well, at least if you know what you are doing, and know how to specify these things based on an AST and not markdown notes, for example.

(Judge for yourself if Claude is the right IDE for that, given that their source code from a couple weeks ago is available)

Languages that use pointers and have dependencies on time need strong specifications for LLMs to make sense. And that's what's missing.

Disclaimer: I am building a pentesting and Go focused agentic IDE for short living agents, so my point of view is not using hyped tools but trying to understand harness engineering well enough to let the kids mess with your codebase.