You now decide separately whether cloud sessions may use your plugins and your local settings.
What's wrong with this entry?
Two separate consents now decide what a cloud session inherits from this machine. /cloud-plugins asks whether cloud sessions may use the plugins you have enabled here. A second prompt, "Use this machine's settings in cloud sessions?", covers CLAUDE.md, rules, output styles, preferences and portable permission rules. Both default to unanswered, and until you answer nothing is sent. A new hidden flag --no-home-settings suppresses the settings copy for a single launch.
/cloud-pluginsoffers "Yes, use my enabled plugins in cloud sessions" / "No, keep them on this machine only" / "Not now", with "Not now" focused by default. The answer is stored per machine and logged astengu_cloud_plugins_consentwith the new and previous choice. Undecided sessions reportno_consentand forward nothing; elsewhere a nudge reads "Your plugins are not used in cloud sessions from this machine yet: run /cloud-plugins in claude on this machine to decide."- The command is offered only when a capability check passes and
CLAUDE_CODE_DISABLE_PLUGIN_FORWARDINGis unset. The forwarding machinery itself already shipped in 2.1.241; this build adds the way to say yes. - Settings forwarding is stored as
remoteHomeSettingsMode, valuesforward/keep_local/ unanswered, with prompt and change eventstengu_home_settings_mode_prompt_shownandtengu_home_settings_mode_set. Forwarding requires all of: the account having settings-to-cloud enabled server-side, a launch that may forward, and the mode being exactlyforward. - A
/configrow named "Use this machine's settings in cloud sessions" can turn it off but not on: enabling from the settings list returns "Turn this on from the /config panel, which shows what will be sent", which lists what would be sent. If the account flag is off, turning it on is refused with "Could not turn this on: forwarding settings to cloud sessions is not enabled for you right now". - On the cloud side the forwarded pack is signed, schema-checked and written under the config home with symlink, hard-link and parent-escape checks, then announced as "Started with settings from your machine: ". With the account flag off that path throws "settings forwarding is not enabled for this account" and does nothing.
--no-home-settingsrequires--cloudor--environmentand is rejected otherwise.- Off-switch reasons you may see reported:
launch_flag,flag_off,declined,no_consent,unbound,not_seeded. - Plugin installs that a reload stopped waiting for now report their late outcome (
tengu_cloud_plugins_late_install).
Use this machine's settings in cloud sessions, Choose whether cloud sessions use the plugins enabled on this machine, Use this machine's settings in cloud sessions?, Your plugins are not used in cloud sessions from this machine yet: run /cloud-plugins in claude on this machine to decide., forwardHomeSettings, settings forwarding is not enabled for this account, Could not turn this on: forwarding settings to cloud sessions is not enabled for you right now, "Choose whether cloud sessions use the plugins enabled on this machine", "Don't send this machine's settings (CLAUDE.md, rules, output styles, preferences, portable permission rules) into the cloud session this launch creates or attaches to. Requires --cloud or --environment.", tengu_cloud_plugins_late_install, forwardHomeSettings: e.homeSettings !== !1, tengu_home_settings_mode_prompt_shown
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.