{"version":"2.1.318","anchor":"org-uuid-resolution-helper-and-new-session-transcript-marker","canonical_anchor":"org-uuid-resolution-helper-and-new-session-transcript-marker","heading":"Claude Code can work out your organization ID from environment variables","tier":"notice","area":"Auth","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/org-uuid-resolution-helper-and-new-session-transcript-marker","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Claude Code can work out your organization ID from environment variables\n\nClaude Code can now take your organization ID from CLAUDE_CODE_ORGANIZATION_UUID when signed in by token, and has new owner and organization markers for sessions\n\n**Unclear.** It is not clear whether Claude Code writes these session markers yet or what it does with them.\n\n**What**\n\nClaude Code has a new way to work out which organization you belong to, always as a lowercase ID:\n\n- When `CLAUDE_CODE_OAUTH_TOKEN` is set, or another token source applies, it uses `CLAUDE_CODE_ORGANIZATION_UUID`.\n\n- Otherwise it uses the organization saved with your signed-in account.\n\nNew markers also appear for session records: a session owner entry, a history suppression entry and a credential organization entry. A session is one conversation with Claude Code, saved so you can resume it. There are also new patterns for spotting account and organization IDs.\n\n**Why**\n\nThis points toward sessions recording which organization or account they belong to, for example to check a session when it is resumed under different sign-in details.\n\n- Area: Auth\n- Names: `CLAUDE_CODE_OAUTH_TOKEN`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}