Skip to content

Weekly digest -- 2026-08-24 (PR Trace end-to-end + cost accuracy hardened + 4 new runtimes) #5146

Description

@vivekchand

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

Fixes — user-visible

Chore / refactor / docs

Cloud (vivekchand/clawmetry-cloud)

Features

  • vivekchand/clawmetry-cloud#2092 feat(trace): serve PR traces at trace.clawmetry.com — the cloud half of PR Trace
  • vivekchand/clawmetry-cloud#2067 feat(cloud): serve orchestration capture from the snapshot (session tree + bulk summary)
  • vivekchand/clawmetry-cloud#2061 feat(desktop): open telemetry sink, admin panel, and per-account desktop list

Fixes

  • vivekchand/clawmetry-cloud#2073 Fix the five ways a paying account can lose its plan
  • vivekchand/clawmetry-cloud#2074 Describe a returning registration the way the heartbeat will
  • vivekchand/clawmetry-cloud#2075 A completed checkout reactivates the account it paid for
  • vivekchand/clawmetry-cloud#2076 Never send trial email to a paying customer
  • vivekchand/clawmetry-cloud#2089 fix(silence): stop paging every cloud user when a laptop sleeps
  • vivekchand/clawmetry-cloud#2093 fix(trace): the host shim must not rewrite /api/ paths
  • vivekchand/clawmetry-cloud#2072 fix(email): every urllib sender identifies itself, or Cloudflare 403s it
  • vivekchand/clawmetry-cloud#2083 fix(ci): retry the OSS pin install past PyPI's cross-CDN index race
  • vivekchand/clawmetry-cloud#2084 Show which machine a fleet card means; name the machines on runtime cards
  • vivekchand/clawmetry-cloud#2056 Approve/Deny-all in the fleet inbox; evict requests no longer pending
  • vivekchand/clawmetry-cloud#2059 Stop/Pause buttons for 10 more runtimes (matrix-gap mirror)

Chore / refactor / docs

  • ~15 chore: auto-pin clawmetry==0.12.7XX (mirrors OSS release chain)
  • 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)

Bot productivity (cross-repo aware)

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.

Suggested focus next week

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions