{"version":"2.1.302","anchor":"statusrefresh-config-now-declares-mode-full-and-maxinputtok","canonical_anchor":"statusrefresh-config-now-declares-mode-full-and-maxinputtok","heading":"A refresh setting now also includes a mode and a maximum input size","tier":"internal","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/statusrefresh-config-now-declares-mode-full-and-maxinputtok","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### A refresh setting now also includes a mode and a maximum input size\n\nA configuration that held only a refresh interval now also sets a \"full\" mode and a maximum number of input tokens\n\n**Unclear.** Which feature this configuration belongs to is not known.\n\n**What**\n\nA configuration that used to hold only how often something refreshes now also holds a mode, set to \"full\", and a maximum number of input tokens. Tokens are the small chunks of text a model reads, so this is a cap on how much input is used.\n\n**Why**\n\nIt looks like a new limit on input size for whatever this setting controls.\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}