{"version":"2.1.286","anchor":"teleport-upgrade-wrapped-in-try-and-step-up-reauth-exhausti","canonical_anchor":"teleport-upgrade-wrapped-in-try-and-step-up-reauth-exhausti","heading":"Safer handling of a cache upgrade and of repeated MCP re-sign-in attempts","tier":"internal","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/teleport-upgrade-wrapped-in-try-and-step-up-reauth-exhausti","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Safer handling of a cache upgrade and of repeated MCP re-sign-in attempts\n\nA cache upgrade step now catches its own errors, and MCP sign-in now tracks when extra re-sign-in attempts have run out\n\n**Unclear.** It is unclear whether either change is something you would notice.\n\n**What**\n\nTwo small changes:\n\n- Cache upgrade: a step that upgrades a stored cache used when moving a session between machines now catches errors instead of letting them escape.\n\n- MCP sign-in: the part of Claude Code that signs in to MCP servers (external services that give Claude extra tools) now tracks which servers have run out of attempts to ask you to sign in again with higher access.\n\n**Why**\n\nBoth are about robustness, so that a failure in either place is handled instead of causing further trouble.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}