{"version":"2.1.307","anchor":"update-environment-variables-routes-claude-code-oauth-token","canonical_anchor":"update-environment-variables-routes-claude-code-oauth-token","heading":"A remote host's new sign-in token may be held back instead of applied","tier":"internal","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/update-environment-variables-routes-claude-code-oauth-token","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### A remote host's new sign-in token may be held back instead of applied\n\nWhen a remote connection sends a new CLAUDE_CODE_OAUTH_TOKEN, Claude Code can now pass it to a separate check rather than switching to it\n\n**Unclear.** What condition decides this and whether the token is ever applied afterwards is not known.\n\n**What**\n\n`CLAUDE_CODE_OAUTH_TOKEN` is an environment variable holding a sign-in token. A remote connection controlling a running Claude Code can send new environment variables. When it sends this token and a certain condition holds, Claude Code no longer applies it straight away. It hands the token to a separate check and logs that the token was offered to the session's judge but not applied yet. Before, the token was applied immediately.\n\nThe log message for variables Claude Code does not accept from a remote connection was also reworded.\n\n**Why**\n\nIt makes it harder for a remote connection to swap the account a running session is signed in as.\n\n- Area: Auth\n- Names: `CLAUDE_CODE_OAUTH_TOKEN`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}