Live data from Hacker News

Claude Fable is relentlessly proactive

simonwillison.net

411–420 of 748 posts

Re: Claude Fable is relentlessly proactive

#411

It feels like Fable is slightly smarter but overall worse tool exactly due to this. It's constantly turning what should be 50 LOC patch of a single prompt into 30 minute exploration that is totally not worth it. Often wrong even. I trialed it on some rather simple stuff - backfill redis dedupe cache when the hash function changed: instead of running new hash func on every db value to expand the cache it implemented s…

I actually think internally they knew they hit diminishing returns awhile ago.

They’ve been doing a lot of strategic introduction and manipulation in the run up to the IPO, and it’s worked in that regard.

Re: Claude Fable is relentlessly proactive

#413
post #370

Earlier quoted context omitted.

People are missing that Willison is among the very best people we have in the role of (for lack of a good name): early access to frontier models, evaluate them in real scenarios, no wishful thinking, hype, or doom, communicate the possibilities. Yes he could have fixed this himself but then he would have learned nothing about the AI, and we wouldn't have read a fascinating and important article.

>> he would have learned nothing about the AI there is absolutely zero value in spending time to learn about new models as in few months new model will be out and whatever you learned about the current one will be useless. Also with models getting better and better you have to know less and less to achieve same results.

you know, women make a big deal about you meeting their father/parents, and honestly, I'm too autistic to really fucking have put any importance until now as to why that was remotely important, but if N+1 is coming for your job, it seems it might be worth your while to know the capabilities of N, no?

Re: Claude Fable is relentlessly proactive

#414
post #127
post #98

Earlier quoted context omitted.

Lines of code for a bugfix is a really bad proxy for effort required. You should estimate how much time it would have taken a human

30 seconds or a minute? Look at the diff he links to: https://github.com/datasette/datasette-agent/commit/a75a8b72... Every browser has an inspector that can show you which element is causing overflow. You walk through the tree, find the offender, and add min-width or overflow. Zero tokens, just like in the old days! Now, granted, because the garbage LLM code he’s working with has CSS inside HTML inside JavaScript in…

A small diff /= a small change! They are completely separate things. Quite often a small diff is hours of actual work. Even in this case _finding_ those lines could have taken work - we don't really know.

Re: Claude Fable is relentlessly proactive

#415
post #127

Earlier quoted context omitted.

30 seconds or a minute? Look at the diff he links to: https://github.com/datasette/datasette-agent/commit/a75a8b72... Every browser has an inspector that can show you which element is causing overflow. You walk through the tree, find the offender, and add min-width or overflow. Zero tokens, just like in the old days! Now, granted, because the garbage LLM code he’s working with has CSS inside HTML inside JavaScript in…

A small diff /= a small change! They are completely separate things. Quite often a small diff is hours of actual work. Even in this case _finding_ those lines could have taken work - we don't really know.

Did you actually look at the diff, though? That’s the kind of change you make 10 times a day while working on frontend. It is a tiny change.

Re: Claude Fable is relentlessly proactive

#416
post #99

Earlier quoted context omitted.

$12 worth, it seems

Imagine telling someone in 2015 that you can just tell your computer to fix a 2-line CSS bug and it only costs $12

Or even in 2026. You absoutely will pay a human that for that work.

Re: Claude Fable is relentlessly proactive

#417
post #402

Earlier quoted context omitted.

I was trying to capture the idea that Claude Fable will act a whole lot more aggressively in pursuit of the goals that you set it than other models I've worked with. The case I described is a good example of this. I told it to fix a scroll bar, and it built test HTML pages and a throwaway Python server and tried several ways of testing in a browser before settling on a weird Frankenstein mechanism because it identifi…

It's not being aggressive, it's just trying throwing shit at problems until it sticks... or doesn't. That doesn't make it smart or aggressive, if anything it's just been turned to crank tokens until something happens, which doesn't make it a good model. Why are you positively anthropomorphizing this? It's an LLM, it's been tuned via RL, and it's been tuned by engineers at Anthropic to use a metric fuck-load of sub-ag…

I don't think calling a model "relentlessly proactive" is positive anthropomorphism.

Spinning up 50 unnecessary subagents is exactly what I'd expect from a "relentlessly proactive" model.

Re: Claude Fable is relentlessly proactive

#419
post #81

Honestly -- the thing that has impressed me the most about Fable is how diligent it is about testing its own changes. I think this is exactly what Simon is picking up here - Fable is absolutely heckbent on screenshotting that darn scroll bar and will stop at NOTHING until it manages it! In my own use I was also impressed how it proactively installed Playwright and set it up to test a FE change. The previous models tr…

Yes I had a fun experience where it kept on timing out on a seemingly mundane task and it turned out I had written the ask in a way that was impossible to test

Re: Claude Fable is relentlessly proactive

#420
post #395

Earlier quoted context omitted.

>> he would have learned nothing about the AI there is absolutely zero value in spending time to learn about new models as in few months new model will be out and whatever you learned about the current one will be useless. Also with models getting better and better you have to know less and less to achieve same results.

My experience has been the exact opposite. As the models get better you need to know more about their capabilities, because otherwise you risk prompting Claude Fable 5 like it's GPT-4o and complaining loudly about how it's all hype and nothing about these models is improving at all (yes, I do see people say that.) Getting the best results out of these models requires skill, experience, intuition, and domain expertise…

Isn't the whole point of a better model that it should be better at understanding you than the previous one? So the same prompt should return a better answer.

Prompting differently to the new model seems entirely backwards when trying to determine if the model has improved.

Post reply on HN