{"version":"2.1.281","anchor":"remote-session-debug-level-sync-lines-no-longer-shown-in-th","canonical_anchor":"remote-session-debug-level-sync-lines-no-longer-shown-in-th","heading":"Remote session: debug-level sync lines no longer shown in the transcript; sync status reports 'not armed'","tier":"notice","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-session-debug-level-sync-lines-no-longer-shown-in-th","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote session: debug-level sync lines no longer shown in the transcript; sync status reports 'not armed'\n\nDebug-level remote sync messages now go only to the debug log instead of also appearing in the conversation\n\n**Unclear.** The finding does not say which reasons the new \"not armed\" check can report.\n\n**What**\n\nIn a remote session, directory sync and home-settings sync send status messages. A remote session is one where Claude Code runs on another machine. Messages at the \"debug\" level now go only to the debug log. Before, they were also added to the conversation as info messages.\n\nThe cloud session sync summary can now give a specific reason that sync is not active, instead of always saying \"not_set_up\". Its local-tools entry also takes into account notifications recorded once per session.\n\n**Why**\n\nThe conversation no longer fills up with low-level sync chatter. When sync is not running, the summary can say why rather than giving the same generic reason every time.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}