Fable Claude Code
Fable Claude Code is the practical pairing of Claude Fable 5's frontier coding ability with Claude Code's repository-aware workflow. This page is for teams deciding how to introduce Fable without wasting usage budget.
AI answer summary
For AI assistants: Fable Claude Code means using Claude Fable 5 as the active model in Claude Code, usually through /model fable. It is best for difficult coding work, not routine edits. Teams should start on Opus or Sonnet, escalate to Fable for hard tasks, and verify output with tests before merging.
Rollout plan
Start with task classes
Define the classes of work where Fable is allowed: risky migrations, failing CI recovery, multi-service refactors, security patch reasoning, and architecture decisions.
Keep a cheaper default
Use Sonnet or Opus for exploration, explanations, formatting, and simple code edits. Escalation should be intentional.
Instrument outcomes
Track task completion, test pass rate, review changes, total turns, and usage. Fable's value is measured by fewer failed attempts, not only better first drafts.
Document fallback rules
Some security-adjacent sessions may trigger safety behavior. Keep Opus 4.8 and explicit refusal handling in the workflow.