{"version":"2.1.323","anchor":"oauth-refresh-requires-standalone-scope-check","canonical_anchor":"oauth-refresh-requires-standalone-scope-check","heading":"Cloud session sign-in refresh checks standalone sessions more strictly","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/oauth-refresh-requires-standalone-scope-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Cloud session sign-in refresh checks standalone sessions more strictly\n\nWhen Claude Code renews cloud session sign-in, it now checks standalone sessions for a valid permission scope and keeps account email and organization\n\n**Unclear.** It is not clear what a standalone session is or which users sign in that way.\n\n**What**\n\nWhen Claude Code renews its sign-in for cloud sessions, it now checks that standalone sessions have a valid scope (the set of permissions the sign-in grants). Before, it checked only the sessions scope. It also now keeps whether the session is standalone, the account email and the organization name.\n\n**Why**\n\nThis matters to anyone using a standalone sign-in for cloud sessions.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}