If only Claude didn't constantly drop to less capable models whenever it encountered anything vaguely cybersecurity related (despite being part of the Anthropic Cyber Verification Program and having Mythos access, albeit limited).

We're strongly pushing for a move to a mix of Codex and open models at my workplace because of Anthropic's ridiculous nanny-ing.

Yep, gotta really mind the language, sometimes saying something like “when implementing <foo> feature you gotta pay attention to <bar> to avoid <baz> attack” is enough to trigger it, along with a cache miss of 300k tokens in the downgraded request to rub it in. Frustrating.

These types of flip flop posts are the new security theater. One week Anthropic will post a doom and gloom about how open weight models running a fraction of a token per second on your Grandma's popped Android TV is a national security threat and the next week they'll tell you how awesome their 200+ billion parameter model is at doing something they don't actually allow you to do because they gatekeep all the normies. I really do hope history remembers them correctly, but I'm sure they'll be attributed as being a significant and load bearing linchpin during the new world order of LLMs.

Having a big brother on the frontier models in the cyber verification program defeats the whole purpose of the program. My team has found ourselves leaning the same direction your team is going. I was looking into GLM 5.3 to host in our env and come to find there is an article from anthropic trying to say that model is "dangerous" and/or not good compared to their models.

Also in the CVP and kept tripping cyber a couple days ago due to an MCP server that had the ability to connect to remote devices. Maybe it thought I was trying to make a C&C server. But you literally have to start the MCP first, have it generate a key, give the key to the remote device and then it'll generate its key, then give that key back to the MCP server before they can connect.