Google IDX is a cloud-based AI development environment that deeply integrates Firebase, Flutter and Google Cloud services to provide a full-stack development experience in the browser.

GoogleIDX

Core parameters and statistics

Google IDX is a cloud AI development environment launched by Google based on Code OSS (VS Code core). It is positioned as a "browser-based development environment for full-stack application development." It is not a general cloud IDE platform, but an integrated development workbench deeply customized around the Google ecosystem (Flutter, Firebase, Gemini).

Parameter items	Public information
Product positioning	AI-enhanced cloud full-stack development context
Underlying kernel	Code OSS (VS Code open source version)
AI engine	Gemini series models (code completion, generation, debugging dialogue)
Preset framework templates	Flutter, Next.js, Angular, React, Svelte, Go, Python, Node.js, etc.
Deep integration services	Firebase, Google Cloud Run, Chrome DevTools, Android Emulator
Contextual management	Nix package manager (customizable system-level tool chain and SDK)
Preview capabilities	Web preview + Android emulator + iOS emulator (in-browser)
Deployment Targets	Firebase Hosting, Cloud Run, Cloud Functions
Current Status	Public Preview (Free)
Home	US
Support Platform	Web
Supported languages	en-US

Positioning difference from competing products: Google IDX is not intended to replace Replit or GitHub Codespaces, but to accurately target Google technology stack developers. Replit emphasizes zero-configuration quick startup and multi-person collaboration, Codespaces emphasizes deep binding to the GitHub ecosystem and enterprise-level containerization configuration, while the core difference of Google IDX lies in the end-to-end experience of the trinity of Flutter + Firebase + Gemini. From project creation to coding, preview, debugging, and deployment are all completed in the browser, without the need to install Flutter SDK, Firebase CLI or Android Studio locally. For projects outside of the Google technology stack, this deep integration becomes a bundled cost.

User and market recognition

Google IDX is still in the public preview stage, and officials have not announced the number of active users, number of enterprise customers, or revenue data. The following dimensions can help determine its current market position:

Community Attention: Google IDX was first released under the name Project IDX at Google I/O in 2023, attracting widespread attention from the Flutter and Firebase communities. It will be officially renamed Google IDX in 2024 and open to public preview. As of now, discussions on GitHub and social media are mainly concentrated within the Flutter community, and have not yet formed a cross-language and cross-framework voice like Replit or Codespaces.

Developer Awareness: According to discussions in third-party technology communities (such as Stack Overflow, Reddit), Google IDX has higher awareness among Flutter developers, but it is still a niche tool among general front-end or back-end developers. The main reason is that developers outside the Google ecosystem cannot get the same depth of integration experience in IDX.

Enterprise adoption signal: Google itself has begun to embed IDX as a recommended development method in the official documentation of Flutter and Firebase. For example, Flutter's "Get Started" page provides a one-click entry to "Open in IDX". This implies that Google is positioning IDX as a first-level context for Flutter development, but enterprise-level customer cases have not yet been made public.

Market structure: There are many competitors in the cloud IDE track-GitHub Codespaces (Microsoft), Replit, GitPod, StackBlitz, CodeSandbox. Google IDX's differentiation lies in Google Cloud integration and Flutter-first strategy, but this also means that its core audience is naturally limited to the Google ecosystem. For teams not using Firebase or Flutter, the value proposition of IDX needs to be cut across the higher migration costs.

Cost advantage

Google IDX's current cost structure is extremely simple - it's completely free during public preview, but a post-launch pricing model has yet to be announced. The following is a cost analysis from three perspectives:

C client/individual developer: Free to use, no need to bind a credit card. The free quota during the current preview period includes: a certain amount of storage space (the exact value is not officially disclosed, but it is enough to support single to multiple medium-sized projects), and calculation time (the workspace automatically sleeps after being idle for a period of time to save quota). Individual developers can use IDX as their main development tool at zero cost, but they must accept the stability and resource limitations of the preview period. Hidden Cost: Project data is stored in Google Cloud. If the pricing model changes after the preview period, additional time costs will be required to migrate to local or other cloud IDEs.

API/Developer Cost: Google IDX does not provide a standalone AI API - its AI capabilities (code completion, generation, conversational debugging) are embedded in the editor, driven by the Gemini model, and are not billed separately. This means that during the preview period, the cost of using AI features is zero. After the official release, there is currently no public information on whether the AI ​​call volume will be included in the subscription level or billed independently. For developers who need to use Gemini API for other scenarios, Gemini API can be used directly through https://ai.google.dev/, and its pricing has nothing to do with IDX.

