ClawSweeper is a maintenance bot designed specifically for OpenClaw repositories that automates the review and management of issues and pull requests. Written in TypeScript, it scans open issues and PRs on a scheduled basis and through exact GitHub events to propose which items can be safely closed and why. The bot runs reviews on every PR and issue once a week, maintaining a conservative approach to automation by keeping proposals separate from enforcement and requiring explicit maintainer approval before taking action.
The bot's primary targets are openclaw/openclaw, openclaw/clawhub, and its own repository for self-review. ClawSweeper is not positioned as a public review service and does not provide free reviews for third-party repositories. Users who want to use ClawSweeper for their own projects must fork the repository, deploy it within their own organization, and configure it for their specific repositories.
At its core, ClawSweeper performs several interconnected functions. It reviews open issues and pull requests on a schedule and in response to exact GitHub events, writing one durable markdown report per item in generated state. The bot syncs one marker-backed public review comment per issue or PR, editing it in place rather than posting repeated comments. It closes only unchanged, high-confidence, policy-allowed proposals and routes maintainer commands such as @clawsweeper review, @clawsweeper fix, @clawsweeper autofix, and @clawsweeper automerge. The bot can repair opted-in PRs through a bounded Codex review and fix loop before merge, automatically open guarded implementation PRs for viable reviewed issues in eligible public repositories, and manually review selected code-bearing commits on target main branches.
The review process is deliberately conservative. ClawSweeper may propose closing an item only when it is clearly implemented on current main, not reproducible on current main, better suited for ClawHub work, a duplicate or superseded item, a low-signal pull request with an unrelated or unmergeable branch, an external low-rated PR whose proof never arrived and whose branch has been idle for 14 or more days, an external PR abandoned for 30 or more days, concrete but not actionable in the source repo, incoherent enough that no action can be taken, or a stale issue older than 60 days with insufficient data to verify. Maintainer-authored items stay open unless ClawSweeper can verify the request is already implemented on current main. Issues with open PRs that reference them using GitHub closing syntax remain open until that PR merges, is closed, or ClawSweeper closes that PR candidate.
GitGenius activity tracking shows that across 48 items, the repository has a median issue and PR response latency of 0.6 hours with a mean of 55.5 hours. The most active issue labels are clawsweeper:fix-shape-clear with 19 occurrences, impact:other with 17, and clawsweeper:no-new-fix-pr with 16. The most active contributors tracked are Takhoffman with 41 events, steipete with 36 events, and brokemac79 with 14 events. The repository shares overlapping contributors with openclaw/openclaw, nousresearch/hermes-agent, and amantus-ai/vibetunnel. Repository-specific rules live in src/repository-profiles.ts, allowing OpenClaw, ClawHub, and ClawSweeper to share the same engine while maintaining different apply limits for each project. Generated state is published to openclaw/clawsweeper-state on the state branch, containing durable records, jobs, results, audit output, workflow status, repair ledgers, and the rendered dashboard.
