{"version":"2.1.246","anchor":"restoring-plan-mode-at-startup-is-still-an-empty-function-wh","canonical_anchor":"restoring-plan-mode-at-startup-is-still-an-empty-function-wh","heading":"Restoring plan mode at startup is still an empty function while its reporting fills out","tier":"soon","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/restoring-plan-mode-at-startup-is-still-an-empty-function-wh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Restoring plan mode at startup is still an empty function while its reporting fills out\n\nThe startup handler meant to restore plan mode is still an empty function.\n\n**What**\n\nThe non-interactive and SDK startup path calls a handler meant to restore a previous plan-mode state, and that handler's body is empty. A companion function, also uncalled, gained a `planModeRestoredAtBoot` option this release with an equally empty body.\n\n**Details**\n\n- The surrounding decision logic did change: the report for restoring a permission mode can now carry whether transcript state was recorded and whether the transcript was open, and an open transcript is now treated the same as a recorded plan mode when classifying a restore as declined.\n- Nothing at startup applies any of that yet, since the function that would is hollow and has no caller.\n\n**Evidence**\n\n`planModeRestoredAtBoot`\n\n- Area: Elsewhere\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 0\/5\n- Present in the build but not switched on"}