fix(core): Reduce planner workflow bias and fix data-table task routing (no-changelog)#28299
Merged
OlegIvaniv merged 1 commit intomasterfrom Apr 10, 2026
Merged
fix(core): Reduce planner workflow bias and fix data-table task routing (no-changelog)#28299OlegIvaniv merged 1 commit intomasterfrom
OlegIvaniv merged 1 commit intomasterfrom
Conversation
…k routing - Planner now uses data-table kind for all table operations (create, delete, modify) instead of falling back to delegate with incomplete tools - Made blueprint data-table columns optional to support non-creation operations - Updated accumulator to derive task title/spec from purpose when columns absent - Added scope boundary to data-table agent to prevent cross-task side effects - Orchestrator now handles single remaining tasks directly on replan instead of always creating a new plan via create-tasks - Added standalone data-table operations section to best-practices guide
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Contributor
There was a problem hiding this comment.
No issues found across 7 files
Architecture diagram
sequenceDiagram
participant User
participant Orch as Orchestrator (System Prompt)
participant Planner as Plan Agent
participant Accum as Blueprint Accumulator
participant DTAgent as Data Table Agent
participant Tool as Specialized Tools (Workflow/DT/Delegate)
Note over User,Tool: Planning Phase (Initial Request)
User->>Orch: Request table/workflow operations
Orch->>Planner: Identify tasks & design blueprint
loop For each task
Planner->>Planner: CHANGED: Use 'data-table' kind for ALL table ops<br/>(Create, Delete, Modify, Seed)
Planner->>Accum: NEW: add-plan-item (Columns optional)
Accum->>Accum: NEW: Derive task spec from 'purpose'<br/>if columns are absent
end
Planner-->>Orch: Submit Plan
Orch->>Orch: Schedule tasks
Note over Orch,DTAgent: Execution Phase
Orch->>DTAgent: Execute Data Table task
DTAgent->>DTAgent: NEW: Enforce scope boundary<br/>(Ignore context from other tasks)
opt Task includes seed data
DTAgent->>DTAgent: NEW: Create table THEN insert rows
end
DTAgent-->>Orch: Task Result (Success/Failure)
Note over Orch,Tool: Recovery Phase (on Failure)
alt Task Failed: Replan needed
Orch->>Orch: Inspect failure & remaining work
alt NEW: Only 1 simple task remains
Orch->>Tool: Call specific agent tool directly<br/>(e.g., manage-data-tables-with-agent)
Tool-->>User: Final Result
else Multiple tasks or complex dependencies
Orch->>Planner: Call 'create-tasks' for full replan
Planner-->>User: New Plan Visibility
end
end
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Related Linear tickets, Github issues, and Community forum posts
Review / Merge checklist
Backport to Beta,Backport to Stable, orBackport to v1(if the PR is an urgent fix that needs to be backported)