{"version":"2.1.318","anchor":"experimental-mode-refusal-reasons-and-messages-added","canonical_anchor":"experimental-mode-refusal-reasons-and-messages-added","heading":"Messages explaining when an experimental opt-in mode can't be used","tier":"soon","area":"Code Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/experimental-mode-refusal-reasons-and-messages-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Messages explaining when an experimental opt-in mode can't be used\n\nClaude Code has text for an experimental mode turned on by an environment variable, listing the many reasons it can be refused\n\n**Unclear.** The mode's name and the environment variable that turns it on are not shown.\n\n**What**\n\nClaude Code contains messages for an experimental mode you opt into by setting an environment variable to `1`. An environment variable is a setting passed to a program from your shell. The mode also has to be opened for your account by Anthropic's servers, and one message says it \"isn't open to your account yet\".\n\nThe messages explain why the mode can be refused, including:\n\n- Managed settings or organization policy\n\n- HIPAA or zero data retention arrangements\n\n- OpenTelemetry being set up\n\n- Using a model other than Opus 5.5 or Sonnet 5.5\n\n- Tool restrictions\n\n- Agent teams\n\n- Credentials\n\nA session started in this mode cannot be resumed without it, and Remote Control is not available inside it. There is also a flow that asks you to sign in again and restart.\n\n**Why**\n\nThis is the wording you would see if you tried the mode and something about your setup ruled it out.\n\n- Area: Code Mode\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}