7 ms·
Ever since Opus 4.7, the model has been tuned to emit such complex commands that not only a human can’t reasonably review them in reasonable time, even a fairly
by oefrha 1mo ago
Ever since Opus 4.7, the model has been tuned to emit such complex commands that not only a human can’t reasonably review them in reasonable time, even a fairly sophisticated command approval framework I built over time that broke down shell commands/scripts into separately approvable/whitelistable units—with its own mini DSL—got completely lost; it worked great up to Opus 4.6.
So not surprisingly, auto mode is the only sane way to use Opus 4.7+.
- stefan_ 1mo agoIt's really getting extremely obnoxious. There is no point to the whole "shell commands output" view anymore because the model aggressively redirects everything to some scratchpad file, so besides the output viewer being a broken mess, it doesn't show anything regardless. My favorite is when it wraps commands in convoluted pgrep wait patterns that end up matching it's own bullshit, and thus never exit. It also feels like Opus 5 will now always write some adhoc Python script to MAKE UPDATES TO FILES, which seems extremely terrible. The complicated shell commands also constantly trip up against quoting rules, requiring another iteration.