{"version":"2.1.318","anchor":"queue-setpassive-and-control-protocol-additions","canonical_anchor":"queue-setpassive-and-control-protocol-additions","heading":"New plumbing for remote and attached-project sessions","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/queue-setpassive-and-control-protocol-additions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### New plumbing for remote and attached-project sessions\n\nClaude Code gains several internal additions for remote and attached-project sessions, including a `set_attached_project` control message\n\n**Unclear.** It is not clear whether any of these are used yet or how `set_attached_project` is reached.\n\n**What**\n\nSeveral pieces were added to how Claude Code exchanges messages with programs controlling it and with remote sessions:\n\n- Waiting commands in the queue can now be marked as passive, or have that mark removed.\n\n- The control protocol, the set of messages a controlling program can send, gains `set_attached_project`.\n\n- Events from remote sessions can now say who authored the session.\n\n- A task run through an MCP server, an outside tool provider, can now finish with the reason `connector_changed`.\n\n- Claude Code now reports when a connection to an MCP server was not passed along.\n\n**Why**\n\nThese are groundwork for remote sessions and sessions tied to a project.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}