Screenshots could be scaled and zoomed to a region, but both config tables switch it off.
A scale parameter and a region-based batched schema are implemented, with both capability suppliers setting them false.
tengu_malort_pedway 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.242: not a boolean we can read
Read once, for one account on one subscription tier, against v2.1.242. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
A new adaptive-resolution capability adds a scale parameter to the screenshot and batched computer-use tools and switches to a richer batched schema with a region for zoom. Both places in this build that supply the capability set it to false, so absent a server-supplied config, no user sees scale.
- The two sources are the terminal computer-use descriptor, which sets adaptive resolution false alongside native screenshot filtering, and the computer-use settings defaults object.
- That defaults object is merged with remote configuration under
tengu_malort_pedway; the same local fallback also has the whole feature disabled. - The
scaledescription tells the model that coordinates stay in the full-resolution frame regardless of the returned image size. - The capability key is new in this release.
adaptiveResolution
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.248
Computer-use app blocklists extended on Windows
Both mention computer