{"version":"2.1.268","anchor":"token-cost-validation-caps-values-at-10000-instead-of-allow","canonical_anchor":"token-cost-validation-caps-values-at-10000-instead-of-allow","heading":"Token-cost validation caps values at 10,000 instead of allowing any finite positive number","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/token-cost-validation-caps-values-at-10000-instead-of-allow","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Token-cost validation caps values at 10,000 instead of allowing any finite positive number\n\nPer-model cost figures in config are now capped at 10,000 instead of allowing any finite positive number\n\n**What**\n\nWhen Claude Code validates per-model cost settings (input, output, cache-read, cache-write pricing), a cost value now must be no greater than 10,000. Previously any positive finite number was accepted; a config with a cost figure above 10,000 now fails validation instead of being allowed through.\n\n**Why**\n\nThis catches unreasonably large cost values in configuration, which were likely typos or misconfigurations rather than intentional, by rejecting them at validation time instead of silently accepting them.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}