What probably matters to youSection of the release
What
Unattended 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".
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.
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."
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.
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.
Why
You 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.
