{"version":"2.1.239","anchor":"two-model-behaviours-can-be-switched-on-by-a-server-payload","canonical_anchor":"two-model-behaviours-can-be-switched-on-by-a-server-payload","heading":"Two model behaviours can be switched on by a server payload","tier":"use","area":"System Prompt","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/two-model-behaviours-can-be-switched-on-by-a-server-payload","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Two model behaviours can be switched on by a server payload\n\nTwo model behaviours, a silent turn reminder and a Bash-output audience note, can be forced on by env vars.\n\n**What**\n\nA silent turn reminder and a new note telling Claude who will read Bash output now resolve the same way: an environment variable wins, then whatever the model catalog declares, then a cached blob of settings the server delivers. Anything else is off. In practice both are off unless the server enables them or you set `CLAUDE_CODE_SILENT_TURN_REMINDER` or `CLAUDE_CODE_BASH_OUTPUT_AUDIENCE_NOTE` yourself.\n\n**Details**\n\n- The silent turn reminder previously came from a per-model experiment lookup; that path is gone.\n- The first time a given model takes a capability from the server payload it reports it once, tracked with a small cache of recently seen models.\n\n**Evidence**\n\n`tengu_model_capability_from_client_data`\n\n- Area: System Prompt\n- Names: `CLAUDE_CODE_SILENT_TURN_REMINDER`, `CLAUDE_CODE_BASH_OUTPUT_AUDIENCE_NOTE`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 4\/5"}