@agent-native/core 0.119.3 → 0.119.4

package/corpus/core/src/templates/chat/react-router.config.ts

@@ -0,0 +1,7 @@
+import type { Config } from "@react-router/dev/config";
+
+export default {
+  appDirectory: "app",
+  ssr: true,
+  routeDiscovery: { mode: "initial" },
+} satisfies Config;

package/corpus/core/src/templates/chat/server/middleware/auth.ts

@@ -0,0 +1,15 @@
+import { runAuthGuard } from "@agent-native/core/server";
+/**
+ * Global auth middleware — runs for ALL requests (page routes, API routes,
+ * framework routes). The auth plugin configures the guard; this middleware
+ * enforces it on every request.
+ *
+ * Without this, auth only runs for /_agent-native/* routes because the
+ * framework handler's middleware registry is scoped to that catch-all.
+ * Page routes (/, /settings) and API routes (/api/*) would bypass auth.
+ */
+import { defineEventHandler } from "h3";
+
+export default defineEventHandler(async (event) => {
+  return runAuthGuard(event);
+});

package/corpus/core/src/templates/chat/server/plugins/agent-chat.ts

@@ -0,0 +1,21 @@
+import { getOrgContext } from "@agent-native/core/org";
+import {
+  createAgentChatPlugin,
+  loadActionsFromStaticRegistry,
+} from "@agent-native/core/server";
+
+import actionsRegistry from "../../.generated/actions-registry.js";
+
+const INITIAL_TOOL_NAMES = ["view-screen", "navigate", "hello"];
+
+export default createAgentChatPlugin({
+  appId: "chat",
+  actions: loadActionsFromStaticRegistry(actionsRegistry),
+  initialToolNames: INITIAL_TOOL_NAMES,
+  resolveOrgId: async (event) => (await getOrgContext(event)).orgId,
+  systemPrompt: `You are the Chat app agent.
+
+This is a minimal chat-first Agent-Native app. The chat is the product surface, and actions are the contract shared by chat, UI, HTTP, MCP, A2A, and CLI.
+
+Use actions as the source of truth. Start by inspecting the current screen when context matters. When the user asks to extend this app, keep the change small and agent-native: add or update actions, expose useful UI, and keep application state/navigation visible to the agent.`,
+});

package/corpus/core/src/templates/chat/server/plugins/auth.ts

@@ -0,0 +1,17 @@
+import { createAuthPlugin } from "@agent-native/core/server";
+
+const rawAppTitle = "{{APP_TITLE}}";
+const appTitle = rawAppTitle === "{" + "{APP_TITLE}}" ? "Chat" : rawAppTitle;
+
+export default createAuthPlugin({
+  marketing: {
+    appName: appTitle,
+    tagline:
+      "Start from a chat-first agent-native app and add actions, screens, and workflows as you grow.",
+    features: [
+      "Full-page chat with durable threads and tool call history",
+      "Add actions once and use them from chat, UI, HTTP, MCP, A2A, and CLI",
+      "Plug in your own agent runtime or build on the included app-agent loop",
+    ],
+  },
+});

package/corpus/core/src/templates/chat/server/routes/[...page].get.ts

@@ -0,0 +1,5 @@
+import { createH3SSRHandler } from "@agent-native/core/server/ssr-handler";
+
+export default createH3SSRHandler(
+  () => import("virtual:react-router/server-build"),
+);

package/corpus/core/src/templates/chat/ssr-entry.ts

@@ -0,0 +1,15 @@
+/**
+ * SSR entry point for Nitro.
+ * Wraps React Router's request handler so Nitro can use it as a service.
+ */
+import { createRequestHandler } from "react-router";
+
+const handler = createRequestHandler(
+  () => import("virtual:react-router/server-build"),
+);
+
+export default {
+  async fetch(request: Request) {
+    return handler(request);
+  },
+};

package/corpus/core/src/templates/chat/tsconfig.json

