Download Latest Version ClawSweeper 0.2.0 source code.tar.gz (485.5 kB)
Email in envelope

Get an email when there's a new version of ClawSweeper

Home / v0.2.0
Name Modified Size InfoDownloads / Week
Parent folder
ClawSweeper 0.2.0 source code.tar.gz 2026-05-03 485.5 kB
ClawSweeper 0.2.0 source code.zip 2026-05-03 601.0 kB
README.md 2026-05-03 3.9 kB
Totals: 3 Items   1.1 MB 1

Added

  • Accepted @clawsweeper fix as a short issue implementation command that creates or updates one guarded ClawSweeper PR for an open issue.
  • Added an openclaw/openclaw active review-shard floor so scheduled normal review keeps capacity warm around the clock even when the due backlog is temporarily below full shard capacity.
  • Added coarse automerge repair progress updates to the existing mutable status timeline for validation, Codex edit, review, base-sync, and wait phases.

Changed

  • Switched the shared Codex setup action to a per-run CODEX_HOME with a local Responses proxy so Codex subprocesses no longer inherit raw OpenAI/Codex API key environment variables.
  • Replaced duplicate-lobster command status badges with one lobster plus a state emoji for acknowledgement, review, repair, and completed/paused work.
  • Kept broad review continuations warm and faster by preserving the openclaw/openclaw active shard floor, stopping saturated planning once capacity is full, capping optional pre-shard dashboard publishes, and moving broad continuation comment sync into the separate comment-sync lane.
  • Removed the expensive record reconciler from pre-shard planning status so review jobs can start without waiting on a full GitHub state scan; publish, apply, and audit still reconcile before mutating records.
  • Made read-only review planning hydrate generated state from a shallow checkout instead of cloning the full generated-state history.
  • Removed generated-state checkout and hydration from review shards; the planner already passes exact item numbers, so shards can start Codex after checkout and runtime setup instead of copying historical records first.
  • Moved exact event review state hydration after the Codex review step so maintainer-triggered single-item reviews can start the model before generated records are copied.
  • Made the GitHub activity notifier workflow use a lean uncached Node/pnpm setup so bursty events do not wait on actions/cache downloads before notifying OpenClaw.
  • Wrapped review shard execution in a computed shell timeout so one hung broad review shard records failed-shard artifacts and enters recovery instead of blocking publish until the full GitHub job timeout.
  • Updated sweep and commit-review artifact upload/download actions to their Node 24-compatible versions so review runs no longer emit artifact action runtime deprecation annotations.
  • Updated TypeScript tooling while preserving the existing pnpm workflow.

Fixed

  • Kept review continuations warm when the normal backlog is below the target active shard floor.
  • Retried transient Codex edit-pass transport failures where the Codex tool router reports a closed stdin session, instead of failing the whole repair worker after an otherwise recoverable automation run.
  • Accepted scoped scripts/run-opengrep.sh --error -- <paths> validation hints so automerge repair execution does not fail preflight before normalizing OpenClaw repairs to the changed-surface gate.
  • Accepted spaced auto merge command aliases everywhere automerge and auto-merge are accepted, including the top-level /auto merge shorthand.
  • Updated issue implementation command comments after a fix PR opens, linking the generated PR from the original ClawSweeper status comment instead of leaving the acknowledgement at "queued".
  • Recovered issue implementation workers from state propagation races by reconstructing minimal source: issue_implementation jobs from the dispatched job path instead of skipping the worker as stale.
  • Routed trusted ClawSweeper verdicts with P0/P1/P2/P3 findings through the repair loop even when the same review also contains a pass marker.
  • Made /clawsweeper stop revoke repair-loop labels and block older automerge/autofix comments from continuing, so a trusted pass marker cannot clear a human-review pause and merge after a maintainer stop.
Source: README.md, updated 2026-05-03