Strata rewrote its whole Git history, and the Claude co-author trailers are gone

Strata, an MIT-licensed engine for running Qwen3.8-Flash-Next on consumer GPUs, replaced the entire history of its main branch on 6 October 2026. The repository, created on 24 September, had about 19,250 stars and 1,735 forks on 9 October. Every commit got a new ID. The code did not change. What changed is that Claude Code’s co-author trailers are gone.

What the commits show

User nirvash opened issue #1276 on 6 October after a fetch reported a forced update. Their old checkout and the new main had no common ancestor: “the old history and the corresponding rewritten history each contain 845 commits, with no shared commit IDs.” The issue gives one pair to compare, and it holds up through the GitHub API. Old commit 6f32ec0 and new commit a1641e9 have the same file tree (27b0e86), the same author date and the same message body, except that the old one ends with Co-Authored-By: Claude Opus 5.5 (1M context) and a Claude-Session link, and the new one does not.

Pasquale Pillitteri recounted the full history through the GitHub API. His figures: 595 of the 845 old commits carried a Claude co-author trailer (542 naming Claude Opus 5.5), 453 carried a Claude-Session link, and 844 of 845 rewritten commits have identical trees, dates and subjects. The one exception updates a short hash that one commit message referenced. By his count, none of the more than 400 commits added since the rewrite carries a Claude trailer. A Co-Authored-By trailer records that Claude Code took part in a commit, not how much of it the model wrote.

What the maintainer said

The maintainer, Niko1221, closed the issue on 7 October at 12:41 UTC with version 0.1.40.2. The comment says UPDATE.bat and update.sh now detect a clone on “the history from before 2026-10-06,” keep its old commits in a branch called pre-cleanup-backup, and move it to the new history when no tracked file is edited. Models, settings and the engine are untracked and “never touched.” For older scripts, the maintainer gave three commands:

git fetch origin
git branch pre-cleanup-backup
git checkout -B main origin/main

Run git stash first if git status lists edited files. Thirteen minutes after the issue closed, another user asked, “Why was history rewritten?” There is no answer in the thread, and the README carries no statement about it. The maintainer has not given a reason, and we are not going to guess one.

Why a rewrite costs others

Rewriting a public branch with 1,735 forks forces every clone, fork and open pull request to reconcile with a history that shares no commits with theirs. Pillitteri points to a pull request already resubmitted “on the new main.”

If the goal is simply no agent trailers on future commits, Claude Code’s settings reference lists an attribution option that changes or removes the co-author line and session link going forward. That changes what you write tomorrow, without changing what everyone else already pulled.