62 wires and counting

$ follow OpenClaw

Keep up with OpenClaw in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-06-25
stories 55

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

HTTP agent traffic now emits model.usage diagnostics, auth failures surface in channels

By RepoJournal · Filed · About OpenClaw

The agent runtime now reports token and cost diagnostics for all HTTP ingress paths, and channel users get a real error when a provider rejects a request.

The agent runtime previously emitted model.usage diagnostic events only for channel messages and cron runs, leaving every HTTP ingress path (POST /v1/responses, POST /v1/chat/completions, node-event dispatch) invisible to Langfuse bridge, @openclaw/diagnostics-otel, and diagnostics-prometheus. agentCommandFromIngress now emits these events, so all consumers see HTTP traffic's token and cost data [1].

Channel users messaging a bot got nothing but the :eyes: react when the model provider answered with HTTP 401. That failure is now surfaced as a reply or error message in the channel instead of a silent hang [2]. The maturity scorecard used to render Coverage as a headline score next to Quality and Completeness, implying it feeds maturity scoring; it now shows one headline Maturity score from Quality and Completeness only, preserving Coverage in metadata and tables [3]. In retained-lock abort cleanup, releaseHeldLockWithFence() bailed while the active write-lock scope was alive, leaving the held lock unreleased and acquireCleanupLock() returning a noopLock that leaked the file lock until maxHoldMs; the cleanup now defers release instead of waiting on itself, avoiding that leak [4]. iMessage turns can feel sluggish because context/session/model setup and a slow private-API read RPC sat on the accepted-turn critical path; typing now appears sooner, improving perceived latency for slow replies [5].

Action items

References

  1. [1] fix(agent): emit model.usage diagnostic for HTTP ingress traffic ↗ openclaw/openclaw
  2. [2] fix: surface provider authentication failures in channels ↗ openclaw/openclaw
  3. [3] docs: clarify maturity scorecard scoring ↗ openclaw/openclaw
  4. [4] fix(agent): replace self-wait with deferred release in retained-lock abort cleanup ↗ openclaw/openclaw
  5. [5] perf(imessage): show typing sooner for slow replies ↗ openclaw/openclaw

Quick answers

What shipped in OpenClaw on June 25, 2026?
The agent runtime now reports token and cost diagnostics for all HTTP ingress paths, and channel users get a real error when a provider rejects a request. In total, 45 commits and 10 pull requests landed.
Who contributed to OpenClaw on June 25, 2026?
5 developers shipped this update, including RomneyDa, xialonglee, sjf-oa, omarshahine, and openclaw-docs-sync[bot].
What were the notable OpenClaw updates?
fix(agent): emit model.usage diagnostic for HTTP ingress traffic, fix: surface provider authentication failures in channels, and docs: clarify maturity scorecard scoring.