feat(subplans): implement parallel subplan executor with configurable max_parallel concurrency #4998

Open
opened 2026-04-09 00:24:44 +00:00 by HAL9000 · 1 comment
Owner

Metadata

  • Commit Message: feat(subplans): implement parallel subplan executor with configurable max_parallel concurrency
  • Branch: feat/m4/parallel-subplan-executor
  • Parent Epic: #4972

Background and Context

Once subplans are spawned (see #4995), they need to execute in parallel with configurable concurrency limits. This issue implements the ParallelSubplanExecutor that manages concurrent execution of child plans.

Expected Behavior

  • ParallelSubplanExecutor executes up to max_parallel child plans concurrently
  • Parent plan waits for all child plans to complete before proceeding
  • Child plan failures are surfaced to the parent
  • Execution status is tracked and queryable

Acceptance Criteria

  • ParallelSubplanExecutor service implemented
  • Concurrent execution respects max_parallel limit
  • Parent plan status reflects all child plan states
  • Child plan failures propagate to parent
  • agents plan status <PLAN_ID> shows child plan statuses
  • Unit tests (Behave) cover parallel execution scenarios
  • Integration test (Robot) verifies parallel execution

Subtasks

  • Implement ParallelSubplanExecutor service
  • Implement max_parallel semaphore-based concurrency control
  • Implement parent plan status aggregation from child statuses
  • Wire ParallelSubplanExecutor into plan execution pipeline
  • Tests (Behave): Add scenarios for parallel execution
  • Tests (Robot): Add integration test
  • Verify coverage >=97% via nox -s coverage_report
  • Run nox (all default sessions), fix any errors

Definition of Done

This issue is complete when:

  • All subtasks above are completed and checked off.
  • A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly.
  • The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
  • The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planner

## Metadata - **Commit Message**: `feat(subplans): implement parallel subplan executor with configurable max_parallel concurrency` - **Branch**: `feat/m4/parallel-subplan-executor` - **Parent Epic**: #4972 ## Background and Context Once subplans are spawned (see #4995), they need to execute in parallel with configurable concurrency limits. This issue implements the `ParallelSubplanExecutor` that manages concurrent execution of child plans. ## Expected Behavior - `ParallelSubplanExecutor` executes up to `max_parallel` child plans concurrently - Parent plan waits for all child plans to complete before proceeding - Child plan failures are surfaced to the parent - Execution status is tracked and queryable ## Acceptance Criteria - [ ] `ParallelSubplanExecutor` service implemented - [ ] Concurrent execution respects `max_parallel` limit - [ ] Parent plan status reflects all child plan states - [ ] Child plan failures propagate to parent - [ ] `agents plan status <PLAN_ID>` shows child plan statuses - [ ] Unit tests (Behave) cover parallel execution scenarios - [ ] Integration test (Robot) verifies parallel execution ## Subtasks - [ ] Implement `ParallelSubplanExecutor` service - [ ] Implement `max_parallel` semaphore-based concurrency control - [ ] Implement parent plan status aggregation from child statuses - [ ] Wire `ParallelSubplanExecutor` into plan execution pipeline - [ ] Tests (Behave): Add scenarios for parallel execution - [ ] Tests (Robot): Add integration test - [ ] Verify coverage >=97% via `nox -s coverage_report` - [ ] Run `nox` (all default sessions), fix any errors ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done. --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planner
HAL9000 added this to the v3.3.0 milestone 2026-04-09 01:03:27 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: High — Core checkpoint/subplan feature required for Decision Intelligence Legendary
  • Milestone: v3.3.0
  • Story Points: 8 — XL
  • MoSCoW: Must Have — Required for Checkpoint/Subplan Epics (#4973/#4972)

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner

Issue triaged by project owner: - **State**: Verified - **Priority**: High — Core checkpoint/subplan feature required for Decision Intelligence Legendary - **Milestone**: v3.3.0 - **Story Points**: 8 — XL - **MoSCoW**: Must Have — Required for Checkpoint/Subplan Epics (#4973/#4972) --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner
Sign in to join this conversation.
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.

Reference
cleveragents/cleveragents-core#4998
No description provided.