{"version":"2.1.307","anchor":"auth-a-launcher-lent-oauth-token-is-now-honoured-but-not-r","canonical_anchor":"auth-a-launcher-lent-oauth-token-is-now-honoured-but-not-r","heading":"Claude Code can sign in with a login lent by the desktop app","tier":"notice","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/auth-a-launcher-lent-oauth-token-is-now-honoured-but-not-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Claude Code can sign in with a login lent by the desktop app\n\nA sign-in lent by the desktop app now counts like `CLAUDE_CODE_OAUTH_TOKEN`, though plugins cannot use it\n\n**What**\n\nClaude Code now accepts a new source for your login: a sign-in lent by the program that launched it, such as the desktop app. Claude Code treats it the same as `CLAUDE_CODE_OAUTH_TOKEN`, and having it stops the error that says a key is required.\n\nWhat else differs with this lent sign-in:\n\n- If the server rejects the login, a session started by the desktop app now asks the desktop app for help instead of using the usual callback.\n\n- Plugin sessions refuse to use it, with the message \"the desktop app's sign-in is not lent to plugins\".\n\n- When the sign-in method is pinned, which means fixed to one method, the lent sign-in is not renewed.\n\n**Why**\n\nThis changes how Claude Code signs in when the desktop app or another program starts it.\n\n- Area: Auth\n- Names: `CLAUDE_CODE_OAUTH_TOKEN`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}