{"version":"2.1.309","anchor":"post-turn-instruction-field-accepted-in-a-server-config-sche","canonical_anchor":"post-turn-instruction-field-accepted-in-a-server-config-sche","heading":"Server settings can now carry an after-turn instruction","tier":"internal","area":"Remote Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/post-turn-instruction-field-accepted-in-a-server-config-sche","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Server settings can now carry an after-turn instruction\n\nA settings object Claude Code reads now accepts an optional post_turn_instruction text, and ignores it if malformed\n\n**What**\n\nA settings object that Claude Code reads now accepts an optional `post_turn_instruction` text field. It must not be empty and has a length limit. If the value is malformed, Claude Code ignores it rather than failing.\n\n**Why**\n\nThis looks like a way for instructions sent from the server to be added after a turn.\n\n- Area: Remote Settings\n- Names: `post_turn_instruction`\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: org\n- Heads-up: no"}