Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug]: Antigravity API key instance shows Google "Sign in" wording, and the user does not know that a click is necessary to load models

Open Beginner friendly
#25,885 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
backend, desktop

Research direction

Start with AntigravityProvider.ts and inspect AUTH_UNCHECKED_MESSAGE, antigravityAuthLabel(), and the provider card’s sign-in button wording. Trace how the selected auth method controls the unchecked status and button action. Done when an API-key instance explains that connecting starts the runtime and loads models, while Google account instances retain appropriate wording; verify both flows in the provider settings.

Written by the indexing model from the issue text.

Description

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/web

Steps to reproduce
  1. Settings > Providers > Add provider > Antigravity.
  2. Set Sign-in method to gemini-api-key and enter a valid Gemini API key. The field then shows "Stored secret, enter a new value to replace".
  3. Look at the provider card and the model picker.
Expected behavior

The card uses words that match the API key method. For example: status "Installed · Not connected yet", and a button labelled Connect or Verify API key that starts the runtime with the stored key and loads the model list.

Actual behavior

The card shows Google account wording for an API key instance:

  • Status: Needs attention · Antigravity is installed. Google account access is not checked yet.
  • Account section: "Sign in on " with a Sign in button.
  • Models: "0 models. No models reported for this provider yet." Thus the instance does not appear in the model picker and the user cannot start a thread with it.

With an API key already stored, "Sign in" reads like a Google OAuth step that is not necessary. I thought the key was not used, and I did not click it. In fact, for gemini-api-key this button only starts the runtime with GEMINI_API_KEY and then loads the models. Nothing on the card says that this click is necessary to use the instance.

In the bundled server, AUTH_UNCHECKED_MESSAGE in AntigravityProvider.ts is the same for all auth methods, and the status changes to authenticated only after a runtime session starts. antigravityAuthLabel() already knows the method ("Gemini API key"), so the unchecked message and the button label can use the method too.

Related: #12751 (the "Needs attention" styling for an unchecked Google account, partly fixed in #18623).

Impact

Minor bug or occasional failure

Version or commit

0.1.0

Environment

macOS 15.2 (Darwin 24.2.0) arm64, T3 Code desktop with local server, Antigravity runtime v1.3.0

Logs or stack traces
No error is logged. The health check succeeds (checkAntigravityProvider: Success),
but the status stays "not checked yet" until a session starts.
Workaround

Click Sign in on each API key instance. For gemini-api-key it connects without a browser, and then the status is "Authenticated · Gemini API key" and the models show.

Dominant language
TypeScript
Stars
24.8k
Forks
6.4k
Avg merge
2h 54m
Merged PRs (30d)
350

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pingdotgg/t3code

All issues in pingdotgg/t3code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.