{"version":"2.1.295","anchor":"spawned-sessions-get-claude-code-restrict-personal-config1","canonical_anchor":"spawned-sessions-get-claude-code-restrict-personal-config1","heading":"Sessions started by Claude Code can inherit the restrict-personal-config mode","tier":"internal","area":"Settings","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/spawned-sessions-get-claude-code-restrict-personal-config1","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Sessions started by Claude Code can inherit the restrict-personal-config mode\n\nUnder a certain condition, Claude Code now sets `CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG` to `1` for the sessions it starts\n\n**What**\n\nWhen Claude Code starts another Claude Code process, it passes along some environment variables (named values a program reads at start-up), such as `CLAUDE_CODE_DISABLE_PROACTIVITY` and `CLAUDE_CODE_AUTO_MODE_SERVER`. Under a certain condition it now also sets `CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG` to `1` for that process.\n\n**Why**\n\nIf this mode is in effect, sessions started from it are restricted too, so your personal configuration stays out of them as well.\n\n- Area: Settings\n- Names: `CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}