Strata Scrubbed Claude From Their GitHub History — Then It Got Weird

A repository's commit history is supposed to be append-only. Sometime this week, Strata appears to have treated that as a suggestion.

Reports surfacing on r/LocalLLaMA claim that Strata force-pushed a rewritten version of their repository, scrubbing commit metadata that had identified Anthropic's Claude as a co-author. If the claim holds up, it is the clearest case yet of a company retroactively editing its own development record to hide AI involvement in shipped code.

I should be precise about what I can and cannot confirm here. The primary evidence is a single community thread, and Reddit's anti-bot wall limits what a casual reader can see of it. Independent verification, such as archived objects pulled from GitHub's API before the rewrite, would settle this quickly. Until then, the technical mechanics are worth walking through regardless, because the same move is available to any team and the same defenses are available to any observer.

Here is the pattern alleged. Claude Code, Anthropic's terminal agent, appends a trailer to commits it makes directly: Co-Authored-By: Claude <[email protected]>. That trailer lands in the commit message body. The author field also names the configured committer, but the trailer is the visible breadcrumb. Anyone running git log --grep="Claude" against an affected repo gets a hit.

Removing that trail requires rewriting history. The tools are old and well documented. git filter-branch was the standard for years and is now discouraged for large repos. The modern choice is git-filter-repo, a Python tool that rewrites every commit, changing both the message body and, if requested, the author and committer fields. Crucially, rewriting a commit changes its SHA-1 hash. Every descendant commit gets a new hash too. The result looks identical when you read the code, and is a completely different object database underneath.

To publish that rewrite, the maintainer deletes the remote branch and pushes a new one with git push --force, or git push --force-with-lease, which refuses to overwrite if someone else pushed since your last fetch. That second command is the polite version of a destructive act. Both versions are permitted by GitHub for anyone with write access unless branch protection rules block them.

So the question for Strata is not whether this is possible. It plainly is. The question is what survives the rewrite.

Several things do survive. Forks. Any public fork that predates the force-push retains the original object graph, including the original commit SHAs. git fetch <fork-remote> <old-sha> will still resolve, as long as GitHub's servers keep the orphaned objects around. Fork networks in GitHub are shared object stores, which is precisely why deletions often linger. Archives. Software Heritage, GH Archive event dumps, and any developer's local clone all keep the old history. GitHub's own event timeline records force pushes and branch deletions as distinct public events, timestamped.

The rewrite also changes every SHA from that point forward, which breaks anything pinned to a commit hash: CI caches, security scanners, reproducible build references, and dependency pinning in downstream manifests.

None of this proves the underlying accusation. It does mean the accusation is cheap to verify or refute. An old SHA that still resolves would be decisive. Strata could also kill the story outright by publishing an unfiltered git log from a pre-rewrite clone.

There is a separate and more interesting argument lurking underneath, which the thread's commenters have already started picking at. Hiding a Co-Authored-By trailer says very little about how much AI wrote the code. Developers routinely accept agent output, squash it, and commit under their own name from the start. The trailer is a convention, not a forensic record. A team that squashes agent commits into a human-authored one leaves no breadcrumb at all, and has violated no platform policy.

That gap is the real problem. GitHub's "Verified" badge attests that a commit was signed by a key associated with the account. It says nothing about who or what produced the diff. An agent can commit through a signed key and appear exactly as trustworthy as a human maintainer. There is no cryptographic attestation of authorship, and no standard for one.

Strata has not, to my knowledge, published a response addressing the thread. Anthropic does not require disclosure of Claude-assisted contributions in its public terms for Claude Code, which leaves the policy call to the company doing the committing. That means the disclosure standard for AI-authored production code is currently whatever a given company decides you will never find out about.

If the rewrite happened, the old SHAs still exist in someone's clone. That is the part no force-push can undo: which repository still resolves commit 8d1b3a2?

Source: Strata rewrote their Github history to wipe evidence of Claude-authoring