feat: retire loop engine — loops execute via workflow scheduler #331

New issue

Closed

opened 2026-07-14 09:04:03 +02:00 by dries · 0 comments

dries commented

2026-07-14 09:04:03 +02:00

Owner

Parent

#311, follows #325

What to build

#325 delivered only the one-time state migration copying persisted loops into one-node workflow definitions/runs. The loop execution path was intentionally left in place. Complete the consolidation so a single scheduler owns execution.

Acceptance criteria

Existing loop create/list/status/pause/resume/restart/step/delete REST behavior delegates to the workflow service over one-node workflows.
Existing loop MCP tools delegate to the same workflow service.
The Loops UI is a filtered compatibility view over one-node workflows.
Loop actions (prompt_root/prompt_child/spawn_child/spawn_worktree) execute through workflow agent-node execution.
The separate loop execution engine (runLoopEngine) is removed; no dual execution path remains.
Loop identifiers stay resolvable via the existing loop_workflow_map.
No observable regression to schedule/cron/PR/child/turn behavior; old and fresh DBs pass.
Compatibility-wrapper behavior and the removal timeline are documented.

Blocked by

#325

## Parent #311, follows #325 ## What to build #325 delivered only the one-time state migration copying persisted loops into one-node workflow definitions/runs. The loop execution path was intentionally left in place. Complete the consolidation so a single scheduler owns execution. ## Acceptance criteria - [ ] Existing loop create/list/status/pause/resume/restart/step/delete REST behavior delegates to the workflow service over one-node workflows. - [ ] Existing loop MCP tools delegate to the same workflow service. - [ ] The Loops UI is a filtered compatibility view over one-node workflows. - [ ] Loop actions (prompt_root/prompt_child/spawn_child/spawn_worktree) execute through workflow agent-node execution. - [ ] The separate loop execution engine (runLoopEngine) is removed; no dual execution path remains. - [ ] Loop identifiers stay resolvable via the existing loop_workflow_map. - [ ] No observable regression to schedule/cron/PR/child/turn behavior; old and fresh DBs pass. - [ ] Compatibility-wrapper behavior and the removal timeline are documented. ## Blocked by - #325