I just experienced an interesting thing for the first time. I was watching Opus run a large refactor and it launched a bunch of agents to work on things (that’s normal). What wasn’t normal was that Opus was monitoring progress of the agents in real time and would make statements noticing that changes were “unexpected” and then undoing the work the sub agents were doing while they were still running. And then Opus would check to confirm it had successfully undone the changes and the agents had already either made more changes or restored the changes Opus was trying to undo. And this kept escalating. Anyway I was morbidly curious about what was going on and kept watching it. Ultimately everything finished but it was interesting to watch and think about how much churn and wasted cycles were happening caused by agents stepping on each other. This is the only time I have seen this happen and otherwise I’ve never had those “my usage was burned up instantly” situations previously. Anyway I don’t really know what happened. One theory I am pondering is whether Opus somehow lost control of the sub agents or accidentally launched multiple agents with overlapping tasks. It was interesting! But also funny and relatable (as a parent) watching a harried Opus trying to keep decorum and muttering about its brood while trying to keep things from going to hell. submitted by /u/thirst-trap-enabler
Originally posted by u/thirst-trap-enabler on r/ClaudeCode
You must log in or # to comment.