{"version":"2.1.236","anchor":"token-reminder-settings-can-now-be-delivered-by-the-server-d","canonical_anchor":"token-reminder-settings-can-now-be-delivered-by-the-server-d","heading":"Token-reminder settings can now be delivered by the server directly","tier":"use","area":"Context Reminders","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/token-reminder-settings-can-now-be-delivered-by-the-server-d","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Token-reminder settings can now be delivered by the server directly\n\nToken-reminder settings can now arrive from the server, but your env var and setting still win.\n\n**What**\n\nThe three settings behind the total-tokens reminder (its mode, its budget, and whether it appears after your turn) are read first from a configuration blob the server sends, and only fall back to the feature-flag defaults `\"padded-countdown\"`, the default budget and on. The `CLAUDE_CODE_TOTAL_TOKENS_REMINDER` environment variable and the `totalTokensReminder` settings key still override both.\n\n**Details**\n\n- When a server-provided value is used, it is reported as `tengu_lapis_anchor_from_client_data`.\n- A server value of the wrong type logs a warning and falls back to the flag default rather than failing.\n\n**Evidence**\n\n`falling through to GrowthBook`\n\n- Area: Context Reminders\n- Names: `CLAUDE_CODE_TOTAL_TOKENS_REMINDER`, `totalTokensReminder`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 4\/5"}