Cant connect with my Gemini account

[MatQV]

Hi, just testing the app, it worked perfectly when adding my ChatGPT account, but with google I just get a "Authentication successful!
You can close this window." but nothing happens inside VibeProxy, am I doing something wrong?

Thanks!

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• Error: 400 unknown provider for model gemini-2.5-pro #42

Related Issues

• Add account error #99
• How do I use Gemini in Factory CLI? #16

👤 Suggested Assignees

• appscaptain
• kts-kris
• Whiteknight07

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[MatQV]

Any ideas how to fix it?

[ranaroussi]

This issue appears to be related to Gemini authentication. A few things to check:

1. Verify auth file was created:

ls -la ~/.cli-proxy-api/*.json
cat ~/.cli-proxy-api/*.json | grep -i gemini

2. Check VibeProxy logs:
Go to Help > Show Logs in VibeProxy and look for any errors during the Gemini auth process.

3. Multi-project issue:
If you have multiple Google Cloud projects, the auth may be writing to an unexpected project. Try:

• Set your desired project as default in Google AI Studio before connecting
• Or authenticate with Antigravity instead (which wraps Gemini)

4. Try re-authenticating:

# Remove any existing Gemini auth files
rm ~/.cli-proxy-api/*gemini*.json 2>/dev/null
rm ~/.cli-proxy-api/*google*.json 2>/dev/null

# Restart VibeProxy and try again

Could you share:

1. Contents of ~/.cli-proxy-api/ directory after auth attempt
2. VibeProxy version number
3. Any relevant logs from VibeProxy

This will help us diagnose whether the auth file is being created but not parsed correctly.

[Muzych]

same issues here, and my vibeproxy version is v1.8.39. and nothing exists under the ~/.cli-proxy-api/. this seems like I trying to create oauth token many times in a short term and it triggers googles risk control?

[ranaroussi]

Friendly reminder: This issue will be closed in 7 days if we don't receive the requested information. Please provide the details above so we can help resolve your issue.