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
squad-issue-assign: allow configuring the Copilot agent model (currently hard-coded model: '') #2081
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).
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.
Activity
dat-intellis commentedon Sep 26, 2026
I believe there's ways to dictate a fixed model. Either in the charters (not relevant here) or in the .squad/config.json file.
bradygaster commentedon Oct 3, 2026
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.