{"version":"2.1.296","anchor":"claude-auto-background-tasks-is-now-read-from-a-config-objec","canonical_anchor":"claude-auto-background-tasks-is-now-read-from-a-config-objec","heading":"CLAUDE_AUTO_BACKGROUND_TASKS is now read from Claude Code's own configuration","tier":"use","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/claude-auto-background-tasks-is-now-read-from-a-config-objec","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### `CLAUDE_AUTO_BACKGROUND_TASKS` is now read from Claude Code's own configuration\n\nClaude Code now reads `CLAUDE_AUTO_BACKGROUND_TASKS` from its own configuration values instead of straight from the shell environment\n\n**Unclear.** Whether the variable can now be set through Claude Code settings, and whether values like `0` or `false` are read the same way, is not shown.\n\n**What**\n\n`CLAUDE_AUTO_BACKGROUND_TASKS` is an environment variable, a setting you put in your shell before starting Claude Code. When it is set, long-running agent tasks move to the background after about two minutes. Claude Code now reads this variable from its own set of configuration values instead of straight from the process environment.\n\nThe result is the same as before: a wait of about two minutes (120000 milliseconds) when the variable is set, and no automatic backgrounding when it is not.\n\n**Why**\n\nThe value may now come from somewhere other than your shell. Check the variable still behaves as you expect if you rely on it.\n\n- Area: Elsewhere\n- Names: `CLAUDE_AUTO_BACKGROUND_TASKS`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}