Skip to content

Topic

Agent Reliability

Making probabilistic model behaviour dependable through deterministic verification, guardrails, retries and observability.

Current stories

buildConfirmed2 publishers

Two-thirds of failed agent runs in ThinkingBox exited cleanly with the backend still wrong

Microsoft and Hugging Face's ThinkingBox found that 67.24% of 79,853 failed agent runs ended cleanly, with no final tool error. Those failures showed up only when executable checks read the records each run left in the backend.

Perspective Coverage

3 publishers
Builder
Builder 55%
Operator
Operator 37%
Investor
Investor 8%

Reality

Evidence60
Adoption
Not scored
Hype gap+15
Incentives40
Confidence62
buildOne report1 publisher

Harsher tool-schema changes broke Strands, LangGraph and CrewAI in three different ways over 36 runs

Only a renamed tool argument got through Strands, LangGraph and CrewAI cleanly in a 36-run schema-change test posted on dev.to. Harsher changes let Strands and CrewAI exit 0 with nothing verified while LangGraph crashed outright, so each framework needs its own schema-change test.

Publishers:dev.to

Reality

Evidence42
Adoption
Not scored
Hype gap+12
Incentives15
Confidence40
buildOne report1 publisher

A return-policy question routes to either of two tools depending on how it is phrased

A dev.to post puts the fragile layer of a multi-tool agent in the choice between two tools that both fit the request, and argues that better tool descriptions plateau because the ambiguity belongs to the request itself.

Publishers:dev.to

Reality

Evidence22
Adoption
Not scored
Hype gap+12
Incentives22
Confidence34
buildOne report1 publisher

Running every AppWorld task five times drops a ReAct agent from 77% to 53%

IBM Research calls the 24-point drop between passing once and passing five times the consistency gap. Independence would have predicted a 27% five-run rate, so the failures are clustering on particular tasks.

Publishers:dev.to

Reality

Evidence45
Adoption20
Hype gap+12
Incentives45
Confidence48
buildOne report1 publisher

Thinkingbox grades 507 agent workflows on the backend state they leave behind

Every task in the benchmark is checked against its required terminal state, so any tool order can pass and any extra side effect fails. Claude Opus 5, the strongest model tested, cleared 66.50% at pass@1.

Publishers:arxiv.org

Reality

Evidence60
Adoption18
Hype gap+12
Incentives35
Confidence52
buildOne report1 publisher

A stale "unpublished" flag outlived four hours, four documents and two reviewers

One team's canonical records said a piece was unshipped for 260 minutes after it went live. The rule about checking the artifact only runs in one direction, and that is the cheaper direction.

Publishers:dev.to

Reality

Evidence45
Adoption18
Hype gap+18
Incentives35
Confidence55
buildOne report1 publisher

The false green: a cached "connected" cleared a live health check before any model ran

A failed Fivetran lookup fell back to a cached snapshot, and deterministic logic promoted last-known state into a current Healthy verdict. The request returned successfully.

Publishers:dev.to

Reality

Evidence44
Adoption
Not scored
Hype gap+12
Incentives62
Confidence41
buildOne report1 publisher

Memora grades memory agents on what they should have forgotten, and six of them fail

A new benchmark penalises agents for acting on facts the user already revoked. The dedicated memory layers barely beat the plain models on it.

Publishers:arxiv.org

Reality

Evidence42
Adoption10
Hype gap+22
Incentives62
Confidence45
buildOne report1 publisher

The failure mode your dashboard cannot see: 43% of agent errors are wrong-shaped output at HTTP 200

A 58-day log of 78 unattended agents found 43% of failures were malformed output returning HTTP 200. On one day uptime read 97-100% while finished deliverables were zero.

Publishers:dev.to

Reality

Evidence56
Adoption24
Hype gap+14
Incentives44
Confidence54
buildOne report1 publisher

Uptime monitoring cannot see the way remote MCP servers actually break

A dev.to writeup makes the structural case: tool and schema drift exists only as a diff between two snapshots, so no single health probe can find it, however thorough.

Publishers:dev.to

Reality

Evidence52
Adoption10
Hype gap+16
Incentives78
Confidence44
buildOne report1 publisher

Solar Pro 4 turns model routing into a procurement decision, not a research one

Upstage is selling tool-calling discipline rather than reasoning, and says 370 billion tokens moved through OpenRouter in its first week. The price, the part that matters most, is still qualitative.

Publishers:thenewstack.io

Reality

Evidence27
Adoption40
Hype gap+33
Incentives83
Confidence41
investOne report1 publisher

Google's 180-config sweep: extra agents cut sequential-task scores by 39 to 70%

A controlled evaluation across four benchmarks found centralized coordination lifted financial reasoning 80.9%, while every multi-agent variant tested made strict sequential planning worse.

Publishers:research.google

Reality

Evidence46
Adoption18
Hype gap+12
Incentives62
Confidence52
buildOne report1 publisher

Agent reliability is a harness problem, not a prompt problem

A dev.to write-up splits agent work into prompts, context and harness. The interesting part is the harness: tool execution, permissions, validation and recovery, all of it code you own.

Publishers:dev.to

Reality

Evidence26
Adoption
Not scored
Hype gap+22
Incentives34
Confidence38