Agent Context Hygiene Audit

In short

Sessions, memory, autostart, integrations, and background tasks grow over time, but deleting them based solely on size is dangerous.

Outcome

A strictly read-only audit collects sizes, ages, last-run evidence, and duplicates, explains risk by set thresholds, and forms a queue of manual actions without applying changes.

How the automation runs

Trigger

Owner initiated an audit or a scheduled check window arrived

Automation steps

1. Inventories authorized areas without reading secret content and private messages
2. Collects size, age, freshness, and actual usage
3. Applies explicit thresholds and flags missing data
4. Finds candidates for archive, duplicates, and orphaned background tasks
5. Creates an evidence report and a preview of safe manual actions

Human check

The audit does not delete, move, or edit anything; each action affecting a file, session, memory, or schedule requires separate review and confirmation by the owner.

Outcome

A strictly read-only audit collects sizes, ages, last-run evidence, and duplicates, explains risk by set thresholds, and forms a queue of manual actions without applying changes.

Using it

When to use it

Context has become expensive or unstable, compactions have increased, and a documented revision of sessions, memory, and background tasks hasn't been performed in a long time.

How to verify

The report covers all authorized areas with measured evidence and an unknown state if data is insufficient, and control hashes confirm no file changes.

Tools

Recipe details