devActivitydevActivity Logo

Optimizing Your Software Engineering Goals: Understanding GitHub Copilot Model Availability in JetBrains IDEs

Developers often rely on powerful AI assistants like GitHub Copilot to streamline their workflow and achieve their software engineering goals more efficiently. However, it can be frustrating when you enable new, advanced AI models in your Copilot settings, only to find they don't appear in your preferred Integrated Development Environment (IDE). This common scenario was recently highlighted in a GitHub Community discussion, where a user encountered issues with Copilot model availability in JetBrains Rider.

Developer working with AI assistant in an IDE.
Developer working with AI assistant in an IDE.

The Challenge: Unseen AI Models in JetBrains IDEs

The discussion began with sebas77, who had linked their account to a company Copilot subscription and enabled several models: Codex 5.3, Opus 4.6, and Gemini 3. Despite enabling all three, only Gemini 3 was visible and usable within JetBrains Rider. This raised a critical question: why weren't the other models appearing?

The core of the issue, as explained by community member its-Kashie, lies in the complex interplay between new model rollouts, IDE plugin support, and specific version requirements. While GitHub Copilot continuously adds support for innovative models like GPT-5.3-Codex, their availability in various IDEs, particularly JetBrains products like Rider, can lag.

Key Reasons for Model Discrepancies:

  • Gradual Rollouts: New Copilot models and features, even when announced as generally available (e.g., GPT-5.3-Codex), often roll out gradually across different user bases and regions. This means that even if enabled in your account settings, a model might not be immediately accessible to everyone.
  • IDE Plugin Lag: The integration of GitHub Copilot with various IDEs relies on dedicated plugins. These plugins need to be updated to support the latest AI models and features. JetBrains IDEs, including Rider, can sometimes experience a delay in updating their Copilot plugin to expose the full range of available models. Community reports, such as those found on Reddit, often highlight this limitation.
  • Version Compatibility: Specific models might require certain minimum versions of the Copilot plugin or even the IDE itself. An older plugin version might not have the necessary code to recognize or display newer models, even if they are technically enabled on the backend.
  • Actual Availability: As sebas77 later discovered, sometimes models that appear in a list of options (perhaps generic or future-looking) are not yet truly available for general use within Copilot itself, irrespective of the IDE.
AI models integrating with an IDE, showing some models as unavailable.
AI models integrating with an IDE, showing some models as unavailable.

Optimizing Your AI Assistant Experience for Software Engineering Goals

To ensure you're getting the most out of your GitHub Copilot and leveraging its full potential to meet your software engineering goals, consider these actionable steps:

  • Update Your Copilot Plugin: Always ensure your GitHub Copilot plugin within your JetBrains IDE (Rider, IntelliJ, etc.) is updated to the latest version. This is often the quickest way to gain access to newly supported models and features.
  • Check for IDE Updates: Sometimes, the plugin's functionality is tied to the IDE version. Keep your JetBrains IDE updated to ensure optimal compatibility.
  • Monitor Official Announcements: Follow the official GitHub Blog and Copilot changelog for announcements regarding new model availability and specific IDE support. This helps manage expectations about when a model will truly become usable in your environment.
  • Community Insights: Engage with community discussions on GitHub, Reddit, or other developer forums. Other users often share their experiences and workarounds for similar issues.
  • Verify Model Status: If a model isn't showing up, it's worth double-checking if it's genuinely available for your Copilot plan and region, or if it's still in a limited rollout phase.

Understanding these nuances is crucial for developers aiming to integrate AI tools seamlessly into their daily work. While the promise of advanced AI models is exciting, the practicalities of software integration mean that patience and proactive updates are key to unlocking their full potential and driving your software engineering goals forward.