{"version":"2.1.288","anchor":"session-persistence-tool-host-worktree-telemetry-and-misc","canonical_anchor":"session-persistence-tool-host-worktree-telemetry-and-misc","heading":"Groundwork for holding sessions open and parking answers","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/session-persistence-tool-host-worktree-telemetry-and-misc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Groundwork for holding sessions open and parking answers\n\nClaude Code clears two more pieces of session state on reset and gains internal fields for holding a session open, with nothing yet visible\n\n**Unclear.** It is not clear what will use the hold and park fields.\n\n**What**\n\nA session is one conversation with Claude Code. When Claude Code resets a session's saved state, it now also clears two more values: a count of deleted rows and the last boundary marker.\n\nIt has also gained internal fields for holding a session open, parking an answer, and noting whether a hold was revoked or was still active at shutdown. Nothing visible uses these yet.\n\n**Why**\n\nThese look like groundwork for keeping background sessions waiting or on hold, and change nothing you can see today.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}