GuidesRunning & maintaining

Claude Code "Remote Control is not yet enabled for your account"

Why Claude Code refuses Remote Control or hides Fable 5.2 when DISABLE_TELEMETRY or NONESSENTIAL_TRAFFIC is set, where to unset it, and the other causes.

November 19, 2026The Everpod team
The short answer

On a machine where Claude Code has been told to keep quiet, this error usually means a variable that switches off its feature flags is set, and Remote Control is one of the features those flags turn on. The variables are CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC, CLAUDE_CODE_DISABLE_FEATURE_FLAGS (or its older name DISABLE_GROWTHBOOK), and on older versions DISABLE_TELEMETRY and DO_NOT_TRACK. For some of them, setting 0 does not help: unset it in your shell and in the env block of any settings.json, then start claude again. If you only wanted telemetry off, update Claude Code past 2.1.282 and keep DISABLE_TELEMETRY: on a Pro, Max, Ultra, Team or Enterprise plan, Remote Control now works with it set.

The three messages

The same cause has worn different wording as Claude Code has changed. Before version 2.1.154 it printed:

Error: Remote Control is not yet enabled for your account.
Copied

From 2.1.154 the message names the variable it found, for example, as reported on 2.1.282:

Remote Control requires feature-flag evaluation, which is disabled because DISABLE_TELEMETRY is set
Copied

The third symptom has no message at all: the newest model is missing from /model. Since November 2026 users on 2.1.322 report that with DISABLE_TELEMETRY set, Fable 5.2 is absent from the picker, which still shows Fable 5.1, while the account has access to it. That one is covered further down.

The old wording also had a second meaning. Until 2.1.239, “not yet enabled for your account” was also what the account check itself said when it came back off; it now reads “Remote Control isn’t enabled for this account.” If none of the variables below is set, that is your case, and Anthropic’s fix is to refresh the sign-in with claude auth logout then claude auth login, usually after a plan change, and to update Claude Code. claude doctor shows which eligibility check failed.

Why a quiet server loses Remote Control

Claude Code switches some features on through flags it fetches from Anthropic, and the environment variables reference lists the variables that skip that fetch. The usual one on a server is CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC, set to stop auto-updates, telemetry, error reporting and release notes in one go. Its documented side effect is that it “also disables feature-flag fetching, which makes Remote Control and the other features that need feature-flag fetching unavailable.” The same list costs you sessions messaging each other across machines, claude import, the advisor tool, MCP tasks and Code Mode.

Two details catch people. This variable, DISABLE_TELEMETRY and DISABLE_ERROR_REPORTING read only whether they are set, so DISABLE_TELEMETRY=0 or =false still turns the behaviour on; unset the variable, or set it to an empty value. DO_NOT_TRACK is the exception, read as an ordinary on/off, so 0 leaves it off. And the version matters for the telemetry pair: from 2.1.154 through 2.1.282, DISABLE_TELEMETRY or DO_NOT_TRACK alone blocked Remote Control. The Remote Control troubleshooting page now says that on a Pro, Max, Ultra, Team or Enterprise plan it stays available with either set, as long as CLAUDE_CODE_DISABLE_FEATURE_FLAGS and DISABLE_GROWTHBOOK are unset, unless your organization requires Trusted Devices, in which case the variable has to go. claude update gets you there.

One report on the long-running issue disagrees for the VS Code extension: on 2.1.322, a user found the extension starts Claude Code with DISABLE_TELEMETRY set whenever VS Code’s telemetry.telemetryLevel is anything but "all", and Remote Control failed with “Remote Control initialization failed” until the level was "all". That issue has been open since February with no reply from Anthropic. If you connect to your server through VS Code, that is a place the variable can come from without being in any file of yours.

Finding where it is set

Claude Code reads these variables from two places: the environment it was started in, and the env block of a settings file, which applies however claude was launched. Check both on the machine where the session runs:

env | grep -E 'NONESSENTIAL|FEATURE_FLAGS|GROWTHBOOK|TELEMETRY|DO_NOT_TRACK'
grep -nE 'NONESSENTIAL|FEATURE_FLAGS|GROWTHBOOK|TELEMETRY|DO_NOT_TRACK' \
  ~/.claude/settings.json .claude/settings.json .claude/settings.local.json
Copied

In the environment, it comes from whatever exported it: your shell profile, or the script or service that starts claude on a server, which is worth checking if you run Claude Code on a schedule and copied a quiet-mode line into it. Remove it there and open a new shell, since a running one keeps the old value. In /status, the Setting sources line names every settings file that loaded. If it names managed settings, your organization put the variable there; nothing in your own files overrides a managed key, so the route is your administrator.

Keeping it quiet without losing Remote Control

If the point of the umbrella variable was a server that does not update itself or report errors, the narrower switches do that without touching the flags: DISABLE_AUTOUPDATER=1 stops background updates while claude update still works, and DISABLE_ERROR_REPORTING=1 opts out of error reports. Neither is on the feature-flag list. For telemetry, the documented position is that DISABLE_TELEMETRY no longer blocks Remote Control on a current version, but it does still stop the flag fetch, so the next section applies.

Fable 5.2 missing from /model

Anthropic’s documentation does not list the model picker among the features that need feature flags; what ties them together is users’ debug logs. On the report with the most support, with DISABLE_TELEMETRY=1 the log shows the served model list switched off and the picker falls back to the list built into the client, whose Fable row is still 5.1. Removing the variable brings 5.2 back. Users report two ways to keep the variable and still reach the model, since the account’s access to it never changed. One is to name it:

/model claude-fable-5-2
Copied

The other is to add a row to the picker with the modelPicker setting (Claude Code 2.1.242 or later) in ~/.claude/settings.json:

{
  "modelPicker": {
    "options": [
      { "model": "claude-fable-5-2", "label": "Fable 5.2" }
    ]
  }
}
Copied

The same missing row is also reported with no telemetry variable set at all, on accounts whose cached model list had not refreshed and behind a custom ANTHROPIC_BASE_URL, so a missing Fable 5.2 alone does not prove the variable is the cause. As of November 19, 2026 all four reports are open with no answer from Anthropic.

When none of the variables is set

Remote Control has conditions of its own, each with its own message: a claude.ai sign-in on Pro, Max, Ultra, Team or Enterprise, never an API key or a setup-token, which can only make model requests; a session talking to api.anthropic.com, so not Bedrock, Google Cloud, Foundry or a custom ANTHROPIC_BASE_URL; and on Team and Enterprise, an Owner who has switched it on, since it is off by default there. “Couldn’t verify Remote Control eligibility” is different again: the flag service could not be reached, usually a proxy or no network. What Remote Control gives you once it starts, and how to keep it running on a server, is in Claude Code from your phone; if the sign-in itself is the problem, see Claude Code “Not logged in”.

Run Claude Code on an always-on developer pod.

A developer pod is a permanent cloud computer (VPS), set up and secured for you, with your pick of Claude Code, Codex, OpenCode, Pi, Hermes and OpenClaw installed. Run more agents at once than your laptop can hold, and keep them working when it’s closed. From $24 a month, built in about ten minutes.