Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.319 ·

OAuth token refreshes no longer ask for a specific scope

When Claude Code refreshes an OAuth sign-in token, it no longer sends a scope value, so the server grants its default access

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

OAuth is a standard way for one service to give another limited access without sharing a password. Some services, such as MCP servers, sign Claude Code in this way. MCP servers are outside tools that Claude Code can connect to. Claude Code renews the sign-in token from time to time. This renewal is called a refresh.

A refresh request no longer includes the scope value, which lists the permissions being asked for. Before, Claude Code sent the stored scope whenever it had one. The server now decides which permissions the refreshed token gets, using its own default.

Why

A refreshed token may now carry different permissions than before. Servers that rejected a refresh because it included a scope may now accept it.

See this entry in the whole of v2.1.319 →

Feedback