{"version":"2.1.242","anchor":"computer-use-tells-the-model-when-background-app-control-is-","canonical_anchor":"computer-use-tells-the-model-when-background-app-control-is-","heading":"Computer use tells the model when background app control is switched off remotely","tier":"notice","area":"Computer Use","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/computer-use-tells-the-model-when-background-app-control-is-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Computer use tells the model when background app control is switched off remotely\n\nIf background app control is switched off remotely mid-session, Claude is told to stop retrying.\n\n**What**\n\nIf per-app background control is disabled for your device by remote configuration while a session is running, the model now gets an explicit notice that app locks were released, that it should not retry the app_* tools for the rest of the session, and that it should fall back to display-scope tools.\n\n**Details**\n\n- The screen-takeover consent flow records distinct failure kinds in telemetry: allowlist_empty, cu_lock_held, takeover_unavailable, takeover_declined, takeover_not_answered, unattended_no_approver, feature_unavailable, state_conflict.\n- The consent dialog gives up after 290000 ms.\n- Whether the control is on is decided by remote configuration, not by anything in this build.\n\n**Evidence**\n\n`Per-app background control (the app_* tools) was just turned off for this device by a remote configuration change.`\n\n- Area: Computer Use\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}