{"version":"2.1.317","anchor":"new-tengu-swift-pelican-allowlist-check-first-party-only","canonical_anchor":"new-tengu-swift-pelican-allowlist-check-first-party-only","heading":"New server-controlled allow list for Anthropic API users","tier":"internal","area":"API","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/new-tengu-swift-pelican-allowlist-check-first-party-only","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### New server-controlled allow list for Anthropic API users\n\nA new check allows an item through a built-in test, or for Anthropic API users when it appears on a list the server sends\n\n**Unclear.** It is not clear what this check allows or blocks.\n\n**What**\n\nClaude Code adds a check that allows an item in either of two ways:\n\n- it passes an existing built-in test\n\n- Claude Code is connected directly to Anthropic's own API, and the item appears on a list sent by the server\n\nWhen the server sends no list, only the built-in test applies.\n\n**Why**\n\nAnthropic can extend what this check allows for direct API users without a new release.\n\n- Flag `tengu_swift_pelican`: Not enough to say (read for one account on one subscription tier against v2.1.317; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: API\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}