{"version":"2.1.282","anchor":"mid-conversation-system-turns-can-be-forced-by-env-var-or-a","canonical_anchor":"mid-conversation-system-turns-can-be-forced-by-env-var-or-a","heading":"Mid-conversation system turns can now also be forced by a per-model setting","tier":"use","area":"System Prompt","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/mid-conversation-system-turns-can-be-forced-by-env-var-or-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Mid-conversation system turns can now also be forced by a per-model setting\n\nA per-model setting and CLAUDE_CODE_FORCE_MID_CONVERSATION_SYSTEM now keep mid-conversation system turns on even when stored settings say off\n\n**Unclear.** Only one extra use of the environment variable is confirmed, so this may be existing code that moved rather than new behaviour.\n\n**What**\n\nA system turn is an instruction from Claude Code to the model, placed partway through a conversation rather than only at its start. The environment variable `CLAUDE_CODE_FORCE_MID_CONVERSATION_SYSTEM` can already force these turns on. A setting for each model, named `mid_conv_system`, can now force them on too.\n\nThe override now also applies when Claude Code first sets the format it uses to send the conversation to the model. If either the environment variable or the model setting is present, system turns stay on even when the saved starting record says they are off. Claude Code also records whether system turns were forced this way.\n\n**Why**\n\nThis controls the format of the requests sent to the model. In practice, setting `CLAUDE_CODE_FORCE_MID_CONVERSATION_SYSTEM` now overrides the stored starting choice as well.\n\n- Area: System Prompt\n- Names: `CLAUDE_CODE_FORCE_MID_CONVERSATION_SYSTEM`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}