Forwarding home settings to cloud sessions now follows a new launch-consent check

What

Claude Code can copy your local "home" settings into a cloud session it starts for you, or into a remote session it attaches to. This is called seeding. Whether it does so depends on your consent, and this release changes how that consent is worked out.

• launchConsent replaces hostConsent in the remote-attach consent check. A stored value of "stored" now becomes "answered", and any other value is passed through unchanged. Before, any value at all produced "host".
• planHomeSeed now receives launchConsent instead of consentMode. In teleportToRemote, seeding is no longer decided by whether homeSettingsConsent equals "forward". It goes through a new consent helper instead.
• A check on whether the folder is a project root, or whether you opted in, now runs before seeding is planned.
• launchConsent also depends on whether the project is still synced (isProjectStillSynced). On attach, settings are sent again only if your own settings flags are on or the project is synced.
• An upload of a synced file can now be refused as too_large, and reads have a size cap.
• The session-creation telemetry gained an extra reason, used after a create attempt fails.

The related gates tengu_home_seed_upload and tengu_home_seed_ready_seen have not been read, so their state is unknown.

Why

This decides when your personal settings leave your machine and are placed in a cloud session. The settings prompt may now be skipped or shown in different cases than before. If you care where your settings end up, check what happens the next time you start or attach to a remote session.