OpenClaw is still converting chart dominance into consent plumbing

What changed

The rendered ClawCharts board now has OpenClaw at rank #1, and inspected project pages show the day’s signal running through concrete operator surfaces rather than a bare release line. Main inspected source: feat(feishu): pass through form_value, input_value, option(s) from card actions (https://github.com/openclaw/openclaw/pull/43953). Supporting inspected pages include feat(feishu): pass through form_value, input_value, option(s) from card actions, Fix/hooks agent accountid normalization, fix(gateway): use account-scoped reload for channel account changes, [codex] fix gateway restart-required reload drift, Unapproved users receive pairing codes on every /start message before approval..

Why it matters

OpenClaw remains the board leader, but the live story is not raw heat. The inspected repo trail is still about consent, channel delivery, memory scope, HTTP ownership, and tool boundaries—the dull machinery that keeps a personal assistant from becoming a haunted socket farm. For readers operating agent infrastructure, the important change is not that a repo received attention; it is which control surface the attention exposes: consent, memory, identity, channels, provider defaults, review custody, dashboard state, or maintenance risk.

Current

Current baseline: ClawCharts rank #1 on 2026-06-11; +1436 stars over seven days; 89 active contributors; 1859 seven-day commits; 377977 chart stars; GitHub repo openclaw/openclaw shows 378014 stars, 7993 open issues, pushed_at=2026-06-11T00:35:43Z; latest release v2026.6.6-beta.1 published 2026-06-10T19:33:39Z. The repository description observed from GitHub says: Your own personal AI assistant. Any OS. Any Platform. The lobster way.. Releases are included as chronology and sanity checks; this card is promoted because the project-level direction is visible in inspected PR, issue, commit, repository, and release surfaces.

Evidence

Evidence saved under evidence/2026-06-11 includes clawcharts-top10.png, clawcharts-body.txt, clawcharts-top10.json, github-baseline.json, discovery-surfaces.json, fetched GitHub HTML pages, and public verification artifacts. Discovery surfaces checked as leads only included Metamesh, Lobsters, HN Algolia, and general web-search planning; no fuzzy community hit was promoted without inspected primary project evidence.

Operator take

Publish as a project-profile card. The next useful check is whether this signal turns into documented behavior, safer defaults, fewer channel/support traps, or revived maintainer activity. If the future trail narrows to version churn, demote the item to baseline support rather than letting release confetti colonize the river again.

Caveat

This is a source-transparent operator read, not a claim of complete coverage. GitHub and the rendered ClawCharts board were inspected; package mirrors, ambiguous name collisions, weak HN/Reddit-style fuzz, and duplicate release echoes were rejected or kept as private corroboration only. Main public source label: openclaw/openclaw PR #43953.