Gemini 3 Pro and Gemini 3 Flash have been released and are available to select Gemini Code Assist users in VS Code and IntelliJ. Gemini 3 is supported in agent mode, chat, and code generation. Agent mode and chat responses include a label when they are generated using Gemini 3.
If you are running into issues, see the troubleshooting section for assistance.
Gemini 3 Availability
Gemini 3 is gradually being made available to Gemini Code Assist users.
| License / Subscription | Gemini 3 Availability |
|---|---|
| Google AI Ultra | Available now to all users in VS Code and IntelliJ |
| Google AI Pro | Available now to all users in VS Code and IntelliJ |
| Gemini Code Assist Enterprise | Available now to all users in VS Code and IntelliJ whose administrator has configured the Preview release channel |
| Gemini Code Assist Standard | Available now to all users in VS Code and IntelliJ whose administrator has configured the Preview release channel |
| Gemini Code Assist for individuals | Available to select users from the waitlist in VS Code and IntelliJ. Coming soon for other users |
| Google Developer Program | Coming soon |
| Google AI Ultra for Business | Coming soon |
Use Gemini 3 in VS Code
If Gemini 3 is available to you, it will automatically be used for chat and code generation. The model selector can be used in chat to select a different model. Additional steps are required to use Gemini 3 in agent mode.
Agent mode
To use Gemini 3 in agent mode in VS Code, you need to enable the Gemini CLI Preview Features setting. This will configure Gemini 3 to be used by both Gemini CLI and agent mode in VS Code. There are several ways to configure the Gemini CLI Preview Features setting.
Workspace settings file
This file applies only when running the VS Code agent mode or Gemini CLI from within the specific project directory or its subdirectories. It overrides user settings.
If it doesn't exist already, create the following directory and file at the root of your workspace:
.gemini/settings.json
Add the following contents to the file:
{ "general": { "previewFeatures": true } }Save the file and reopen VS Code.
User settings file
These settings apply to all projects for the current user.
If it doesn't exist already, create the following directory and file on your file system:
Linux/macOS:
~/.gemini/settings.json
Windows:
C:\Users\<YourUsername>\.gemini\settings.json
Add the following contents to the file:
{ "general": { "previewFeatures": true } }Save the file and reopen VS Code.
Gemini CLI
Using the Gemini CLI, you can choose enable Gemini 3 at the user or workspace level by changing the Preview Feature setting to true. To apply the Preview Features setting for a specific workspace, ensure you run Gemini CLI from that workspaces directory.
Close VS Code.
Install the latest stable Gemini CLI if you haven't already done so.
Run Gemini CLI after installation using the following command:
gemini
In the Gemini CLI, open settings using the following command:
/settings
Navigate to the Preview Features setting and enable it at the workspace or user level.
Reopen VS Code.
Use Gemini 3 in IntelliJ
If Gemini 3 is available to you, it will automatically be used for agent mode, chat and code generation. The model selector can be used in chat to select a different model.
Troubleshooting
If you are running into issues using Gemini 3, there are several troubleshooting steps that may help.
Account not eligible for Gemini 3 in VS Code agent mode
If you enable Preview Features in Gemini CLI settings but aren't eligible for Gemini 3, you will see an error when trying to use agent mode in VS Code. You can resolve this by changing the Preview Feature setting to false for your at the user or workspace level using the prior instructions.
Unable to toggle into agent mode
This is the result of the same issue as Account not eligible for Gemini 3 in VS Code agent mode.
Gemini 3 works in Gemini CLI but not agent mode in VS Code
This can occur when the Gemini CLI Preview Features setting is enabled at the system level, which agent mode in VS Code does not use. If that is the case, try enabling the Preview Features setting at the user or workspace level using the prior instructions.