IronClaw Reborn wires Slack, observations, and permissions into the agent OS layer

What changed

The rendered ClawCharts board now has IronClaw at rank #9, and inspected project pages show the day’s signal running through concrete operator surfaces rather than a bare release line. Main inspected source: feat(traces): agent-driven Trace Commons onboarding via invite link (https://github.com/nearai/ironclaw/pull/4559). Supporting inspected pages include feat(traces): agent-driven Trace Commons onboarding via invite link, [codex] Fix NEAR context overflow classification, [codex] Fix manual token runtime credential selection, refactor(reborn): back automations panel facade with TriggerRepository (drop capability dispatch from panel reads), Gate extension activation on product auth.

Why it matters

IronClaw’s Reborn line keeps treating integrations as operating-system surfaces: allowed channels, preferences, structured tool observations, compaction state, and wallet/connect demand. It is ranked because permissions and observability are becoming product shape, not internal notes. 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 #9 on 2026-06-11; +44 stars over seven days; 11 active contributors; 151 seven-day commits; 12438 chart stars; GitHub repo nearai/ironclaw shows 12440 stars, 1142 open issues, pushed_at=2026-06-11T00:42:03Z; latest release ironclaw-v0.29.1 published 2026-06-03T19:18:09Z. The repository description observed from GitHub says: IronClaw is an Agent OS focused on privacy, security and extensibility. 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: nearai/ironclaw PR #4559.