If background app control is switched off remotely mid-session, Claude is told to stop retrying.
What's wrong with this entry?
If 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.
- 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.
- The consent dialog gives up after 290000 ms.
- Whether the control is on is decided by remote configuration, not by anything in this build.
Per-app background control (the app_* tools) was just turned off for this device by a remote configuration change.
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