Skip to content

squad-issue-assign: allow configuring the Copilot agent model (currently hard-coded model: '') #2081

Open

Description

@AmittaiShapira

Problem

squad-issue-assign.yml (generated, overwritten by squad upgrade) sends the Copilot assignment request with a hard-coded empty model:

agent_assignment: {
  base_branch: baseBranch,
  custom_instructions: '',
  custom_agent: '',
  model: ''
}

An empty model means GitHub falls back to its default cloud-agent model. A project cannot choose the model for label-triggered squad:copilot work without editing a Squad-owned workflow, and that edit is lost on the next squad upgrade.

Proposal

Read the model (and optionally custom_agent / custom_instructions) from project-owned configuration, for example:

  • a repository Actions variable such as vars.COPILOT_AGENT_MODEL, or
  • a field in .squad/config.json (e.g. copilot.model), consistent with the existing per-agent model settings.

When the value is unset, keep today's behavior (model: '' → platform default).

Acceptance criteria

  • The model sent in agent_assignment.model comes from project-owned configuration and survives squad upgrade.
  • An unset value preserves the current default behavior.
  • Docs describe the setting next to the COPILOT_ASSIGN_TOKEN setup.

Context

Found while validating end-to-end squad:copilot assignment in a downstream repository. Related: #2080 (assignment token fallback / duplicate assignment).

Activity

  1. dat-intellis commented on Sep 26, 2026

    @dat-intellis

    I believe there's ways to dictate a fixed model. Either in the charters (not relevant here) or in the .squad/config.json file.

  2. bradygaster commented on Oct 3, 2026

    @bradygaster
    Collaborator

    Thanks for the clear report. We are deferring configurable cloud-agent models for now and leaving this issue open. First we are addressing #2080 so label-triggered Copilot assignment has one authoritative workflow and fails explicitly when its required token is missing. After that, we can revisit a project-owned model setting that survives upgrades, preserves the platform default when unset, and is documented alongside token setup. The assessment found the generated assignment payload still sends an empty model; existing charter or config model preferences should not be assumed to control this separate cloud-agent assignment path.

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

    wave1:P3Wave 1 PR group P3wave:1-nextWave 1 — immediate next sprint

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions