Dispatch hardcodes branches as {worker_key}/{slug} (e.g. spacedock-ensign/<slug>), and that name becomes the public PR head branch on GitHub. Operator feedback: branch names should stay semantic and platform-neutral — encoding which agent platform produced the work is tool noise in a shared upstream repo, inconsistent with hand-named branches, and it outlives the tool (a PR head can never be renamed).
Request: make branch naming configurable at the workflow level — e.g. a README key like branch-style: slug (default could stay worker_key/slug for compatibility). Worktree directory names can keep the worker prefix (local-only); the ask is scoped to the branch/bookmark that reaches the remote.
Workaround used today: FO renames the branch (git branch -m) after worktree creation and before first push — works but is easy to forget and races the worker's first push.
Scale: 7-stage flow with worktree stages + PR-based merge. spacedock@0.26.0.
Dispatch hardcodes branches as
{worker_key}/{slug}(e.g.spacedock-ensign/<slug>), and that name becomes the public PR head branch on GitHub. Operator feedback: branch names should stay semantic and platform-neutral — encoding which agent platform produced the work is tool noise in a shared upstream repo, inconsistent with hand-named branches, and it outlives the tool (a PR head can never be renamed).Request: make branch naming configurable at the workflow level — e.g. a README key like
branch-style: slug(default could stayworker_key/slugfor compatibility). Worktree directory names can keep the worker prefix (local-only); the ask is scoped to the branch/bookmark that reaches the remote.Workaround used today: FO renames the branch (
git branch -m) after worktree creation and before first push — works but is easy to forget and races the worker's first push.Scale: 7-stage flow with worktree stages + PR-based merge. spacedock@0.26.0.