Strata force-pushed 845 commits, erased 595 Claude trailers, and never said why

On 6 October the main branch of the Strata repository was force-pushed, and the history it carried was replaced. Strata is Niko1221's MIT-licensed C++ inference engine for the open-weight Qwen3.8-Flash-Next model, Alibaba's 125-billion-parameter release from August, and by 9 October it had drawn 18,983 stars and 1,712 forks. The project's README claims 53 to 94 tokens per second on an RTX 5070 depending on quantization, a figure the project measures itself and no independent party has reproduced. The rewrite is not a matter of interpretation: both histories contain 845 commits, and not one commit ID is shared between them. The motive is a separate question, and nobody outside the project has answered it.

What the force-push actually changed

Comparing the two histories is mechanical, and the comparison comes back almost boring. Both the old and the new main hold 845 commits, and the two sets share no commit ID at all; even the root commit IDs differ. For every commit, the file tree, the author date and the subject line are identical. The only object that differs beyond the identities of the commits themselves is a single 27 September commit that cited another commit by its short hash, referencing be6d09b in the old history and 7f21e2b in the new one. A hash that changes when its target does is the fingerprint of a scripted rewrite rather than a hand-edited branch. What makes this one legible is how total it was: every commit was recreated, so every SHA anyone had cited, linked or pinned now points nowhere.

The trailers that are gone, and the count behind them

In the old history, 595 commits carried a Co-Authored-By trailer naming Claude. The distribution is uneven: 542 name Claude Opus 5.5, 26 name Claude Fable 5.1, 4 name Claude Sonnet 5.5, and the remainder name only Claude or Claude Code. A further 453 of those commits carried a Claude-Session line, the trailer Claude Code writes when it commits from a cloud or Remote Control session, linking back to a claude.ai/code session. In the rewritten history, not one of those trailers survives. Since the rewrite, 403 new commits have landed, none carries a Claude trailer, and 39 credit a human co-author. That the earlier history was substantially drafted by a model is not a new finding: Strata's hype backlash already documented the trailers sitting in the repository.

The issue, and the fifteen hours it lasted

The rewrite broke something concrete. Issue #1276, opened by a user named nirvash about three days before 9 October, reports that a checkout on the old main can no longer update. "The recent force-update of main prevents existing checkouts from updating through the normal UPDATE.bat workflow," the report reads. The reporter is careful about what they did and did not test: "I do not normally use UPDATE.bat and did not run it to reproduce this failure." Their checkout sat on commit 6f32ec0, git recorded a forced-update, and merge-base finds no common ancestor between the two histories. The issue asks for an announcement, a documented recovery path, a friendlier updater message, and no automatic git reset --hard or git clean; it labels the cause an observed difference rather than a confirmed explanation from the maintainer. The maintainer closed it on 7 October at 12:41 UTC, under fifteen hours after it opened, with release v0.1.40.2. Its update scripts now recognise a clone left on the pre-6-October history, keep the old commits in a branch called pre-cleanup-backup, and move the clone onto the new main, provided no tracked file has been modified. Models, settings and the engine are untracked files and stay put; users on older scripts must run three commands by hand. The maintainer has not publicly explained why the history was rewritten.

What the thread argues, and what it does not show

The story surfaced on r/LocalLLaMA on 8 October, where the thread was the subreddit's top post at roughly 539 points and about 348 comments as of 9 October. The most-upvoted comment, at roughly 927 points by third-party recounting, argues that the Claude trailer was an advertisement slipped into users' repositories without consent, and many commenters compare it to a "Sent from my iPhone" signature, which makes its removal hygiene. Others say the rebase of a public branch bothers them more than the trailer, and that the episode has cost the project their trust in its update process. That split is the useful part: the objection with the most support is not that a model wrote the code, but that the fix was applied to a shared, public history without warning. The thread itself links no proof, and the counts used here come from re-counting the repository rather than from the post. The reputation accusations circulating in the thread are not repeated here, because none of them is supported by evidence the public can check.

Every fork inherits the new base

The rewrite does not stay inside one repository. Strata had 1,712 forks as of 9 October, and each fork's history descends from the rewritten main, so a contributor's local clone and the upstream no longer share an ancestor. A fork left untouched for two weeks cannot simply be fast-forwarded onto the new main; its owner has to choose between rebasing the work and abandoning it. That is the real cost of rewriting a public branch, and it is visible in the pull requests: PR #1117 presents itself as a "resubmission of #1030 on the new main," a contributor reapplying work the rewrite had orphaned. There is precedent for the trailer cleanup and none for the silence that followed it. Lutris, in March 2026, hid that it was being built with Claude after a backlash and reversed the decision within days, as GamingOnLinux reported. The scale differs, days of commits against an entire history, and Strata has not reversed.

What is verifiable, and what would settle the rest

The public record is narrow and firm: the history was rewritten, every commit ID changed, the Claude trailers are gone, the updater broke for existing checkouts, and the maintainer shipped a migration path without stating a reason. The public record does not say why. "To wipe evidence" is a motive, and no one has produced proof of it; that Strata is hiding something specific is a claim, not a finding. The one action available to the maintainer is also the cheapest — a note in the repository saying what was rewritten and why. That would not undo the rewrite, and it need not: migrations are ordinary now. What is missing is the sentence that turns a surprising force-push into a documented one. Until it appears, the safest reading is procedural rather than conspiratorial: a maintainer cleaned commit metadata and did not anticipate that the same rewrite would strand every clone and fork downstream of it.