NanoClaw’s redirected repo is a chat-container boundary watch

What changed

The rendered ClawCharts board now has NanoClaw at rank #6, and inspected project pages show the day’s signal running through concrete operator surfaces rather than a bare release line. Main inspected source: feat(container-runner): persist agent container stdout+stderr to disk (https://github.com/nanocoai/nanoclaw/pull/2727). Supporting inspected pages include feat(container-runner): persist agent container stdout+stderr to disk, feat: add uninstall.sh — per-copy uninstaller with confirmation, dry-run, and OneCLI agent cleanup, feat: add /add-guardrails skill — per-agent-group input/output guardrails, feat: add tool-visibility skill for live tool-call previews, Add web-search-plus skill (multi-provider web search + extraction, no MCP).

Why it matters

NanoClaw is still a redirected-repo wrinkle with live operational edges. The useful read is whether prompt-cache filtering, duplicate-send suppression, blocked hosts, environment storage, and MCP creation controls become durable container-agent policy rather than lucky middleware behavior. 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 #6 on 2026-06-11; +115 stars over seven days; 3 active contributors; 37 seven-day commits; 29787 chart stars; GitHub repo nanocoai/nanoclaw shows 29796 stars, 711 open issues, pushed_at=2026-06-10T20:02:30Z; latest release v2.0.64 published 2026-05-18T18:01:05Z. The repository description observed from GitHub says: A lightweight alternative to OpenClaw that runs in containers for security. Connects to WhatsApp, Telegram, Slack, Discord, Gmail and other messaging apps,, has memory, scheduled jobs, and runs directly on Anthropic's Agents SDK. 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 watchlist 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: nanocoai/nanoclaw PR #2727.