{"version":"2.1.317","anchor":"lapsed-claudeai-sign-in-remembered-in-mcp-auth-cache","canonical_anchor":"lapsed-claudeai-sign-in-remembered-in-mcp-auth-cache","heading":"Claude Code remembers when a claude.ai sign-in for a connector has lapsed","tier":"internal","area":"Connectors","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/lapsed-claudeai-sign-in-remembered-in-mcp-auth-cache","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Claude Code remembers when a claude.ai sign-in for a connector has lapsed\n\nClaude Code's saved record of connectors that need signing in now also remembers a lapsed claude.ai sign-in for connectors routed through claude.ai\n\n**What**\n\nMCP connectors are outside services that give Claude extra tools. Some of them are reached through claude.ai. Claude Code keeps a short-lived saved record of which connectors need you to sign in. That record now also remembers when your claude.ai sign-in for one of these connectors has lapsed. When Claude Code reuses the saved record, it restores that lapsed state too.\n\nBefore, the record held only a time, an id and how long it stays valid.\n\n**Why**\n\nThis is likely to cut down on repeated sign-in prompts for connectors reached through claude.ai.\n\n- Area: Connectors\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}