{"version":"2.1.242","anchor":"asking-the-user-to-escalate-from-one-app-to-the-whole-screen","canonical_anchor":"asking-the-user-to-escalate-from-one-app-to-the-whole-screen","heading":"Asking the user to escalate from one app to the whole screen","tier":"soon","area":"Computer Use","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/asking-the-user-to-escalate-from-one-app-to-the-whole-screen","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Asking the user to escalate from one app to the whole screen\n\nA session can ask to escalate from one app to full screen control, and hand it back.\n\n**What**\n\nTwo tools, request_full_control and release_full_control, let a session ask permission to move from controlling one application to controlling the whole screen, and hand that control back. Escalation needs the host's takeover handler and an explicit user approval; during scheduled or unattended runs it is refused with the reason code unattended_no_approver.\n\n**Details**\n\n- The permission dialog now carries a preferred-mode default, so a user who prefers per-app control keeps it as the default choice.\n- The access-request result includes guidance steering the model toward the per-app tools when that is the user's preference.\n- Neither tool name nor the preferred-mode setting exists in v2.1.241.\n\n**Evidence**\n\n`release_full_control`\n\n- Area: Computer Use\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}