Skip to content

suggest models in claude setup for claude selection #424

Closed

Description

@JacobStephens2
No description provided.

Activity

  1. JacobStephens2 commented on Oct 17, 2026

    @JacobStephens2
    OwnerAuthor

    This was generated by AI during triage.

    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.

  2. JacobStephens2 commented on Oct 25, 2026

    @JacobStephens2
    OwnerAuthor

    This was generated by AI during triage.

    Agent Brief

    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
    • The test-call validation still runs

    Out of scope:

  3. added
    ready-for-agentFully specified, ready for an AFK agent
    in-progressA Claim: thirdshift has taken this issue
    and removed
    needs-triageMaintainer needs to evaluate this issue
    ready-for-agentFully specified, ready for an AFK agent
    on Oct 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions