OpenClaw Maintainer Activity

High visible activity: 242 commits, 9 PRs opened, and 31 merged across openclaw/openclaw, fs-safe, docs, ask-molty, and imsg. Focus areas included filesystem boundary guards, ClawSweeper dashboard/link repair fixes, and macOS 26/iMessage bridge work, alongside 114 Discord messages mostly in maintainers.

High visible activity: 166 commits, 23 PRs opened, and 26 merged across openclaw/openclaw, crabbox, graincrawl, gitcrawl, and discrawl. Focus areas included crabbox CI capacity pressure, AWS regional capacity routing, crawlkit dependency updates, and active maintainers/security-ops Discord discussion.

Visible activity centered on ClawHub: 15 commits, 10 PRs opened, and 11 merged, mostly in openclaw/clawhub. Work included adding a PR template, a friendlier 404 page, and worktree bootstrap fixes, with Discord discussion also mentioning ClawHub 404 work and plugin-owner mismatch checks.

Visible activity included 26 commits and one merged PR across openclaw/openclaw and Kova. Focus areas included no-proxy undici fetch side effects, manifest registry reuse, Codex native approval prompts, provider auth alias scope, and turn plugin metadata snapshots, with 61 maintainers-channel Discord messages.

Visible activity was mostly Nix-related: 31 commits and one merged PR across nix-openclaw, nix-openclaw-tools, and openclaw. Work focused on immutable/declarative workspace and config handling, including automatic write guards for Nix mutators, with a small amount of maintainers Discord discussion.

Visible activity was in openclaw/openclaw with 12 commits, 3 PRs opened, and 5 merged. Focus areas included Telegram transcript gap-fill and picker behavior, guarded fetch dispatcher cleanup, and gateway session-list model refs, plus Discord discussion around doctor behavior, API keys, and setup breakage.

Visible activity was in openclaw/openclaw with 8 commits, 7 PRs opened, and 7 merged. Focus areas included cron self-introspection, pnpm global root preservation, and ACP streamed progress summary spacing; no Discord activity was visible.

Visible activity spanned clawsweeper and openclaw/openclaw with 4 commits, 2 PRs opened, and 2 merged. Focus areas included proof-review nudges toward screenshots/redaction, contributor redaction reminders, channel restart recovery, and same-session Codex reply routing, with 41 maintainers-channel Discord messages.

Visible activity focused on fs-safe and openclaw/openclaw with 4 commits, 3 PRs opened, and 2 merged. Work covered boundary bypass test renames and expanded parity coverage plus narrowing a Gateway proxy bypass target, with Discord discussion around screenshot risk text and allow/block list parsing.

Visible activity was in openclaw/openclaw with 2 commits, 5 PRs opened, and 2 merged. Focus areas included cron persisted model sentinels, cron default model inheritance, OAuth refresh race gateway proof, and a Discord note about starting on Codex harness issues.

Visible activity focused on imsg with 2 commits, 2 issues opened, 2 issues closed, and 2 PRs opened/closed. Work and discussion centered on macOS 26 send-attachment bridge failures, BlueBubbles private API parity, iMessage/OpenClaw interop, and plugin deprecation/migration concerns.

Visible activity was in openclaw/openclaw with 2 commits, 2 PRs opened, and 2 merged. Focus areas included resilient gateway startup for optional plugin capabilities and bounding live exec output events, echoed in maintainers Discord with commit references and gateway/exec-loop context.

Visible activity covered fs-safe and openclaw/openclaw with 3 commits, 3 PRs opened, and 2 merged. Focus areas included shell completion profile guards, pnpm workspace prepare fixes, and hardening file store writes against symlink swaps; no Discord activity was visible.

Visible GitHub activity was in clawbench with 2 commits and one merged PR around Kubernetes docs/manifests and sidecar deploy flow. Discord activity included maintainers and offtopic messages, including eval-suite and meeting-join command discussion.

Visible activity included one commit, 2 PRs opened, and one merged across openclaw/openclaw and clawbench. Focus areas included Kubernetes docs/manifests in clawbench and a basic-ftp dependency bump, with Discord discussion around CI/test completion.

Visible activity was in openclaw/openclaw with 3 PRs opened and 3 merged, without commits recorded in this window. Focus areas included restoring Control UI /new hooks, preserving mixed assistant history text, and repairing iOS LAN pairing, plus a few maintainers Discord messages.

Visible activity was in openclaw/openclaw with one commit and 4 merged PRs. Focus areas included compaction max token clamping, context engine cache invalidation, doctor load-path plugin contracts, and Pi auto-compaction safeguards, with Discord noting ongoing compaction/context-engine fixes.

Visible activity was in openclaw/openclaw with 2 commits and one merged PR. Focus areas included recovering externalized channel plugins from stale config and a matching changelog entry, with Discord discussion about channel listing and configured/enabled channel state.

Visible activity was in openclaw/openclaw with 2 commits, 2 PRs opened, and 2 merged. Work focused on cleaning temporary directories after script and update-cli test cases; no Discord activity was visible.

Visible activity was in openclaw/openclaw with one commit and one merged PR. Focus area was Mattermost wizard setup URL collection, with a maintainers Discord message describing rough-edge work on Mattermost as an agent chat surface.

Visible GitHub activity was one closed openclaw/openclaw PR on reply-path runtime surface reuse. Discord activity was mostly maintainer-offtopic with a few maintainers-channel messages, but no concrete technical focus beyond the closed PR title was visible.

No visible GitHub activity in this window. Visible Discord activity was 12 maintainers-channel messages, including discussion of conference timing and breakage from an external safety-system error.

Visible activity was in openclaw-windows-node with one commit and one merged PR for agent events UI cleanup/redesign. Discord context described moving windows-node toward parity with the Mac Companion for install, pairing, and settings management.

Visible activity was two merged openclaw/openclaw PRs. Focus areas were enforcing allowlist argument patterns for exec and enforcing wiki session visibility for memory; no Discord activity was visible.

Visible activity was in openclaw/openclaw with one commit and one merged PR. Focus area was gating Slack startup user allowlist resolution; no Discord activity was visible.

No visible GitHub activity in this window. Visible Discord activity was 6 maintainers-channel messages focused on whether a Feishu package was community-maintained, official, buggy, or should be removed.

Visible GitHub activity was one closed openclaw/openclaw PR about xAI auth reuse and configure UX polish. One maintainers Discord message discussed a generic message bus in another project and possible application to OpenClaw.

No visible GitHub activity in this window. One maintainers Discord message asked about stale skill-list updates in channels such as Signal after OpenClaw skill changes.