Rsync 3.4.3 has hundreds of Claude commits

A routine software update turned into full-on backup panic when developer Jeremiah Fieldhaven said his system started failing right after moving to rsync 3.4.3, a popular file-copying tool many people trust for backups. He rolled back to an older version, things worked again, then checked the code history — and found a pile of commits co-authored by Claude. His reaction, posted on Mastodon, was the kind of raw, exhausted scream that instantly launched a thousand hot takes.

And oh, the comments delivered. One camp is in full "AI slop is breaking trusted tools" mode, with users claiming there are now hundreds of Claude-linked commits and accusing the maintainer of pushing more "security in depth" fixes while real-world features keep breaking. Another crowd is already posting breakup advice — "people are recommending rclone instead" — turning the whole thing into a classic open-source rebound story. Then came the darker jokes: if this is happening in boring old command-line tools people rely on, commenters fear today’s "cute vibecoded tools" could become tomorrow’s malware buffet.

But not everyone is ready to grab the pitchforks. One reply tried to play detective, asking whether people had actually pinned the bug on 3.4.3 specifically, since rolling back skipped another release in between. Even so, the mood is less calm bug report and more community trust crisis: users aren’t just arguing about a broken feature, they’re arguing about whether AI is quietly rewiring the plumbing of Linux itself — and whether anyone upstream is listening.