Something went seriously wrong there, and I'm not sure it's just Claude copying an existing project bug-for-bug. For more context, see also this post from Gruber at Daring Fireball:

https://daringfireball.net/2026/08/retraction_app_store_reje...

▲

firasd 5 hours ago | parent [-]

Yeah... If you even say to Claude I want to make an app like github.com/user/repo it's not gonna just clone it and do some touch ups. Anything can happen of course, but my spidey sense says generally AI won't fork a project unasked (just because of the implied maintenance burden of applying future patches from upstream if nothing else)

	▲	vikramkr 4 hours ago \| parent \| next [-]
		Yeah - the whole Claude did it thing here reads to me like blaming a grammar issue on an LLM. Yes they have their issues but this isn't one of them - they're not deterministic they aren't going to make the exact same bug as a project you never heard of unless it's a specific technical shortcoming/training data gap/skill issue of the model. If you say "I want something exactly like xyz in every way" though then sure - but you're claiming you never asked for that? Not passing the sniff test here
	▲	supriyo-biswas 4 hours ago \| parent \| prev \| next [-]
		I have tried this with Codex, and if you ask it to implement a project based on an algorithm or design in a given repo, it always puts an attribution link saying that part of it was adapted from that repo. Unfortunately I think we’re being duped here.
	▲	mft_ 4 hours ago \| parent \| prev [-]
		Also, Claude has the habit of finding and fixing bugs without being asked - for example, in code that an earlier version of itself wrote. So while you can never be sure, there's a non-zero chance that even if it had copied the original code it would have found and fixed the accidental trap.