Original Reddit post

Opus 4.7 seems extremely tempting based on the raw benchmark numbers. I’ve tried to work with it a few times after its launch, but almost always I realize it’s extremely difficult, and then I revert back. The official Claude Code team has been saying “it is literal”. But working with an extremely literal model which does not extrapolate any information is difficult in a day to day task scenario. When I ask it to build something—say, an API with endpoints, I assume it will include things like rate limiting and basic authentication as part of it. Sometimes it skips those features; other times it might build it partially. 4.6 always builds the rate limiting if I use the word “production-ready” because it extrapolates. Also, when I’m discussing a big problem and, at the end, I ask a question about a different, small, minor problem, then I say, “Okay, let’s go fix it.” It tends to fix the minor problem we discussed recently rather than the main problem we’re working on. Those kinds of literal behaviors have been extremely difficult. Either I’m should be extremely cautious about how I write my prompts to make 4.7 work (like hand-holding it) or I stick with Opus 4.6, which I’m doing right now. What extra benefit are you getting from 4.7? And is anyone even able to work with it and how did you set it up so you can still work with 4.7? submitted by /u/Putrid-Pay5714

Originally posted by u/Putrid-Pay5714 on r/ClaudeCode

  • Serinus@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    4 days ago

    Why would you expect it to implement rate limiting without saying “rate limiting”?

    I’m guessing this guy isn’t a developer and/or expects this thing to be magic.