$ 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
- → If you run diagnostics pipelines (Langfuse, diagnostics-otel, prometheus), verify HTTP API traffic now appears in usage dashboards openclaw/openclaw [monitor]
- → After deploying the agent fix, confirm provider 401s now show a reply in channels and adjust bot error handling as needed openclaw/openclaw [plan]
- → If you rely on the maturity scorecard, re-read the docs to reflect the new single Maturity score from Quality and Completeness openclaw/docs [plan]
References
- [1] fix(agent): emit model.usage diagnostic for HTTP ingress traffic ↗ openclaw/openclaw
- [2] fix: surface provider authentication failures in channels ↗ openclaw/openclaw
- [3] docs: clarify maturity scorecard scoring ↗ openclaw/openclaw
- [4] fix(agent): replace self-wait with deferred release in retained-lock abort cleanup ↗ openclaw/openclaw
- [5] perf(imessage): show typing sooner for slow replies ↗ openclaw/openclaw