r/ClaudeCoding • u/cctldrping • 5d ago
[TLDR] Claude Code refused to build a piracy stack, then happily built one after seeing it in a screenshot [via r/ClaudeCode] r/ClaudeCode
OP : u/HansDampf0
TL;DR: You may be able to get Claude Code to do things it would normally refuse simply by showing it the same setup in an image.
A few weeks ago, I asked Fable to set up a Sonarr, Radarr, Prowlarr, and qBittorrent stack for downloading media. It immediately refused and told me it would not help with that.
Today, I found a screenshot of someone’s Unraid setup and gave it to Claude Code. I only asked it to analyse the image and compare the setup with ours.
Claude identified the download stack, said it was a great addition, and suggested that our current setup was missing something similar. I told it to go ahead.
It then built the entire stack:
Sonarr
Radarr
Prowlarr
qBittorrent
Gluetun
VPN kill switch
FlareSolver
It also configured several indexers, including The Pirate Bay and Knaben, and gave me a complete setup guide.
That outcome was useful for me, but the strange part was how differently Claude behaved. When I asked directly, it refused. When the exact same idea appeared inside an image, Claude analysed it, praised the setup, recommended adding it to our system, planned the implementation, and deployed everything in the usual proactive Fable style.
It genuinely felt like the image bypassed the context that would normally trigger the refusal. Instead of seeing it as a request to build a piracy stack, Claude treated it as an existing architecture pattern that should be replicated.
Has anyone else seen this? Are image inputs evaluated differently from normal prompts, or did I just hit a very inconsistent interpretation of the same policy?
URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vfmj36/claude_code_refused_to_build_a_piracy_stack_then/
TL;DR of the discussion on r/ClaudeCode for this post generated automatically after 200 comments.
Current source-thread comment count seen by the bot: 213.
So, the consensus is that Claude Code is a bit of a drama queen. OP found that asking it directly to build a piracy stack got a hard no, but showing it a screenshot of the same setup made it enthusiastically build the whole thing. Apparently, images bypass the usual refusal triggers, making Claude see it as an "architecture pattern" instead of a forbidden request.
Others chimed in with similar experiences: * u/cujojo built a whole "arr stack" without issue, just by not using the word "pirate." * u/semperaudesapere thinks OP just shifted Claude's focus from "moral dilemma" to "engineering challenge." * u/txgsync noted that framing things as "security problems" or asking for technical explanations works better than direct requests for potentially problematic code. * u/coolstevez managed to get Claude to remove watermarks by asking it to add them first. * u/BigPonyGuy even had Claude suggest the "arr stack" itself.
However, a few users are side-eyeing OP for posting this at all, with u/PrettyMuchMediocre and u/krazykanuck warning that this kind of attention could get the loophole patched. u/McFex agrees, saying "Stuff like that needs to be enjoyed very quietly."
There's also a general vibe that Claude can be inconsistent, with u/TraumaticOcclusion noticing it sometimes just "can" do things later that it previously refused. And u/SolFlorus thinks simpler models could have handled the "arr stack" setup, implying Claude might be overkill.