{"version":"2.1.228","anchor":"per-session-directory-sync-registry-for-laptop-sessions","canonical_anchor":"per-session-directory-sync-registry-for-laptop-sessions","heading":"Per-session directory sync registry for laptop sessions","tier":"soon","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/per-session-directory-sync-registry-for-laptop-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Per-session directory sync registry for laptop sessions\n\nEach session gets at most one directory sync, with the oldest released once a cap is hit.\n\n**What**\n\nNew code keeps one directory sync per session, shutting down an existing one before replacing it and releasing the oldest once a cap is reached. It only attaches when the session's git root resolves to container sync mode and a remote already exists, so most sessions never reach it.\n\n**Details**\n\n- Each entry pairs a status publisher with a bounded backlog and a lane row client, keyed by session id.\n\n**Evidence**\n\n`container_sync`\n\n- Area: Cloud Sessions\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}