OpenClaw Maintainer Activity

High visible activity across openclaw/openclaw, clawpatch, crabbox, crabyard, and clawhub, with 193 commits, 43 PRs opened, and 83 merged; focus included update EACCES recovery, session route projection, notification wake policy, Admin HTTP RPC gateway isolation, and Claude CLI doctor behavior. Discord activity was also high in maintainers, clawtributors, and security ops, including release/social links, mode confusion, and feedback discussion.

High GitHub activity with 164 commits and work across openclaw/openclaw, crabbox, crawlbar, clawpatch, and openclaw-rtt; focus included release gate regression repair, gitcrawl-store changed file path retention, and clawpatch monorepo root mapping. Discord activity was mostly in maintainers, with some off-topic discussion around token efficiency and optimization tradeoffs.

Visible activity centered on openclaw/Kova with 91 commits, including report snapshot refreshes, resolving reports by run id, failed post-ready health sample gating, and compare metric labeling and ordering. Discord discussion touched report improvements and release RSS behavior in maintainers and clawtributors.

Activity focused on clawsweeper and openclaw with 22 commits, 37 PRs opened, and 35 merged; work included preserving proof labels for clawsweeper/Barnacle and explaining human-review pauses. Discord comments in maintainers referenced proof override usage and labels for maintainer review readiness.

Openclaw-focused activity with 44 commits and 7 merged PRs, mainly around Telegram/channel delivery, tool-progress drafts, transcript mirroring, topic media completion, Android talk mode relay, final reply delivery, and release stability/auth fallback. Discord activity in maintainers and clawtributors included PR review/landing notes and Codex app progress-update behavior.

ClawHub-focused activity with 5 commits, 9 PRs opened, and 7 merged; work included autoban remediation, owner-scoped skill slugs, and security scan admin tooling. Discord activity in maintainers and clawtributors included overlap checks and discussion around security-related tooling direction.

Activity was concentrated in openclaw/openclaw-windows-node, with 3 commits, 7 PRs opened, 9 merged, and 1 issue opened; focus included WSL gateway validation tray output paths, onboarding blockers, chat revamp work, tray disconnected behavior, and v2 wizard reload mode handling. Discord activity was minimal in maintainers.

Openclaw activity included 4 commits, 6 PRs opened, and 7 merged, with focus on rejecting empty CLI subprocess replies, Codex harness provider ownership, Telegram/Ollama image passing, and stalled isolated spool handler recovery. Discord activity in maintainers and clawtributors included release tweet discussion and bug-worth-fixing triage.

Visible GitHub work covered openclaw and proxyline with 2 commits, 2 PRs opened, and 2 merged, focused on approval runtime gateway calls and pinning a managed fetch dispatcher. Discord activity was moderate in maintainers and clawtributors, including crabbox/local VM setup discussion and local workflow pain points.

Openclaw activity included 4 commits and 8 merged PRs, with focus on doctor repairs for channel model providers, export trajectory session keys, read-only health checks, WhatsApp TUI process matching, and legacy package upgrade handoff. No Discord activity was visible in the provided window.

Light GitHub activity across hermit and community included 2 commits and 1 merged PR, focused on deduplicating clawtributor claim requests, documenting hermit D1 deploy flow, and Cloudflare Builds deploy command use. Discord activity in maintainers and clawtributors covered npm package freshness/plugin discovery, filtering, telemetry, and log-gathering concerns.

Openclaw activity included 3 commits, 2 PRs opened, and 3 merged, focused on iOS live activity lifecycle, WhatsApp media sends, and mobile OS metadata refresh. Discord discussion included iOS/Android QR bootstrap operator scopes and related security-ops coordination.

Activity covered openclaw and graincrawl with 1 commit, 2 PRs opened, and 1 merged, focused on sync skip flags, plugin diagnostics nonfatal handling, and pending exec approval resolution. Discord maintainers discussion referenced model behavior, context corruption, and message tool behavior.

Minimal GitHub activity: 1 merged openclaw item focused on resolving lmstudio env-template API keys. Discord activity was mostly in maintainers and off-topic, with discussion around token use, OpenClaw framing, and misinformation.

Light openclaw activity included 1 PR opened and 1 merged around skipping the real-behavior-proof gate for private maintainers. Discord maintainers discussion covered a TUI final-response display issue and proof override/maintainer status behavior.

Light clawpatch activity included 1 commit and 1 closed PR, with items around deslopify review mode and ranked report clusters. Discord maintainers messages included a wacli media-file PR pointer and off-topic travel/location discussion.

Openclaw activity included 1 commit, 2 merged PRs, and 1 closed PR, focused on Mattermost missing channel types, browser current-tab route guarding, and tagging NVIDIA NIM requests with app origin. No Discord activity was visible in the provided window.

No GitHub activity was visible. Discord activity in maintainers and clawtributors included asking for an openclaw PR for review and discussing deferred dynamic tool registration and shorthand tool names in developer instructions.

Light openclaw activity included 2 merged PRs, focused on sanitizing unsafe GitHub Copilot reasoning replay ids and skipping changelog-only workflow runs. Discord activity was limited to 5 maintainer-channel messages with no provided excerpts.

Light openclaw activity included 1 commit, 1 PR opened, and 1 merged, focused on shortening the qqbot typing keepalive window. Discord activity was minimal in maintainers.

Light openclaw activity included 3 merged PRs, focused on flaky config set help text tests, sidebar tree collapse behavior, and exposing reload kind in config schema lookup. No Discord activity was visible in the provided window.

Minimal GitHub activity: 1 merged acpx item adding slophammer TypeScript constraints. Discord maintainers discussion referenced local-model/tool-schema behavior, context bloat, Gemma prompt/schema optimization, and contact routing.

Minimal openclaw GitHub activity: 1 commit for bypassing npm freshness during managed installs. Discord maintainers messages referenced PR #83761 and a locally reproduced release-distance-related issue.

Minimal GitHub activity: 1 closed openclaw PR around optional Slack speaker labels for group threads. Discord maintainers discussion referenced a small plugin-related fix, issue #83762, and thread participation persistence affecting Slack, Discord, Matrix, and Teams.

No GitHub activity was visible. Discord activity in maintainers and maintainer-lounge included Red Hat-related release-image discussion, a Codex module error traced to a live app-server child process, and whether to add codex to OPENCLAW_EXTENSIONS.

No GitHub activity was visible. Discord activity in security ops, maintainers, and lounge included stable release impact discussion, affected-user pattern investigation, and automation to find GitHub issues caused by PRs.

No GitHub activity was visible. Discord activity in maintainers and off-topic included asking for current priorities around bugs, stability, and usability, plus discussion of OpenClaw content creation.

No GitHub activity was visible. Discord maintainers activity referenced investigating account switching and plugin use being blocked by Cloudflare bot detection, with backend WAF rule updates for OpenClaw originator bypass.

No GitHub activity was visible. Discord activity was minimal in maintainers, including a greeting and a note about adding an entry in the middle of a section.