I must admit I was drawn to Claude because of their (obviously successful with me) publicity stunt about "being too dangerous to make widely available", when Mythos came out.
It's a shame because I was really looking forward to use it specifically to find potential security holes in my own software.
That being said, Opus 4.7/4.8 have been quite useful already, especially for finding things in the harder to test, non-happy paths.
If I recall, Fable 5 is supposed to be basically Mythos which falls back to Opus 4.8 when dealing with cybersecurity. I wonder if that also includes "finding bugs that could lead to security exploits".
Is Opus 4.8 equally or more capabale for the actual mechanics of the coding work?
It seems to me that having a powerful Fable layer for the planning, coordination, orchestration-type work and delegating to a suitable model for the actual execution of "coding tasks" is perfectly appropriate, if that is the case.
That aside, they said "some routine tasks like coding and debugging". Since I'm using it for coding right now and it's notably better than Opus 4.8, I think what they mean is that some coding and debugging tasks will fall back.
This is a misinterpretation. Fable 5's acceptable use policy has false positives during some coding tasks, and that's what they were talking about. But I've been using it for web dev tasks since it relaunched today, and it's worked fine without fallback.
(On a firmware-customization project involving a ghidra MCP, it triggered and switched to Opus; that was sort of expected.)
17 comments
[ 4.1 ms ] story [ 41.7 ms ] threadIt is one thing if I, as the user, choose to down-level but Claude shouldn't do this on its own.
Not like you can tell the difference if you dont own any of the implementation.
"You won't be charged Fable prices for rerouted requests. Learn more about how the fallback experience works."
https://www.anthropic.com/claude/fable Under "Safeguards"
It's a shame because I was really looking forward to use it specifically to find potential security holes in my own software.
That being said, Opus 4.7/4.8 have been quite useful already, especially for finding things in the harder to test, non-happy paths.
If I recall, Fable 5 is supposed to be basically Mythos which falls back to Opus 4.8 when dealing with cybersecurity. I wonder if that also includes "finding bugs that could lead to security exploits".
It seems to me that having a powerful Fable layer for the planning, coordination, orchestration-type work and delegating to a suitable model for the actual execution of "coding tasks" is perfectly appropriate, if that is the case.
Gave it a small coding challenge. It wrote the code just fine.
That aside, they said "some routine tasks like coding and debugging". Since I'm using it for coding right now and it's notably better than Opus 4.8, I think what they mean is that some coding and debugging tasks will fall back.
(On a firmware-customization project involving a ghidra MCP, it triggered and switched to Opus; that was sort of expected.)