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
The two biggest surface changes were invisible-to-the-eye infrastructure: cloud relay queries that used to stall ≤60s now resolve in seconds (wake long-poll), and any app already emitting OpenTelemetry traces now gets full ClawMetry session attribution without a code change (OTLP BYO-agent). On top of that, CI got a systematic credential-hygiene sweep (8 separate hardening PRs), two new runtimes shipped (Lovable #29, Replit Agent #30), and Windows desktop installs became self-healing.
Note:vivekchand/clawmetry-cloud is outside this session's MCP scope — cloud-side PR/issue counts are unavailable this week. Cloud sections are marked accordingly.
Shipped (OSS — 36 meaningful PRs; cloud data unavailable)
MCP access not scoped to this repo this session — PR/issue counts unavailable. Cloud-side velocity proxy: clawmetry-pro references in #5340 and #5337 confirm at least 2 cloud-side PRs (#196, #197) merged this week.
Biggest user-visible win
#5342 + #5347 Wake long-poll: cloud relay queries answered in seconds (was ≤60s)
Before this, a cloud user clicking into a session transcript had to wait for the daemon's next heartbeat cycle — up to a full minute of spinner before any content appeared. The wake long-poll holds the relay connection open and resolves the query the instant the answer is ready, eliminating the wait entirely. Combined with the heartbeat-inside-wake fix (#5358), the round-trip is now measured in single-digit seconds on a live daemon. For cloud users this is the most felt change of the week: transcripts and Brain windows now load at the speed they'd expect from a local session.
What users asked for (intel)
No explicit intel-feedback or intel-pain labelled issues were filed this week in OSS (label may live in the cloud repo). The highest-signal user-surface signals from the week:
Median open-issue age: ~35 days (estimated — dominated by recurring bot-filed obs-gap + audit issues filed in the last 30 days, offset by several 150+ day epics)
Top label counts (OSS):
triaged: ~100+
enhancement / harness-gap / observability: ~40
bot-plan-only: ~30
weekly-digest: 9 (previous digests still open)
regression: 4 open
Bot productivity (OSS — cross-repo aware only where data available)
Intel/obs-gap scout: ~15 new [obs-gap:*] issues filed this week (runtime:openclaw and runtime:nemoclaw); several correctly de-duped as duplicate on filing
CI babysit / PR autofix: multiple CI-harden PRs opened and merged by vivekchand directly; no bot-babysit marker PRs spotted in OSS this week
Concerning signal
#5335 — Watchdog can't reach vivekchand/clawmetry-cloud to file cloud regressions. The smoke watchdog detected a new regression on 2026-08-29 but couldn't file it to the cloud repo, so it fell into this OSS blocker issue instead. This means cloud-side regressions that only manifest against the cloud surface are currently creating a silent blind spot — the watchdog knows something is wrong but has nowhere to file it. Concrete next step: fix the cross-repo token/permission used by the watchdog workflow so it can write to clawmetry-cloud, or route cloud regressions through OSS with a regression:cloud label as a short-term fix.
Secondary: The [obs-gap:openclaw] secret egress host-binding fail-closed events not captured gap has been re-filed as 5 separate issues this week alone (#5044, #5287, #5377, #5395, and older ones) — identical finding, different issue numbers. The duplicate-detection logic isn't catching it. Either the gap needs a fix to close the loop, or the dedup threshold needs tightening so repeat filings land on the existing issue rather than creating new ones.
[OSS] Secret egress host-binding obs-gap — the recurring duplicate signal. Either ship the observer fix or add dedup logic to close-on-refile so the issue count stops climbing.
Code activity (OSS — cloud unavailable)
OSS
Commits: 49 (since 2026-08-24)
Lines: +753,177 / -420 across 2,183 files (dominated by i18n translation files added this week)
Contributors: Vivek Chand (+ GitHub Actions bot for i18n/version bumps)
Releases: v0.12.784 → v0.12.794 (11 releases shipped this week)
Auto-generated 2026-08-31 07:30 UTC by the weekly digest bot. Tagged triaged so other bots leave it alone. Cross-repo aware — cloud data unavailable this run (vivekchand/clawmetry-cloud outside MCP scope; add repo to session scope to restore full cross-repo view).
Theme of the week
The two biggest surface changes were invisible-to-the-eye infrastructure: cloud relay queries that used to stall ≤60s now resolve in seconds (wake long-poll), and any app already emitting OpenTelemetry traces now gets full ClawMetry session attribution without a code change (OTLP BYO-agent). On top of that, CI got a systematic credential-hygiene sweep (8 separate hardening PRs), two new runtimes shipped (Lovable #29, Replit Agent #30), and Windows desktop installs became self-healing.
Shipped (OSS — 36 meaningful PRs; cloud data unavailable)
OSS (vivekchand/clawmetry)
Features
Fixes
sandbox exec ... tail, not host filesystem read #5192) — NemoClaw container-backed sessions now surface gateway logs that were silently droppingclawmetry updatefails — bad upgrade no longer leaves the install in a broken state.exestub is not a valid install; the shell now detects and heals itChore / security / CI
Cloud (vivekchand/clawmetry-cloud)
MCP access not scoped to this repo this session — PR/issue counts unavailable. Cloud-side velocity proxy: clawmetry-pro references in #5340 and #5337 confirm at least 2 cloud-side PRs (#196, #197) merged this week.
Biggest user-visible win
#5342 + #5347 Wake long-poll: cloud relay queries answered in seconds (was ≤60s)
Before this, a cloud user clicking into a session transcript had to wait for the daemon's next heartbeat cycle — up to a full minute of spinner before any content appeared. The wake long-poll holds the relay connection open and resolves the query the instant the answer is ready, eliminating the wait entirely. Combined with the heartbeat-inside-wake fix (#5358), the round-trip is now measured in single-digit seconds on a live daemon. For cloud users this is the most felt change of the week: transcripts and Brain windows now load at the speed they'd expect from a local session.
What users asked for (intel)
No explicit
intel-feedbackorintel-painlabelled issues were filed this week in OSS (label may live in the cloud repo). The highest-signal user-surface signals from the week:sandbox exec ... tail, not host filesystem read #5192 [obs-gap:nemoclaw] Container-sandbox gateway log fetched via host glob instead of sandbox-exec path (severity:high) — surfaced by the intel/obs-gap bot, fixed same week via fix(nemoclaw): fall back to sandbox exec when host path yields no gateway logs (#5192) #5205. Fast loop.Backlog health (OSS — cloud unavailable)
feat(v0.13): Native Event Stream Consumer(opened 2026-02-28, 184 days)triaged: ~100+enhancement/harness-gap/observability: ~40bot-plan-only: ~30weekly-digest: 9 (previous digests still open)regression: 4 openBot productivity (OSS — cross-repo aware only where data available)
[obs-gap:*]issues filed this week (runtime:openclaw and runtime:nemoclaw); several correctly de-duped asduplicateon filingtriagedon creation — 0 manual triage neededbot-babysitmarker PRs spotted in OSS this weekConcerning signal
#5335 — Watchdog can't reach
vivekchand/clawmetry-cloudto file cloud regressions. The smoke watchdog detected a new regression on 2026-08-29 but couldn't file it to the cloud repo, so it fell into this OSS blocker issue instead. This means cloud-side regressions that only manifest against the cloud surface are currently creating a silent blind spot — the watchdog knows something is wrong but has nowhere to file it. Concrete next step: fix the cross-repo token/permission used by the watchdog workflow so it can write to clawmetry-cloud, or route cloud regressions through OSS with aregression:cloudlabel as a short-term fix.Secondary: The
[obs-gap:openclaw] secret egress host-binding fail-closed events not capturedgap has been re-filed as 5 separate issues this week alone (#5044, #5287, #5377, #5395, and older ones) — identical finding, different issue numbers. The duplicate-detection logic isn't catching it. Either the gap needs a fix to close the loop, or the dedup threshold needs tightening so repeat filings land on the existing issue rather than creating new ones.Suggested focus next week
Code activity (OSS — cloud unavailable)
OSS
Cloud
Bot meta
Auto-generated 2026-08-31 07:30 UTC by the weekly digest bot. Tagged
triagedso other bots leave it alone. Cross-repo aware — cloud data unavailable this run (vivekchand/clawmetry-cloud outside MCP scope; add repo to session scope to restore full cross-repo view).