{"version":"2.1.290","anchor":"new-automatic-memory-extraction-adjacent-queue-handler-sm","canonical_anchor":"new-automatic-memory-extraction-adjacent-queue-handler-sm","heading":"New handler for queued work that waits on your decisions","tier":"internal","area":"Messaging","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/new-automatic-memory-extraction-adjacent-queue-handler-sm","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### New handler for queued work that waits on your decisions\n\nA third handler for queued work is built in, aware of running tasks and of decisions waiting on you, behind a switch\n\n**Unclear.** What this handler does and what turns its switch on is not established.\n\n**What**\n\nClaude Code has a third handler for queued work, alongside the existing two. It looks at running tasks, whether a foreground tool call has been listed, and whether a decision from you is pending. A switch controls whether it runs.\n\n**Why**\n\nThis adds a new way of working through queued items that holds back while you still have a decision to make.\n\n- Area: Messaging\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}