{"version":"2.1.295","anchor":"new-claude-code-restrict-personal-config-env-var-recognized","canonical_anchor":"new-claude-code-restrict-personal-config-env-var-recognized","heading":"New CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG mode restricts your own Claude Code files","tier":"use","area":"Settings","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/new-claude-code-restrict-personal-config-env-var-recognized","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### New `CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG` mode restricts your own Claude Code files\n\nSetting `CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG` starts a session that restricts your own Claude Code files, alongside the other restricted modes\n\n**Unclear.** Which of your own files and settings this mode actually stops from loading is not settled.\n\n**What**\n\nClaude Code recognizes a new environment variable, `CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG`. An environment variable is a named value set in your shell before you start a program. When it is set, Claude Code describes the session as one that restricts your own Claude Code files. It is checked alongside the existing locked-down modes:\n\n- `CLAUDE_CODE_RESTRICTED`\n\n- `CLAUDE_CODE_SAFE_MODE`\n\n- `CLAUDE_CODE_SIMPLE`\n\nWhen Claude Code starts a background session in tmux (a program that keeps terminal sessions running out of sight), it can now launch that session with `CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG=1` set, and still passes `--restricted` as well.\n\n**Why**\n\nThis is a new switch for locking down the configuration that belongs to you personally, and Claude Code checks it in many places.\n\n- Area: Settings\n- Names: `CLAUDE_CODE_RESTRICT_PERSONAL_CONFIG`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}