You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Three things landed in sequence and each depended on the other: the Session Trail (Inputs → Decisions → Outcome for every runtime, schema v15) gave users the per-session narrative they'd been missing; Guard control was fixed to actually send signals to non-OpenClaw runtimes (it had been silently no-oping for Claude Code, Codex, Cursor, and every other adapter since the feature launched); and three successive OpenAI cost-accuracy PRs corrected a systematic problem in rate lookup, cache discount application, and double-counting that made every OpenAI cost figure wrong.
Note:vivekchand/clawmetry-cloud is not accessible to this session's GitHub token. The "Cloud" rows throughout this digest are marked [data unavailable]. To fix: add clawmetry-cloud to the session's allowed repos in the Claude Code connector settings.
fix(guard): Pause/Stop/Kill did nothing on every runtime except OpenClaw #5529fix(guard): Pause/Stop/Kill did nothing on every runtime except OpenClaw — the pid guard compared the session record's timestamp instead of the process start time, so every signal went to the wrong (or no) process. All runtimes now controllable.
i18n: two translation syncs (README translations + UI strings).
Cloud (vivekchand/clawmetry-cloud)
[data unavailable — GitHub token not scoped to this repo this session]
Proxy: at least 19 PyPI releases shipped from OSS RELEASE PRs this week (v0.12.807 → v0.12.826), all of which deploy to cloud on merge. Cloud-specific PRs and issues cannot be enumerated.
Biggest user-visible win
#5512 Session Trail: Inputs / Decisions / Outcome for every runtime
Every session now has a three-panel narrative alongside the transcript: Inputs (what the agent was actually handed — CLAUDE.md, MCP servers, system prompt, context window), Decisions (which detector alerts fired, what the guard policy did, what mode the agent chose), and Outcome (git commits, merged PRs, test results, cost split). This works on the hosted dashboard via snapshot relay and locally via DuckDB. Schema v15 is the largest structural change since schema v10.
The secondary win this week is practical rather than new: Guard's Pause/Stop/Kill (#5529) now actually sends signals to non-OpenClaw runtimes. Every user who tried to pause a running Claude Code session from the Guard tab and saw it keep going was hitting this. Fixed.
What users asked for (intel)
No intel-feedback or intel-pain labelled issues this week. One external enhancement proposal:
Feature proposal: opt-in capability-gap event export for machine-demand measurement #5412 (flyoung588) — "Feature proposal: opt-in capability-gap event export for machine-demand measurement" — asks for a machine-readable feed of the obs-gap events so teams can programmatically see where ClawMetry's coverage is thin on their runtimes. Good signal that the harness-gap system is now visible enough for users to want to consume it.
Intel coverage was lighter than usual this week — possibly because the accuracy-audit and obs-gap bots dominated the issue stream. Worth checking if user-filed issues are getting buried.
Two regression issues are 12–14 days stale with no PR.
#5236 (/fleet/ returning 302 instead of 200) and #5162 (/healthz returning 404) have been open since Aug 24–26 with bot-plan-only / needs-info status. Neither has a PR. These are route-level failures that the smoke watchdog catches on every run and every maintainer checks by hand — if they're still failing, the fleet and health endpoints are broken in the smoke environment. If they're phantom (fixed but watchdog not updated), the watchdog needs its expected-status list corrected. Either way, close or assign by Monday EOD.
Auto-generated 2026-09-07 07:15 UTC by the weekly digest bot. Tagged weekly-digest + triaged so triage bots leave it alone. Cross-repo aware as of 2026-05; cloud data unavailable this run (session token not scoped to vivekchand/clawmetry-cloud — fix in connector settings to restore cloud coverage next week).
Theme of the week
Three things landed in sequence and each depended on the other: the Session Trail (Inputs → Decisions → Outcome for every runtime, schema v15) gave users the per-session narrative they'd been missing; Guard control was fixed to actually send signals to non-OpenClaw runtimes (it had been silently no-oping for Claude Code, Codex, Cursor, and every other adapter since the feature launched); and three successive OpenAI cost-accuracy PRs corrected a systematic problem in rate lookup, cache discount application, and double-counting that made every OpenAI cost figure wrong.
Shipped (OSS only — ~52 meaningful PRs)
OSS (vivekchand/clawmetry)
Features
feat(openclaw)surface OOM-victim events for local model servers ([obs-gap:openclaw] openclaw: OOM-victim preference for local model servers not tracked #5548) — when a GPU model server is killed by the kernel, it now shows up in the dashboard.feat(openclaw)capture response-steered spans in Tracing tab ([obs-gap:openclaw] OpenClaw: response-steering history for async tool calls not captured #5578) — async tool-call steering history is now visible per span.feat(openclaw)capture reply recovery state in assistant spans ([obs-gap:openclaw] OpenClaw: reply recovery state across Gateway restarts not captured #5577) — Gateway-restart recovery attempts tracked and surfaced.feat(nemoclaw)resolve vLLM sandbox provider distinctly ([obs-gap:nemoclaw] nemoclaw: vLLM sandbox provider not resolved distinctly (generic 'inference' fallback) #5579) — vLLM no longer collapses to the genericinferencefallback in cost and tracing.feat(openclaw)surface gateway degraded-start from migration warnings ([obs-gap:openclaw] openclaw: degraded-start (migration warning) Gateway state not captured #5547).feat(crons)surface quarantined cron rows in health-summary ([obs-gap:openclaw] openclaw: cron quarantine on malformed legacy rows not surfaced #5546) — malformed legacy rows are now visible rather than silently dropped.Fixes
fix(guard): Pause/Stop/Kill did nothing on every runtime except OpenClaw — the pid guard compared the session record's timestamp instead of the process start time, so every signal went to the wrong (or no) process. All runtimes now controllable.fix(approvals)make an approval request legible; stop the preset that paused everything — the default approval preset was blocking every session; the request card was unreadable.fixper-repo agent memory never reached the cloud Memory tab (Codex, Cursor, opencode).cache_readtokens in/api/token-attribution.fix(accuracy)restore full event shape in sessions clusters (tool_count regression from perf(cost): ship slim event rows and share one round trip for the Cost tab scans #5524).fix(replay)Sessions replay lost its column; a reloaded Trail link never loaded.fix(trail)Inputs card showed each kind twice, both labelled "Empty".fix(overview)"No agents running" printed above "3 sessions are working right now."fix(guard)running session duration shown in milliseconds instead of minutes.fix(guard)pid guard used session record timestamp, not process start — root cause of the Pause/Stop/Kill regression.clawmetry --help/-hmust not import dashboard #5535fix(cli)bareclawmetry --help/-hmust not import dashboard (500ms startup regression).fix(c6-health)bot was posting to closed tracking issue E2E Robustness Epic: 7-criterion automated testing tracker (active) #4552; redirected to active E2E Robustness Epic: 7-criterion tracker (cron-managed) #5266.Perf
Chore / refactor / CI hardening / docs
Cloud (vivekchand/clawmetry-cloud)
[data unavailable — GitHub token not scoped to this repo this session]
Proxy: at least 19 PyPI releases shipped from OSS RELEASE PRs this week (v0.12.807 → v0.12.826), all of which deploy to cloud on merge. Cloud-specific PRs and issues cannot be enumerated.
Biggest user-visible win
#5512 Session Trail: Inputs / Decisions / Outcome for every runtime
Every session now has a three-panel narrative alongside the transcript: Inputs (what the agent was actually handed — CLAUDE.md, MCP servers, system prompt, context window), Decisions (which detector alerts fired, what the guard policy did, what mode the agent chose), and Outcome (git commits, merged PRs, test results, cost split). This works on the hosted dashboard via snapshot relay and locally via DuckDB. Schema v15 is the largest structural change since schema v10.
The secondary win this week is practical rather than new: Guard's Pause/Stop/Kill (#5529) now actually sends signals to non-OpenClaw runtimes. Every user who tried to pause a running Claude Code session from the Guard tab and saw it keep going was hitting this. Fixed.
What users asked for (intel)
No
intel-feedbackorintel-painlabelled issues this week. One external enhancement proposal:Intel coverage was lighter than usual this week — possibly because the accuracy-audit and obs-gap bots dominated the issue stream. Worth checking if user-filed issues are getting buried.
Backlog health (OSS only)
feat(channels): add Fish Audio voice/telephony channel ingest— open 17 daysfeat(entitlement): has_capacity_batch + has_capacity_batch_at + endpoints— open 15 daystriaged: ~110 of 134harness-gap/observability(obs-gap series): ~45enhancement: ~55bot-plan-only: ~50weekly-digest: 10bug: ~5Two regressions that were open entering this week have not yet been closed:
[regression] GET /fleet/ -- FAIL_STATUS got 302 expected 200— opened 2026-08-26 (12 days).bot-plan-only, no PR.[regression] GET /healthz -- FAIL_STATUS got 404 expected 200— opened 2026-08-24 (14 days).needs-info.Bot productivity
triagedwithin hours.Concerning signal
Two regression issues are 12–14 days stale with no PR.
#5236(/fleet/returning 302 instead of 200) and#5162(/healthzreturning 404) have been open since Aug 24–26 withbot-plan-only/needs-infostatus. Neither has a PR. These are route-level failures that the smoke watchdog catches on every run and every maintainer checks by hand — if they're still failing, the fleet and health endpoints are broken in the smoke environment. If they're phantom (fixed but watchdog not updated), the watchdog needs its expected-status list corrected. Either way, close or assign by Monday EOD.Suggested focus next week
/fleet/302) and [regression] GET /healthz -- FAIL_STATUS got 404 expected 200 #5162 (/healthz404) — longest-standing open regressions, 12–14 days.Code activity (OSS only — cloud data unavailable)
OSS
Cloud
Bot meta
Auto-generated 2026-09-07 07:15 UTC by the weekly digest bot. Tagged
weekly-digest+triagedso triage bots leave it alone. Cross-repo aware as of 2026-05; cloud data unavailable this run (session token not scoped tovivekchand/clawmetry-cloud— fix in connector settings to restore cloud coverage next week).