{"version":"2.1.273","anchor":"hostcarrier-check-special-cases-webagent-and-claude-code-rem","canonical_anchor":"hostcarrier-check-special-cases-webagent-and-claude-code-rem","heading":"hostCarrier check special-cases webagent and claude-code-remote carriers","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/hostcarrier-check-special-cases-webagent-and-claude-code-rem","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### hostCarrier check special-cases webagent and claude-code-remote carriers\n\nCarrier eligibility check now special-cases webagent and claude-code-remote carriers\n\n**What**\n\nA function that checks whether a \"carrier\" (an internal identifier for how a session is running) is eligible now handles `webagent` and `claude-code-remote` carriers as a special case: for these two, it only returns true if the carrier matches exactly, before falling back to the general set-based check used for other carriers.\n\n**Why**\n\nThis makes the eligibility check stricter and more precise for webagent and claude-code-remote sessions specifically, avoiding them being matched by the more permissive general logic.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}