MAX_MCP_OUTPUT_TOKENS is still honoured first, but it's no longer sanity-checked as a number.
tengu_velvet_ibis Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.248: not a boolean we can read
Read once, for one account on one subscription tier, against v2.1.248. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The limit on how much output an MCP tool may return still reads the MAX_MCP_OUTPUT_TOKENS environment variable first, then a server-side config value, then a built-in default. The environment value is no longer checked for being a finite number before use.
- Server config comes from
tengu_velvet_ibis, whose fallback is an empty object, so with no server value the built-in default applies.
tengu_velvet_ibis
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.229
Assistant messages built from streamed text now report a stop reason
Both mention output
-
v2.1.235
Eval results written inside a plugin warn that they may load as components
Both mention output
-
v2.1.238
Files changed during a turn are uploaded to the cloud session worker
Both mention output