{"version":"2.1.281","anchor":"bridge-honours-a-server-request-to-run-a-session-in-a-worktr","canonical_anchor":"bridge-honours-a-server-request-to-run-a-session-in-a-worktr","heading":"Bridge honours a server request to run a session in a worktree","tier":"notice","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/bridge-honours-a-server-request-to-run-a-session-in-a-worktr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Bridge honours a server request to run a session in a worktree\n\nRemote Control sessions now run in a git worktree whenever the server asks for one, and run in place if the folder is not a git repo\n\n**What**\n\nRemote Control starts Claude Code sessions on your machine at the server's request. It now creates a worktree, a separate working copy of a git repository, whenever the server's session settings include `worktree: true`. Before, it did this only when the spawn mode was set to `\"worktree\"`.\n\nIt first checks that the folder is a git repository. If it is not, it logs \"asked for a worktree \u00b7 is not a git repository, running there\" and runs the session in the folder itself. The saved worktree details now also include `baseChangeset` and `sessionDir`, and the usage data sent when a session starts gains `worktree_requested`.\n\n**Why**\n\nA remotely started session can now keep its changes apart from your main copy of the project more often. In a folder that is not a git repository, the session edits the files directly, and the log line tells you why.\n\n- Flag `tengu_bridge_apply_server_session_config`: Not enough to say (read for one account on one subscription tier against v2.1.281; 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: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}