Enterprise/Team Cost: Enterprise pricing is completely undisclosed. It is expected that a paid model based on Cloud Workstations will be introduced after the official release (because the underlying computing resources of IDX come from Cloud Workstations), which may include a combined structure of "basic IDE subscription + AI function addition + storage excess". In addition, resource fees for Firebase and Google Cloud (such as the running fee after Cloud Run deployment and the Firebase service usage fee) need to be paid separately and are not included in the IDX subscription. Hidden costs: The binding of IDX's Nix bounded configuration and Google services means that the team needs to have corresponding technical capabilities; if the existing technology stack is not within the Google ecosystem, the learning costs and process modification costs involved in migrating to IDX may far exceed the IDE subscription fee itself.

Main functions

The functional design of Google IDX revolves around the three main lines of "in-browser full-stack development + Google ecosystem deep integration + AI assistance". The core capabilities can be broken down into the following six items:

• Full-featured IDE in the browser: Based on the Code OSS kernel, it supports a complete VS Code experience - terminal, debugger Git integration, and expanded market. Workspace persistent storage supports pause and resume. The key difference from ordinary VS Code is that running Youjing is completely hosted in the cloud and requires only a browser locally. Synergy: Traditional VS Code requires local installation of SDKs, simulators and extensions, while IDX completely abstracts this layer to the cloud - meaning that you can also develop Flutter mobile applications with a Chromebook or iPad, which was not possible before.

• AI code completion and generation (Gemini driver): Provides inline code completion, function-level generation, and code conversion suggestions in the editor. Based on Google's code-specific model (the same origin as Gemini Code Assist), the completion quality for Dart/Flutter is significantly better than the general model. Expert View: The core value of AI completion is not to "write more code", but to reduce context switching - developers do not need to leave the editor to search for API usage or boilerplate code. For Flutter developers, the automatic completion of Widget nested structures can significantly improve UI coding efficiency, and is expected to reduce manual input of boilerplate code by 30%-50%.

• AI conversation debugging (Gemini in IDX): Talk to AI in the IDE side panel. AI can read the contents of the currently opened file, terminal output and error stack, and assist in troubleshooting compilation errors, runtime exceptions and configuration issues. The difference from using the Gemini web version independently is that AI can directly access the project context and build logs, and the suggestions given are more actionable. Synergy: The triangular linkage of AI debugging + terminal + editor shortens the path of troubleshooting from "copy error → paste to search engine → return to editor to modify" to "dialogue within IDE → directly apply suggestions".

• Flutter/Firebase Deep Integration: You can select Flutter templates when creating a new project and have a built-in Firebase simulator suite (Auth, Firestore, Storage, Functions). There is no need to install Firebase CLI or configure a local simulator. After the project is created, you can preview the running effects of Android, iOS and Web platforms in the browser. Synergy: Traditional Flutter development requires local configuration of Flutter SDK + Android Studio/Xcode + Firebase CLI + emulator, and the total installation step takes about 30-60 minutes (depending on the network and context). IDX compresses it into three steps: "Open browser → select template → start coding", and the preparation time is close to zero.

• Cross-platform inline preview: Supports web preview (real-time refresh), Android emulator (in-browser), iOS emulator (in-browser, requires Mac backend). The interaction between the preview and the editor is two-way - clicking on a UI element in the simulator can directly navigate to the corresponding code. Implementation Tips: The startup speed of the Android emulator depends on the resource allocation of the Google Cloud backend, and the first load may take 30-60 seconds; the iOS emulator is only available on Google's Mac backend, and the queue resources are limited, making it not a daily high-speed development tool.

• Nix context management and templating: The system-level context (SDK version, system package, extension configuration) of each workspace is managed through Nix, and the configuration is stored in the project-level nixpacks file. This means team members can share exactly the same context configuration, avoiding the classic "it works on my machine" problem. The SDK and tool chain of mainstream frameworks are preset, and advanced users can customize the environment by modifying the Nix configuration. Synergy: The combination of Nix Contextual Configuration + Firebase Simulator + Deployment Integration means that the entire chain from "create project" to "run online" is within the same context, without the need for local-cloud context alignment steps beyond CI/CD scripts.

