What
A cloud session that could itself rewrite your plugin configuration will not reuse the Yes you saved in /cloud-plugins. A new check works out where that saved answer is stored relative to everything the session can write to, and unless the answer sits outside all of it, the stored Yes is treated as unset. The session says so in plain text, names the reason, and asks you to run /cloud-plugins to decide for that session.
Details
- The message begins
The saved answer about your plugins is not used for this cloud session, becauseand ends with one of four reasons: the answer is in the session's launch directory, in its sync root, in another writable root, or was not checked at all. - A separate notice covers the other case, a cloud worker coming back up after
the saved Yes was withdrawn (a No in /cloud-plugins, or the answer was removed), with the session restarted without plugins. - Nothing gates the behaviour: no flag, no setting, no environment variable. It is reachable in any cloud session that forwards plugins.
- The
/cloud-pluginscommand itself is unchanged; it remains the place to answer for the current session.
Evidence
the saved Yes was withdrawn (a No in /cloud-plugins, or the answer was removed), The saved answer about your plugins is not used for this cloud session, because
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle/cloud-plugins