{"version":"2.1.301","anchor":"teleport-source-decision-telemetry-extended","canonical_anchor":"teleport-source-decision-telemetry-extended","heading":"The --project refusal message no longer varies","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/teleport-source-decision-telemetry-extended","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### The `--project` refusal message no longer varies\n\nMoving a session to the cloud now reports more about branch handling, and the `--project` error is always the same message\n\n**What**\n\nWhen Claude Code decides where a session's code comes from while moving it into the cloud, it now records whether it started its own checkout and whether the branch it launched was the one it was given.\n\nThe error shown when `--project` cannot be used was worded differently depending on a condition. It is now always the same single message.\n\n**Why**\n\nMost of this is usage reporting. The way branches are handled when a session starts may also have changed.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}