@@ -0,0 +1,21 @@
+{
+  "extends": "@agent-native/core/tsconfig.base.json",
+  "compilerOptions": {
+    "ignoreDeprecations": "6.0",
+    "rootDirs": [".", "./.react-router/types"],
+    "paths": {
+      "*": ["./*"],
+      "@/*": ["./app/*"],
+      "@shared/*": ["./shared/*"]
+    }
+  },
+  "include": [
+    "app/**/*",
+    "server/**/*",
+    "shared/**/*",
+    "vite.config.ts",
+    "react-router.config.ts",
+    ".react-router/types/**/*",
+    ".generated/**/*"
+  ]
+}

package/corpus/core/src/templates/chat/vite.config.ts

@@ -0,0 +1,19 @@
+import { agentNative } from "@agent-native/core/vite";
+import { reactRouter } from "@react-router/dev/vite";
+import { defineConfig } from "vite";
+
+const reactRouterPlugins = reactRouter as unknown as () => any[];
+const agentNativePlugins = agentNative as unknown as (
+  options?: Parameters<typeof agentNative>[0],
+) => any[];
+
+export default defineConfig({
+  plugins: [
+    ...reactRouterPlugins(),
+    ...agentNativePlugins({
+      // shiki only runs in AssistantChat's useEffect — keep it out of the
+      // CF Pages Functions bundle (25 MiB limit).
+      ssrStubs: ["shiki"],
+    }),
+  ],
+});

package/corpus/templates/analytics/AGENTS.md

@@ -26,23 +26,31 @@ membership id when its native update status reports `update-available`.
 - Never hardcode API keys, tokens, webhook URLs, signing secrets, private Builder/internal data, customer data, or credential-looking literals. Use secrets/OAuth/runtime configuration and obvious placeholders in examples.
 - Data integrity comes first. Do not invent numbers, dimensions, filters, or
   source semantics. State uncertainty and inspect the source when needed.
-- Catalog-first: before querying, consult known data sources (data-source
-  status) and call `list-data-dictionary` with a focused search to learn what
-  exists and which table/columns/join paths to use. Don't fan out blind queries
-  when the catalog already answers where a fact lives.
+- Existing-work-first: treat analytics definitions like code. For a bounded
+  metric lookup, call `search-analytics-query-catalog` once with focused
+  metric/entity terms before writing a new query. It searches accessible
+  dashboard/chart SQL and data-dictionary definitions together. Prefer the
+  strongest approved definition or saved chart, preserve its source and
+  business logic, adapt only the requested filters/time window, then run one
+  bounded query and stop.
+- Use `list-data-dictionary` separately only when the user asks to browse
+  definitions or filter them by department. Use `data-source-status`, schema
+  discovery, or provider catalogs only when the combined catalog search does
+  not establish a source/query shape.
 - `data-source-status` always includes the built-in first-party Analytics source
   and returns `hasConnectedExternalDataSources`,
   `dataSourcesSetupLink` (a real deep link to `/data-sources`). Chat stays
   available when no external provider is connected; for a request that needs
   one, explain the missing source in context and include that returned link so
   the user can connect it. Do not replace this with a generic canned response.
-- Simple time-bounded metric fast path: when the data dictionary or a known
-  canonical source already identifies the metric, run one bounded aggregate.
-  Once that query returns a valid result, answer immediately with the source,
-  time window, row count, and only necessary caveats. Do not schema-discover,
-  retry, enrich, or add breakdowns unless the query fails or its result
-  conflicts with the known metric definition. This never waives the real-data
-  requirement: do not answer from a guess, stale value, or unverified result.
+- Bounded structured lookup fast path: after the one catalog search, run one
+  query against the matched authoritative source. That source may be first-party
+  Analytics, BigQuery, HubSpot, Gong, or another connected provider. Once it
+  succeeds, answer immediately. Do not schema-discover, cross-check, enrich,
+  retry, or add breakdowns unless the user requested them, the first query
+  failed, or its result conflicts with the known definition. `all`, `total`,
+  and `exact` in a structured aggregate do not by themselves require a corpus
+  workflow.
 - Clarify-first for ambiguous ad-hoc work: when the metric definition, date
   range, or grain is ambiguous and a wrong guess would change the numbers, use
   the `ask-question` clarifying tool (multiple-choice) before computing. Ask at

