{"version":"2.1.319","anchor":"server-classifier-continue-no-save-thread-type-and-refusal","canonical_anchor":"server-classifier-continue-no-save-thread-type-and-refusal","heading":"Safety-check requests can use a thread that saves nothing","tier":"internal","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/server-classifier-continue-no-save-thread-type-and-refusal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Safety-check requests can use a thread that saves nothing\n\nRequests to the server-side safety check can use a thread type that stores nothing, and a refusal of it is now recorded instead of dropped\n\n**Unclear.** It is not stated what makes Claude Code use the thread that saves nothing.\n\n**What**\n\nSome of Claude Code's requests are checked by a classifier on the server, a model that judges whether an action is safe. These requests can now be grouped into a thread type that saves nothing. If the server answers that it does not support this type, Claude Code notes the refusal and keeps the thread instead of dropping it.\n\n**Why**\n\nThis changes how those safety-check requests are grouped when nothing is meant to be saved.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}