Session scope guard Why this exists In the audited workspace, 16 of 25 sampled sessions began with a bare or . The average session ran 145 tool uses and 452 minutes. Two sessions ended with the user explicitly saying they had lost track of what the session was doing. The pattern underneath: a session that "stays open" keeps being used for whatever the user asks next, even when the next ask is a new subtask. Claude happily continues. The cost is paid later, when the session either overruns context, the user forgets the state, or the next resume has to rebuild it all. The fix is a decision chec…