package/corpus/templates/analytics/actions/list-data-dictionary.ts

@@ -10,7 +10,7 @@ const KEY_PREFIX = "data-dict-";
 
 export default defineAction({
   description:
-    "List entries in the data dictionary — the internal catalog of metrics, tables, columns, and business definitions the analytics agent should consult before writing SQL or proposing a dashboard. Call this FIRST when the user asks for a dashboard or metric so you know what's already defined, where the numbers come from, and how to query them correctly. Returns all entries sorted by metric name; filter with `search` or `department` when you only need a slice.",
+    "List or browse entries in the data dictionary — the internal catalog of metrics, tables, columns, and business definitions. For an ordinary metric lookup, use search-analytics-query-catalog instead because it searches dictionary entries and existing dashboard/chart SQL together in one bounded call. Use this action when the user specifically asks to browse dictionary definitions or filter them by department.",
   schema: z.object({
     search: z
       .string()
@@ -64,6 +64,8 @@ export default defineAction({
           e.metric,
           e.definition,
           e.department,
+          e.source,
+          e.action,
           e.table,
           e.columnsUsed,
           e.cuts,

package/corpus/templates/analytics/actions/save-data-dictionary-entry.ts

@@ -42,6 +42,18 @@ export default defineAction({
       .string()
       .optional()
       .describe("Owning team (e.g. 'Sales', 'Marketing', 'Product', 'Data')"),
+    source: z
+      .string()
+      .optional()
+      .describe(
+        "Canonical source/provider id for this definition (for example first-party, bigquery, or hubspot)",
+      ),
+    action: z
+      .string()
+      .optional()
+      .describe(
+        "Preferred Analytics action name when this metric is not expressed as SQL",
+      ),
     table: z
       .string()
       .optional()
@@ -143,6 +155,8 @@ export default defineAction({
       metric: args.metric,
       definition: args.definition,
       department: args.department ?? (existing as any)?.department ?? "",
+      source: args.source ?? (existing as any)?.source ?? "",
+      action: args.action ?? (existing as any)?.action ?? "",
       table: args.table ?? (existing as any)?.table ?? "",
       columnsUsed: args.columnsUsed ?? (existing as any)?.columnsUsed ?? "",
       cuts: args.cuts ?? (existing as any)?.cuts ?? "",

package/corpus/templates/analytics/actions/search-analytics-query-catalog.ts

@@ -0,0 +1,41 @@
+import { defineAction } from "@agent-native/core";
+import {
+  getRequestOrgId,
+  getRequestUserEmail,
+} from "@agent-native/core/server";
+import { z } from "zod";
+
+import { searchAnalyticsQueryCatalog } from "../server/lib/analytics-query-catalog";
+
+export default defineAction({
+  description:
+    "Search Analytics' existing query knowledge before writing a new query. This is the analytics equivalent of grepping for similar code: one bounded call searches accessible saved dashboard names, chart titles/descriptions/queries, shipped dashboard patterns, and data-dictionary definitions. Use it first for an ordinary metric lookup unless the user supplied an exact source and query. Prefer the highest-trust close match, adapt its saved query only for the requested filters/time window, run one authoritative source query, and stop on success. Do not separately list every dashboard or scan provider catalogs after a strong match.",
+  schema: z.object({
+    search: z
+      .string()
+      .trim()
+      .min(2)
+      .describe(
+        "Focused metric/entity terms from the user's question, for example 'agent native signups' or 'HubSpot closed won revenue'",
+      ),
+    limit: z
+      .number()
+      .int()
+      .min(1)
+      .max(12)
+      .optional()
+      .default(6)
+      .describe("Maximum ranked candidates to return"),
+  }),
+  readOnly: true,
+  run: async ({ search, limit }) => {
+    const email = getRequestUserEmail();
+    if (!email) throw new Error("no authenticated user");
+    return searchAnalyticsQueryCatalog({
+      search,
+      limit,
+      email,
+      orgId: getRequestOrgId() || null,
+    });
+  },
+});

package/corpus/templates/analytics/app/components/dashboard/DashboardPanelSkeleton.tsx

@@ -0,0 +1,13 @@
+import type { ComponentProps } from "react";
+
+import { Skeleton } from "@/components/ui/skeleton";
+import { cn } from "@/lib/utils";
+
+export function DashboardPanelSkeleton({
+  className,
+  ...props
+}: ComponentProps<typeof Skeleton>) {
+  return (
+    <Skeleton {...props} className={cn("bg-muted-foreground/20", className)} />
+  );
+}

package/corpus/templates/analytics/app/components/dashboard/SqlChart.tsx

@@ -60,7 +60,6 @@ import {
   SelectTrigger,
   SelectValue,
 } from "@/components/ui/select";
-import { Skeleton } from "@/components/ui/skeleton";
 import { useChartTooltipPortalPosition } from "@/hooks/use-chart-tooltip-portal";
 
 const PAGE_SIZE_OPTIONS = [10, 25, 50, 100];
@@ -75,6 +74,8 @@ import type {
   ColumnFormat,
 } from "@/pages/adhoc/sql-dashboard/types";
 
+import { DashboardPanelSkeleton } from "./DashboardPanelSkeleton";
+
 const DEFAULT_COLORS = [
   "var(--brand-blue)",
   "var(--brand-teal)",
@@ -820,7 +821,7 @@ function TableLoadingSkeleton() {
         <div className="min-w-[480px]">
           <div className="grid h-8 grid-cols-4 items-center border-b border-border px-2">
             {columnWidths.map((width, index) => (
-              <Skeleton key={index} className={`h-3 ${width}`} />
+              <DashboardPanelSkeleton key={index} className={`h-3 ${width}`} />
             ))}
           </div>
           {Array.from({ length: TABLE_PANEL_SKELETON_ROWS }).map((_, row) => (
@@ -829,7 +830,7 @@ function TableLoadingSkeleton() {
               className="grid h-8 grid-cols-4 items-center border-b border-border/50 px-2"
             >
               {columnWidths.map((width, col) => (
-                <Skeleton
+                <DashboardPanelSkeleton
                   key={col}
                   className={`h-3 ${
                     col === 0 ? "w-36" : col === 2 ? "ml-auto w-16" : width
@@ -841,8 +842,8 @@ function TableLoadingSkeleton() {
         </div>
       </div>
       <div className="flex h-8 items-center justify-between border-t border-border px-1 text-xs">
-        <Skeleton className="h-3 w-28" />
-        <Skeleton className="h-3 w-24" />
+        <DashboardPanelSkeleton className="h-3 w-28" />
+        <DashboardPanelSkeleton className="h-3 w-24" />
       </div>
     </div>
   );
@@ -853,7 +854,7 @@ function SqlChartLoadingSkeleton({ panel }: { panel: SqlPanel }) {
 
   if (panel.chartType === "metric") {
     return (
-      <Skeleton
+      <DashboardPanelSkeleton
         data-dashboard-report-loading="true"
         className="w-full flex-1 min-h-12"
       />
@@ -868,7 +869,7 @@ function SqlChartLoadingSkeleton({ panel }: { panel: SqlPanel }) {
 
   if (!reserveLegend) {
     return (
-      <Skeleton
+      <DashboardPanelSkeleton
         data-dashboard-report-loading="true"
         className={`w-full flex-1 ${fill ? "h-full min-h-[250px]" : "min-h-[250px]"}`}
       />
@@ -880,14 +881,14 @@ function SqlChartLoadingSkeleton({ panel }: { panel: SqlPanel }) {
       data-dashboard-report-loading="true"
       className={`flex w-full flex-1 flex-col overflow-hidden ${fill ? "h-full" : ""}`}
     >
-      <Skeleton
+      <DashboardPanelSkeleton
         className={`w-full ${fill ? "h-full min-h-[250px] flex-1" : "h-[250px]"}`}
       />
       <div className="mt-1 flex min-h-6 flex-wrap gap-x-3 gap-y-1 overflow-hidden pr-1">
         {Array.from({ length: 3 }).map((_, index) => (
           <div key={index} className="flex min-h-6 items-center gap-1.5">
-            <Skeleton className="h-2.5 w-3 shrink-0 rounded-sm" />
-            <Skeleton className="h-3 w-20 min-w-0" />
+            <DashboardPanelSkeleton className="h-2.5 w-3 shrink-0 rounded-sm" />
+            <DashboardPanelSkeleton className="h-3 w-20 min-w-0" />
           </div>
         ))}
       </div>
@@ -1329,7 +1330,7 @@ function DashboardExtensionPanel({
   const [ready, setReady] = useState(false);
   const [unavailable, setUnavailable] = useState(false);
   const loadingSkeleton = !ready ? (
-    <Skeleton
+    <DashboardPanelSkeleton
       data-dashboard-extension-loading="true"
       className="absolute inset-0 z-10 h-full min-h-[180px] w-full rounded-md"
       aria-hidden="true"

package/corpus/templates/analytics/app/pages/adhoc/DashboardSkeleton.tsx

@@ -1,7 +1,7 @@
 import type { CSSProperties } from "react";
 
+import { DashboardPanelSkeleton } from "@/components/dashboard/DashboardPanelSkeleton";
 import { Card, CardContent, CardHeader } from "@/components/ui/card";
-import { Skeleton } from "@/components/ui/skeleton";
 
 interface DashboardSkeletonProps {
   columns?: number;
@@ -22,10 +22,10 @@ export function DashboardSkeleton({
           <div key={i} className="dashboard-grid-cell h-full">
             <Card className="flex h-full flex-col overflow-visible">
               <CardHeader className="pb-2 shrink-0">
-                <Skeleton className="h-4 w-32" />
+                <DashboardPanelSkeleton className="h-4 w-32" />
               </CardHeader>
               <CardContent className="flex flex-1 flex-col pt-0">
-                <Skeleton className="w-full flex-1 min-h-[250px]" />
+                <DashboardPanelSkeleton className="w-full flex-1 min-h-[250px]" />
               </CardContent>
             </Card>
           </div>

package/corpus/templates/analytics/changelog/2026-07-23-dashboard-chart-loading-placeholders-are-easier-to-see-in-da.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-07-23
+---
+
+Dashboard chart loading placeholders are easier to see in dark mode.

package/corpus/templates/analytics/changelog/2026-07-23-routine-analytics-lookups-reuse-existing-query-definitions.md

@@ -0,0 +1,6 @@
+---
+type: improved
+date: 2026-07-23
+---
+
+Routine analytics lookups now search existing dashboard queries and dictionary definitions, then stop after one successful authoritative query.

package/corpus/templates/analytics/server/lib/agent-chat-plan-mode.ts

@@ -31,21 +31,10 @@ export const INITIAL_TOOL_NAMES = [
   "list-extensions",
   "get-extension",
   "generate-chart",
+  "search-analytics-query-catalog",
   "query-agent-native-analytics",
   "bigquery",
   "search-bigquery-schema",
-  "provider-api-catalog",
-  "provider-api-docs",
-  "provider-api-request",
-  "run-code",
-  "get-code-execution",
-  "provider-corpus-job",
-  "query-staged-dataset",
-  "list-staged-datasets",
-  "account-deep-dive",
-  "gong-calls",
-  "gong-native-insights",
-  "github-repo-files",
   "list-data-dictionary",
   "navigate",
 ];