BeaCox

CleanerX — Development skill for Claude Code

Development community

A local-only desktop app to review and safely clean storage created by Codex, Claude Code, OpenCode, and pi.

How to install CleanerX

This entry records only its repository, not the path inside it, so there is no exact command to give. Open BeaCox/CleanerX and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What CleanerX does

A local-only desktop app to review and safely clean storage created by Codex, Claude Code, OpenCode, and pi.

Alternatives in Development

  • IPolloWork — Enterprise-grade, local-first Agent Workbench for people and agent teams 4.9k ★
  • Hapi — App for Claude Code / Codex / Gemini / OpenCode, vibe coding anytime, anywhere 3.6k ★
  • OpenSail — OpenSail is the open-source alternative to Codex App, Claude Desktop, Cursor, and Cowork for agentic software 634 ★

README

CleanerX — Clean storage. Clear mind. Better code.

CleanerX

Review and safely clean private local data left by coding agents.

Product CI Apache-2.0 license

CleanerX is a local-only desktop application for inspecting and cleaning storage created by Codex, Claude Code, OpenCode, and pi. It presents a metadata-first inventory, expands the exact cleanup scope for review, and fails closed when an Agent capability, storage schema, path, or writer state cannot be verified.

CleanerX does not upload data, collect telemetry, synchronize with cloud services, or run in the background. A project path is grouping metadata only: CleanerX never recursively scans or modifies a source directory. The only built-in network action is an explicit application-update check against CleanerX's GitHub Releases feed.

[!CAUTION] CleanerX permanently deletes private local data. The repository is an engineering preview and does not yet provide a promoted binary release; current builds are unsigned. Nothing is selected automatically. Review every cleanup plan; if backup is unavailable or left off, deletion is irreversible.

Why CleanerX

Coding agents can retain session histories, generated media, memories, logs, caches, and temporary files across many projects. Those data classes do not share one safe deletion rule: some have an official API, some use documented files, and some must remain read-only.

CleanerX gives them one review workflow without flattening those differences:

  • inventory first, without retaining content bodies beyond one bounded pi display-title e