fix(tables): resolve the views flag on the chat route too

Author: TheodoreSpeaks

apps/sim/app/workspace/[workspaceId]/chat/[chatId]/page.tsx

@@ -3,6 +3,7 @@ import type { Metadata } from 'next'
 import { getSession } from '@/lib/auth'
 import { Home } from '@/app/workspace/[workspaceId]/home/home'
 import { HomeFallback } from '@/app/workspace/[workspaceId]/home/home-fallback'
+import { resolveTableViewsEnabled } from '@/app/workspace/[workspaceId]/home/resolve-table-views-flag'
 
 export const metadata: Metadata = {
   title: 'Chat',
@@ -16,14 +17,17 @@ interface ChatPageProps {
 }
 
 export default async function ChatPage({ params }: ChatPageProps) {
-  const [{ chatId }, session] = await Promise.all([params, getSession()])
+  const [{ workspaceId, chatId }, session] = await Promise.all([params, getSession()])
+  const userId = session?.user?.id
+  const tableViewsEnabled = await resolveTableViewsEnabled(workspaceId, userId)
   return (
     <Suspense fallback={<HomeFallback />}>
       <Home
         key={chatId}
         chatId={chatId}
         userName={session?.user?.name}
-        userId={session?.user?.id}
+        userId={userId}
+        tableViewsEnabled={tableViewsEnabled}
       />
     </Suspense>
   )

apps/sim/app/workspace/[workspaceId]/home/page.tsx

@@ -2,10 +2,9 @@ import { Suspense } from 'react'
 import { dehydrate, HydrationBoundary } from '@tanstack/react-query'
 import type { Metadata } from 'next'
 import { getSession } from '@/lib/auth'
-import { isFeatureEnabled } from '@/lib/core/config/feature-flags'
-import { getWorkspaceHostContextForViewer } from '@/lib/workspaces/host-context'
 import { getQueryClient } from '@/app/_shell/providers/get-query-client'
 import { prefetchHomeLists } from '@/app/workspace/[workspaceId]/home/prefetch'
+import { resolveTableViewsEnabled } from '@/app/workspace/[workspaceId]/home/resolve-table-views-flag'
 import { Home } from './home'
 import { HomeFallback } from './home-fallback'
 
@@ -21,15 +20,7 @@ export default async function HomePage({ params }: { params: Promise<{ workspace
 
   const session = await getSession()
   const userId = session?.user?.id
-  // Resolved here for the same reason the table page does it: the flag's gating
-  // lives in AppConfig, which has no client counterpart, and the embedded table is
-  // a client component. Keyed on the workspace's host organization, matching the
-  // table page so both surfaces gate identically. Both reads are request-memoized.
-  const host = userId ? await getWorkspaceHostContextForViewer(workspaceId, userId) : null
-  const tableViewsEnabled = await isFeatureEnabled('table-views', {
-    userId,
-    orgId: host?.hostOrganizationId ?? undefined,
-  })
+  const tableViewsEnabled = await resolveTableViewsEnabled(workspaceId, userId)
   await listsPrefetch
 
   return (

apps/sim/app/workspace/[workspaceId]/home/resolve-table-views-flag.ts

@@ -0,0 +1,26 @@
+import { isFeatureEnabled } from '@/lib/core/config/feature-flags'
+import { getWorkspaceHostContextForViewer } from '@/lib/workspaces/host-context'
+
+/**
+ * Resolves `table-views` for the mothership panel's embedded table.
+ *
+ * Lives here rather than inline because BOTH routes that render `<Home>` need it
+ * — `home/page.tsx` and `chat/[chatId]/page.tsx` — and the flag can only be read
+ * server-side (its gating is in AppConfig, which has no client counterpart).
+ * Resolving it in one place is what keeps the two routes from drifting; the chat
+ * route missing it is precisely why views didn't appear in the panel.
+ *
+ * Keyed on the workspace's HOST organization, matching the table page, so the
+ * same workspace gates identically wherever its tables are rendered. Both this
+ * and `getSession` are request-memoized, so callers pay no extra round-trip.
+ */
+export async function resolveTableViewsEnabled(
+  workspaceId: string,
+  userId: string | undefined
+): Promise<boolean> {
+  const host = userId ? await getWorkspaceHostContextForViewer(workspaceId, userId) : null
+  return isFeatureEnabled('table-views', {
+    userId,
+    orgId: host?.hostOrganizationId ?? undefined,
+  })
+}