{"version":"2.1.223","anchor":"telemetry-run-files-get-their-own-cleanup-pass","canonical_anchor":"telemetry-run-files-get-their-own-cleanup-pass","heading":"Telemetry run files get their own cleanup pass","tier":"notice","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/telemetry-run-files-get-their-own-cleanup-pass","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Telemetry run files get their own cleanup pass\n\nLeftover telemetry run files are cleaned up properly, and cleanup no longer probes folders that don't exist.\n\n**What**\n\nTelemetry cleanup now covers run files and avoids descending into agent subdirectories that are not there.\n\n**Details**\n\n- The telemetry directory cleanup walks a `runs` subdirectory using a `.json` entry matcher.\n- Recursive agent-directory cleanup descends into subagents, workflows and remote-agents only when the directory actually exists.\n\n**Evidence**\n\n`\"subagents\", \"workflows\", \"remote-agents\"`\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}