v0.5.1

Installation fix

Installation can now complete on affected filesystems where dependency tools rename temporary directories. The installer checks cumulative logical and allocated growth before and after each subprocess, and monitors the free-space floor while the subprocess runs. Temporary growth that disappears between those boundaries is not measured by the growth check.

Updating

Use the verified 0.5.1 installer to stage this release alongside existing installations, then activate it and register the reported MCP command. Keep previous installations while unresolved cleanup receipts depend on them. The published v0.5.0 release remains available with its original tag and files.

See the installation instructions and upgrade procedure.

Cleanup compatibility

This patch reuses the qualified native component and cleanup contract from 0.5.0. Compatibility remains scoped to the documented Linux x86_64 deployment and exact storage schemas. Related metadata updates and history-reference publication must have finished before selected cleanup.

Full cleanup previews inspect the managed history namespace and can take substantial time on large or slow filesystems. Completion within a fixed time is not guaranteed when filesystem calls block.

v0.5.0

Changes

• Clean up stopped session and agent histories even when their stored spawn relationship remains Open. Writer ownership, retained-history dependencies and exact file/SQL effect checks remain enforced.
• Assess newer versions against the source paths and storage behavior that affect cleanup. Reuse the qualified native helper when execution inputs remain compatible, and import signed support records without restarting the MCP server.
• Install and update a matched Python/native bundle with verified GitHub provenance and hash-locked dependencies. Preserve previous installations needed to inspect saved cleanup receipts.
• Use the shared cleanup pipeline through CLI, Textual and MCP, including explicit selection, project/work grouping, sorting and supported Guardian histories.

Using this release

Follow the installation and upgrade guide. The attached installer verifies the release before activation. Reconnect existing MCP clients after updating the application.

Select stopped work. Related updates to the selected histories' metadata and publication of dependency references must have finished; unrelated sessions may continue running. Fresh validation can refuse an operation if its approved effects have changed. Use reconciliation to inspect an uncertain result; do not resend an uncertain deletion.

Cleanup removes the approved histories directly without copying their contents to a backup or substituting compression for deletion.

Full preview validates the entire managed history namespace, including retained dependencies. It can take substantial time on large or slow filesystems. Blocked filesystem calls have no finite completion guarantee; catalogue browsing and full preview are separate operations.

Compatibility

Qualified for Linux x86_64 with the documented runtime and local-filesystem requirements, including the supported Codex 0.166.0 persistent workflows. Plain and Zstandard-compressed histories and paginated storage remain supported within the qualified profile. See the compatibility guide and cleanup contract for exact conditions.

The bundle, wheel, source archive and installer have GitHub artifact attestations. The support record is separately attested. SHA256SUMS lists the assembly checksums; the native material is additionally pinned by the source qualification and bundle manifests.

The native-material.tar.gz asset is the qualified native build input for maintainers and CI. End-user installation uses the verified installer and matched runtime bundle.

v0.4.0

Version 0.4.0 makes it easier to find the histories you want to remove and understand cleanup results.

• Browse individual histories across work groups, ordered by stored size or last activity in either direction. Find the largest histories or oldest activity without opening each group. Reordering preserves your selection; unknown sizes and dates stay last.
• Filter by exact stored working directory, archive state, ordinary agents or Guardians, alongside existing text, date and size filters.
• Run doctor to observe helper and storage compatibility before cleanup. Its report is diagnostic; cleanup still performs fresh checks.
• Use MCP with --read-only for browsing, conditional previews and saved status without exposing apply or reconciliation tools.
• The terminal interface shows elapsed waiting time, the operation ID and actual returned results for each work group. Silence from the helper remains waiting, rather than an invented progress percentage.
• Catalogue observation and preparation avoid unnecessary waiting on larger collections.

Cleanup confirmation no longer depends on clients preserving large filesystem numbers exactly. A history outside the chosen work produces a structured refusal. Failed launches and uncertain operations retain clearer status, and confirmed selections remain bound to the storage reviewed during preparation.

Custom MCP integrations must pass the unchanged operation_id and digest strings from the preparation response’s confirmation to apply_cleanup. Full declarations are no longer accepted.

Install the matched bundle using the installation instructions. Reconnect MCP clients after updating. Keep the old installation and receipts while any operation remains unresolved; a lost reply is not a reason to repeat deletion. Follow the upgrade and recovery procedure.

v0.2.0

Closed-history cleanup through Textual, CLI and MCP while unrelated sessions continue.

The Linux x86_64 bundle includes the qualified native helper and Python wheel. Python 3.14 or newer is required; the qualified host is Ubuntu 26.04 with glibc 2.43. The standalone wheel does not include the helper.

Verify SHA256SUMS before extracting. Installation, selection rules, recovery and compatibility are documented in the README.

The source archive includes helper sources, patches, synthetic tests and license notices. Project code is Apache-2.0; third-party terms accompany the artifacts.