feat(framework): remove AI meta-select (#545)#548
Merged
Conversation
A run no longer spends an agent turn guessing which domain preset, modes, and build event kind to run under. A preset is used only when asked for (--preset / the-framework.yml); otherwise the plain flow runs. The routing turn chose part of the run's own framing mid-run, so the prompt could not be known before the run started. Also removes --no-auto-preset, the autoSelectPreset / workspaceSummary / metaSelect exports, and the bench:meta-select benchmark. Drops the two pending changesets that describe refinements to the removed router.
This was referenced Jul 15, 2026
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
1 participant
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.
Closes part of #545. First of two: meta-select now, the architect next.
A run no longer spends a turn guessing which preset to run under. A preset is used only when you ask for one (
--preset/the-framework.yml); otherwise the plain flow runs. Nothing infers one.This is the part of #545 that stands alone. It also removes a turn that picked part of the run's own framing mid-run, which is what made a build prompt unknowable before it started.
What goes
autoSelectPreset(cli.ts),meta-select.ts,meta-select-bench.ts,bench/meta-select.mjs+ thebench:meta-selectscript--no-auto-preset(nothing left to opt out of)workspaceSummary— it existed only to summarize the repo for the router prompt, and had no other callernarrow-metaselect-vague-502,dashboard-preset-routing-narration). Both describe refinements to the router, and neither has shipped yet (release PR chore: version packages #285 is still open), so keeping them would put "we narrowed the router" and "we removed the router" in the same changelog. Shout if you'd rather I kept them.Verify
framework --helpno longer offers--no-auto-preset;--presetandthe-framework.ymlstill resolve as before