{"version":"2.1.315","anchor":"remote-session-token-renewal-hook-and-thawing-stub","canonical_anchor":"remote-session-token-renewal-hook-and-thawing-stub","heading":"Remote sessions gain unused renewSessionTokens and isThawing hooks","tier":"soon","area":"Sessions","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/remote-session-token-renewal-hook-and-thawing-stub","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Remote sessions gain unused renewSessionTokens and isThawing hooks\n\nRemote session code gains renewSessionTokens and isThawing hooks, but isThawing always returns false and the function receiving them does nothing\n\n**What**\n\nThe object that controls a remote session (a session running in the cloud) gains two new hooks:\n\n- `renewSessionTokens`, which asks the session to renew its access tokens.\n\n- `isThawing`, which is hardcoded to always return false.\n\nBoth are handed to the runner's health-port loop, a routine that only runs when a health port is configured. That routine's body is empty, so it does nothing with them. With `isThawing` always false, the thaw path cannot be reached from there.\n\n**Why**\n\nNothing changes for you in this build. The hooks exist in the code but have no effect yet.\n\n- Area: Sessions\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: both\n- Heads-up: no\n- Present in the build but not switched on"}