Per-purpose model defaults in the built-in agent templates (plan vs dispatch)#84
Merged
Merged
Conversation
The built-in claude templates passed no --model flag, so dispatch and the interactive plan verb both ran whatever the CLI defaulted to. Encode the per-purpose intent instead: dispatch runs --model opus (a workhorse for implementation) and plan runs --model fable (a stronger reasoning model for interactive planning). Both use the `claude` model *aliases* rather than pinned model ids, which resolves the brittleness the task flagged — aliases track the current model of their class, so the built-ins do not churn as models are released. An operator wanting other models overrides the agent wholesale in voro.toml. The starter config derives from BUILTIN_AGENTS, so it and its tests pick the flags up unchanged; the reproduced block in agent-integration.md and the DESIGN.md §8 note are updated to match, and a new test pins the two flags. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H5MedxfX6VHVzz9GfDWoWo
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.
Give the built-in claude verbs per-purpose model defaults.
The built-in claude templates in crates/voro-core/src/agent.rs passed no --model flag, so both dispatch and the interactive plan verb ran whatever the claude CLI defaulted to. This encodes the per-purpose intent from the task:
Decision on brittleness: rather than pinning model ids (which churn faster than Voro releases, the risk the task called out), the templates pass the claude model aliases opus/fable.
claude --helpconfirms --model accepts these aliases ('fable', 'opus', 'sonnet') and resolves each to the current model of that class, so the built-ins track model releases without edits. An operator wanting other models overrides the agent wholesale in voro.toml (copy the block, change the flags) -- no new config surface, as the task suggested.Changes:
Verification: cargo fmt --all clean; cargo test --workspace passes (194 tests); cargo clippy --workspace --all-targets -- -D warnings clean.
Branch: worktree-per-purpose-agent-models (committed locally; not pushed from this background session per the no-remote-git rule).