{"version":"2.1.271","anchor":"model-config-schema-gains-default-output-tokens","canonical_anchor":"model-config-schema-gains-default-output-tokens","heading":"Model config schema gains 'default_output_tokens'","tier":"internal","area":"Model Config","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/model-config-schema-gains-default-output-tokens","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Model config schema gains 'default_output_tokens'\n\nModel config schema adds an optional 'default_output_tokens' field\n\n**Unclear.** Where or how `default_output_tokens` is used once set is not stated.\n\n**What**\n\nThe schema used to define model pricing and configuration for loop models now accepts an optional `default_output_tokens` field, in addition to the existing `max_output_tokens` field.\n\n**Why**\n\nHaving a separate default, distinct from the maximum, suggests model configuration can now specify a typical output-token count to use in addition to the upper limit, though the finding does not say where this default is applied.\n\n- Area: Model Config\n- Names: `default_output_tokens`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}