While Claude controls one app, whole-screen actions are refused until it releases the app.
App locking blocks screen-wide computer use, but availability rests on a host implementation absent here.
What's wrong with this entry?
While the new per-app control holds a lock on an application, whole-screen computer-use actions are refused with a message telling the model to release the app first. Whether any of this is available is decided by the host program at runtime, not by a setting visible in the build.
- The tool router branches on the app-scoped tools, including app_release and the new request_full_control and release_full_control.
- If the host provides app-scoped control but its enabled check returns false, any app-scoped call other than release drops the app lock, clears the stored screenshot and returns a feature_disabled error.
- Sessions holding a lock report it in text beginning "This session is currently controlling ".
This session is currently controlling
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