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
PR Trace shipped end-to-end. The OSS daemon can now capture the agent session behind any pull request, publish it to trace.clawmetry.com, and drop the link back into the PR — no config, no flags. Alongside that, cost accuracy got a hard reconciliation across three surfaces, verification gained a six-layer architecture with acceptance-criterion traceability, and four more runtimes (Cline, Gemini CLI, OpenHands, plus Cursor/Copilot posture) landed.
vivekchand/clawmetry-cloud#2088 docs: the PR Trace open-source grant programme (private half)
vivekchand/clawmetry-cloud#2091 docs(flywheel): §2b — Drift Bot is a merge blocker, not an advisory
vivekchand/clawmetry-cloud#2060 docs(flywheel): rebase on fresh origin/main before every PR
Biggest user-visible win
#5131 [RELEASE] PR tracing happens on its own (carries #5126, #5127, #5129, #5130) — combined with the cloud-side vivekchand/clawmetry-cloud#2092 feat(trace): serve PR traces at trace.clawmetry.com. The user experience change: install ClawMetry, run any agent (Claude Code / OpenClaw / Cline / …), and every pull request that agent opens now gets a public trace URL commented on it, automatically, no flags. The full session — prompts, tool calls, sub-agents, cost, quality grade — is browsable at trace.clawmetry.com/<id>. This is the first user-facing product surface built on top of the observability substrate; it turns "your agent is observed" from "look at the dashboard on localhost:8900" into "here's the trace, shareable, on every PR." The open-source grant programme (vivekchand/clawmetry-cloud#2088) starts the go-to-market motion on the same feature.
What users asked for (intel)
No new intel-* issues filed in either repo this week. The 105+ existing intel-* items in cloud (from 2026-05 onward) are the standing backlog; the closest recent proxy for demand is #4707 (fresh-install desktop uninstall complaint, shipped) and the P0 canary-failure heartbeats (#5106/#5108/#5119) which are the smoke watchdog acting as a synthetic user. The Fish Audio channel PR (#5055) is the only open one carrying a runtime:openclaw obs-gap signal from last week.
Backlog health (across both repos)
Open issues: 203 total (84 OSS + 119 cloud) — vs 82 OSS at end of last week's digest, so essentially flat OSS with +2. Cloud backlog unchanged.
PR babysit: Not surfaced as its own signal in this data pull — release loop merged 128 OSS + 37 cloud PRs, so the babysitter kept up.
Weekly digest bot: filing this one.
Concerning signal
The release canary is broken and has been for at least two versions in a row.#5106 flagged 0.12.759 as failing verification (Aug 22), #5108 flagged the published product failing verification (Aug 23), and #5119 flagged 0.12.760 also failing (Aug 23). All three P0 heartbeats are still open. #5095 fixed one part ("the release canary never fired"), #5133 fixed another ("retry the pip install for CDN propagation lag"), but the P0s themselves haven't been closed — meaning either the fixes didn't fully land the guarantee, or the heartbeat/canary logic itself is filing false positives. Either way, the release-verification pipe is currently unreliable at exactly the moment PR Trace is going live.
Next step: verify a fresh pip install clawmetry==0.12.763 in a clean matrix job (all three OSes × Py 3.9/3.11), then either close #5106/#5108/#5119 with the ratchet-forward evidence or reopen the root-cause investigation. Do this before announcing PR Trace externally — a broken canary is a public embarrassment waiting to happen if a user hits the same failure the bot did.
[both] Restart the intel scout — 0 intel-* issues this week is the first time that's happened. If it's silently broken, the demand-signal pipeline is off.
Code activity (across both repos)
OSS
Commits (on main): 49
Lines: roughly +11k / −2k across the non-vendor commits (a single 1820-file / +702k vendored import commit is excluded as noise; noted so no one is misled by a raw shortstat)
Contributors: Vivek Chand + github-actions[bot]
Releases: v0.12.725 → v0.12.763 — 38 patch releases in 7 days
Cloud
Commits / lines / contributors: unavailable this week — the digest environment has no gh CLI to clone the private repo. (Filed via the search API instead.) Recommend adding a git clone step or piping the daemon's cloud-repo mirror to /tmp so the next digest can quote actual diff stats.
Releases (proxy): 37 PRs merged to main in the past 7 days (~15 auto-pin mirrors + ~22 real product PRs, weighted toward payment-flow hardening and PR Trace serving).
Bot meta
Auto-generated 2026-08-24 07:15 UTC by the weekly digest bot. Tagged triaged so other bots leave it alone. Cross-repo aware as of 2026-05.
Theme of the week
PR Trace shipped end-to-end. The OSS daemon can now capture the agent session behind any pull request, publish it to
trace.clawmetry.com, and drop the link back into the PR — no config, no flags. Alongside that, cost accuracy got a hard reconciliation across three surfaces, verification gained a six-layer architecture with acceptance-criterion traceability, and four more runtimes (Cline, Gemini CLI, OpenHands, plus Cursor/Copilot posture) landed.Shipped (128 OSS PRs + 37 cloud PRs merged, most auto-pin/[RELEASE] bookkeeping)
OSS (vivekchand/clawmetry)
Features — new surface area
feat(trace): link a pull request to the agent session that produced it— PR Trace, local halffeat(trace): publish a captured bundle to trace.clawmetry.com— publish halffeat(trace): capture takes no arguments— zero-config capturefeat(trace): automatic tracing, and a comment on the pull request— auto-comment PR wiring, end of trilogyfeat(verification): six-layer verification architecture (L0–L5)— the new verification spinefeat(ci): make every acceptance criterion traceable to a test— closes the untested-criteria class of bug (Blueprint-vs-tests one-way ratchet)feat(orchestration): workflows + sub-agents fully captured per session— parent edges, prompt/reply, live statusfeat(cloud-parity): carry orchestration fields on /api/subagents shaperfeat(openclaw): surface gatewayLogLevel from openclaw.jsonfeat(entitlement): has_all_breakdown— per-axis blocking breakdownfeat(entitlement): has_features/runtimes/missing_features/missing_runtimes bundle_batch endpointsfeat(adapters/openclaw): per-endpoint pool health from nemoclaw model-routerFixes — user-visible
fix(entitlements): fail open on resolver exception even under enforcefix(desktop): verify certificates on both open pingsfix(test): main has been red for three weeks on a guard for deleted UI— three-week undetected main-red rotted throughfix(canary): the release canary never fired, so nothing verified a releasefix(gate): every merge-blocking check must be reachable without secretsfix(trace): strip provider identifiers before publicationfix(trace): refuse to install a hook the PATH binary cannot runpython -m(fail-closed DoS) #5035 / [RELEASE] Gate hooks launch via the console script (carries #5035) #5037 / Claude Code gate uses the same shadow-proof launcher (consistency) #5038 / [RELEASE] Claude Code gate uses the shadow-proof launcher (carries #5038) #5040 Gate hooks launch via console script, notpython -m(fail-closed DoS)fix(supply-chain): a Google Fonts outage is not font driftfix(supply-chain): the OpenSSF Scorecard job has never runfix(canary): retry pip install in matrix jobs for CDN propagation lagfix(verification): register the AC gate's guard filesfix(desktop): uninstall removes every ClawMetry trace; fresh install always asks to sign inChore / refactor / docs
chore: auto-pin clawmetry==0.12.7XX(v0.12.725 → v0.12.763)[RELEASE]umbrella tagstest(trace): make the self-containment guard assert what it claimsfix(ci): make drift-bot a required checkfix(ci): the lint step never linted, and the cloud pin never follows a releasefix(packaging): stop shipping the repo test suite, which could never pass thereCloud (vivekchand/clawmetry-cloud)
Features
feat(trace): serve PR traces at trace.clawmetry.com— the cloud half of PR Tracefeat(cloud): serve orchestration capture from the snapshot (session tree + bulk summary)feat(desktop): open telemetry sink, admin panel, and per-account desktop listFixes
fix(silence): stop paging every cloud user when a laptop sleepsfix(trace): the host shim must not rewrite /api/ pathsfix(email): every urllib sender identifies itself, or Cloudflare 403s itfix(ci): retry the OSS pin install past PyPI's cross-CDN index raceChore / refactor / docs
chore: auto-pin clawmetry==0.12.7XX(mirrors OSS release chain)docs: the PR Trace open-source grant programme (private half)docs(flywheel): §2b — Drift Bot is a merge blocker, not an advisorydocs(flywheel): rebase on fresh origin/main before every PRBiggest user-visible win
#5131 [RELEASE] PR tracing happens on its own (carries #5126, #5127, #5129, #5130) — combined with the cloud-side vivekchand/clawmetry-cloud#2092
feat(trace): serve PR traces at trace.clawmetry.com. The user experience change: install ClawMetry, run any agent (Claude Code / OpenClaw / Cline / …), and every pull request that agent opens now gets a public trace URL commented on it, automatically, no flags. The full session — prompts, tool calls, sub-agents, cost, quality grade — is browsable attrace.clawmetry.com/<id>. This is the first user-facing product surface built on top of the observability substrate; it turns "your agent is observed" from "look at the dashboard on localhost:8900" into "here's the trace, shareable, on every PR." The open-source grant programme (vivekchand/clawmetry-cloud#2088) starts the go-to-market motion on the same feature.What users asked for (intel)
No new
intel-*issues filed in either repo this week. The 105+ existingintel-*items in cloud (from 2026-05 onward) are the standing backlog; the closest recent proxy for demand is #4707 (fresh-install desktop uninstall complaint, shipped) and the P0 canary-failure heartbeats (#5106/#5108/#5119) which are the smoke watchdog acting as a synthetic user. The Fish Audio channel PR (#5055) is the only open one carrying aruntime:openclawobs-gap signal from last week.Backlog health (across both repos)
pin cffi<2 to prevent py3.9 SIGSEGV). No PR stale >14 days — oldest open PR is OSS feat(channels): add Fish Audio voice/telephony channel ingest (#5045) #5055 (3 days).feat(v0.13): Native Event Stream Consumer(opened 2026-02-28, ~178 days)feat: Remote approval gates(opened 2026-03-03, ~174 days)triaged(84),enhancement(33),bot-plan-only(~28),harness-gap+observability+runtime:openclawobs-gap cluster (~12),bug(3),weekly-digest(8)enhancement(68),bug(~4),P0(~4),P1(~10)Bot productivity (cross-repo aware)
triaged. 4 obs-gapduplicateclosures in the past 24h ([obs-gap:openclaw] OpenClaw: no visibility into secret egress host-binding enforcement/denials #5110–[obs-gap:nemoclaw] NemoClaw: model-router endpoint-pool NVIDIA-only compliance verdict not surfaced #5113), 4 moreduplicateclosures earlier this week ([obs-gap:openclaw] OpenClaw: secret egress host-binding fail-closed events not captured #4953–[obs-gap:openclaw] OpenClaw: Fish Audio speech/telephony sessions not tracked #4956, [obs-gap:openclaw] OpenClaw: secret egress host-binding fail-closed events uncaptured #5059). Twocompletedclosures ([obs-gap:openclaw] OpenClaw: configured file-log level/severity filter not surfaced #5060, [obs-gap:nemoclaw] nemoclaw: model-router /health endpoint body (per-endpoint pool health) discarded #5048) both viabot-pr-opened.bot-pr-openedlabels seen on this week's new issues ([heartbeat] The published product is failing verification #5108, [obs-gap:openclaw] OpenClaw: Fish Audio voice/telephony surface not in known channel set #5045); ~5bot-plan-only([P0] Published release 0.12.759 fails canary verification #5106, [obs-gap:openclaw] OpenClaw: trusted-proxy device auto-pairing decisions not captured #5047, [obs-gap:openclaw] OpenClaw: cloud-worker workspace-conflict transcript events not ingested #5046, [accuracy-audit] Fixer run 2026-08-20 UTC #5019, plus older). Cloud split: not detectable from search (labels absent).intel-*issues filed this week in either repo — a notable dip vs prior weeks. Worth investigating whether the scavenger is running.bot-pr-opened. All three still open. No cloud regression heartbeats detected this week.Concerning signal
The release canary is broken and has been for at least two versions in a row. #5106 flagged 0.12.759 as failing verification (Aug 22), #5108 flagged the published product failing verification (Aug 23), and #5119 flagged 0.12.760 also failing (Aug 23). All three P0 heartbeats are still open. #5095 fixed one part ("the release canary never fired"), #5133 fixed another ("retry the pip install for CDN propagation lag"), but the P0s themselves haven't been closed — meaning either the fixes didn't fully land the guarantee, or the heartbeat/canary logic itself is filing false positives. Either way, the release-verification pipe is currently unreliable at exactly the moment PR Trace is going live.
Next step: verify a fresh
pip install clawmetry==0.12.763in a clean matrix job (all three OSes × Py 3.9/3.11), then either close #5106/#5108/#5119 with the ratchet-forward evidence or reopen the root-cause investigation. Do this before announcing PR Trace externally — a broken canary is a public embarrassment waiting to happen if a user hits the same failure the bot did.Suggested focus next week
runtime:openclawobs-gap; close the loop before the smoke scanner refiles.intel-*issues this week is the first time that's happened. If it's silently broken, the demand-signal pipeline is off.Code activity (across both repos)
OSS
main): 49github-actions[bot]Cloud
ghCLI to clone the private repo. (Filed via the search API instead.) Recommend adding a git clone step or piping the daemon's cloud-repo mirror to/tmpso the next digest can quote actual diff stats.mainin the past 7 days (~15 auto-pin mirrors + ~22 real product PRs, weighted toward payment-flow hardening and PR Trace serving).Bot meta
Auto-generated 2026-08-24 07:15 UTC by the weekly digest bot. Tagged
triagedso other bots leave it alone. Cross-repo aware as of 2026-05.