feat: Migrate Agent Loops into one-node workflows

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

dries/ocman#325

dries commented

2026-07-13 19:46:14 +02:00

Owner

Parent

#311

What to build

Consolidate Agent Loops into the workflow model by migrating each existing loop into a triggered one-node workflow while preserving current REST, MCP, and UI behavior as compatibility wrappers for one release.

Acceptance criteria

Migration converts active, paused, completed, and errored loop definitions into one-node workflow definitions with corresponding triggers and policies.
Historical loop iterations become historical workflow run/attempt records as faithfully as available data permits.
Existing loop identifiers or an explicit mapping keep external references resolvable.
Current loop create/list/status/pause/resume/restart/step/delete REST and MCP behavior delegates to the workflow service.
The Loops UI remains usable as a filtered compatibility view over one-node workflows.
Existing schedule, cron, PR, child, and turn behavior has no observable regression.
The separate loop execution engine is retired after migration; one scheduler owns future execution.
Migration is idempotent and safe across interrupted upgrades.
Old databases and fresh databases both pass integration/coverage checks.
Compatibility behavior and planned removal timing are documented.

Blocked by

#315
#322

## Parent #311 ## What to build Consolidate Agent Loops into the workflow model by migrating each existing loop into a triggered one-node workflow while preserving current REST, MCP, and UI behavior as compatibility wrappers for one release. ## Acceptance criteria - [ ] Migration converts active, paused, completed, and errored loop definitions into one-node workflow definitions with corresponding triggers and policies. - [ ] Historical loop iterations become historical workflow run/attempt records as faithfully as available data permits. - [ ] Existing loop identifiers or an explicit mapping keep external references resolvable. - [ ] Current loop create/list/status/pause/resume/restart/step/delete REST and MCP behavior delegates to the workflow service. - [ ] The Loops UI remains usable as a filtered compatibility view over one-node workflows. - [ ] Existing schedule, cron, PR, child, and turn behavior has no observable regression. - [ ] The separate loop execution engine is retired after migration; one scheduler owns future execution. - [ ] Migration is idempotent and safe across interrupted upgrades. - [ ] Old databases and fresh databases both pass integration/coverage checks. - [ ] Compatibility behavior and planned removal timing are documented. ## Blocked by - #315 - #322

dries added the

label

dries referenced this issue

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

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

dries referenced this issue from a commit

2026-07-14 14:50:11 +02:00

feat: trigger immutable workflow runs with overlap policies (#322)

feat: migrate agent loops into one-node workflows (#325)

2026-07-16 00:48:06 +02:00