An agent on a GitHub Actions runner is told two branch names.
prompts/branch_yourself.md tells it: "Create and check out the branch agent-<SESSION_NAME> yourself (git checkout -b agent-<SESSION_NAME>), and commit your work to it."- The GitHub Actions driver asks the workflow to push to
claude/<session id> (agent-driver's ActionsSession.runBranch, default prefix claude/ — we pass no branchPrefix in target-driver.ts), and dispatches every later turn from that branch.
So the same run has an agent-… branch the agent made and a claude/… branch the workflow pushes; which one carries the work depends on what the workflow does with the branch input, and the reclaim rule in @gemstack/skill-branches only ever looks at agent-* branches. Local and cloud agents end on one agent-<name> branch; Actions agents don't tell the same story.
Options I see: (a) pass branchPrefix: 'agent-' and have the workflow push the branch the agent created; (b) drop the branch instruction from branch_yourself.md for Actions and let the workflow's branch be the one; (c) leave it and document it. No code before Rom weighs in — this is the naming convention users see in their branch list.
Found by the stranger review of the two packages (#1743, #1744 follow-ups).
An agent on a GitHub Actions runner is told two branch names.
prompts/branch_yourself.mdtells it: "Create and check out the branchagent-<SESSION_NAME>yourself (git checkout -b agent-<SESSION_NAME>), and commit your work to it."claude/<session id>(agent-driver'sActionsSession.runBranch, default prefixclaude/— we pass nobranchPrefixintarget-driver.ts), and dispatches every later turn from that branch.So the same run has an
agent-…branch the agent made and aclaude/…branch the workflow pushes; which one carries the work depends on what the workflow does with thebranchinput, and the reclaim rule in@gemstack/skill-branchesonly ever looks atagent-*branches. Local and cloud agents end on oneagent-<name>branch; Actions agents don't tell the same story.Options I see: (a) pass
branchPrefix: 'agent-'and have the workflow push the branch the agent created; (b) drop the branch instruction frombranch_yourself.mdfor Actions and let the workflow's branch be the one; (c) leave it and document it. No code before Rom weighs in — this is the naming convention users see in their branch list.Found by the stranger review of the two packages (#1743, #1744 follow-ups).