# Antigravity desktop: use your Google Cloud project

URL: https://research-memex.org/docs/implementation/agentic-ai-tools/antigravity-google-cloud-setup
Description: Connect Antigravity Desktop through Google Cloud browser sign-in and use your project's billing account.



*Use your Cloud project to work with Google's desktop assistant.*

Use this route to connect Antigravity Desktop to an existing Google Cloud project through browser sign-in. It is separate from personal subscriptions, the standalone Antigravity IDE and the [Antigravity CLI](/docs/implementation/agentic-ai-tools/antigravity-cli-setup-guide).

Install the desktop app from [Google's Antigravity download page](https://antigravity.google/download), then [check your Cloud project](/docs/implementation/ai-environment-setup/vertex-ai-setup#check-your-project). For class-project funding options, see [AI credits for teaching](/docs/implementation/ai-environment-setup/course-ai-funding).

The steps below combine Google's documented Cloud route with our October 4, 2026 staff pilot using Antigravity 2.19.1.

## Sign in through Google Cloud [#sign-in-through-google-cloud]

1. In the desktop app, choose the business-account sign-in route, then Continue with Google Cloud.
2. Complete browser sign-in with the identity authorized for your intended project.
3. Select the Cloud project route for consumption-based billing. The pilot labeled this Pay as you go, separately from a Gemini Enterprise license.
4. Enter your project ID when prompted. Copy the ID from Cloud Console, not the project's display name.
5. Choose a supported location that meets your institutional requirements. The pilot used `global`; your requirements may differ.

[Google's enterprise documentation](https://antigravity.google/docs/enterprise/) covers license selection and other authentication methods. The sign-in screen also explains the route's terms and logging.

## Check the connected account [#check-the-connected-account]

Open the account settings and inspect the signed-in identity, project ID and selected plan before sending a request. In the pilot, the connected account panel labeled the plan Agent Platform.

If the project or identity is wrong, sign out and repeat the Cloud selection. If access is denied, ask the project administrator to check your identity and permissions. Do not create a service-account private key as a shortcut for this browser sign-in route.

Pay as you go identifies how consumption is billed. It does not prove that education credits will cover a request.

## Check one request and reopen it [#check-one-request-and-reopen-it]

Send a short message to an available Gemini model without project files or tools. Check the response, then reopen the conversation from history. If that works, the basic connection is ready; test the features your project needs next.

Our pilot checked a short Gemini response and history reopening. It did not test student onboarding, credit offsets or project-building features.

## Find the step that failed [#find-the-step-that-failed]

| Symptom                                             | Next check                                                                                                                                                   |
| --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| You cannot find the Cloud sign-in route             | Confirm you are using the desktop app, then compare its version and sign-in screen with Google's documentation                                               |
| The wrong account or project appears                | Sign out and select the intended Cloud identity and project                                                                                                  |
| The project is missing or a request is denied       | Return to the [project checks](/docs/implementation/ai-environment-setup/vertex-ai-setup#check-your-project); do not broaden permissions as a first response |
| A conversation works but credit coverage is unclear | Inspect the project's billing records and award terms; do not infer coverage from the app's plan label                                                       |

## Keep assistant access separate from application access [#keep-assistant-access-separate-from-application-access]

Signing into the assistant does not give an application you build its own model access. Configure that application's credentials and billing separately. Keep credentials out of browser code and shared project files.

For a different desktop client, return to [Choose a client](/docs/implementation/ai-environment-setup/vertex-ai-setup#choose-a-client). For terminal work, follow the separate [Antigravity CLI guide](/docs/implementation/agentic-ai-tools/antigravity-cli-setup-guide).