Fix 500 error when AI tab encounters a 401 from the runtime

web-admin/src/components/errors/user-facing-errors.ts

@@ -27,6 +27,12 @@ export function createUserFacingError(
       body: "It looks like this link is no longer active. Please reach out to the sender to request a new link.",
       fatal: true,
     };
+  } else if (status === 401) {
+    return {
+      statusCode: 401,
+      header: "Authentication error",
+      body: "Try refreshing the page. If the problem persists, try signing out and back in.",
+    };
   } else if (status === 403) {
     return {
       statusCode: status,

web-admin/src/features/projects/selectors.ts

@@ -142,6 +142,7 @@ export async function fetchProjectDeploymentDetails(
       instanceId: projResp.deployment?.runtimeInstanceId,
       jwt: {
         token: projResp.jwt,
+        receivedAt: Date.now(),
         authContext: token ? "magic" : "user",
       },
     },

web-admin/src/routes/[organization]/[project]/-/ai/+layout.ts

@@ -14,7 +14,13 @@ export const load = async ({
   // Wait for the feature flags to load
   const { runtime } = await parent();
 
-  const fetchedFeatureFlags = await getFeatureFlags(runtime);
+  let fetchedFeatureFlags: Awaited<ReturnType<typeof getFeatureFlags>> = {};
+  try {
+    fetchedFeatureFlags = await getFeatureFlags(runtime);
+  } catch {
+    // If the runtime is unreachable or the JWT is invalid, fall back to defaults.
+    // The project layout's JWT refresh polling will recover on the next interval.
+  }
 
   // Redirect to `/-/dashboards` if chat feature is disabled
   // NOTE: In the future, we'll use user-level `ai` permissions for more granular access control