Under the hood
No documentation found
Model config schema adds an optional 'default_output_tokens' field
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.
Names in the bundledefault_output_tokens
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Where or how `default_output_tokens` is used once set is not stated.