Allow setting different models for different squad members

I'd like to be able to specify the models that my different squad members use eriod in some cases I'd like to specify that they use the inexpensive or free GPT models or I might want to specify that they can use the latest and greatest most expensive models.

Can we introduce a standard for a way to specify these perhaps in a Agents charter or be able to provide a command line that allows us to blanket specify a model that's going to be used by any or all team members

feat: CI/CD workflows + squad resolution algorithms

docs(ai-team): Merge next-wave triage decisions, update agent history

fix: wire missing CLI commands into cli-entry.ts (#244)

📋 Assigned to Keaton (Lead)

Issue: #205 — Allow setting different models for different squad members

Keaton 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:
Keaton, work on issue #205

🏗️ Squad Triage — Keaton (Lead)

Issue: #205 — Allow setting different models for different squad members
Assigned to: Hockney (Tester)
Reason: Issue relates to testing/quality work

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

Team roster:

Keaton (Lead) → label: squad:keaton
Verbal (Prompt Engineer) → label: squad:verbal
Fenster (Core Dev) → label: squad:fenster
Hockney (Tester) → label: squad:hockney
McManus (DevRel) → label: squad:mcmanus
Kujan (SDK Expert) → label: squad:kujan
Edie (TypeScript Engineer) → label: squad:edie
Kobayashi (Git & Release) → label: squad:kobayashi
Fortier (Node.js Runtime) → label: squad:fortier
Rabin (Distribution) → label: squad:rabin
Baer (Security) → label: squad:baer
Redfoot (Graphic Designer) → label: squad:redfoot
Strausz (VS Code Extension) → label: squad:strausz
Saul (Aspire & Observability) → label: squad:saul
Kovash (REPL & Interactive Shell) → label: squad:kovash
Marquez (CLI UX Designer) → label: squad:marquez
Cheritto (TUI Engineer) → label: squad:cheritto
Breedan (E2E Test Engineer) → label: squad:breedan
Nate (Accessibility Reviewer) → label: squad:nate
Waingro (Product Dogfooder) → label: squad:waingro
Ralph (Work Monitor) → label: squad:ralph
@copilot (Coding Agent) → label: squad:copilot

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

Thanks for raising this! Model configuration and agent customization is something we're actively working on. We've made progress on related areas like charter-based governance (see #242 and our recent architecture work), and we're building out the foundations that'll support per-agent model selection. If you're still looking to test this approach, feel free to reopen or file a follow-up issue with your specific use case — we'd love to hear how you're thinking about using different models. 🙌

@csharpfritz

Thanks for pushing on model flexibility, @csharpfritz! Being able to specify which models different squad members use—cheaper for routine work, premium for complex reasoning—is a huge UX gap. We've got this in active design now. Charter-level configuration is the right mental model. Really appreciate this input! 🚀

— McManus 📝, on behalf of the Squad

Navigation Menu

Repository navigation

Allow setting different models for different squad members #205

📋 Assigned to Keaton (Lead)

🏗️ Squad Triage — Keaton (Lead)

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

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Allow setting different models for different squad members #205

Description

Activity

github-actions commented on Mar 7, 2026

📋 Assigned to Keaton (Lead)

github-actions commented on Mar 7, 2026

🏗️ Squad Triage — Keaton (Lead)

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

bradygaster commented on Mar 7, 2026

bradygaster commented on Mar 7, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions