I canceled my Claude subscription, though I did get some utility out of it, because of how much steering was required to use it on complex projects. A big reas

I canceled my Claude subscription, though I did get some utility out of it, because of how much steering was required to use it on complex projects. A big reason being that anyone who is using Fable seriously will run out of usage limits very quickly, and so will lean on the "Fable for review + design discussion, Opus 5 agents for implementation" paradigm. But an incredibly annoying UX problem is that the resulting report from the agents that Fable reads isn't surfaced to us in the main dialog, it's only summarized back to us (unless you idle in the agent's window to avoid it closing so you can read what it said directly). As a consequence of this game of telephone, the Fable agent will start using some "terms of art" that it and the agents invented, leaving out literally all context that would be useful in helping me understand what converged/diverged from the implementation attempt. It will often try to ask me for input or say that I have to deliberate on something while also referring to things I've never seen (from the agent result) and without providing any context. I have to repeatedly prompt it to verbosely explain every time (putting it into the system prompt did little to improve this) and remind it that I can't see what the hell it's talking about. I'm not sure I'll re-subscribe or even really use AI again because it's honestly more frustrating than it's worth, and so the net emotion I'm left with is frustration and without the satisfaction of learning + building something myself. But at the very least, I thought I'd give someone at the company a tip on what seems to me like a common and obvious UX/UI/workflow failing for using Fable, as some last bit of good will.