Your home Claude settings can now be sent to cloud sessions

What

Claude Code can now copy your personal Claude settings from this machine into a cloud session. This is called home seeding. It uploads CLAUDE.md, rules and output styles from ~/.claude, plus a bundle of settings. The request is signed with a key belonging to this device. When the cloud session confirms it is ready, you see messages such as "The cloud session applied your settings before its first reply" or "Settings from this machine were not sent to the cloud session".

• It runs when a session is created and stays attached, and now also when you attach to an existing session. Attaching used to return "unsupported".
• It runs only if you agreed to forward home settings (consent mode "forward"), forwardHomeSettings is not false, the environment is not byoc (bring your own compute) and no agent is set.
• Sensitive files and files you have denied Claude from reading are held back.
• It is skipped when --setting-sources leaves out user settings.

Nothing has been read about the gates tengu_home_seed_upload and tengu_home_seed_ready_seen.

Why

Cloud sessions can behave like your local Claude Code from the first reply, with the same instructions and styles. It also means local configuration and memory files leave your machine, so check what your ~/.claude folder contains before you opt in.