feat(orchestrator): experimental task-queue orchestrator (behind wizard-orchestrator flag)#606
Merged
Merged
Conversation
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Results will be posted here when complete. |
Collaborator
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Jun 9, 2026
gewenyu99
force-pushed
the
experiment/orchestrator-01-bootstrap-gating
branch
from
4438709 to
7112748
Compare
gewenyu99
changed the title
gewenyu99
force-pushed
the
experiment/orchestrator-01-bootstrap-gating
branch
from
7112748 to
f6620f8
Compare
edwinyjlim
reviewed
Jun 10, 2026
This was referenced Jun 10, 2026
gewenyu99
force-pushed
the
experiment/orchestrator-01-bootstrap-gating
branch
from
f6620f8 to
51706a2
Compare
This was referenced Jun 16, 2026
gewenyu99
commented
Jun 17, 2026
gewenyu99
changed the title
Collaborator
Author
Merge activity
|
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…607) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…with guards (#608) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…low (#619) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…il (#620) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…lls (#637) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
#677) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…k outage (#678) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
gewenyu99
force-pushed
the
experiment/orchestrator-01-bootstrap-gating
branch
from
87cdb43 to
b2842fa
Compare
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
2 participants
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.
Experimental task-queue orchestrator, collapsed from an 11-PR stack into this single branch. Behind the
wizard-orchestratorfeature flag, off by default — with the flag off it is a no-op and the existing linear flow runs unchanged.Wizard PRs folded in (squash-merged into this branch)
Related PRs, other repos
agentscontent type, built and served alongside skills context-mill#181 —agentscontent type: agent prompts plus thebasic-integrationstep-skills, built and served alongside skillsFlag gating — why this is a no-op with the flag off
runProgramforks onisOrchestratorEnabled(flags)=flags['wizard-orchestrator'] === 'true'(default false). Off, it runsrunLinearProgram, the existing path, untouched.runAgentthreads the same flag through, so its orchestrator-specific message handling is gated too.WIZARD_CI_FLAG_OVERRIDES) is guarded byNODE_ENV === 'production'and stripped from published builds — a smoke test asserts the env-var names are physically absent — so it cannot flip the flag for real users.