Skip to content

explicit model picker - aligned to sesson model #618

Closed

Description

@cwiza

When dealing with tented stuff - we need to be able to select certain models. right now I had to go back through and change a bunch of stuff afterward. Is there away to make it easier to do this before?

GHCP suggested - In VS Code mode, Squad subagents inherit the current session model. The repo config now says GPT-5.4 only, but if someone manually changes the VS Code model picker and ignores the instruction, the platform can still run that session on a different model.

Activity

  1. bradygaster commented on Mar 26, 2026

    @bradygaster
    Collaborator

    Thanks for this, @cwiza! You've identified something we absolutely believe in.

    Brady's response says it perfectly: users should be able to pin a model to an agent, and Squad should respect that — full stop. This is a first-class feature, not an edge case.

    Here's the good news: the SDK support already exists. Our model resolution pipeline has this locked in:

    agentOverride > defaultModel > sessionDirective > charterPreference > taskModel > fallback
    

    This means once configured, an agent's model choice takes priority. Perfect for tented/restricted models — explicit user configuration always wins.

    Here's what you get today:

    Your .squad/config.json can pin models:

    {
      "defaultModel": "claude-sonnet-4.6",
      "agentModelOverrides": {
        "flight": "claude-opus-4.6",
        "fido": "claude-haiku-4.5"
      }
    }

    Here's what's coming:

    We're building squad config model command right now so you can configure this conversationally from the CLI — no JSON editing needed. And yes, you can also just tell your coordinator "always use Opus for Flight" and it persists.

    This is a win for enterprise workflows where model choices matter. Thanks for pushing on this. ��

  2. github-actions commented on Mar 26, 2026

    @github-actions
    Contributor

    📋 Assigned to EECOM (Core Dev)

    Issue: #618 — explicit model picker - aligned to sesson model

    EECOM will pick this up in the next Copilot session.

    For Copilot coding agent: If enabled, this issue will be worked automatically.
    Otherwise, start a Copilot session and say:
    EECOM, work on issue #618

  3. github-actions commented on Mar 26, 2026

    @github-actions
    Contributor

    🏗️ Squad Triage — Flight (Lead)

    Issue: #618 — explicit model picker - aligned to sesson model
    Assigned to: Flight (Lead)
    Reason: No specific domain match — assigned to Lead for further analysis

    @copilot evaluation: No strong capability match — routed to squad member.

    Team roster:

    • Flight (Lead) → label: squad:flight
    • Procedures (Prompt Engineer) → label: squad:procedures
    • EECOM (Core Dev) → label: squad:eecom
    • FIDO (Quality Owner) → label: squad:fido
    • PAO (DevRel) → label: squad:pao
    • CAPCOM (SDK Expert) → label: squad:capcom
    • CONTROL (TypeScript Engineer) → label: squad:control
    • Surgeon (Release Manager) → label: squad:surgeon
    • Booster (CI/CD Engineer) → label: squad:booster
    • GNC (Node.js Runtime) → label: squad:gnc
    • Network (Distribution) → label: squad:network
    • RETRO (Security) → label: squad:retro
    • INCO (CLI UX & Visual Design) → label: squad:inco
    • GUIDO (VS Code Extension) → label: squad:guido
    • Telemetry (Aspire & Observability) → label: squad:telemetry
    • VOX (REPL & Interactive Shell) → label: squad:vox
    • DSKY (TUI Engineer) → label: squad:dsky
    • Sims (E2E Test Engineer) → label: squad:sims
    • Handbook (SDK Usability) → label: squad:handbook
    • Ralph (Work Monitor) → label: squad:ralph
    • @copilot (Coding Agent) → label: squad:copilot

    To reassign, remove the current squad:* label and add the correct one.

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

    go:needs-researchNeeds investigationpriority:p2Next sprintsquadSquad triage inbox — Lead will assign to a membertype:featureNew capability

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions