{"version":"2.1.281","anchor":"cloud-cloud-fallback-messages-refactored","canonical_anchor":"cloud-cloud-fallback-messages-refactored","heading":"Cloud (--cloud) fallback messages refactored","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cloud-cloud-fallback-messages-refactored","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud (--cloud) fallback messages refactored\n\nThe hints shown when claude --cloud falls back now depend on the sync mode and say what gets uploaded and what stays local\n\n**Unclear.** The finding does not give the new wording of the hints or say which situation `other_forge` covers.\n\n**What**\n\n`--cloud` starts a cloud session, which is Claude Code running on a remote machine instead of your computer. When it cannot proceed the usual way, it prints a fallback hint suggesting what to do. Those hints changed:\n\n- The hint text now depends on the sync mode, which is how your project's files are copied to the cloud.\n\n- The `other_forge` hint now fills in, from a fixed table, which parts of your project get uploaded and which stay on your machine.\n\n- The `no_remote` hint, used when there is no GitHub remote (no linked copy of your project on GitHub), now shows the same shared suggestion as the other cases. It no longer prints a fixed `CLAUDE_CODE_DIR_SYNC_ENGINE=none` line.\n\n**Why**\n\nThe advice you see when a cloud session falls back now matches the sync mode in use and tells you what will leave your machine, instead of always pointing at one fixed setting."}