{"version":"2.1.232","anchor":"non-interactive-auto-mode-setup-no-longer-needs-the-onboardi","canonical_anchor":"non-interactive-auto-mode-setup-no-longer-needs-the-onboardi","heading":"Non-interactive \/auto-mode-setup no longer needs the onboarding flag","tier":"use","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/non-interactive-auto-mode-setup-no-longer-needs-the-onboardi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Non-interactive \/auto-mode-setup no longer needs the onboarding flag\n\nNon-interactive \/auto-mode-setup now just needs a resolved model and no remote flag.\n\n**What**\n\nThe two forms of `\/auto-mode-setup` now have separate availability. The interactive form still requires the `envOnboarding` field of the `tengu_auto_mode_config` remote setting to be on. The non-interactive form now only needs a resolved auto-mode model and `CLAUDE_CODE_REMOTE` to be unset. Previously both shared the gated check.\n\n**Evidence**\n\n`isEnabled: () => lRa() && On(),`\n\n- Flag `tengu_auto_mode_config`: Not enough to say (read for one account on one subscription tier against v2.1.232; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Permissions\n- Names: `\/auto-mode-setup`, `CLAUDE_CODE_REMOTE`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}