-
-
Notifications
You must be signed in to change notification settings - Fork 0
feat(workflow): add parallel agent execution with batch spawning #1293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
0a9be40
4146f9c
efa307a
896684c
42d64db
3a15527
5b9f4d7
fe35f33
82e3500
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -107,3 +107,16 @@ default_modes: | |
| # fixed set of tools to use as the base tool set (if non-empty), replacing Serena's default set of tools. | ||
| # This cannot be combined with non-empty excluded_tools or included_optional_tools. | ||
| fixed_tools: [] | ||
|
|
||
| # time budget (seconds) per tool call for the retrieval of additional symbol information | ||
| # such as docstrings or parameter information. | ||
| # This overrides the corresponding setting in the global configuration; see the documentation there. | ||
| # If null or missing, use the setting from the global configuration. | ||
| symbol_info_budget: | ||
|
|
||
| # The language backend to use for this project. | ||
| # If not set, the global setting from serena_config.yml is used. | ||
| # Valid values: LSP, JetBrains | ||
| # Note: the backend is fixed at startup. If a project with a different backend | ||
| # is activated post-init, an error will be returned. | ||
| language_backend: | ||
|
Comment on lines
+110
to
+122
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,7 @@ | ||
| """Workflow execution and chaining for agent pipelines.""" | ||
| """Workflow execution and chaining for agent pipelines. | ||
|
|
||
| Supports sequential chaining, parallel execution, and refinement loops. | ||
| """ | ||
|
|
||
| from scripts.workflow.coordinator import ( | ||
| CentralizedStrategy, | ||
|
|
@@ -10,6 +13,15 @@ | |
| find_ready_steps, | ||
| get_strategy, | ||
| ) | ||
| from scripts.workflow.executor import WorkflowExecutor | ||
| from scripts.workflow.parallel import ( | ||
| AggregationStrategy, | ||
| ParallelGroup, | ||
| ParallelStepExecutor, | ||
| can_parallelize, | ||
| identify_parallel_groups, | ||
| mark_parallel_steps, | ||
| ) | ||
| from scripts.workflow.schema import ( | ||
| CoordinationMode, | ||
| StepKind, | ||
|
|
@@ -22,20 +34,27 @@ | |
| ) | ||
|
|
||
| __all__ = [ | ||
| "AggregationStrategy", | ||
| "CentralizedStrategy", | ||
| "CoordinationMode", | ||
| "CoordinationStrategy", | ||
| "CentralizedStrategy", | ||
| "HierarchicalStrategy", | ||
|
Comment on lines
+37
to
41
|
||
| "MeshStrategy", | ||
| "ParallelGroup", | ||
| "ParallelStepExecutor", | ||
| "StepKind", | ||
| "StepRef", | ||
| "StepResult", | ||
| "WorkflowDefinition", | ||
| "WorkflowExecutor", | ||
| "WorkflowResult", | ||
| "WorkflowStatus", | ||
| "WorkflowStep", | ||
| "aggregate_subordinate_outputs", | ||
| "build_execution_plan", | ||
| "can_parallelize", | ||
| "find_ready_steps", | ||
| "get_strategy", | ||
| "identify_parallel_groups", | ||
| "mark_parallel_steps", | ||
| ] | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two jobs in the workflow have the same name "Aggregate Results" (aggregate-skip at line 304 and aggregate at line 314). GitHub Actions uses job names in the UI and for branch protection rules. Having duplicate job names can cause confusion and may lead to issues with branch protection rule matching. The aggregate-skip job should have a distinct name like "Aggregate Results (Skip)" to differentiate it from the actual aggregate job.