IMO Astra isn’t really lazy, just extremely literal so when you use it side by side with gpt-6.1-sol, it might appear more lazy but it’s often just the big difference in prompting between the 2. Astra wants a clear goal definition of what you want it to do, while sol infers a bit more. And the Claude’s infer a lot lot more.
From memory, prompts like “this file is a bit messy” would trigger Sol and Claude to start editing the file immediately, while Astra wouldn’t. But if you give Astra a clear plan and a definition of what you want it to do, then it will keep working until that ask is fulfilled.
Especially compared with Claude that’s a huge difference, Claude is so proactive, I have to ESC it multiple times during the day and tell it to wait because I only asked a simple question.
For that claude problem in specific about 95% of the time it will follow the rule that a plan file needs to be made before any changes to the project are allowed. Haven't had to ESC it in a while now during a question, things definitely improved in 5.5.
In my experience the failure mode is more broad than just lazy, the issue is:
* It doesn't do things you ask it to
* It adds things you didn't ask it to
It still does both and therefore I still consider it failing. If you don't want to call it "lazy"; fine, but it seems as though the underlying issue is still there.
Claude does this too, FWIW.