You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
suggest models in claude setup for claude selection #424
Claude Setup currently accepts Model/Effort text and validates an explicit Model with a test call; it does not offer model suggestions. Other Harnesses have their own catalog mechanisms.
Decision needed: Should Claude suggestions use a small documented alias list, or a supported catalog source? Suggestions should permit custom model identifiers and preserve the existing validation/default behavior. Coordinate with #425's multi-Harness Setup work; do not freeze current model names without a source/update policy.
Category: enhancement Summary:thirdshift setup suggests Claude Code's model aliases when asking for Claude's Model
Current behavior:
Setup asks for Claude's Model as free text and validates it with a test call. Codex, by contrast, offers choices from its Catalog.
Desired behavior:
When Setup asks for Claude's Model, it lists Claude Code's documented aliases (for example opus, sonnet, haiku, default) as suggestions. The user can still type any model ID, or leave it blank for the default. Existing test-call validation and the current-value default are kept.
Key interfaces:
The Claude Harness's Setup question for Model
Acceptance criteria:
A Setup unit test shows the suggestions and accepts a custom model ID
Leaving it blank keeps the current value or default
Activity
JacobStephens2 commentedon Oct 17, 2026
Triage Notes
Claude Setup currently accepts Model/Effort text and validates an explicit Model with a test call; it does not offer model suggestions. Other Harnesses have their own catalog mechanisms.
Decision needed: Should Claude suggestions use a small documented alias list, or a supported catalog source? Suggestions should permit custom model identifiers and preserve the existing validation/default behavior. Coordinate with #425's multi-Harness Setup work; do not freeze current model names without a source/update policy.
JacobStephens2 commentedon Oct 25, 2026
Agent Brief
Category: enhancement
Summary:
thirdshift setupsuggests Claude Code's model aliases when asking for Claude's ModelCurrent behavior:
Setup asks for Claude's Model as free text and validates it with a test call. Codex, by contrast, offers choices from its Catalog.
Desired behavior:
When Setup asks for Claude's Model, it lists Claude Code's documented aliases (for example
opus,sonnet,haiku,default) as suggestions. The user can still type any model ID, or leave it blank for the default. Existing test-call validation and the current-value default are kept.Key interfaces:
Acceptance criteria:
Out of scope:
harness.default(make a way to choose model config for claude and codex inthirdshift setup#425)