Conversation
Treat a healthy Antigravity install with unchecked Google auth as informational in Settings (Installed · Sign-in required) instead of amber Needs attention. Keep the server health probe as warning so readiness semantics stay unchanged. Add a Sign in with Google action on the Antigravity settings card that starts the existing OAuth flow. Co-authored-by: maco <macodev00@users.noreply.github.com>
Co-authored-by: maco <macodev00@users.noreply.github.com>
| onStarted?.(); | ||
| pendingRef.current = true; | ||
| setPending(true); | ||
| void startAuth(target).finally(() => { |
There was a problem hiding this comment.
🟡 Medium settings/ProviderSetupSection.tsx:136
When startAuth(target) returns a setup failure, this handler discards the AtomCommandResult, so the button simply becomes enabled again without showing an error. Because both failure reporters are disabled, stale-provider cases such as a removed instance fail silently; remove those reporter overrides or explicitly surface the command failure.
🤖 Copy this AI Prompt to have your agent fix this:
In file @apps/web/src/components/settings/ProviderSetupSection.tsx around line 136:
When `startAuth(target)` returns a setup failure, this handler discards the `AtomCommandResult`, so the button simply becomes enabled again without showing an error. Because both failure reporters are disabled, stale-provider cases such as a removed instance fail silently; remove those reporter overrides or explicitly surface the command failure.
ApprovabilityVerdict: Not approved Macroscope's review found this PR not approvable — This PR adds a new Google OAuth entry point and changes authentication-related provider status behavior in production settings. The new action also suppresses setup failures, so stale-provider errors may be invisible to users until the failure handling is addressed. Not approved because:
Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more. |
|
Understand this PR’s impact Explore downstream dependencies and potential security impact with Blast Radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: pingdotgg/t3code/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (7)
Included review availability: Your plan provides up to 10 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughAntigravity providers with unchecked Google authentication now show “Installed · Sign-in required” instead of “Needs attention”. Eligible provider cards display a “Sign in with Google” action that starts the existing OAuth flow in list, editor, and setup views. ChangesAntigravity sign-in experience
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~25 minutes Change: Bug fix · Severity of issue fixed: Low Sequence Diagram(s)sequenceDiagram
participant ProviderSettingsPanel
participant ProviderInstanceCard
participant AntigravityGoogleSignInButton
participant startProviderAuth
ProviderSettingsPanel->>AntigravityGoogleSignInButton: render when provider and auth method are eligible
ProviderSettingsPanel->>ProviderInstanceCard: pass signInAction
ProviderInstanceCard->>AntigravityGoogleSignInButton: render in list or editor mode
AntigravityGoogleSignInButton->>startProviderAuth: start Google OAuth
startProviderAuth-->>AntigravityGoogleSignInButton: update authentication state
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
What
readyor cached-model retention.startProviderAuthOAuth.Why
Fixes #12751
Redo of closed #12861 addressing Macroscope Not-approved (readiness semantics): UI-only framing; probe/registry contracts unchanged.
UI
Settings → Providers → Antigravity: informational sign-in-required copy; Sign in with Google on list row and selected card.
Checklist
Summary by CodeRabbit
New Features
Bug Fixes
Tests