{"version":"2.1.319","anchor":"session-activity-signal-for-connector-and-peer-messages-ten","canonical_anchor":"session-activity-signal-for-connector-and-peer-messages-ten","heading":"Messages from connectors and other sessions now count as session activity","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/session-activity-signal-for-connector-and-peer-messages-ten","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Messages from connectors and other sessions now count as session activity\n\nMessages that arrive from connectors or from other sessions now record a session activity marker, and user messages note when they came from a connector\n\n**What**\n\nA session is one running conversation with Claude Code. Messages that arrive from a connector, a tool from claude.ai, now record a marker saying the session is active. Messages relayed from other sessions do the same, behind a switch that is on unless it is turned off remotely.\n\n- User messages carry a new `fromConnector` flag.\n\n- Attached files listed in `file_attachments` gain a `from_connector` field.\n\nThe recording of these events no longer waits on a separate check that it is enabled.\n\n**Why**\n\nSessions driven by connectors or other sessions, not by someone typing, can now be seen as active. If you read user messages or their attachments, you can tell which ones came from a connector.\n\n- Flag `tengu_lively_plover`: Not enough to say (read for one account on one subscription tier against v2.1.319; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}