Google IDX model and version evolution

The version evolution of Google IDX is highly related to the timeline of the Google I/O conference. The key nodes that can be verified currently are as follows:

Public preview stage (2023-08 to present)

• Project IDX Preview (2023-08): First announced at Google I/O 2023, open in limited preview (waitlist mode) under the codename Project IDX. Initially supports Flutter, Next.js, Angular, React, Svelte and other frameworks, and integrates Gemini AI code completion.
• Google IDX Public Preview (2024-06): Announced the name change to Google IDX at Google I/O 2024, canceled the waitlist, and opened public preview to all users (requires Google account login). Added iOS simulator support (Mac backend), Nix contextual custom Chrome DevTools integration.
• 2025 iteration (2025-01 to 2025-12): Continuous enhancement of AI functions - Gemini dialogue debugging is launched, AI code generation supports natural language description creation of functions and components, Flutter template library extension, Firebase simulator upgrade supports Genkit. New deployment targets are Cloud Run and Cloud Functions.
• 2026.06 version (~2026-06): Enhanced AI code completion integration with Google Cloud services. For specific changes, please refer to the official release notes.

Time nodes	Events	Key changes
2023-08	Project IDX limited preview	Based on Code OSS, integrated with Gemini AI, supporting Flutter/Next.js/Angular/React/Svelte
2024-06	Renamed Google IDX, public preview	Cancel waitlist, add iOS simulator Nix contextual custom Chrome DevTools
During 2025	Continuous feature enhancement	AI conversation debugging Firebase emulator upgrade Genkit integration Cloud Run deployment
~2026-06	2026.06 version update	AI code completion enhances Google Cloud service integration and deepens

Version Note: As a cloud service, Google IDX adopts a continuous delivery model and does not have the concept of "version number" in the traditional sense. The official does not provide downloading and installation packages, and all updates are pushed in grayscale on the server. The above timeline corresponds to public milestone events, and the specific function launch date is subject to the official release channel.

Technical advantages

The technical advantage of Google IDX does not lie in the leadership of a single indicator, but in the collaboration of two dimensions: "full-link cloudification from coding to deployment" and "deep coupling of the Google ecosystem".

Cloud Computing Architecture: IDX's workspace runs on Google Cloud Workstations, and each workspace is an independent containerized environment. Container lifecycle management (creation, hibernation, recovery, destruction) is automatically handled by Google Cloud, and users do not need to care about the underlying infrastructure. The workspace automatically hibernates to save resources after being idle for a period of time, and reloads from the saved disk snapshot when resumed. Encoding status can usually be restored within 10-30 seconds. Mechanism → Effect: Containerized isolation ensures that the dependencies and configuration of one workspace will not affect other workspaces, making it suitable for maintaining multiple projects at the same time; however, the hibernation-resume mechanism also means that cold start delays cannot be completely eliminated. For developers who are accustomed to opening the editor at any time to work immediately, this 10-30 second waiting time is a change of pace that needs to be adapted to.

Embedding method of Gemini AI engine: The AI ​​capabilities in IDX are not simply "embedding a chat interface in the side panel", but directly implanting AI into the core interaction path of the editor. The specific performance is as follows: completion suggestions are automatically triggered when the cursor stays; right-clicking after selecting the code can directly ask AI to interpret, reconstruct or generate tests; when compiling errors, AI automatically analyzes the terminal output and pops up repair suggestions at the error location. The key advantage of this inline approach is "contextual auto-passing" - the AI ​​does not require the user to manually paste code or describe the problem, it already knows the currently open file, recent edit history and terminal output. Effect: The "explanation context" section in AI dialogue is reduced, making AI assistance closer to a "second pair of hands" rather than a "search engine".

Reproducibility of Nix contextual declarations: IDX uses Nix as a contextual management tool, and the SDK version, system package, and extended configuration are all defined through declarative configuration. This means that a nixpacks file can accurately reproduce the development context, and there is no "context drift" problem between team members. The difference compared to Docker containers is that Nix is ​​more granular and can replace only a single tool chain version without rebuilding the entire container image. Applicable scenarios: For Flutter projects that require precise control of dependency versions (such as breaking changes between Flutter 3.16 and 3.22), Nix can ensure that all developers use the exact same SDK version.

