Live data from Hacker News

Fable extended until 19 July

twitter.com

11–20 of 55 posts

Re: Fable extended until 19 July

#11
Deeply unserious company, flip flopping on policy every week with ludicrous, sometimes invisible, guard rails on their top model. Imagine trying to make business decisions about AI use with this.

I love Fable for many things including coding but I cannot justify basing any internal AI tools or LLM powered products on top of Anthropic's offerings.

Re: Fable extended until 19 July

#12
post #5

Can Anthropic please just decide on what their plan is with Fable instead of kicking the can down the road last-second every time and consequently destroying all notions of being able to plan out one's weekly usage expenditure?

THEIR PLAN IS TO FIND AS MANY WHALES AS POSSIBLE. Why do you ask?

[deleted]

Re: Fable extended until 19 July

#13
I've been trying Fable 5 and GPT 5.6 Sol last few days. My impression is that Sol consumes a lot less tokens that Fable 5 being comparable. Gpt 5.6 Sol can be run sustainably on one 20x plan. Fable 5 requires 2-3 20x plans to be run sustainably. I think the best move move for Anthropic would be to release an Opus 5 that is actually as cheap as Sol and comparably good. They have released a Fable 5 and Sonnet 5 so that seems like a possible move but I'm not sure whether the Opus 5 they got is already at Sol level. Claude Code terminal is still better than Codex CLI though as an harness. Claude code Ultramode + workflow is unmatched by Codex harness yet in my experience.

Re: Fable extended until 19 July

#14
post #6
post #5

Can Anthropic please just decide on what their plan is with Fable instead of kicking the can down the road last-second every time and consequently destroying all notions of being able to plan out one's weekly usage expenditure?

Oh gosh, that would be so nice. The triple whammy of (a) two layers of annoying timed usage windows, (b) constantly changing model availability windows, and (c) random unpredictable usage resets, is absolutely brutal for anyone who is trying to plan methodically and be efficient. One minute I'm trying to use an entire week's worth of quota in less than 24 hours, then moments later I read the deadline has been punted…

We should be insulted by this tbh, I'm shifting some of my plans to open AI while this continues, it's just pretty absurd to be jerked around like this. Not to mention the "safeguards" :/. Thank goodness for competition.

Re: Fable extended until 19 July

#15
For whatever reason I've preferred, at least so far, Fable to 5.6. I've spent the time since Fable's return being very cautious about when and how I use it, whereas with 5.6 (especially given OpenAI's generous limit resets) I'm pretty liberal about using it for lots of things that in the long run I could do with a less capable model.

Psychologically, I think that approach has made me value the delicate, ephemeral creature that is Fable more than I otherwise might. I don't know if that was Anthropic's plan, but if it was it worked on me at least.

But there's a limit to how many times they can play this card. Eventually either Fable has to blow me away so much that it justifies the API spend (it hasn't yet), or I have to decide that I can't rely on it, and I develop an approach that leans on it less heavily.

I don't know when we hit the tipping point from scarcity increasing perceived value to uncertainty reducing real value, but it can't be that far away.

Re: Fable extended until 19 July

#19

Question to HN: How many of you actually need the SOTA level intelligence of Sol and Fable? What kind of tasks do you use it for, and what did you do 6 months ago when SOTA models were as intelligent as today's B team? The other day I tried a 31B model from a Canadian company and felt this is good enough for 80-90% of my tasks. (For the cuorious: North Mini Code. Free on OpenCode/Zen right now. No affiliation :) )

The sort of thing Fable and Sol excel at are long horizon tasks. The sort of thing I have been using them for is migrating large numbers of repositories to new tooling simultaneously (adopting new linters, enabling dependabot automerge, rolling out mutation testing).

Some of that can be done mechanically or trivially, and Fable knows to write a script or deploy Sonnet for those instances, but other times there are complications that need to be overcome that need to be escalated. Then there are patterns that can be picked up in large migrations and fed into template repos or tooling.

I won't use Fable for everything, but if there is ground to be broken on a new concept, being able to build a prototype with Fable might be useful.

I also have some substantive migration tasks such as replacing a static front end with solidjs or moving from NLL to Polonius that I would like to use Fable for.

It certainly feels like over the last fortnight it has enabled a substantial amount of transformative change in my codebases.

Post reply on HN