{"version":"2.1.304","anchor":"diskmemory-watchdog-no-longer-depends-on-claude-code-diagno","canonical_anchor":"diskmemory-watchdog-no-longer-depends-on-claude-code-diagno","heading":"Low disk and memory watchdog no longer needs the diagnostics variable","tier":"notice","area":"Diagnostics","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/diskmemory-watchdog-no-longer-depends-on-claude-code-diagno","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Low disk and memory watchdog no longer needs the diagnostics variable\n\nThe watchdog that warns about low disk space or memory no longer requires CLAUDE_CODE_DIAGNOSTICS_FILE to be set before it can start\n\n**Unclear.** It is not clear where the low-disk and low-memory thresholds come from, so which sessions now run the watchdog is unknown.\n\n**What**\n\nClaude Code has a watchdog, a background timer that checks whether disk space or memory is running low. It used to start only when `CLAUDE_CODE_DIAGNOSTICS_FILE` was set and `CLAUDECODE` was not set.\n\nThose two checks are gone. The watchdog now starts when either of these holds:\n\n- a low-disk or low-memory threshold is set to something other than zero\n\n- a separate check passes\n\n**Why**\n\nThe watchdog is no longer tied to the diagnostics file, so it can run in more sessions than before.\n\n- Area: Diagnostics\n- Names: `CLAUDE_CODE_DIAGNOSTICS_FILE`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}