Firebase emulator full stack built-in: IDX pre-integrates the Firebase native emulator suite in the workspace, including Authentication, Cloud Firestore, Cloud Storage, Cloud Functions, Extensions, and more. Developers can complete full-featured development and debugging offline (or, more accurately, without consuming Firebase production bounded quota). Mechanism → Effect: After the simulator is started, the Flutter application can directly connect to the endpoint of the local simulator. All read and write operations occur in memory, and the data is automatically cleared after closing the workspace. This makes the context state clean every time the project is started, reducing the problem of "residual data from the last test affecting this round of testing".

How to use

The usage path of Google IDX is based on the core design concept of "just use the browser", and all operations are completed at https://idx.dev/.

Quick Start (Zero Configuration Path):

1. Visit https://idx.dev/ and log in with your Google account.
2. Click "Create a new workspace" and select a framework (Flutter, Next.js, Angular, React, Go, Python, etc.) from the template list.
3. Wait for 10-30 seconds for the workspace initialization to complete and automatically enter the editor of the VS Code interface.
4. Start coding - AI completion is automatically triggered when typing, and the terminal has pre-installed CLI tools for the corresponding framework.
5. Press Cmd/Ctrl+Enter to talk to Gemini for debugging in the side panel.

Import existing project:

1. Click "Import from GitHub" or git clone directly in the workspace terminal.
2. If the project uses a package manager such as npm/pip/go mod, just run the installation command in the terminal.
3. For projects without preset frameworks, you can customize the bounded configuration by modifying the .idx/dev.nix file.

Deployment path:

• Flutter Web projects can be deployed directly to Firebase Hosting (one-click operation within the workspace).
• Backend projects (Node.js, Python, Go) can be deployed to Cloud Run.
• Cloud functions can be deployed directly to Cloud Functions.
• Deployment configuration is integrated into the IDE interface, eliminating the need to switch to the Google Cloud Console.

How to use	Suitable scenarios	Prerequisites	Features
Web IDE (idx.dev)	Quickly start new project Flutter development	Google account	Zero installation, AI embedded, Firebase simulator preset
GitHub import	Migrate existing projects to the cloud	GitHub account authorization	Keep Git history, automatically detect frameworks
Nix custom context	Non-preset framework, special dependency requirements	Understand Nix syntax	Contextual configuration can be versioned and managed, team sharing
Deploy to Cloud Run/Hosting	Project online or preview	Google Cloud project	Deploy directly within the IDE without switching consoles

AI function usage strategy:

• Code Completion: No need to trigger it explicitly, just type normally in the editor. It is recommended to take full advantage when writing highly repetitive code (Widget template JSON serialization API call scaffolding).
• AI Dialogue: Click the Gemini icon on the side panel to open the dialogue panel. You can directly select the code and press Cmd+I to send it to AI. It is recommended to use it when troubleshooting compilation errors, understanding unfamiliar API usage, or when you need to generate test code.
• Code Conversion: After selecting the code, right-click and select "Refactor with AI" or "Generate with AI", and enter a natural language description to perform code conversion. Suitable for batch modification of variable naming, extraction of functions, generation of type definitions and other operations.

Product Pricing

Google IDX is currently in public preview and all features are free to use. Here are the known pricing boundaries and future expectations:

Current free quota: During the public preview period, there is no charge to use Google IDX, and no credit card is required. Free quota includes:

• Workspace storage space (each workspace has an independent persistent disk, the limit is not disclosed)
• Computing duration (when the workspace is active, it consumes cloud CPU/GPU resources and automatically sleeps when idle)
• AI functions (Gemini code completion and dialogue)
• Android/iOS emulator (limited quota)
• Firebase Emulator Suite

Known limitations:

• The number of workspaces per account is limited (the specific limit is not disclosed)
• The resource allocation of the simulator (especially iOS) is limited by the queue, and you may need to wait during peak periods
• After hibernating a workspace, there may be a 10-30 second cold start delay in resuming
• No support for working offline - must stay connected to the internet

Pricing expectations after official launch: Google has not announced the official launch pricing model. Based on the existing pricing of Cloud Workstations (baseline starting at approximately $0.04/hour), and the regular pricing model of Google Cloud services, it is reasonable to speculate that the official version may adopt one of the following structures:

• Free Tier: Basic IDE + Limited AI calls + Limited storage space
• Subscription: Monthly payment includes more workspace quotas, AI calls and priority resource allocation
• Enterprise Customization: Includes enterprise functions such as custom domain name SSO, audit log VPC isolation, etc.

