Skip to content

Weekly digest -- 2026-09-07 (Session Trail + Guard made real + OpenAI cost crisis resolved) #5624

Description

@vivekchand

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.

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.


Shipped (OSS only — ~52 meaningful PRs)

OSS (vivekchand/clawmetry)

Features

Fixes

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-feedback or intel-pain labelled 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)

Two regressions that were open entering this week have not yet been closed:


Bot productivity


Concerning signal

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.


Suggested focus next week


Code activity (OSS only — cloud data unavailable)

OSS

  • Commits (7 days): 49
  • Lines: +831,265 −7,915 across 2,383 files (large addition count reflects the i18n / generated README sync that touched many files)
  • Contributors: Vivek Chand, dependabot[bot], github-actions[bot]
  • Releases: v0.12.807 → v0.12.826 (19 PyPI releases this week)

Cloud

  • [data unavailable] (proxy: 19 OSS RELEASE PRs merged = 19 cloud deployments via release-on-merge)

Bot meta

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).

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