Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.242 ·

Scaled screenshots for computer use are built but off in both config tables

Screenshots could be scaled and zoomed to a region, but both config tables switch it off.

Nothing to try yet Notable In Development
JSON All of v2.1.242
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Computer UseArea: what it touches
In DevelopmentKind: in v2.1.242,
What probably matters to youSection of the release

A scale parameter and a region-based batched schema are implemented, with both capability suppliers setting them false.

What

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.

Details
  • 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 scale description 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.
Evidence

adaptiveResolution

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Feature flag
tengu_malort_pedway Not enough to say

Nothing 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 has happened since
Flag reading moved The flag server now returns {"autoTargetDisplay":false,"clipboardPasteMultiline":true,"coordinateMode":"pixels","enabled":true,"hideBeforeAction":true,"mouseAnimation":true,"pixelValidation":false,"screenshotFilter":true} for tengu_malort_pedway, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_malort_pedway, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

See this entry in the whole of v2.1.242 →

Feedback