Terms to pay attention to: Migration/retention policy for projects and data created during the preview period after the official release; whether the code generated by the AI function involves data usage terms; downgrade path for free users after the preview period. The above terms are subject to the official announcement when officially released.

Summary of three-tier cost structure:

Cost layer	Preview period	After general release (expected)	Core variables
C-side/Personal	Completely free	May be free tier + subscription upgrade	AI call volume, storage space, number of workspaces
Developer/API	No billing for built-in AI	May be included in subscription or billed based on AI calls	Is there any additional charge for Gemini API use
Enterprise/Team	No enterprise plan	Expected to introduce Cloud Workstations billing + enterprise additional features	Data residency SSO, audit SLA

Application scenarios

The applicable scenarios of Google IDX are determined by its "Google Ecosystem First" product gene. The following four scenarios have verified its value:

• Flutter cross-platform application development: This is the core applicable scenario of IDX. From creating a Flutter project, previewing Android/iOS/Web tri-end effects in the browser, integrating Firebase backend services, and finally deploying to the app store - everything is covered within IDX. Implementation Tips: The experience of the Flutter project in IDX is close to local development, but the availability of the iOS simulator relies on Mac back-end resources, and queues may occur during peak hours. It is recommended to use iOS preview for final UI verification, and daily development to focus on Android and Web preview.

• Firebase + front-end full-stack project: For Next.js/Angular/React projects that use Firebase as the backend, IDX provides full-link support for built-in Firebase simulator, pre-configuration of contextual variables, and one-click deployment to Firebase Hosting. Quantitative comparison: It takes about 20-40 minutes to build a local context of Firebase + Next.js in the traditional way (installing Node.js, configuring Firebase CLI, initializing the project, starting the simulator). In IDX, you only need to select the template → wait for initialization (about 10-30 seconds) → start coding.

• Google Cloud Microservice Development and Debugging: IDX workspace can be associated with Google Cloud projects and supports the deployment and debugging of Cloud Run and Cloud Functions. Suitable for teams that need to develop microservices in the Cloud context but don't want to run Docker and Cloud SDK locally. Implementation Tips: IDX is more suitable for development and debugging at the current stage. The production-level CI/CD pipeline still needs to be configured in Cloud Build or GitHub Actions.

• Programming Teaching and Code Labs: The zero-local configuration feature makes IDX an ideal choice for programming education scenarios. Students can get a consistent development environment by opening the browser, and teachers do not need to deal with issues such as "operating system differences" and "SDK version inconsistencies". Google has officially embedded the "Open in IDX" button in Flutter's Code Labs and Codelabs pages. Not suitable for boundaries: IDX currently only supports online use and is not suitable for teaching environments with limited networks (such as intranet classrooms). For environments with poor network conditions, the experience of loading IDEs and emulators may not be as smooth as the local environment.

Applicable people

Google IDX is positioned through the combination of "cloud IDE + Google ecological integration" and targets the following four types of people:

• Flutter Developers: This is the core target user. IDX provides a full-link Flutter development experience from project creation to deployment and launch, without the need to install Flutter SDK, Android Studio, Xcode or Firebase CLI locally. Implementation Tips: It is recommended to use IDX as the main context or alternative context for Flutter development. If you have a well-configured local Flutter development environment, the value of IDX lies in rapid prototype verification and cross-platform preview. Not suitable for boundaries: If the project relies on native plug-ins (Platform Channel, custom Kotlin/Swift code), IDX's Native code editing and debugging capabilities are limited to the cloud environment and are not as comprehensive as local Xcode/Android Studio.

• Google Cloud/Firebase Users: Technical teams and individual developers who are already using Firebase or Google Cloud services. IDX can simplify the process from development to deployment, and the built-in Firebase simulator allows back-end logic to be tested locally (in the cloud workspace) before being pushed to the production environment. Implementation Tips: The IDX workspace can be bound to the Google Cloud project, and the deployment credentials automatically inherit the permissions of the login account, eliminating the need to manually configure the service account key.

• Programming education and training scenario: Technical lecturers, participants of Code Labs, a training institution. IDX eliminates "contextual configuration", the biggest friction point in teaching, and students can follow the tutorial operations in a unified context. Prerequisites: Students need to have a Google account and a stable Internet connection. Not suitable for offline teaching or restricted network environments.

