{"version":"2.1.234","anchor":"sessionend-hooks-lose-the-bypass-permissions-disabled-reason","canonical_anchor":"sessionend-hooks-lose-the-bypass-permissions-disabled-reason","heading":"SessionEnd hooks lose the bypass_permissions_disabled reason","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/sessionend-hooks-lose-the-bypass-permissions-disabled-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### SessionEnd hooks lose the `bypass_permissions_disabled` reason\n\nSessionEnd hooks no longer see a bypass_permissions_disabled reason, since nothing can end your session that way.\n\n**What**\n\nThe `reason` a SessionEnd hook receives is now one of five values: `clear`, `resume`, `logout`, `prompt_input_exit` and `other`. The `bypass_permissions_disabled` value is gone from the whole build, along with the mid-session check that used to log a warning and exit with it, so nothing emits it any more.\n\n**Details**\n\n- The hook schema and the runtime list now agree, and the hook documentation's matcher values are generated from the same shared constant instead of being hardcoded a second time.\n\n**Evidence**\n\n`prompt_input_exit`, `\"clear\", \"resume\", \"logout\", \"prompt_input_exit\", \"other\"`\n\n- Area: Hooks\n- Names: `SessionEnd`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}