{"version":"2.1.300","anchor":"remote-control-credential-renewal-explains-sign-in-failures","canonical_anchor":"remote-control-credential-renewal-explains-sign-in-failures","heading":"Remote Control retries failed credential renewals and warns before the connection ends","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/remote-control-credential-renewal-explains-sign-in-failures","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Remote Control retries failed credential renewals and warns before the connection ends\n\nRemote Control now retries sign-in errors when renewing its connection and, if it gives up, says why and how long the connection still works\n\n**What**\n\nRemote Control links a Claude Code session on your computer to claude.ai. It renews its credential, the proof that it is allowed to stay connected, ahead of time.\n\nIf a renewal is refused for a sign-in reason and the sign-in service looks unreachable, Claude Code now tries again. If it finally gives up, the warning starts with \"Remote Control could not renew this computer's connection:\", gives the reason, and says how long the connection will keep working. Before, there was a single message telling you your claude.ai login was no longer valid and to run `claude \/login`.\n\nHeartbeats, the regular check-ins that show a connection is alive, are now tracked separately for each session.\n\n**Why**\n\nA short network problem no longer reads as an expired login. When renewal does fail, you learn the reason and how much time you have before the connection drops.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}