{"version":"2.1.242","anchor":"app-locks-block-whole-screen-actions-and-a-remote-switch-off","canonical_anchor":"app-locks-block-whole-screen-actions-and-a-remote-switch-off","heading":"App locks block whole-screen actions, and a remote switch-off releases them","tier":"soon","area":"Computer Use","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/app-locks-block-whole-screen-actions-and-a-remote-switch-off","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### App locks block whole-screen actions, and a remote switch-off releases them\n\nWhile Claude controls one app, whole-screen actions are refused until it releases the app.\n\n**What**\n\nWhile 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.\n\n**Details**\n\n- The tool router branches on the app-scoped tools, including app_release and the new request_full_control and release_full_control.\n- 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.\n- Sessions holding a lock report it in text beginning \"This session is currently controlling \".\n\n**Evidence**\n\n`This session is currently controlling `\n\n- Area: Computer Use\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}