Purge trace content

Remove stored trace content when you no longer need it, keeping scores and costs so runs stay resumable, and understanding what Kno stores where.

Runs are stored locally in SQLite (kno.db in the working directory), including the agent’s output, which is conversation content if your evals come from production logs.

kno purge --run-id <run id>

--run-id is required, purge is per-run. Add --yes for unattended/scheduled runs.

What purge does

Deletes trace content only.
Keeps scores and costs, a purged run stays resumable.
Deletes nothing on its own: nothing expires unless you decide.

What Kno does not do

Kno sends nothing anywhere: there is no telemetry of content, ever.
Your cases go only to the provider you point Kno at; that provider’s retention is theirs.
Trace content never appears in log lines above DEBUG, and none ever goes into telemetry.

Full retention semantics: the retention recipe.