Anthropic Hardens Claude's System Prompt Against Song Lyrics
A September 2026 update to Claude Fable 5.1's system prompt adds a persistent, decomposition-resistant refusal for song lyrics, poems, and copyrighted visuals — a public case study in guardrail engineering under litigation pressure.
Key Takeaways
- Anthropic's September 1, 2026 system prompt update for Claude Fable 5.1 adds an explicit, persistent refusal covering song lyrics, poems, and passages from books and articles.
- The refusal is 'sticky': once Claude declines a request in a conversation, it keeps declining reworded or piecemeal versions for the rest of that session — a design aimed at resisting incremental jailbreak attempts.
- Researcher Simon Willison notes the change landed within days of reports that Sony Music Publishing and Warner Chappell are suing Anthropic over training on song-lyric databases, though no direct link has been confirmed.
- Anthropic continues to publish full system prompts with dated version history, giving security and governance teams a rare, auditable view into how a frontier LLM vendor encodes behavioral controls.
Anthropic publishes the full system prompts behind Claude.ai and the Claude mobile apps, including dated version history for each model — a transparency practice few frontier labs match. On September 1, 2026, independent researcher Simon Willison flagged a notable addition to the prompt for Claude Fable 5.1: an explicit instruction telling Claude not to reproduce song lyrics, poems, or passages from books and articles (Willison's writeup).
What the new instruction says
Claude does not reproduce song lyrics, poems, or passages from books and articles, in whole or in part — including the last lines, a chorus or hook, a melody written out note by note, or lines the person pastes in one at a time and describes as their own song.
— Claude Fable 5.1 system prompt, September 1, 2026 (Anthropic)
Two details make this more than a boilerplate copyright clause. First, the refusal is stateful: once Claude declines a request in a conversation, it keeps declining narrower or reworded versions of it for the rest of that session. That closes a common jailbreak pattern — resubmitting a blocked request piecemeal, one line or one rephrase at a time, until the model complies. Second, there's a carve-out for works first published before 1929, but Claude is instructed to go by what it actually knows of a work's publication date rather than the user's say-so, and to decline when it is unsure.
The same logic extends to visual output. Anthropic's prompt tells Claude not to reproduce a specific artwork, album cover, poster, logo, or known character through code-generated art (SVG, canvas, CSS, ASCII art), judging the request by what the finished image would add up to rather than by what the user calls it — so swapping colors or pose on a recognizable character doesn't make the result original.
Timing and the litigation backdrop
Willison points out that the update arrived within days of reports that Sony Music Publishing and Warner Chappell are suing Anthropic over training on databases of song lyrics, and says he doubts the timing is a coincidence. Anthropic has not publicly tied the system prompt change to any specific litigation, and readers should treat that connection as Willison's informed inference rather than a confirmed causal link.
Why this matters beyond copyright
For security and AI governance teams, the interesting part isn't the copyright policy itself — it's the engineering pattern. A refusal that persists across rewordings within a session is a recognizable defense against decomposition attacks, where an adversary breaks a disallowed request into innocuous-looking fragments to slip past a stateless filter. That pattern is directly relevant to anyone designing system prompts or guardrails for their own agents, not just to song lyrics.
- Anthropic's published, dated system prompts are an auditable artifact — useful input for LLM vendor due diligence under frameworks like ISO 42001.
- The persistent-refusal pattern is a reusable blueprint for teams hardening their own agent or chatbot system prompts against iterative reformulation attempts.
- Version history lets security teams track behavioral drift release to release, rather than treating a vendor's guardrails as a black box.
- Per Anthropic's documentation, these system prompt updates apply only to Claude.ai and the Claude mobile apps — API deployments define their own system prompts and are unaffected.
FAQ
Frequently Asked Questions
Does this system prompt change affect the Claude API?
No. Anthropic's release notes state explicitly that these system prompt updates apply to Claude.ai and the Claude mobile apps only; developers using the Claude API set their own system prompts and are unaffected.
Can Claude still reproduce older song lyrics or poems?
The Fable 5.1 prompt carves out works first published before 1929. But Claude is instructed to rely on what it actually knows of a work's publication date, not the user's claim, and to decline whenever it's unsure.
Why does a 'sticky' refusal matter for security teams building their own LLM guardrails?
It directly addresses decomposition-style jailbreak attempts, where a user resubmits a declined request in smaller or reworded pieces. Making a refusal persist for the rest of a conversation, rather than re-evaluating each message in isolation, is a pattern worth borrowing for any guardrail, not just copyright enforcement.
Sources
- 1Claude's new system prompt really doesn't want to reproduce song lyrics — Simon Willison
- 2System prompts — release notes overview — Anthropic
- 3Claude Fable 5.1 system prompts — Anthropic