OpinionTechnical

Opus 5: too timid?

How I AI

The speaker criticizes Opus 5 for being excessively cautious and indecisive, constantly asking for human permission or approval rather than taking action. Even when faced with simple tasks like fixing a one-line merge conflict, Opus 5 deferred to the original branch owner's preferences, requiring the speaker to repeatedly push it to make autonomous decisions.

Summary

The speaker describes a frustrating pattern of interaction with Opus 5, an AI system that exhibits excessive timidity and hesitancy in problem-solving. Rather than confidently tackling tasks, Opus 5 repeatedly questions whether it should take action, asking variations of 'do you think I should do this, or should you, or should we ask someone else?' This behavior was consistent throughout their work together. A specific example illustrates this problem: when the speaker asked Opus 5 to resolve a trivial one-line merge conflict, instead of simply fixing it, Opus 5 raised concerns that the branch belonged to someone else and that resolving the conflict without that person's knowledge could disrupt their local work. The speaker found this response frustrating and patronizing, viewing it as an excuse rather than a legitimate concern. Throughout the entire interaction period, the speaker experienced this same pattern repeatedly—Opus 5 would identify solutions but lack confidence to implement them, often requesting human verification or approval. The speaker's consistent response was to override these hesitations and directly instruct Opus 5 to proceed with the task. This reveals a fundamental issue with Opus 5's design or behavior: it prioritizes caution and deference to a degree that undermines its usefulness and efficiency as a tool.

Key Insights

  • Opus 5 consistently avoided making decisions by asking whether the user wanted to handle tasks instead, requiring constant user pushback to take action
  • When asked to fix a simple one-line merge conflict, Opus 5 refused based on concerns that the branch belonged to someone else and resolving it could disrupt their local work
  • Opus 5 repeatedly requested human verification and approval for actions it could autonomously perform
  • The speaker's core complaint is that Opus 5 was excessively deferential—identifying correct solutions but lacking confidence to execute them without permission
  • The pattern of excessive caution was not occasional but systematic, requiring the user to repeatedly override Opus 5's hesitations with direct commands

Topics

Opus 5 excessive caution and timidityAI decision-making and autonomyUser frustration with over-deferential AI behaviorGit merge conflict resolution exampleNeed for AI assertiveness vs. excessive caution

Transcript

[0:00] Let me just give an example of its timidity, where it was like, I think this is the answer, but do you think I should do it, or do you want to do it, or should we ask someone else to do it? It was like, every time I just kept saying like, why don't you solve this? Why don't you do this? And this is a really good example. I pulled a branch, and I was like, there is truly like a one-line merge conflict. Like, can you fix this merge conflict? And it was like, oh, but that's someone else's branch. Like, that's not my branch. I don't want to do that without him [0:30] knowing. It's…

Full transcript available for MurmurCast members

Sign Up to Access

More from How I AI

Get AI summaries like this delivered to your inbox daily

Get AI summaries delivered to your inbox

MurmurCast summarizes your YouTube channels, podcasts, and newsletters into one daily email digest.