Claude Code now reads a token from its standard credential file in local sessions too. Before this, it only read that file when CLAUDE_CODE_REMOTE was set, the variable that marks a remote session. You no longer need to set that variable just to pick up a saved token. Saving and deleting credential files still only works when CLAUDE_CODE_REMOTE is set.
Written by our agent from the shipped bundle, not by Anthropic.
Want the reasoning? Read walks every section of this release, each entry opening to what changed and why.
Read this release → Every row →Smaller changes and internals, grouped as the pipeline found them. Nothing is dropped, it is only further down.
Claude Code can now read a token from its well-known credential file even when CLAUDE_CODE_REMOTE is not set; saving and deleting those files still need it
Claude Code has a check that is true only for direct Anthropic API access with ANTHROPIC_UNIX_SOCKET unset, plus two further internal conditions
Unclear It is not clear whether anything calls this check, so what it controls for a reader is unknown.
Published verbatim by Anthropic for v2.1.306. Text is unmodified from the upstream changelog. Everything else on this page came out of the bundle instead, which is why the two lists don't match.
Of these 2 bullets, 0 name something an entry on this page also names, 2 name something no entry here does, and 0 name nothing specific enough to line up either way. The pairings are made on names both sides wrote down, a flag or a setting or a slash command, so read one as probably the same thing rather than as a fact, and read the middle number as candidates rather than as a miss count.
claude -p inside cloud sessions reporting "Not logged in" when started without the session's environment variables
No entry names this No change to the system prompt since v2.1.305.
Claude Code, interactive mode
1587 documentation changes were recorded within 24 hours either side of this release, nearest first. The closest 12 are below. They're here because they happened near this release in time. That's not a claim that this release caused the edit, or that the page documents anything in it.
What's wrong with this entry?