When your plugins aren't forwarded to a cloud session, you now get the specific reason.
What's wrong with this entry?
When your local plugin choices are not forwarded to a cloud session, you now get a reason instead of silence: no plugins to send from this machine, your plugin choices here could not be read, they could not be sent this time, or this session is not bound to this machine. The default case nudges you to run the slash command.
- The fallback message points at
/cloud-pluginsto send them manually.
run /cloud-plugins to send them
Strings lifted out of the shipped bundle, so the claim above can be checked against them.