{"version":"2.1.281","anchor":"server-classifier-drops-message-threads-after-an-unsupporte","canonical_anchor":"server-classifier-drops-message-threads-after-an-unsupporte","heading":"Server classifier stops using message threads after an 'unsupported' reply","tier":"internal","area":"Auto Mode","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/server-classifier-drops-message-threads-after-an-unsupporte","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Server classifier stops using message threads after an 'unsupported' reply\n\nIf the server classifier rejects a request sent on a message thread, the rest of the session sends its requests without a thread\n\n**Unclear.** The finding does not say what the server classifier decides.\n\n**What**\n\nThe server classifier is the check that runs on the server to decide how Claude Code should treat an action, for example in auto mode. Classifier requests can now be built with a `thread` option, which sends them as part of a message thread.\n\nIf a request was sent on a message thread and the API answers `server_unsupported`, Claude Code now does the following:\n\n- It reports the result as `server_thread_unsupported` rather than as a plain unsupported reply.\n\n- Unless an internal condition applies, it switches the rest of the session to sending classifier requests without a thread, and logs a warning once.\n\n- The message shown to the user adds a note that the request was sent on a message thread, which the server does not cover, and that the next one will not be.\n\nBefore, the classifier had no such fallback.\n\n**Why**\n\nIf the server does not support threaded requests, classification can recover on its own for the rest of the session instead of failing again on each request.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}