{"version":"2.1.251","anchor":"model-specific-extra-reminders-remain-driven-by-two-client-d","canonical_anchor":"model-specific-extra-reminders-remain-driven-by-two-client-d","heading":"Model-specific extra reminders remain driven by two client-data keys","tier":"internal","area":"System Prompt","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/model-specific-extra-reminders-remain-driven-by-two-client-d","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Model-specific extra reminders remain driven by two client-data keys\n\nTwo client-data keys can still inject model-specific extra instructions once per conversation.\n\n**What**\n\nTwo mechanisms can inject extra instruction text chosen by matching the model name, one for batching behaviour and one as a secondary reminder, each sourced from `CLAUDE_CODE_TOASTY_THIMBLE` or `CLAUDE_CODE_GENTLE_PARASOL` or from a server-supplied map. Each applies once per conversation per model. Both existed before this release; the wiring around them has moved.\n\n**Details**\n\n- Telemetry records when each is applied.\n- With neither the environment variable nor a server-supplied value set, nothing is injected.\n\n**Evidence**\n\n`CLAUDE_CODE_TOASTY_THIMBLE`\n\n- Area: System Prompt\n- Names: `CLAUDE_CODE_TOASTY_THIMBLE`, `CLAUDE_CODE_GENTLE_PARASOL`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5"}