Skip to content

Weekly digest -- 2026-08-17 (attention layer + Memory & Skills real + 2 new runtimes) #4959

Description

@vivekchand

Theme of the week

The big shift this week: ClawMetry stopped guessing and started knowing. The needs-you attention layer tells you exactly which agent is waiting on you across all runtimes; Memory & Skills went from a stub to a real GitHub-style file viewer with per-runtime sync; and the trial paywall was armed — the monetization rail is finally closed. Two new runtimes (DeepSeek Harness, Exo) pushed the catalogue to 21, and the approval-delivery seam moved fully behind the cloud license.


Shipped (~52 feature/fix/test PRs in OSS; cloud data unavailable — see Bot meta)

OSS (vivekchand/clawmetry)

Features

Fixes

Tests

Docs / chore

Cloud (vivekchand/clawmetry-cloud)

⚠️ Cloud repo data unavailable this run. GitHub MCP access for this session is scoped to vivekchand/clawmetry only — vivekchand/clawmetry-cloud calls were denied. Cloud PR/issue/commit data could not be fetched.
Fix: add vivekchand/clawmetry-cloud to the GitHub MCP server's allowed-repo list for the weekly-digest session, or grant this scheduled session access to the private repo.
Cloud-side context inferred from OSS: approval delivery seam, entitlement API blitz, paywall rail, and per-runtime cloud sync of Memory & Skills all have corresponding cloud-side counterparts — but those PRs aren't counted below.


Biggest user-visible win

#4916 + #4922 + #4924 — Needs-you attention layer

Before this week, if an agent was waiting for your input you had no way to know without opening its transcript. Now ClawMetry shows a dedicated attention surface across all runtimes: which session is paused, why it's waiting, and what runtime it belongs to. Wire it with one command — clawmetry hook attention — and the dashboard pings the moment an agent needs you. For anyone running multiple agents in parallel, this is the first time the tool actually tells you where to look.


What users asked for (intel)

No intel-feedback or intel-pain issues were filed this week in the OSS repo. The obs-gap scanner is generating harness-gap issues (see Concerning signal) but there are no user-sourced intel hits to surface.

⚠️ If users are filing feedback in the cloud repo or via other channels, it's invisible to this run — cloud repo is inaccessible (see above).


Backlog health (OSS only — cloud unavailable)

  • Open issues: 69 OSS (cloud unknown)
  • Open PRs: 4 OSS — 1 draft (#4957 feat entitlement batch, opened today), 0 stale (>14 days); oldest non-draft: #4707 (fix desktop uninstall, opened 2026-08-09, 8 days)
  • Oldest open issue: feat(v0.13): Native Event Stream Consumer — reference consumer for openclaw/openclaw#6467 #34 feat(v0.13): Native Event Stream Consumer (opened 2026-02-28, ~170 days)
  • Median open-issue age: ~45 days (many large backlog epics from May–July dragging the median up)
  • Top label counts (OSS):
    Label Count (est.)
    triaged ~60
    bot-plan-only ~30
    enhancement ~30
    harness-gap + observability ~20
    bot-pr-opened ~8
    weekly-digest 6 (incl. this one)
    bug 1 (#4782 OTLP Tracing tab — open 5 days)

Bot productivity (OSS; cloud unavailable)

  • Obs-gap / harness-gap bot: 10 new obs-gap issues spawned PRs (bot-pr-opened) and were closed as fixed this week. However, 9 obs-gap issues were closed as duplicates — the dedup logic is misfiring (same gaps for OpenClaw secret egress, Canvas pin state, workspace conflicts, Fish Audio TTS were refiled on Aug 12, Aug 14-15, and again Aug 16-17). This is the biggest bot hygiene problem this week.
  • Triage bot: operating normally; all new issues arrive pre-tagged triaged.
  • Intel scout: 0 intel issues filed this week (no intel-feedback / intel-pain labels seen).
  • Smoke watchdog: no regression issues observed in OSS backlog.
  • PR babysit: no <!-- bot-babysit --> marker activity visible.

Concerning signal

The obs-gap scanner is re-filing duplicates every 2–3 days. This week, at least 9 issues were filed as duplicates of existing open obs-gap issues — the same signal for OpenClaw secret egress (#4807#4906#4953), workspace conflicts (#4747#4809 → redundant), and Fish Audio TTS (#4724#4749#4956) keeps appearing. The scanner is not checking existing open issues before filing, which is flooding the backlog with noise and making it harder to see what's genuinely new.

Next step: add a dedup check in the obs-gap scanner — query open issues for the same runtime:* + gap title before filing. Close the oldest duplicates in bulk.

Also worth watching: #4782 (Tracing tab: OTLP apps have no trace to open) has been open 5 days while the OTLP SDK and receiver shipped this week. Now that users can send traces, they'll hit this immediately. It should be the first fix next week.


Suggested focus next week


Code activity

OSS (vivekchand/clawmetry)

  • Commits: 49 (past 7 days)
  • Contributors: Vivek Chand, github-actions[bot]
  • Releases: v0.12.685 → v0.12.726 (+41 patch versions; ~6 named releases per day on busy days)
  • Releases published this week: v0.12.721 through v0.12.726 visible in releases API (plus many intermediate patch tags)

Cloud (vivekchand/clawmetry-cloud)

  • Commits: unavailable (repo not accessible — see above)
  • Contributors: unavailable
  • Releases: N/A (proxy: cloud-side approval delivery seam + entitlement API blitz inferred from OSS counterparts)

Bot meta

Auto-generated 2026-08-17 07:25 UTC by the weekly digest bot. Tagged triaged so other bots leave it alone.
Cross-repo design as of 2026-05 — but cloud repo (vivekchand/clawmetry-cloud) was inaccessible this run due to MCP session scope. OSS-only data used throughout.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions