{"version":"2.1.304","anchor":"on-branch-ref-revision-pool-options-threaded-through-a","canonical_anchor":"on-branch-ref-revision-pool-options-threaded-through-a","heading":"Task launches can take their starting branch from --on-branch or --ref","tier":"use","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/on-branch-ref-revision-pool-options-threaded-through-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Task launches can take their starting branch from --on-branch or --ref\n\nA launch path now uses the branch from --on-branch first, then the ref from --ref, and records which flag supplied it\n\n**Unclear.** It is not clear whether anything uses this path yet, so whether these flags change where a task starts is unknown.\n\n**What**\n\nClaude Code now has a path that picks which point in your git history a task should start from. A ref is a named point in that history, such as a branch.\n\n- If a branch was given with `--on-branch`, that branch is used.\n\n- Otherwise, if a ref was given with `--ref`, that ref is used.\n\n- Otherwise, no starting point is set.\n\nThe chosen starting point is kept together with the name of the flag that supplied it. Both flags already existed; what is different is that these choices now feed into this launch path.\n\n**Why**\n\nThis points towards remote sessions, or a pool of ready sessions, being started from a specific branch or ref instead of the default.\n\n- Area: Cloud Sessions\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}