{"version":"2.1.312","anchor":"idle-release-for-control-only-served-sessions","canonical_anchor":"idle-release-for-control-only-served-sessions","heading":"Control-only served sessions now close themselves when idle","tier":"notice","area":"Served Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/idle-release-for-control-only-served-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Control-only served sessions now close themselves when idle\n\nA session served in control-only mode now releases itself after a set idle time with no work\n\n**What**\n\nClaude Code can serve a session to other connected programs. When a session is served in control-only mode and given an idle time limit, it now releases itself once it has done no work for that long. Claude Code notes in its log how long the session ran nothing.\n\n**Why**\n\nRemote sessions that sit idle no longer stay open indefinitely, which frees them up. A program connected to such a session should expect it to end after a quiet period.\n\n- Area: Served Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}