You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Computer UseArea: what it touches
New FeaturesKind: in v2.1.242,
New FeaturesSection of the release
What
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.
Details
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.
Evidence
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.
