Sam asked for this directly from a production retry: when a task is retried it should be possible to choose whether the retry refreshes onto the current base or continues the work already pushed on the task branch, and the retry button should present that choice. Today the chooseable half exists only as an unreachable worktree mode (bead 866m wires the dispatch side and removes the no-op implementation), so this bead is the operator surface on top of that seam: the choice must travel from the dashboard through the task action and be persisted on the task so the daemon reads it at dispatch, and the default must be explicit rather than whichever branch the code happened to take. Cross-layer: task action -> wire -> dashboard -> daemon dispatch.
Acceptance criteria
an operator can pick the retry mode from the dashboard, the chosen mode reaches the daemon dispatch path, the persisted choice survives a reload, and both modes have a test proving which source the worktree lands on
Close reason
Closed
Imported from beads archie-core-vrl5 · GitHub #1462 · type feature · priority P2 · created 2026-10-02 · closed 2026-10-02
Sam asked for this directly from a production retry: when a task is retried it should be possible to choose whether the retry refreshes onto the current base or continues the work already pushed on the task branch, and the retry button should present that choice. Today the chooseable half exists only as an unreachable worktree mode (bead 866m wires the dispatch side and removes the no-op implementation), so this bead is the operator surface on top of that seam: the choice must travel from the dashboard through the task action and be persisted on the task so the daemon reads it at dispatch, and the default must be explicit rather than whichever branch the code happened to take. Cross-layer: task action -> wire -> dashboard -> daemon dispatch.
### Acceptance criteria
an operator can pick the retry mode from the dashboard, the chosen mode reaches the daemon dispatch path, the persisted choice survives a reload, and both modes have a test proving which source the worktree lands on
### Close reason
Closed
---
_Imported from beads `archie-core-vrl5` · GitHub #1462 · type feature · priority P2 · created 2026-10-02 · closed 2026-10-02_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Sam asked for this directly from a production retry: when a task is retried it should be possible to choose whether the retry refreshes onto the current base or continues the work already pushed on the task branch, and the retry button should present that choice. Today the chooseable half exists only as an unreachable worktree mode (bead 866m wires the dispatch side and removes the no-op implementation), so this bead is the operator surface on top of that seam: the choice must travel from the dashboard through the task action and be persisted on the task so the daemon reads it at dispatch, and the default must be explicit rather than whichever branch the code happened to take. Cross-layer: task action -> wire -> dashboard -> daemon dispatch.
Acceptance criteria
an operator can pick the retry mode from the dashboard, the chosen mode reaches the daemon dispatch path, the persisted choice survives a reload, and both modes have a test proving which source the worktree lands on
Close reason
Closed
Imported from beads
archie-core-vrl5· GitHub #1462 · type feature · priority P2 · created 2026-10-02 · closed 2026-10-02