{"version":"2.1.223","anchor":"remote-sessions-stop-shelling-out-for-local-git-state","canonical_anchor":"remote-sessions-stop-shelling-out-for-local-git-state","heading":"Remote sessions stop shelling out for local git state","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/remote-sessions-stop-shelling-out-for-local-git-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Remote sessions stop shelling out for local git state\n\nRemote sessions skip local git and gh lookups, so startup is faster there.\n\n**What**\n\nIn remote mode, several call paths substitute empty or false values instead of probing the local checkout, and startup telemetry gains a coarse classification of the remote host.\n\n**Details**\n\n- Affected call sites: share\/transcript collection, startup context gathering, session-metadata assembly, and the git-info telemetry helper.\n- Skipped work includes git status, worktree counts and `gh` auth checks.\n- A new git-info helper classifies the remote into `github`, `ghe`, `gitlab`, `bitbucket`, `azure` or `other` for startup telemetry.\n\n**Evidence**\n\n`remote_host_class`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}