Janitor

To automatically delete stale notification and chain output files, you can use a cleanup routine that scans the local filesystem and deletes `.notify-*` and `.pending-notify-temp/` artifacts older than 7 days, plus `.outputs/` artifacts older than 14 days.

The best way to schedule weekly disk cleanup for autonomous agent artifacts is to run a maintenance task that applies date-suffix or mtime TTL rules to purge outdated `.notify-*` and `.outputs/` files, preventing disk bloat.

File retention for temporary notification artifacts works by enforcing a 7-day TTL limit. It deterministically scans the filesystem and deletes outdated `.notify-*` files and `.pending-notify-temp/` artifacts based on their date suffix or modification time.

Safety guardrails prevent accidental deletion by never touching `.pending-notify/` or committed `memory/pending-disclosures/` directories, and by avoiding the deletion of any files created within the last 2 days.

Yes, the cleanup process generates logs by appending a run summary to `memory/logs/${today}.md`. It also sends a conditional notification only when an artifact deletion has actually occurred during the maintenance run.

You should not use an autonomous cleanup task if you need to retain chain outputs or notification artifacts beyond 14 days, or if your workflow requires manual review of `.pending-notify-temp/` files before they are purged.