{"version":"2.1.311","anchor":"resource-watchdog-telemetry-env-switches","canonical_anchor":"resource-watchdog-telemetry-env-switches","heading":"Resource watchdog for remote sessions, controlled by environment variables","tier":"use","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/resource-watchdog-telemetry-env-switches","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Resource watchdog for remote sessions, controlled by environment variables\n\nA resource watchdog and its reporting are now switched on or off by environment variables, aimed at certain remote session setups\n\n**Unclear.** It is not clear which values of these variables turn the watchdog or its reporting on.\n\n**What**\n\nClaude Code now has checks that decide whether to run a resource watchdog, a background monitor of the computer's resources, and whether to send reports from it. They read these environment variables, which are values set in the shell before Claude Code starts:\n\n- `CCR_BYOC_RESOURCE_WATCHDOG_TELEMETRY`\n\n- `CLAUDE_CODE_DIAGNOSTICS_FILE`\n\n- `CLAUDECODE`: when it is set, the watchdog's output is skipped\n\n- `CLAUDE_CODE_ENVIRONMENT_KIND`: any value other than `byoc` passes the second check\n\nThe watchdog records its process in a file named `resource-watchdog.pid`.\n\n**Why**\n\nThis adds resource monitoring for remote sessions of the kinds labelled BYOC and CCR, steered by environment settings rather than by anything in the interactive screen.\n\n- Area: Sessions\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}