Claude Fable 5.1 and Claude Mythos 5.1
761–770 of 1001 posts
Re: Claude Fable 5.1 and Claude Mythos 5.1
#762To be honest, these frontier model releases have become boring for me. Opus 4.8 was already good enough for most of my use cases. I don't have any projects right now that I would use Fable for instead of Opus. So when I see announcements like this I just think "that's cool I guess" and then go back to using weaker/cheaper models. What's far more exciting right now is models like DeepSeek V4 Flash and GLM 5.3 Flash. T…
Re: Claude Fable 5.1 and Claude Mythos 5.1
#763(I work at Anthropic) Beyond all the benchmarks, I think Fable 5.1 is a big improvement in writing style. It sounds a lot less stereotypically like other Claude models, has (imho) a much more natural style, and responds to my style instructions more reliably. More work to be done (and we will!) but reading better prose makes me so much happier. Another point I expect not to get much attention until it all happens at…
I have a pet theory that the Opus prose style/smell we all have grown weary of is due at least in part to the models writing more for themselves and each other than for humans. They're packing lots of signal into fewer words and they don't care if it sounds cringe because it works better as glue in long-running tasks. I'm also thinking of the 2017 novel "Void Star" where AIs who operate everything have long since lef…
What does this means?
Re: Claude Fable 5.1 and Claude Mythos 5.1
#764Re: Claude Fable 5.1 and Claude Mythos 5.1
#765> For example, in testing by the investment firm Millennium, Fable 5.1 found the cause of a rare crash on their internal systems that none of their engineers (or any other model) had been able to explain after several years of trying. Say what you will about LLM-generated code, but stories like this give me hope that software will never be as buggy as it once was.
You have a serious engineering problem if you're not able to find the source of a crash after years.
Re: Claude Fable 5.1 and Claude Mythos 5.1
#766Earlier quoted context omitted.
You have a serious engineering problem if you're not able to find the source of a crash after years.
You are either seriously naive, or have never worked on any large and complex legacy codebase.
So it’s not that I haven’t worked on large-scale, complex legacy systems - but that I haven’t worked on any large-scale, complex legacy systems written in languages bereft of runtime reflection and verbose error reporting.
—————
It’s also possible that the bug was never found because its impact was so minimal: e.g. 1 crash per year, each causing 3 minutes’ downtime in a noncritical system: that’s something that will never get investigated fully.
Re: Claude Fable 5.1 and Claude Mythos 5.1
#767On both my work (Team Premium) and personal accounts (Max 20x), Fable 5.1 hit the 5-hour limit before it could finish the first task I gave it. On my work account, it took about 30 minutes, and on my personal account, less than an hour. This has never happened to me before, but if this is normal behavior, Fable 5.1 is essentially unusable.
Re: Claude Fable 5.1 and Claude Mythos 5.1
#768> For example, in testing by the investment firm Millennium, Fable 5.1 found the cause of a rare crash on their internal systems that none of their engineers (or any other model) had been able to explain after several years of trying. Say what you will about LLM-generated code, but stories like this give me hope that software will never be as buggy as it once was.
I sometimes have that feeling too, then ask another LLM to do a code and vulnerability review and OMG: rookie mistakes, over complications and security gaps even a 1st year student would not make regularly. So.. one more year of untreated bipolar AI psychosis I guess..