If there are "No supported models," the CLI should check if there is an org policy blocking access and display this

Describe the feature or problem you'd like to solve

If the "Copilot CLI" policy is disabled, users subject to it log in and see "No supported models"

Proposed solution

If we would display "No supported models," we should check if org policy is the reason for the block. If so, we should display an informative error message

Example prompts or workflows

No response

Additional context

No response

Fix the crash if you also type the /model too

I think there is more to this than just the org policies. For us I've validated at the Enterprise level that the Copilot Policies allow access to all the models: Claude Sonnet 4, GPT-5 and Claude Sonnet 4.5. I've also confirmed Copilot CLI Preview is enabled too.

Like others have said, downgrading to version 0.0.330 works as a workaround.

# Uninstall current version
npm uninstall -g @github/copilot

# Install specific version
npm install -g @github/copilot@0.0.330

# Verify the version
copilot --version

We've made a lot of improvements to how we check policy blocks on models. Going to close this issue!

Navigation Menu

Repository navigation

If there are "No supported models," the CLI should check if there is an org policy blocking access and display this #229

Describe the feature or problem you'd like to solve

Proposed solution

Example prompts or workflows

Additional context

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

If there are "No supported models," the CLI should check if there is an org policy blocking access and display this #229

Description

Describe the feature or problem you'd like to solve

Proposed solution

Example prompts or workflows

Additional context

Activity

er1c commented on Oct 7, 2025

stanvx commented on Oct 7, 2025

RyanHecht commented on Feb 25, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions