Skip to content

chore(agents): use model tier aliases instead of pinned IDs - #4

Merged
raymondware merged 2 commits into
mainfrom
chore/model-aliases
Oct 23, 2026
Merged

raymondware merged 2 commits into
mainfrom
chore/model-aliases

Conversation

@raymondware

Copy link
Copy Markdown
Owner

Why

Every agent pinned an exact model ID. Opus (claude-opus-4-8) and Sonnet (claude-sonnet-4-6) were two generations behind, and each release would leave them stale again.

What changed

  • All 18 agents use tier aliases: 9 haiku, 6 sonnet, 3 opus. Each agent stays in the same tier as before.
  • tools/validate_plugin.py fails when an agent's model isn't haiku, sonnet, opus, or inherit.
  • CLAUDE.md, README.md, and SKILL.md drop the "Opus 4.8" label, and the new-agent steps now say to use an alias.

Verification

  • python3 tools/validate_plugin.py passes, and it fails if an agent is set back to claude-haiku-4-5
  • python3 -m unittest discover -s tests: 7 tests pass

Agents pinned claude-opus-4-8, claude-sonnet-4-6, and claude-haiku-4-5,
which fall behind each model release. Tier aliases resolve to the newest
model in each tier. Each agent keeps its tier, docs drop the 4.8 version
label, and validation now rejects pinned model IDs.
The selector runs on Sonnet but was grouped under the Opus orchestration
heading.
@raymondware
raymondware merged commit 0ed95b0 into main Oct 23, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant