Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.306 ·

Credential files at the standard path are now read in local sessions too

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

You'll notice Improvements
JSON All of v2.1.306
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
AuthArea: what it touches
ImprovementsKind: in v2.1.306,
ImprovementsSection of the release
What

Claude Code can pick up a login token from a credential file kept at a fixed, well-known location on disk. There are two such readers: one reads a token from a file, and the other reads credentials handed over from another process. Both used to return nothing unless the CLAUDE_CODE_REMOTE environment variable was set. An environment variable is a named value you set in your shell or system before starting a program, and this one marks a session (one run of Claude Code) as running remotely.

That requirement is gone from the reading side. The two readers now skip the file only in these cases:

  • Claude Code is running inside a tool server's background process, where it already avoids writing to disk
  • the session has no disk storage at all

In any other case, a local session can now read a token from the well-known file. Writing and deleting these credential files still happens only when CLAUDE_CODE_REMOTE is set.

Why

Reading these credential files is no longer limited to remote sessions, so a local session may pick up a token from that file where it previously would have ignored it. If such a file is present on your machine, it can now affect which credentials a local session uses.

See this entry in the whole of v2.1.306 →

Feedback