{"version":"2.1.287","anchor":"new-thinking-strip-field-in-a-server-config-schema","canonical_anchor":"new-thinking-strip-field-in-a-server-config-schema","heading":"A server-provided configuration now accepts a thinking_strip field","tier":"soon","area":"Internals","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/new-thinking-strip-field-in-a-server-config-schema","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### A server-provided configuration now accepts a thinking_strip field\n\nA configuration Claude Code reads now has a thinking_strip field, alongside its existing role_line_scan and extract_transport fields\n\n**Unclear.** What `thinking_strip` does, and what values it takes, is not known.\n\n**What**\n\nA configuration that Claude Code reads, the same one that holds `extract_transport` and `role_line_scan`, now also reads a field called `thinking_strip`. Nothing yet shows what Claude Code does with it.\n\n**Why**\n\nThe name suggests a future option for removing thinking blocks, which are the passages where the model writes out its reasoning. How it is used is not yet visible.\n\n- Area: Internals\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}