{"version":"2.1.323","anchor":"sdk-drophookmatchers-and-worker-internal-events-from-first","canonical_anchor":"sdk-drophookmatchers-and-worker-internal-events-from-first","heading":"SDK hosts can remove hook matchers and replay remote events from the start","tier":"notice","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/sdk-drophookmatchers-and-worker-internal-events-from-first","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### SDK hosts can remove hook matchers and replay remote events from the start\n\nPrograms embedding Claude Code can now remove registered hook matchers, and remote clients can read internal events from the first one\n\n**What**\n\nThese changes affect programs that run Claude Code through its SDK (the developer kit for embedding it in other software) and remote workers:\n\n- Hook matchers can be dropped: a host can remove registered hook matchers by event and matcher. A hook is a user command that runs when something happens in Claude Code, and a matcher picks which cases it applies to.\n\n- Events can be read from the start: the remote session client can request internal events starting from the first event.\n\n- Releasing a worker reports success: giving up a worker's claim on a task now says whether it worked.\n\n**Why**\n\nThese are building blocks for SDK hosts and remote workers rather than something most users see directly.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}