@agent-native/dispatch 0.8.18 → 0.8.20

package/src/routes/pages/_index.tsx

@@ -23,7 +23,7 @@ export function meta() {
  *
  * We preserve `?` and `#` so deep-links like `?thread=<id>` from a Slack
  * "Open thread" button survive the bounce — `useThreadDeepLink` in
- * `root.tsx` reads them after the redirect lands on `/overview`.
+ * `root.tsx` reads them after the redirect lands and opens `/chat`.
  */
 function buildTarget(request: Request): string {
   const url = new URL(request.url);

package/src/routes/pages/apps.tsx

@@ -2,6 +2,7 @@ import { useState } from "react";
 import { useActionMutation, useActionQuery } from "@agent-native/core/client";
 import {
   IconApps,
+  IconBrain,
   IconBrush,
   IconCalendarMonth,
   IconChartBar,
@@ -11,6 +12,7 @@ import {
   IconFileText,
   IconLoader2,
   IconMail,
+  IconPhoto,
   IconPlus,
   IconPresentation,
   IconScreenShare,
@@ -58,6 +60,8 @@ const TEMPLATE_ICONS: Record<string, typeof IconMail> = {
   FileText: IconFileText,
   Presentation: IconPresentation,
   ScreenShare: IconScreenShare,
+  Brain: IconBrain,
+  Photo: IconPhoto,
   ChartBar: IconChartBar,
   ClipboardList: IconClipboardList,
   Brush: IconBrush,

package/src/routes/pages/chat.tsx

@@ -0,0 +1,99 @@
+import { useEffect, useRef } from "react";
+import { useLocation, useNavigate } from "react-router";
+import { AgentChatSurface } from "@agent-native/core/client";
+import { submitOverviewPrompt } from "@/lib/overview-chat";
+
+interface DispatchChatLocationState {
+  dispatchPrompt?: {
+    id?: string | number;
+    message?: string;
+    selectedModel?: string | null;
+  };
+  dispatchThread?: {
+    id?: string | number;
+    threadId?: string;
+  };
+}
+
+export function meta() {
+  return [{ title: "Chat — Dispatch" }];
+}
+
+export default function ChatRoute() {
+  const location = useLocation();
+  const navigate = useNavigate();
+  const handledStateIds = useRef(new Set<string>());
+  const state = location.state as DispatchChatLocationState | null;
+  const prompt = state?.dispatchPrompt;
+  const thread = state?.dispatchThread;
+
+  useEffect(() => {
+    const message = prompt?.message?.trim();
+    const threadId = thread?.threadId?.trim();
+    if (!message && !threadId) return;
+
+    const stateId = String(
+      prompt?.id ?? thread?.id ?? `${message ?? ""}:${threadId ?? ""}`,
+    );
+    if (handledStateIds.current.has(stateId)) return;
+    handledStateIds.current.add(stateId);
+
+    const timer = window.setTimeout(() => {
+      if (threadId) {
+        window.dispatchEvent(
+          new CustomEvent("agent-chat:open-thread", {
+            detail: { threadId },
+          }),
+        );
+      }
+      if (message) {
+        submitOverviewPrompt(message, prompt?.selectedModel, {
+          openSidebar: false,
+        });
+      }
+      navigate(`${location.pathname}${location.search}${location.hash}`, {
+        replace: true,
+        state: null,
+      });
+    }, 0);
+
+    return () => window.clearTimeout(timer);
+  }, [
+    location.hash,
+    location.pathname,
+    location.search,
+    navigate,
+    prompt?.id,
+    prompt?.message,
+    prompt?.selectedModel,
+    thread?.id,
+    thread?.threadId,
+  ]);
+
+  return (
+    <div className="flex h-full min-h-0 flex-col bg-background">
+      <AgentChatSurface
+        mode="page"
+        className="dispatch-chat-panel"
+        defaultMode="chat"
+        showHeader={false}
+        showTabBar={false}
+        dynamicSuggestions={false}
+        suggestions={[]}
+        emptyStateText="Ask Dispatch to create apps, route work, or manage the workspace."
+        emptyStateDisplay="hidden"
+        centerComposerWhenEmpty
+        composerLayoutVariant="hero"
+        composerPlaceholder="Ask Dispatch..."
+        composerSlot={
+          <div className="dispatch-chat-intro">
+            <h1>What should Dispatch do next?</h1>
+            <p>
+              Create apps, manage shared keys, and route work across agents.
+            </p>
+          </div>
+        }
+      />
+    </div>
+  );
+}

package/src/routes/pages/overview.tsx

@@ -1,10 +1,11 @@
 import { useEffect, useMemo, useState } from "react";
-import { Link } from "react-router";
+import { Link, useNavigate } from "react-router";
 import {
   PromptComposer,
   useActionQuery,
   useChatModels,
   agentNativePath,
+  isInBuilderFrame,
 } from "@agent-native/core/client";
 import {
   IconActivity,
@@ -75,9 +76,26 @@ const HOME_CHAT_SUGGESTIONS = [
 
 function HomeChatPanel() {
   const { selectedModel } = useChatModels();
+  const navigate = useNavigate();
 
   const send = (message: string) => {
-    submitOverviewPrompt(message, selectedModel);
+    const trimmed = message.trim();
+    if (!trimmed) return;
+
+    if (isInBuilderFrame()) {
+      submitOverviewPrompt(trimmed, selectedModel);
+      return;
+    }
+
+    navigate("/chat", {
+      state: {
+        dispatchPrompt: {
+          id: `${Date.now()}-${Math.random().toString(36).slice(2, 8)}`,
+          message: trimmed,
+          selectedModel,
+        },
+      },
+    });
   };
 
   return (
@@ -90,9 +108,7 @@ function HomeChatPanel() {
           <PromptComposer
             placeholder="Message agent…"
             onSubmit={(text) => {
-              const trimmed = text.trim();
-              if (!trimmed) return;
-              send(trimmed);
+              send(text);
             }}
           />
           <div className="flex flex-wrap justify-center gap-2">

package/src/server/lib/app-creation-store.spec.ts

@@ -2,6 +2,7 @@ import { afterEach, describe, expect, it, vi } from "vitest";
 import { runWithRequestContext } from "@agent-native/core/server";
 import {
   generateWorkspaceAppDescription,
+  listAvailableWorkspaceTemplates,
   listWorkspaceApps,
   updateWorkspaceAppMetadata,
 } from "./app-creation-store.js";
@@ -347,4 +348,18 @@ describe("listWorkspaceApps", () => {
       ),
     ).toBe("Tracks customer onboarding risks and handoffs.");
   });
+
+  it("offers Brain and Assets as workspace template tiles", async () => {
+    stubNoPendingContext();
+    stubManifest([{ id: "dispatch", name: "Dispatch", path: "/dispatch" }]);
+
+    const templates = await runWithRequestContext(
+      { userEmail: "dev@example.test" },
+      () => listAvailableWorkspaceTemplates(),
+    );
+
+    expect(templates.map((template) => template.name)).toEqual(
+      expect.arrayContaining(["brain", "assets"]),
+    );
+  });
 });

package/src/server/lib/app-creation-store.ts

@@ -1293,6 +1293,24 @@ const ADDABLE_TEMPLATES: AvailableWorkspaceTemplate[] = [
     colorRgb: "98 93 245",
     core: true,
   },
+  {
+    name: "brain",
+    label: "Brain",
+    hint: "Cited company knowledge from Slack, meetings, transcripts, and decisions",
+    icon: "Brain",
+    color: "#8B5CF6",
+    colorRgb: "139 92 246",
+    core: true,
+  },
+  {
+    name: "assets",
+    label: "Assets",
+    hint: "Upload, organize, search, and generate on-brand images and videos",
+    icon: "Photo",
+    color: "#0F766E",
+    colorRgb: "15 118 110",
+    core: true,
+  },
   {
     name: "analytics",
     label: "Analytics",

package/src/server/plugins/agent-chat.ts

@@ -31,7 +31,7 @@ Use the standard workspace primitives:
 - When answering whether workspace apps expose agent cards or A2A endpoints, call list-workspace-apps with includeAgentCards=true. If you have not requested that probe, absence of agent-card fields means unchecked, not unavailable.
 - When creating a new workspace app, create a separate app under apps/<app-id> with apps/<app-id>/package.json including a concise generated description, mount it at /<app-id>, use relative /<app-id> links, never hardcode localhost or dev ports, use shadcn/ui with @tabler/icons-react rather than lucide-react, and ensure the React Router client entry preserves APP_BASE_PATH/VITE_APP_BASE_PATH via appBasePath(). There is no separate workspace app registry to edit.
 - If the starter template is used, treat it as scaffolding only: the finished app must be branded as the requested app with its own home screen/navigation/package metadata/manifest, and must not leave visible "Starter", "Blank app", or "New app" UI behind.
-- Treat first-party apps such as Mail, Calendar, Analytics, Brain, and Dispatch as existing hosted/connected neighbors available through links and A2A/default connected agents. Do not create wrapper apps, child apps, nested routes, or cloned template copies just to give a new app access to them; build only the genuinely new workflow and delegate cross-app work to those existing apps.
+- Treat first-party apps such as Mail, Calendar, Analytics, Brain, Assets, and Dispatch as existing hosted/connected neighbors available through links and A2A/default connected agents. Do not create wrapper apps, child apps, nested routes, or cloned template copies just to give a new app access to them; build only the genuinely new workflow and delegate cross-app work to those existing apps.
 
 When a user asks for something like a digest, reminder, routing rule, or saved behavior:
 - First decide whether it should be a resource, a recurring job, a destination, or a delegated task.

package/src/server/plugins/integrations.ts

@@ -13,7 +13,7 @@ Default posture:
 - Heavily delegate domain work to specialized agents through A2A (call-agent) when another app owns the job. Apps you can delegate to include slides (decks/presentations), analytics (data/dashboards), content (docs/articles), videos (Remotion compositions), forms (form builder), clips (screen recordings), design (visual designs), and assets (brand libraries plus generated images/videos).
 - Use the available-apps prompt context first, then list-connected-agents when you need fresh details, to see what agents are available before assuming a request must be handled locally.
 - When asked whether workspace apps expose agent cards or A2A endpoints, call list-workspace-apps with includeAgentCards=true. Without that probe, missing agent-card fields mean unchecked, not unavailable.
-- Treat first-party apps such as Mail, Calendar, Analytics, Brain, and Dispatch as existing hosted/connected neighbors available through links and A2A/default connected agents. Do not create wrapper apps, child apps, nested routes, or cloned template copies just to give a new app access to them; build only the genuinely new workflow and delegate cross-app work to those existing apps.
+- Treat first-party apps such as Mail, Calendar, Analytics, Brain, Assets, and Dispatch as existing hosted/connected neighbors available through links and A2A/default connected agents. Do not create wrapper apps, child apps, nested routes, or cloned template copies just to give a new app access to them; build only the genuinely new workflow and delegate cross-app work to those existing apps.
 - Keep durable memory and operating instructions in resources rather than ephemeral chat.
 - Reply in the originating thread unless the user explicitly asks you to send to a saved destination.
 
@@ -22,7 +22,7 @@ When a user asks for something:
 - After call-agent returns an answer, RELAY IT DIRECTLY to the user with at most a one-line preface — do not rephrase, summarize, or add commentary. The downstream agent already crafted the answer; your job is delivery, not editing. This minimizes round-trips and keeps the user-visible reply fast.
 - Exception: if the downstream agent reports a missing model/provider credential, do not name exact env vars, Vault keys, tokens, or secrets. Say the target app needs an LLM connection and recommend connecting Builder/managed LLM for that app; keep bring-your-own provider keys as a secondary option only if the user asks.
 - If the user asks to create, build, make, scaffold, or generate an "agent" from Dispatch chat or by tagging @agent-native in Slack, email, or Telegram, first classify the ask. If it is a simple Dispatch-native behavior like a reminder, digest, monitor, routing rule, saved instruction, or recurring workflow, create or update the recurring job/resource/destination in Dispatch. If it is a robust unique product or teammate that needs its own UI, data model, actions, integrations, or domain workflow, treat it as a new workspace app and call start-workspace-app-creation.
-- If a new-app prompt asks for access to Mail, Calendar, Analytics, Brain, or similar first-party app data/agents, keep using the existing hosted/connected app and A2A path. Do not ask Builder to scaffold those apps as children of the new app unless the user explicitly asks for a customized fork/copy.
+- If a new-app prompt asks for access to Mail, Calendar, Analytics, Brain, Assets, or similar first-party app data/agents, keep using the existing hosted/connected app and A2A path. Do not ask Builder to scaffold those apps as children of the new app unless the user explicitly asks for a customized fork/copy.
 - If the starter template is used, treat it as scaffolding only: the finished app must be branded as the requested app with its own home screen/navigation/package metadata/manifest, and must not leave visible "Starter", "Blank app", or "New app" UI behind.
 - If the user explicitly asks for a new app or workspace app, call start-workspace-app-creation with their prompt and include a concise generated description by default. Do not satisfy a new-app request by adding a route, page, component, or file inside apps/starter or another existing app unless the user explicitly asks to modify that existing app. If the request is too vague to classify, ask one concise follow-up. If the action returns mode "builder", reply with the Builder branch URL; Builder is responsible for creating the separate workspace app under apps/<app-id>, mounting it at /<app-id>, ensuring apps/<app-id>/package.json exists with name/displayName and description so Dispatch discovers it, using relative /<app-id> links instead of hardcoded localhost/dev ports, and preserving APP_BASE_PATH/VITE_APP_BASE_PATH via appBasePath() in the React Router client entry. The new app lives at the workspace root /<app-id>, NOT under /dispatch/<app-id>, /apps/<app-id>, or any other Dispatch tab — when telling the user where to find it, link to /<app-id> only. There is no separate workspace app registry to edit. If it returns mode "local-agent", tell the user it is ready for the local code agent and include the returned app path/prompt summary. If it returns mode "coming-soon" or "builder-unavailable", explain the missing Builder setup and ask them to connect/configure Builder.
 - For digests, reminders, or saved behavior, prefer recurring jobs, resources, or destinations over chat replies.

package/src/styles/dispatch-css.spec.ts

@@ -52,4 +52,13 @@ describe("dispatch route shells", () => {
     expect(indexRoute).toContain("HydrateFallback");
     expect(indexRoute).toContain("@agent-native/dispatch/routes/pages/_index");
   });
+
+  it("re-exports the chat route from the Dispatch template", () => {
+    const chatRoute = fs.readFileSync(
+      path.join(repoRoot, "templates/dispatch/app/routes/chat.tsx"),
+      "utf-8",
+    );
+
+    expect(chatRoute).toContain("@agent-native/dispatch/routes/pages/chat");
+  });
 });

package/src/styles/dispatch.css

@@ -7,3 +7,106 @@
 @source "../components/**/*.{js,mjs,ts,tsx}";
 @source "../hooks/**/*.{js,mjs,ts,tsx}";
 @source "../routes/**/*.{js,mjs,ts,tsx}";
+
+.dispatch-chat-panel [data-agent-empty-state="centered"] {
+  justify-content: center;
+  padding-bottom: clamp(4rem, 12vh, 8rem);
+}
+
+.dispatch-chat-intro {
+  display: none;
+}
+
+.dispatch-chat-panel [data-agent-empty-state="centered"] .dispatch-chat-intro {
+  display: grid;
+  width: 100%;
+  max-width: min(760px, 90%);
+  gap: 0.5rem;
+  margin: 0 auto 1rem;
+  text-align: center;
+}
+
+.dispatch-chat-intro h1 {
+  margin: 0;
+  color: hsl(var(--foreground));
+  font-size: 2.5rem;
+  font-weight: 600;
+  letter-spacing: 0;
+  line-height: 1.12;
+}
+
+.dispatch-chat-intro p {
+  margin: 0;
+  color: hsl(var(--muted-foreground));
+  font-size: 0.9375rem;
+  line-height: 1.5;
+}
+
+.dispatch-chat-panel [data-agent-empty-state="centered"] .agent-chat-scroll {
+  flex: 0 0 auto;
+  min-height: 0;
+  overflow: visible;
+}
+
+.dispatch-chat-panel [data-agent-empty-state="centered"] .agent-composer-area {
+  width: 100%;
+  max-width: min(760px, 90%);
+  padding: 0;
+}
+
+.dispatch-chat-panel [data-agent-empty-state="centered"] .agent-composer-root {
+  min-height: 10.5rem;
+  border-color: hsl(var(--border));
+  border-radius: 1rem;
+  background: hsl(var(--card));
+  box-shadow:
+    0 20px 60px hsl(220 10% 2% / 0.12),
+    0 0 0 1px hsl(var(--border) / 0.45);
+}
+
+.dark
+  .dispatch-chat-panel
+  [data-agent-empty-state="centered"]
+  .agent-composer-root {
+  box-shadow:
+    0 24px 80px hsl(220 10% 2% / 0.4),
+    0 0 0 1px hsl(var(--border) / 0.7);
+}
+
+.dispatch-chat-panel
+  [data-agent-empty-state="centered"]
+  .agent-composer-prosemirror {
+  min-height: 6.75rem;
+  font-size: 1rem;
+  line-height: 1.625rem;
+}
+
+@media (max-width: 767px) {
+  .dispatch-chat-panel [data-agent-empty-state="centered"] {
+    padding: 1rem;
+    padding-bottom: 5rem;
+  }
+
+  .dispatch-chat-panel
+    [data-agent-empty-state="centered"]
+    .dispatch-chat-intro {
+    width: 100%;
+    margin-bottom: 0.875rem;
+  }
+
+  .dispatch-chat-intro h1 {
+    font-size: 1.75rem;
+  }
+
+  .dispatch-chat-panel
+    [data-agent-empty-state="centered"]
+    .agent-composer-area {
+    width: 100%;
+  }
+
+  .dispatch-chat-panel
+    [data-agent-empty-state="centered"]
+    .agent-composer-root {
+    min-height: 9rem;
+  }
+}