{"version":"2.1.284","anchor":"unattended-serving-consent-can-be-managed-from-the-scheduled","canonical_anchor":"unattended-serving-consent-can-be-managed-from-the-scheduled","heading":"Unattended-serving consent gets a Remote Control hub row, and a Yes is not saved when settings turn it off","tier":"use","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/unattended-serving-consent-can-be-managed-from-the-scheduled","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Unattended-serving consent gets a Remote Control hub row, and a Yes is not saved when settings turn it off\n\nA new hub row lets you see or withdraw consent for cloud sessions running commands on your computer, and policy-blocked Yes answers are not stored\n\n**Unclear.** It is not clear when the row appears for someone who has never answered the consent question.\n\n**What**\n\nUnattended serving means letting cloud sessions run commands on your computer while nobody is watching. Your consent for that was only a `\/config` toggle, \"Unattended commands from cloud sessions on this computer\".\n\n- The Scheduled \/ Remote Control hub has a new row, \"Unattended commands from cloud sessions\", in its Remote Control tab. It shows whether you accepted and, when the setting is managed, why it is locked.\n\n- Selecting the row either withdraws consent in place (saved as declined) or opens `UnattendedServingConsentDialog`. If saving fails, it shows \"The answer could not be saved. Nothing was changed.\"\n\n- The row is shown when the `tengu_violin_wood` gate allows it (its fallback is false), or when you already have a consent answer or the stored one is stale or unreadable. For a new user with no value from the server, it stays hidden.\n\n- `remoteTools.allowUnattendedServing: false` in managed, policy or user settings locks the choice.\n\n- With that setting at false, an accepted consent is no longer written to disk: a warning is logged and the save reports failure. Before, any choice was written.\n\n**Why**\n\nYou get a second, more direct place to check and revoke permission for cloud sessions to run commands on your machine, and an admin policy that disables unattended serving cannot be quietly overridden by a stored Yes.\n\n- Area: Remote Control\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}