Files

ethernet 9f2ba1b74d merge origin/main (779 commits) into ethie/pm-clean

Branch semantics kept where main and PM disagree: update_cmd_deps.py,
constraints-termux.txt, the Electron update-api-check module and the
post-swap hand-off test stay deleted; the pending-fleet-restart catch-up
and the local_runtime tag/download ladder stay retired (PM owns engines).

Ported from main onto the branch's shape: profile_scoped_chore for the
auto-archive and plugin-update housekeeping chores, the local-runtime
cross-process boot lock and residency cap, the checkpoint tmp_pack sweep,
the cua daemon-liveness status probe, the remote-served Desktop update
flag (posix.sh / windows.ps1), sign-in for env-pinned remote gateways
(urlDisabled on RemoteSetupFields), the uvloop extra split (uvicorn
without [standard]), and the umask-scoping spawn test.

uv.lock regenerated with pm.build_env --lock-only; new utf-8 reads from
main switched to utf-8-sig (check-windows-footguns).

2026-09-21 00:58:39 -04:00

__init__.py

Merge remote-tracking branch 'origin/main' into ethie/pm-clean

2026-09-19 22:57:07 -04:00

disk_cleanup.py

merge origin/main (779 commits) into ethie/pm-clean

2026-09-21 00:58:39 -04:00

plugin.yaml

…

README.md

chore: mark the deliberate /tmp literals and shrink the lint baseline to one code block

2026-09-19 10:44:26 -07:00

README.md

disk-cleanup

Auto-tracks and cleans up ephemeral files created during Hermes Agent sessions — test scripts, temp outputs, cron logs, stale chrome profiles.

Scoped strictly to $HERMES_HOME and /tmp/hermes-*.

Originally contributed by @LVT382009 as a skill in PR #12212. Ported to the plugin system so the behaviour runs automatically via post_tool_call and on_session_end hooks — the agent never needs to remember to call a tool.

How it works

Hook	Behaviour
`post_tool_call`	When `write_file` / `terminal` / `patch` creates a file matching `test_`, `tmp_`, or `.test.` inside `HERMES_HOME`, track it silently as `test` / `temp` / `cron-output`.
`on_session_end`	If any test files were auto-tracked during this turn, run `quick` cleanup (no prompts).

Deletion rules (same as the original PR):

Category	Threshold	Confirmation
`test`	every session end	Never
`temp`	>7 days since tracked	Never
`cron-output`	>14 days since tracked	Never
empty dirs under HERMES_HOME	always	Never
`research`	>30 days, beyond 10 newest	Always (deep only)
`chrome-profile`	>14 days since tracked	Always (deep only)
files >500 MB	never auto	Always (deep only)

Slash command

/disk-cleanup status                     # breakdown + top-10 largest
/disk-cleanup dry-run                    # preview without deleting
/disk-cleanup quick                      # run safe cleanup now
/disk-cleanup deep                       # quick + list items needing prompt
/disk-cleanup track <path> <category>    # manual tracking
/disk-cleanup forget <path>              # stop tracking

Safety

is_safe_path() rejects anything outside HERMES_HOME or /tmp/hermes-*
Windows mounts (/mnt/c etc.) are rejected
The state directory $HERMES_HOME/disk-cleanup/ is itself excluded
$HERMES_HOME/logs/, memories/, sessions/, skills/, plugins/, and config files are never tracked
User project trees (workspace/, projects/, plans/, home/, patches/, skins/, themes/, contributors/, profiles/, backups/) and kanban/ (task attachments/workspaces) are never tracked or swept, even for files named test_*/tmp_*
A tracked directory under a protected top level (e.g. cache/, which holds terminal snapshots) is never removed; only its files age out. Stale entries are logged as SKIPPED and dropped
Backup/restore is scoped to tracked.json — the plugin never touches agent logs
Atomic writes: .tmp → backup → rename