无法连接

[lpx0007]

Pre-submission checklist

• I have searched existing issues for duplicates
• I have read the 📋 Troubleshooting Guide
• I have read the README installation instructions

Model used

antigravity-gemini-3-pro

Exact error message

●  Authentication failed: Unable to connect. Is the computer able to access the url?
│
■  Failed to authorize

Bug description

弹出连接后，提示认证成功，但是命令行却提示失败

Steps to reproduce

正常操作，一直无法验证成功

Did this ever work?

First time setup (never worked)

Number of Google accounts configured

1

Reproducibility

Always (100%)

Plugin version

最新

OpenCode version

1.1.25

Operating System

win 11

Node.js version

最新

Environment type

Standard (native terminal)

Debug logs (REQUIRED)

找不到日志文件

Configuration (optional)

Compliance

• I'm using this plugin for personal development only
• This issue is not related to commercial use or TOS violations

Additional context

No response

[randolph555]

代理起开TUN 模式在试下 ，我已经解决了

[lpx0007]

代理起开TUN 模式在试下 ，我已经解决了

还得是强大的网友啊，成功了！感谢

[JsonGuo-coder]

相同问题。请问一下具体操作，尝试使用TUN模式也失败了 ( ´•︵•` )

[lpx0007]

相同问题。请问一下具体操作，尝试使用TUN模式也失败了 ( ´•︵•` )

就是开tun+全局 还是失败的话检查下ip纯净度

[github-actions]

👋 Thanks for opening this issue!

感谢您报告此问题。这种“浏览器认证成功，但命令行提示失败”的问题确实比较常见，尤其是在 Windows 环境下。

这通常是因为命令行工具启动了一个本地服务来等待来自浏览器的授权确认，但由于某些原因（例如防火墙、端口冲突或浏览器安全设置），这个确认信息没能成功传回到命令行工具。

为了定位问题，调试日志是必不可少的。您提到找不到日志文件，请在复现问题后，检查一下 C:\Users\<你的用户名>\.opencode\opencode.log 这个路径下是否有日志文件？或者，请再次查看我们的 📋 Troubleshooting Guide 中关于如何启用和定位调试日志的部分。请将日志内容粘贴到这里。

这个问题也可能与 OpenCode v1.1.25 的已知依赖冲突有关 (参考 #223)，日志文件可以帮助我们确认这一点。

拿到日志后，我们就能更好地帮助您解决问题。

---

This is an automated response. A maintainer will review your issue soon.

[github-actions]

👋 Thanks for opening this issue!

Based on your report, it appears that while the browser-based OAuth flow completes successfully, the local authentication server is unable to receive the callback or verify the connection to the Antigravity API. This is often caused by a local firewall or proxy blocking the loopback connection (usually on port 3000 or 8080) or a network restriction preventing the CLI from reaching generativelanguage.googleapis.com.

To resolve this, please try the following:

1. Check Proxy Settings: If you are using a VPN or proxy, ensure that your terminal environment has HTTP_PROXY and HTTPS_PROXY set correctly, or try disabling them during the login process.
2. Firewall: Ensure that your Windows 11 firewall is not blocking the OpenCode process from listening on local ports.
3. Manual Token Entry: If the automatic redirect fails, check if there is a 'manual' mode or try running gemini auth login --no-browser if available in your environment to copy-paste the code.
4. Verify OpenCode Version: You are on version 1.1.25. There is a known dependency conflict with zod in this version (see issue Dependency Conflict: Plugin incompatible with OpenCode v1.1.25 due to zod version mismatch #223) that can sometimes break validation logic during auth. Try updating the plugin or checking if a patch is available for your OpenCode installation.

---

This is an automated response. A maintainer will review your issue soon.

[zjh02249]

相同的问题。请问一下具体操作，尝试使用TUN模式也失败了(´•︵•` )

服务模式 开起来。我就是服务模式开启后就可以了

[github-actions]

👋 Thanks for opening this issue!

The error text comes from the OAuth login flow when the local loopback callback cannot be reached. On Windows this is commonly caused by a firewall/proxy/VPN blocking localhost redirects or the Google OAuth endpoints, so the browser reports success but the CLI cannot complete the callback. The plugin also stores auth and logs under %APPDATA% (not ~/.config), so “log file not found” on Windows usually indicates it is looking in the wrong place. Suggested fixes: ensure your terminal can reach https://accounts.google.com and https://generativelanguage.googleapis.com, allow localhost callbacks through the firewall, temporarily disable proxy/VPN, then delete the existing auth cache under %APPDATA%\opencode-antigravity-auth and re-run the login flow. If you are following the README for paths, use %APPDATA% on Windows.

---

This is an automated response. A maintainer will review your issue soon.