$ the-wire · showcase
Clawsweeper isolates Git overrides, OpenClaw hardens restart recovery
By RepoJournal · Filed · About OpenClaw · Composed from the cited sources · methodology
![openclaw-docs-sync[bot]](https://avatars.githubusercontent.com/u/13697529?v=4)
A day of containment and cleanup: Clawsweeper stops inheriting host Git configuration into model subprocesses, OpenClaw's recovery path keeps tool restrictions and snapshot disposal honest across restarts, and Peekaboo refuses retention flags that would delete more than asked.
fix: isolate model subprocesses from inherited Git overrides (#1645) openclaw/clawsweeper
Model subprocesses no longer inherit indexed or parameter Git configuration from the parent environment; the existing denylist loops strip it, while explicit command-line config, global/system isolation, scoped token handling, and repaired author/committer identity all stay intact. If you run the sweeper against repos with inherited Git overrides, the subprocess behavior changes with it.
fix(recovery): preserve restart-safe tool ownership openclaw/openclaw
An older run could clear a newer recovery owner's restart-safe tool restriction, and a terminal-result race could capture restart-status text as the interrupted turn's final answer. Interrupted turns now retain the current recovery owner and safe-tool policy across restarts, and restart status never becomes a final delivery; the change requires no configuration, schema, protocol, or persistence...
fix: clean interrupted SQLite snapshot allocations openclaw/openclaw
Cancelling a SQLite snapshot could leave an empty nested staging directory behind, blocking parent cleanup and surfacing a snapshot cleanup error in place of the caller's cancellation. The interruption point, between creating the child directory and its ownership token, also matches the exception seen in the database-preflight CI case.
fix(cli): reject non-positive --older-than snapshot cleanup openclaw/Peekaboo
clean --older-than -1 moved the cleanup cutoff into the future and could select every eligible snapshot; zero and negative retention are now rejected in both the CLI and FileService before any data is accessed or removed, mapped to VALIDATION_ERROR. Positive retention and dry-run behavior are unchanged.
fix: keep issue follow-up grounded in the review openclaw/clawsweeper
Issue follow-up could declare reproduction not applicable and still demand screenshots, commands, and expected-versus-actual behavior, because the renderer inferred those requests by keyword-scanning Codex's prose. It now uses plain English and carries the next action Codex actually requested, so design proposals keep their design decision and evidence-thin bugs keep their specific ask. Opencla...
