alt Hacker News> One of my key complaints with Opus 5.5 so far has been that sometimes it'll execute long-running commands in a way that is blocking any further input or it starts doing stuff without providing much visibility.
Is this a problem with the model or the harness in your opinion?
Replies
sceptic123 • today at 10:06 AM
Not the parent, but I've seen it and it's hard to say, 5.5 was being stupidly proactive in monitoring a long-running process in a sub-agent to the point of chowing tokens by continually monitoring.
I queried it and was told that sub-agents can't run processes a blocking fashion, I'm not sure the harness changed, or the model was handling it differently, but it require some changes to skills to prompt around it.
➕ show 1 reply
I have no idea how to evaluate this, but I've had it write down the same rule like 3 times and it still keeps managing to fall into this trap of blocking on commands. The fact that it refuses to adhere to my guidelines and rules is probably a model issue, but a better harness could probably overcome the issues.