Capturing some Fable impressions after a day of use:
- Expect your laptop to heat up and your token budget to drain fast
- The bottleneck you are most like to hit is your own micromanagement. Fable does best with larger, more abstract, harder directives. A great spec is still important. Habits trained on 4.6-4.8 have taught us to get granular and review specific output, which ends up hampering Fable. Try loosening up your harness / gates / restrictions and test trusting it with more open-ended goals.
- Use subagents with cheaper models. Instruct Fable to help you. If you use Fable for everything you're going to take an hour, spend your whole allowance, and not get much back. Fable's great so far at managing Opus and Sonnet-level agents. So, you want Fable to be your design partner and air traffic controller, but directing the cheaper agents and then verifying their work.I'm having luck taking this a step further and using Opus as the verifier, and Fable mostly sticks to final review and design.
- Corollary to above, the next ~2 weeks are a great time to ask Claude to do something big that's been bugging you and you don't think is possible. There's a real chance it can oneshot a working version and surprise you. And we only get these next two weeks with it, so try making them count.
- Ask it to create rich HTML pages for you as explainers, to reflect your design choices, as a spec that agents execute against... basically any time you need more detail than a terminal output. It's slow, so you don't want to do it every time, but Fable's great at rich visualizations. The theme again is "it will surprise you." I'm finding this super helpful for driving my understanding of what it's trying to do.
- Fable's great at pretty graphs and visualizations that can be user-facing, too.
- It will still pattern match you and gas you up, so be careful with how prescriptive you're getting, and watch for when it starts seesawing back and forth.
- Keep an eye on how it uses those permissions. Fable's quite smart at workarounds and might make you nervous by doing so. I had it working on a login auth screen, and when testing, I saw it 1) launch a webpage 2) use the webpage and 3) put in a password and click the "I am human" button to clear the captcha, then nix the webpage. Which spooked me out a bit 🙂 turns out it's because I have Playwrite (a web control toolkit) installed, so it thought "hey cool I'll just use that."