{"id":3235,"date":"2026-07-04T12:53:50","date_gmt":"2026-07-04T12:53:50","guid":{"rendered":"https:\/\/silvybrand.com\/?p=3235"},"modified":"2026-07-04T12:53:50","modified_gmt":"2026-07-04T12:53:50","slug":"ai-fanfiction-ao3-claude-detector","status":"publish","type":"post","link":"https:\/\/silvybrand.com\/?p=3235","title":{"rendered":"The fanfiction community is at war with AI \u2014 and itself"},"content":{"rendered":"


\n<\/p>\n

\n
\n

Over the past week, a new fanworks movement has kicked off, with the aim to root out authors using generative AI. But the detection methods being implemented are questionable, and any fanfic writer could be caught in the crossfire.<\/p>\n<\/div>\n

\n

Broad distaste<\/a> around the use of Claude, ChatGPT, and other AI tools has long been a thing<\/em> in creative communities<\/a>, including the world of fanfiction. Readers and writers have passed around tips for spotting supposedly AI-generated works, citing anything from em dashes to the broad concept<\/a> of purple prose. But on June 29th, an anonymous X account called @heatedrivalryai<\/a> promised a seemingly more reliable solution. It posted a skin \u2014 similar to an extension \u2014 for the popular fanfic repository Archive of Our Own (AO3) that would purportedly identify coding artifacts left behind by Anthropic\u2019s Claude bot.<\/p>\n<\/div>\n

\n

\u201cWhen a Claude-generated response is pasted directly into AO3 from Claude, the text is wrapped by a Claude-injected code \u2018font-claude-response-body,\u2019\u201d said the @heatedrivalryai account. \u201cIts presence indicates the use of Claude definitively.\u201d When a user visits a page (like a work of fanfic) with this code, the skin turns the entire background red.<\/p>\n<\/div>\n

\n

Several test posts<\/a> have been published to AO3 that allow users to check if it works. The screen immediately turned red when I tested the skin against these examples myself, and I published a Claude-generated short story to run my own experiment just in case. The red screen appeared when I directly pasted from the chatbot into the editor and vanished if I pasted text (including the exact same generated story) that didn\u2019t come straight from Claude.<\/p>\n<\/div>\n

\n
\n
\n
\n
\n
\"A<\/a><\/div>\n<\/div>\n<\/div>\n

As far as \u201cred flags\u201d go, this is pretty hard to miss.<\/em><\/figcaption>Image: AO3 via The Verge<\/cite><\/p>\n<\/div>\n<\/div>\n<\/div>\n
\n

The Claude detector post was accompanied by examples of fanfic where the artifacts were spotted, which the anonymous creator said was meant to demonstrate the system works, not \u201ccreate an environment of mistrust or accuse particular users.\u201d But fanfic communities have quickly mobilized to publicly name and shame writers whose published works were flagged by the tool, and its creator certainly doesn\u2019t consider AI a positive thing. \u201cFandom is a uniquely connective, collaborative space. It thrives on the human element and the creative spark which drives it and feeds off it,\u201d they said. \u201cIf we unknowingly allow AI to corrupt these spaces, what will be left of them?\u201d<\/p>\n<\/div>\n

\n

Anthropic did not respond to my request to verify if the fan-made Claude detector works as described. The methodology here does look sound, however, and our own testing backs it up. There\u2019s no apparent reason for the Claude code to be present in a story if the bot wasn\u2019t used somehow. But there\u2019s a clear risk of both false negatives and overgeneralizations.<\/p>\n<\/div>\n

\n

The code wrapping is only preserved if text is copied directly from Claude into AO3\u2019s editor, so it won\u2019t catch anything edited in Google Docs or Microsoft Word and then moved to AO3 \u2014 and as someone who writes for a living, I can testify to how risky writing straight into a CMS is. Some writers who have been flagged have already updated their works to remove the artifacts, and future works can easily evade the tool.<\/p>\n<\/div>\n

\n

Conversely, the tag doesn\u2019t reveal how heavily Claude was used in a given work. That flashbanged scarlet screen could mean the entire story was fully AI-generated, or that an author pasted a few human-written sentences into Claude for spell-checking or translation, then moved them back into AO3.<\/p>\n<\/div>\n

\n

That hasn\u2019t mattered to some fandom members, who view any<\/em> use of generative AI as an inexcusable betrayal to the wider creative community. Many people cite concerns over the environmental impact of the technology and how it\u2019s trained by scraping the open web, which likely includes fanworks uploaded to platforms like AO3.<\/p>\n<\/div>\n

\n

This particular tool\u2019s applicability is limited \u2014 AO3 isn\u2019t the only platform for publishing fanworks, and Claude is just one of many AI models. At least one person claims<\/a> they\u2019ve written separate code that can detect \u201cClaude, Deepseek, and some ChatGPT\u201d usage, but they haven\u2019t released that solution to the public or explained how it works. I asked Google and OpenAI if their models leave any traceable artifacts in text generation that could be detected by similar means, but they haven\u2019t responded.<\/p>\n<\/div>\n

\n

In fact, it\u2019d be highly surprising if a universally reliable system existed. I\u2019ve been reporting on the issues<\/a> surrounding AI detection<\/a> for a few years now, and to my knowledge, there isn\u2019t<\/em> currently a reliable technological solution for distinguishing generated text from that typed out by human hands. Systems like C2PA Content Credentials and Google\u2019s SynthID are making some progress toward identifying generative AI in images, videos, and even audio, but these rely on invisible watermarks and metadata that don\u2019t carry over for copy-pasted text.<\/p>\n<\/div>\n

\n
\n

AI companies have every incentive to at least solve the problem internally<\/p>\n<\/div>\n<\/div>\n

\n

That could change in the future, and AI companies have every incentive to at least solve the problem internally. Early models were trained on text indiscriminately scraped from the internet, and as human writing is crowded out by its synthetic counterpart, they could risk a \u201cmodel collapse<\/a>\u201d scenario that would degrade the accuracy of outputs.<\/p>\n<\/div>\n

\n

For now, though, fandom communities are still mostly relying on vibes. Most fanfics aren\u2019t judged by a tool like the AO3 skin, but by \u201ctells\u201d that could include anything from specific sentence structures \u2014 like the notorious \u201cit\u2019s not X, it\u2019s Y\u201d \u2014 to overuse of flowery metaphors. (At least nobody in fandom, so far, has benches becoming men<\/a>.) But we have to remember that AI often Writes Like That<\/a> because it was trained on stuff that real people have written. It\u2019s trying to replicate us. I\u2019m not bold enough to share my own AO3 bookmarks, but I\u2019ve definitely read some overly grandiloquent fanfics in the pre-ChatGPT internet days that wouldn\u2019t pass this dubious sniff test.<\/p>\n<\/div>\n

\n

The best solution for distinguishing AI works on AO3 is already available: the site\u2019s robust tagging system. A \u201cCreated Using Generative AI<\/a>\u201d tag exists, and many authors do include it to disclose the use of tools like Claude. That requires honest transparency, though, and there\u2019s little incentive for honesty given the backlash. It\u2019s also worth remembering that fanfiction is supposed to be a hobby, not a regulated industry.<\/p>\n<\/div>\n

\n

With these efforts to prevent AI from taking eyeballs away from genuine human-driven creativity, authors who don\u2019t conform to what\u2019s deemed to be an acceptable quality of writing may become innocent victims of the ongoing witch hunt. At least one writer has already been caught up in this because another person they trusted to edit their fic<\/a> did so using Claude. So if the next fanfic you read feels a little robotic, just bear in mind that it might not actually<\/em> be the product of a robot.<\/p>\n<\/div>\n

Follow topics and authors<\/strong> from this story to see more like this in your personalized homepage feed and to receive email updates.<\/span><\/p>\n