{"version":"2.1.317","anchor":"first-party-auth-rejected-error-text-caveat","canonical_anchor":"first-party-auth-rejected-error-text-caveat","heading":"Sign-in rejection errors may read \"Connection failed\" over some connections","tier":"notice","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/first-party-auth-rejected-error-text-caveat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Sign-in rejection errors may read \"Connection failed\" over some connections\n\nOver a connection that stores its messages, a rejected first-party sign-in now shows \"Connection failed\" instead of naming the sign-in that fixes it\n\n**What**\n\nWhen a first-party sign-in (signing in with an Anthropic account) is rejected, the error usually names the sign-in that would fix it. That description now notes one exception: over a connection that stores the messages passing through it, the error reads \"Connection failed\" instead.\n\n**Why**\n\nPrograms built on Claude Code should not rely on this error's wording to tell which sign-in is needed.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}