Claude Fable 5.2 Refactoring Changes With Code-Ownership Prompts
Anthropic’s documentation says Claude Fable 5.2 responds closely to code-ownership wording when working on a codebase. In Anthropic’s testing on small coding tasks, the model merged repeated code in about half the attempts when prompted that the codebase was its own, compared with fewer than one in ten attempts without that wording. Simon Willison’s Weblog quoted these findings from Anthropic’s “Prompting Claude Fable 5.2” documentation.
The vendor-reported result suggests that explicitly assigning code ownership can materially influence whether Claude Fable 5.2 preserves or restructures existing code during small coding tasks.
A quote from Prompting Claude Fable 5.2
Simon Willison’s Weblog
Sponsored by: Dynatrace — Your coding agent can read your code but can’t see how it runs in production. Read the blog to see how Dynatrace MCP closes that gap.
10th November 2026
Claude Fable 5.2 pays close attention to who owns the code it works on. In Anthropic’s testing on small coding tasks, the model tended to add to the existing structure when the prompt said nothing about ownership or presented the code base as someone else’s, even when that duplicated existing code. When the prompt said the code base was the model’s own, it often consolidated duplicated code and sometimes made related fixes without being asked. If you want the model to improve the structure as it works, say that the code is its own:
You are the owner and long-term maintainer of this codebase, and its design is up to you.The ownership sentence makes the model much more likely to consolidate duplicated code into one shared function. In Anthropic’s testing on small coding tasks, the model consolidated duplicated code in under 10 percent of runs without the sentence and in about 75 percent of runs with it.