Yes, Claude Code can decompile itself. Here's the source code

Perceived Security Impact and Alarmism

• Several commenters see this as just making existing reverse‑engineering and decompilation workflows faster, not a fundamental new security threat.
• Blue teams are more focused on control bypass and data protection than on whether code can be reverse‑engineered; once data hits a screen, it’s assumed compromised.
• The tone of the article is widely viewed as sensationalist and possibly self‑promotional rather than a sober security analysis.

Quality and Validity of the “Decompilation”

• Multiple readers inspected the published “decompiled” Claude Code repo and report it does not compile, lacks original prompts, URLs, identifiers, and appears to be largely hallucinated code.
• Critics argue the author didn’t validate functional equivalence, yet presents the result as an actual decompilation.
• Others point to an alternative GitHub reverse‑engineering effort as a more serious, grounded analysis.

LLMs, Deobfuscation, and Decompilation Limits

• Consensus: LLMs are very good at de‑minifying/transpiling JavaScript and inferring structure, names, and types, which is genuinely useful for understanding obfuscated code.
• However, claims about binary “decompilation” are clarified: prior examples relied heavily on string analysis and inference, not true reconstruction of optimized machine code.
• A long subthread debates information loss in compilation/minification: variable names, structure, and some semantics are unrecoverable; LLMs can only guess, sometimes producing code more readable but not original.
• People speculate about future use with tools like Ghidra and on tasks like porting C Python modules to nogil APIs, but emphasize subtle race conditions and training‑data gaps.

Business Models, Licensing, and “Clean Room”

• Commenters reject the idea that this “invalidates” closed‑source or mixed models; customers pay for support, maintenance, and compliance, not just source secrecy.
• The blog’s assertion that restrictive licenses “no longer matter” is challenged: derivative works can still infringe, and this is not a true clean‑room process.
• Genuine clean‑room would require a strict spec‑writer vs implementer separation; some suggest LLM‑mediated two‑step workflows as a possible future variant.

Anthropic’s Distribution Choice

• Some question why Claude Code is shipped as an npm package but not open‑sourced, arguing community study could create positive network effects.
• Others note competitive reasons and licensing concerns, though skeptics say much can already be inferred from API traffic.

Writing Style and Motivations

• The article’s style is heavily criticized as clickbaity, “influencer‑tech” prose; some readers abandoned it midway.
• A minority find it entertaining or refreshing, but many see it as hype‑driven, undermining otherwise interesting technical points.