Grok provider check can open browser login without user action

[andrewxwrz]

T3 Code can open a Grok/xAI browser login window during a background provider check.

What happened:

• I had Grok CLI installed, but I was not using it.
• T3 Code checked the Grok provider in the background.
• Because Grok had no saved auth token, the provider check started the Grok ACP runtime.
• The Grok CLI then opened Chromium to an xAI login page.
• The app later reported: Grok CLI is installed but ACP startup timed out after 15000ms.

This was surprising because no chat was started with Grok and I did not click a Grok sign-in button. From a user's point of view, an unrelated browser window appeared on its own.

Expected behavior:

• Background provider checks should not start an interactive browser auth flow.
• If Grok is installed but not authenticated, T3 Code should show a clear unauthenticated status and tell the user to run grok login.
• T3 Code should only start Grok's interactive auth flow after direct user action.

A local trace showed the browser URL was an xAI OAuth page with referrer=grok-build and a loopback callback. The Grok logs showed there was no ~/.grok/auth.json, then auth started with a browser-based flow.