{"version":"2.1.271","anchor":"session-idleretirement-no-longer-blocked-by-artifact-watch","canonical_anchor":"session-idleretirement-no-longer-blocked-by-artifact-watch","heading":"Session idle\/retirement no longer blocked by artifact-watch monitors","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/session-idleretirement-no-longer-blocked-by-artifact-watch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Session idle\/retirement no longer blocked by artifact-watch monitors\n\nA lingering artifact-watch background monitor no longer blocks a session from going idle\n\n**What**\n\nClaude Code decides whether a session has \"settled\" enough to be considered idle or eligible for retirement by counting outstanding in-flight tasks. That count now subtracts any monitors marked as drainable, and when such monitors exist, an `artifact_watch` background monitor (which watches an artifact for changes) is no longer counted among the things blocking idle or retirement.\n\n**Why**\n\nPreviously a session could be kept from going idle or being retired just because an artifact-watch monitor was still running in the background. Now that monitor no longer holds a session open unnecessarily.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}