A thin newsletter post about AI-slop etiquette drew replies describing real production guardrails against it: one team runs a Claude Code hook that "blocks any comment more than 2 lines long" (joshmoody24), another described a five-gate automatic PR-denial harness covering edit size, comment length, and a required code-line citation for every review comment, "fail any of these, automatic PR denial with no human intervention" (Fordec). Neither mechanism has been tested against a determined attempt to route around it.
In the News: August 17, 2026, Evening
A Wiz security agent autonomously found and exploited, in five days, a Snowflake vulnerability that an AI-assisted GitHub review had cleared.
Evening edition
Machine-readable
Download Markdown
Story
An autonomous AI agent broke into Snowflake's Jira through a bug GitHub's AI review had cleared
Wiz Research's autonomous "Red Agent" scanned Snowflake's public GitHub organization, found a script-injection flaw in a GitHub Actions workflow, and exploited it entirely on its own, five days after the flaw went live. The vulnerable…
Read story →AI;DR (AI; Didn't Read)
Ask HN: GitHub employees, what's going on? Why?
98 points and 78 comments at just under three hours old when last checked, with Simon Willison arguing GitHub's strain is a different shape of scaling problem than LLM serving. A GitHub executive's claim of 14x commit growth is circulating in the thread but traces to a social post this edition has not verified. We have not read the thread itself, so this is a discussion to watch, not a finding.
Mitchell Hashimoto on always-on background agents
1,800 likes and 95,000 views at about 21 hours old. Hashimoto, who coined "harness engineering," says his own machine's overnight CPU utilization has gone from roughly zero to over 20 percent because of background agents. We have not independently read or verified the post beyond what is visible publicly, so this is a claim to watch, not a confirmed figure.