{"version":"2.1.301","anchor":"background-task-check-hunk-now-reads-claude-code-exit-after","canonical_anchor":"background-task-check-hunk-now-reads-claude-code-exit-after","heading":"A background-task check now looks at a different environment variable","tier":"internal","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/background-task-check-hunk-now-reads-claude-code-exit-after","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### A background-task check now looks at a different environment variable\n\nA check that read `CLAUDE_CODE_DISABLE_BACKGROUND_TASKS` now reads `CLAUDE_CODE_EXIT_AFTER_FIRST_RENDER` and a different condition instead\n\n**Unclear.** It is not clear whether `CLAUDE_CODE_DISABLE_BACKGROUND_TASKS` still turns background tasks off or whether its check only moved elsewhere.\n\n**What**\n\nAn environment variable is a setting you give a program from your shell. One check in Claude Code used to be true when any of these held:\n\n- the background-tasks-disabled setting\n\n- `CLAUDE_CODE_DISABLE_BACKGROUND_TASKS`\n\n- a third internal condition\n\nThe check in that same place is now true when `CLAUDE_CODE_EXIT_AFTER_FIRST_RENDER` is set or a different internal condition holds. Both variable names are still in the list of environment variables Claude Code recognises.\n\n**Why**\n\nIf you use `CLAUDE_CODE_DISABLE_BACKGROUND_TASKS` to turn off background tasks, confirm that background tasks are still off after updating.\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}