Skip to content

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

Description

@RyanHecht

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

Activity

  1. added theissue type on Oct 7, 2025
  2. er1c commented on Oct 7, 2025

    @er1c

    Fix the crash if you also type the /model too

  3. stanvx commented on Oct 7, 2025

    @stanvx

    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
  4. RyanHecht commented on Feb 25, 2026

    @RyanHecht
    CollaboratorAuthor

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

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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions