points by n0on3 1 day ago | 0 comments
Speaking for a user-facing use, not autonomous coding or agentic workflows: Fable 5.1 choice of words and general “words salad” expression are horrific. It starts not so good, then as the context grows (still way below any reasonable rotting threshold) it gets completely insane. It’s pointless for a model to be extremely capable if it gives you brain damage. I don’t know if it’s because of the watermark thingy, all I know is it gives me pure rage flares and every time I give it a shot I regret it. And there is no way to steer it away from this, anything I tried, both instructions and harness-wise, either failed or got forgotten/ignored after a while. I really hope the next Fable class moves completely away from whatever they did there to cause this.
Opus 5.5 in comparison is a bit more verbose and appears to settle on evaluations before the depth reached by Fable on very complex stuff, but is still vastly capable and I can read its output without wishing it had a physical form I could punch in the face.
[–] maxerickson 1 day ago
[–] n0on3 22 hours ago
I cannot answer that from direct experience for the latest models. At this point I’ve got pretty good even to eyeball how to chop the work across multiple sessions myself if needed, and depending on how you work on your projects a good harness configuration with proper instructions to delegate portions to dedicated agents plus periodic handoff to a persistent memory mechanism can get you very far. 1M tokens are a lot already, just try to stay way within it for each portion and avoid the need for compaction when possible.
I've been experimenting with a project that is not growing real fast, but wondering about the risk as I try to make it do more.