After re-deploying app asks me to Sign In

[kmikeym]

After redeploying my app the app says: Sign in to use AI features:

click on vibes diy button and I am logged in:

and in fact selecting logout does nothing.

[kmikeym]

App is broken now.

Asked VibesOS to check on it:

the app is asking me to log in to use AI features but I am logged in.

No auth/login code exists in app.jsx. The "log in to use AI features" message is coming from the useAI() hook itself — it's a platform-level check. Let me look at where useAI is called to see if there's an error being surfaced.The issue is that useAI() returns an error object with a message about needing to log in — and the app displays error.message directly. This is a platform-level error from the AI hook, not something in app.jsx code. The user IS logged in, so the error is likely about the AI/OpenRouter key not being configured on this deployment, not actual auth.

Let me check if there's any conditional rendering based on error that might block the UI:The error display is fine — it just shows the error.message from useAI(). The problem is that useAI() is returning an auth-related error persistently (not from a failed call, but immediately). This is likely because error starts non-null. The clearError calls happen only when the user clicks a button.

The fix: filter out auth/login-related errors from useAI() since the user is already authenticated — these are false positives. Or better: don't show the error until the user actually tries to call AI.I see the issue. The useAI() hook's error is likely populated immediately on mount (before any AI call) with a login/auth message. The fix is to only show errors after the user has actually attempted an AI call.Now mark hasTriedAI true when the user clicks feedback:Now update the error display in WorkshopTab to only show after an AI call attempt:Now do the same for BrainstormTab:Fixed. The useAI() hook was returning an auth-related error immediately on mount (before you even tried to use AI), and the app was displaying it right away. Now both WorkshopTab and BrainstormTab only show AI errors after you've actually clicked "Get Feedback" or "Brainstorm Angles" — so that false login prompt won't appear on load anymore.

[popmechanic]

Root cause identified and fixed at the platform level.

The useAI() hook's preflight check was synchronously checking for the OIDC token on every callAI()/streamAI() call. If the token hadn't loaded yet (it arrives asynchronously after auth), the hook would set an AUTH_REQUIRED error — which generated apps displayed as "Sign in to use AI features" even though the user was already authenticated.

Fix:

• Added isReady boolean to useAI() that reactively tracks whether the AI proxy + auth token are available
• Listens for the vibes-oidc-ready event so isReady updates automatically when the user signs in
• Auth/config unavailability no longer populates the error state — error is now reserved for actual API failures (network errors, rate limits, etc.)
• Apps can use isReady to conditionally show/disable AI buttons instead of displaying confusing auth errors

Updated the AI integration docs with the new API surface.