Claude Console adds an organization IP allowlist in beta, up to 1,000 addresses or CIDR ranges, and the Admin API can sign an Enterprise member out everywhere
Two admin controls aimed at the same risk: a leaked API key or a compromised account that keeps working after you notice.
// Key points
- Requests to covered services from addresses not on the organization's list are refused, which limits where a leaked API key can be used
- The allowlist takes IPv4 and IPv6 addresses or CIDR ranges, up to 1,000 per organization
- POST /v1/organizations/users/{user_id}/sign_out (beta, admin-user-sign-out-2026-10-08 header) ends a Claude Enterprise member's sessions, trusted devices and OAuth tokens on every device
- The member stays in the organization and can sign in again right away
Builder's takeThis is cheap insurance for any team whose keys only ever leave from a few egress IPs. I'd put our production gateways' egress ranges on the list first and check what the docs say is not covered, then wire the sign-out call into the offboarding script; note it ends sessions, it doesn't remove the person.
// Background · from #Anthropic
Full timeline →- Nov 4 Claude's Messages API adds message threads in beta: later turns send only the new messages, and a thread expires 5 minutes after its last request
- Nov 4 Text from Claude Mythos 5, Opus 4.7 and Sonnet 4.6 now carries Anthropic's watermark; on Sonnet 4.6, non-default sampling settings may drop it
- Nov 2 Microsoft dissects the tampered Claude Code extension served by Cursor's marketplace: versions 2.1.312 and 2.1.313 planted an SSH key, a reverse tunnel and persistence