• Cross-Device/Light-Device Developers: Developers using Chromebooks, iPads, or other devices that cannot run a full desktop IDE. IDX gives these devices the ability to develop Flutter and web applications. Not suitable for boundaries: For scenarios that require professional debugging tools (such as performance analysis, memory analysis, network packet capture), IDX's built-in DevTools capabilities are weaker than Chrome DevTools independent window or Android Studio Profiler.

Selection comparison: IDX vs other cloud IDEs

Dimensions	Google IDX	GitHub Codespaces	Replit
Core advantages	Deep integration with Google ecosystem	GitHub + VS Code original experience	Zero-configuration quick startup and collaboration
Best Scenarios	Flutter/Firebase Projects	Any GitHub Repository	Rapid Prototyping, Teaching, Team Collaboration
AI capabilities	Gemini built-in (code completion + conversation)	GitHub Copilot integration	Replit AI (built-in)
Free strategy	Completely free during preview	Limited free time per month	Free tier has limits
Contextual customization	Nix declarative configuration	Docker container + devcontainer.json	Limited (mainly preset templates)
Enterprise Readiness	In preview, no Enterprise plan	GA, with Enterprise subscription	With Teams/Enterprise plan
Platform Coverage	Web and Web Only	Web + VS Code/JetBrains Local Connection	Web + Mobile App

Summary and Outlook

Google IDX has established a unique value positioning among the Flutter and Firebase developer groups through the trinity design of "Cloud IDE + Gemini AI + Google Ecosystem". Its core capabilities—zero-configuration Flutter development context, embedded AI assistance, and in-browser cross-platform preview—have irreplaceable advantages in specific scenarios, especially in lowering the threshold for context configuration and simplifying the development-deployment link.

Current Core Advantages:

• Flutter/Firebase is full-link cloud-based, and the bounded configuration time is close to zero.
• AI capabilities are built into the editor interaction path and can be used without switching tools.
• Free during preview, suitable for individuals and small teams to adopt at zero cost.
• Nix contextual declarative management solves the problem of contextual consistency in team collaboration.

Main Current Limitations:

• Still in public preview, stability and availability are not guaranteed by SLA.
• The officially released pricing model is unknown, and currently adopted projects and data may face cost changes after the pricing switch.
• The core audience is limited to the Google ecosystem, and the value proposition of non-Google technology stack teams is weaker.
• The iOS simulator has limited resources and is not available during peak hours; offline scenarios are not supported at all.
• Enterprise-level features (SSO, audit log VPC isolation, custom domain names) have not yet been launched.

Follow-up observation points:

• Official launch timeline and pricing model - this directly affects the adoption decisions of all existing users.
• Whether to extend deep support for non-Google frameworks (such as .NET, AWS SDK integration).
• Whether AI features will be billed independently after official release, and how the quality of AI code generation continues to improve.
• Google Cloud's billing relationship with IDX - whether the IDX subscription includes Cloud resource consumption or is billed independently.

Procurement and Adoption Risk Assessment: For Flutter/Firebase developers, there is no real risk in using it for free during the preview period, and it is worthy of being one of the daily development tools. It is recommended to fully verify whether IDX's workflow matches the team's habits during the preview period, focusing on: whether the AI ​​completion quality significantly improves coding efficiency, whether Nix contextual management adapts to the team's working style, and whether the cross-platform preview meets the testing needs. For enterprise teams, it is not recommended to use IDX as the only development tool for the core production environment until official release and pricing is announced - on-premises environments or other cloud IDEs should be kept as alternatives. Before purchasing, it is important to confirm: the difference between the officially released pricing structure and the current free tier, the storage location and data residency policy of data in Google Cloud, whether the use of AI functions involves code data training terms, and the service availability SLA of Google IDX. For teams that are deeply bound to the Google ecosystem, IDX has long-term value after it becomes a formal product. However, at this stage, it should be positioned as an "exploratory tool" rather than a "core dependency".

Related tools: GitHub Copilot, Cursor

Version Info

• Google IDX 2026.06 ：There is no official precise date yet. Enhanced AI code completion integration with Google Cloud services. （~2026-06）
• Google IDX 2025.08 ：There is no official precise date yet. Officially publicly accessible, introducing AI-assisted features. （~2025-08）