{"version":"2.1.284","anchor":"remote-session-file-sync-notice-rewords-the-explicit-ref-hin","canonical_anchor":"remote-session-file-sync-notice-rewords-the-explicit-ref-hin","heading":"Reworded hint when remote file sync is off because you named a ref","tier":"notice","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/remote-session-file-sync-notice-rewords-the-explicit-ref-hin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Reworded hint when remote file sync is off because you named a ref\n\nWhen file sync is off because you gave an explicit ref, the hint now says running without it starts from this checkout instead\n\n**What**\n\nA remote session is a Claude Code session that runs on another machine rather than your own. When you start one with an explicit ref, meaning a specific git branch, tag or commit, Claude Code does not sync your local files to it. The notice that tells you this also suggests running without that option.\n\nThe end of that suggestion has changed. It used to say the alternative would \"start from an upload of it instead\". It now says it would start \"from this checkout instead.\", where the checkout is the copy of the project on your machine.\n\n**Why**\n\nOnly the wording changed. The hint now names the other choice as your local checkout.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}