Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Model ConfigArea: what it touches
Internal ChangesKind: in v2.1.271,
Internal ChangesSection of the release
Unclear Where or how default_output_tokens is used once set is not stated.
What
The 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.
Why
Having 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.
Read from
Names in the bundledefault_output_tokens
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhere or how `default_output_tokens` is used once set is not stated.
