@agent-native/dispatch 0.2.3 → 0.2.5

package/dist/server/plugins/integrations.js.map

@@ -1 +1 @@
-{"version":3,"file":"integrations.js","sourceRoot":"","sources":["../../../src/server/plugins/integrations.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,wBAAwB,EAAE,MAAM,2BAA2B,CAAC;AACrE,OAAO,EACL,qBAAqB,EACrB,oBAAoB,GACrB,MAAM,iCAAiC,CAAC;AACzC,OAAO,EAAE,iBAAiB,EAAE,MAAM,aAAa,CAAC;AAChD,OAAO,EAAE,eAAe,EAAE,MAAM,wBAAwB,CAAC;AAEzD,MAAM,kCAAkC,GAAG;;;;;;;;;;;;;;;;;;4FAkBiD,CAAC;AAE7F;;;;GAIG;AACH,MAAM,0BAA0B,GAAG,KAAK,EAAE,QAAa,EAAE,EAAE;IACzD,MAAM,EAAE,YAAY,GAAG,EAAE,EAAE,GAAG,iBAAiB,EAAE,CAAC;IAClD,MAAM,cAAc,GAAG,YAAY,CAAC,YAAY,CAAC;IACjD,MAAM,YAAY,GAChB,OAAO,cAAc,KAAK,QAAQ;QAChC,CAAC,CAAC,cAAc;QAChB,CAAC,CAAC,OAAO,cAAc,KAAK,UAAU;YACpC,CAAC,CAAC,cAAc,CAAC,kCAAkC,CAAC;YACpD,CAAC,CAAC,kCAAkC,CAAC;IAE3C,MAAM,MAAM,GAAG,wBAAwB,CAAC;QACtC,KAAK,EAAE,UAAU;QACjB,OAAO,EAAE,eAAe;QACxB,YAAY,EAAE,oBAAoB;QAClC,aAAa,EAAE,qBAAqB;QACpC,YAAY;QACZ,wDAAwD;QACxD,yEAAyE;QACzE,+DAA+D;QAC/D,6EAA6E;KAC9E,CAAC,CAAC;IAEH,OAAO,MAAM,CAAC,QAAQ,CAAC,CAAC;AAC1B,CAAC,CAAC;AAEF,eAAe,0BAA0B,CAAC","sourcesContent":["import { createIntegrationsPlugin } from \"@agent-native/core/server\";\nimport {\n  beforeDispatchProcess,\n  resolveDispatchOwner,\n} from \"../lib/dispatch-integrations.js\";\nimport { getDispatchConfig } from \"../index.js\";\nimport { dispatchActions } from \"../../actions/index.js\";\n\nconst DISPATCH_INTEGRATION_SYSTEM_PROMPT = `You are the central dispatch for this workspace, responding via a messaging platform integration (Slack, Telegram, email, etc.).\n\nDefault posture:\n- Treat Slack, Telegram, and email as shared entrypoints into the workspace.\n- 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), and design (visual designs).\n- Use list-connected-agents to see what agents are available before assuming a request must be handled locally.\n- 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.\n- Keep durable memory and operating instructions in resources rather than ephemeral chat.\n- Reply in the originating thread unless the user explicitly asks you to send to a saved destination.\n\nWhen a user asks for something:\n- If it belongs to analytics, content, slides, videos, etc., delegate via call-agent — do not re-implement the domain logic in dispatch.\n- 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.\n- 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.\n- If the user asks to create, build, make, scaffold, or generate a new workspace app or agent, call start-workspace-app-creation with their prompt. In this codebase, \"agent\" and \"app\" are synonyms — every agent-native app is an agent, so \"build me an agent\" and \"build me an app\" mean the same thing. Route both to start-workspace-app-creation. If the request is too vague to produce an app, ask one concise follow-up. If the action returns mode \"builder\", reply with the Builder branch URL. 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.\n- For digests, reminders, or saved behavior, prefer recurring jobs, resources, or destinations over chat replies.\n- Keep responses concise and operational — messaging platforms have character limits.\n- Use markdown sparingly (bold and lists are fine, avoid complex formatting).\n- If a task requires many steps, summarize what you did rather than streaming every detail.`;\n\n/**\n * Defer plugin construction until the Nitro plugin actually fires so the\n * config-aware system prompt resolves AFTER `setupDispatch(config)` has\n * stamped the active config (plugin module load order is not guaranteed).\n */\nconst dispatchIntegrationsPlugin = async (nitroApp: any) => {\n  const { integrations = {} } = getDispatchConfig();\n  const promptOverride = integrations.systemPrompt;\n  const systemPrompt =\n    typeof promptOverride === \"string\"\n      ? promptOverride\n      : typeof promptOverride === \"function\"\n        ? promptOverride(DISPATCH_INTEGRATION_SYSTEM_PROMPT)\n        : DISPATCH_INTEGRATION_SYSTEM_PROMPT;\n\n  const plugin = createIntegrationsPlugin({\n    appId: \"dispatch\",\n    actions: dispatchActions,\n    resolveOwner: resolveDispatchOwner,\n    beforeProcess: beforeDispatchProcess,\n    systemPrompt,\n    // Inherit the framework default (claude-sonnet-4-6 from\n    // packages/core/src/integrations/plugin.ts). Haiku was tried for latency\n    // but hallucinated URLs/IDs after delegated call-agent results\n    // (e.g. inventing `https://slides.workspace.com/deck/builder-io-deck-2024`).\n  });\n\n  return plugin(nitroApp);\n};\n\nexport default dispatchIntegrationsPlugin;\n"]}
+{"version":3,"file":"integrations.js","sourceRoot":"","sources":["../../../src/server/plugins/integrations.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,wBAAwB,EAAE,MAAM,2BAA2B,CAAC;AACrE,OAAO,EACL,qBAAqB,EACrB,oBAAoB,GACrB,MAAM,iCAAiC,CAAC;AACzC,OAAO,EAAE,iBAAiB,EAAE,MAAM,aAAa,CAAC;AAChD,OAAO,EAAE,eAAe,EAAE,MAAM,wBAAwB,CAAC;AAEzD,MAAM,kCAAkC,GAAG;;;;;;;;;;;;;;;;;;;4FAmBiD,CAAC;AAE7F;;;;GAIG;AACH,MAAM,0BAA0B,GAAG,KAAK,EAAE,QAAa,EAAE,EAAE;IACzD,MAAM,EAAE,YAAY,GAAG,EAAE,EAAE,GAAG,iBAAiB,EAAE,CAAC;IAClD,MAAM,cAAc,GAAG,YAAY,CAAC,YAAY,CAAC;IACjD,MAAM,YAAY,GAChB,OAAO,cAAc,KAAK,QAAQ;QAChC,CAAC,CAAC,cAAc;QAChB,CAAC,CAAC,OAAO,cAAc,KAAK,UAAU;YACpC,CAAC,CAAC,cAAc,CAAC,kCAAkC,CAAC;YACpD,CAAC,CAAC,kCAAkC,CAAC;IAE3C,MAAM,MAAM,GAAG,wBAAwB,CAAC;QACtC,KAAK,EAAE,UAAU;QACjB,OAAO,EAAE,eAAe;QACxB,YAAY,EAAE,oBAAoB;QAClC,aAAa,EAAE,qBAAqB;QACpC,YAAY;QACZ,wDAAwD;QACxD,yEAAyE;QACzE,+DAA+D;QAC/D,6EAA6E;KAC9E,CAAC,CAAC;IAEH,OAAO,MAAM,CAAC,QAAQ,CAAC,CAAC;AAC1B,CAAC,CAAC;AAEF,eAAe,0BAA0B,CAAC","sourcesContent":["import { createIntegrationsPlugin } from \"@agent-native/core/server\";\nimport {\n  beforeDispatchProcess,\n  resolveDispatchOwner,\n} from \"../lib/dispatch-integrations.js\";\nimport { getDispatchConfig } from \"../index.js\";\nimport { dispatchActions } from \"../../actions/index.js\";\n\nconst DISPATCH_INTEGRATION_SYSTEM_PROMPT = `You are the central dispatch for this workspace, responding via a messaging platform integration (Slack, Telegram, email, etc.).\n\nDefault posture:\n- Treat Slack, Telegram, and email as shared entrypoints into the workspace.\n- 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), and design (visual designs).\n- Use list-connected-agents to see what agents are available before assuming a request must be handled locally.\n- 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.\n- Keep durable memory and operating instructions in resources rather than ephemeral chat.\n- Reply in the originating thread unless the user explicitly asks you to send to a saved destination.\n\nWhen a user asks for something:\n- If it belongs to analytics, content, slides, videos, etc., delegate via call-agent — do not re-implement the domain logic in dispatch.\n- 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.\n- 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.\n- 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.\n- If the user explicitly asks for a new app or workspace app, call start-workspace-app-creation with their prompt. 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>, and making it appear in the workspace apps list. 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.\n- For digests, reminders, or saved behavior, prefer recurring jobs, resources, or destinations over chat replies.\n- Keep responses concise and operational — messaging platforms have character limits.\n- Use markdown sparingly (bold and lists are fine, avoid complex formatting).\n- If a task requires many steps, summarize what you did rather than streaming every detail.`;\n\n/**\n * Defer plugin construction until the Nitro plugin actually fires so the\n * config-aware system prompt resolves AFTER `setupDispatch(config)` has\n * stamped the active config (plugin module load order is not guaranteed).\n */\nconst dispatchIntegrationsPlugin = async (nitroApp: any) => {\n  const { integrations = {} } = getDispatchConfig();\n  const promptOverride = integrations.systemPrompt;\n  const systemPrompt =\n    typeof promptOverride === \"string\"\n      ? promptOverride\n      : typeof promptOverride === \"function\"\n        ? promptOverride(DISPATCH_INTEGRATION_SYSTEM_PROMPT)\n        : DISPATCH_INTEGRATION_SYSTEM_PROMPT;\n\n  const plugin = createIntegrationsPlugin({\n    appId: \"dispatch\",\n    actions: dispatchActions,\n    resolveOwner: resolveDispatchOwner,\n    beforeProcess: beforeDispatchProcess,\n    systemPrompt,\n    // Inherit the framework default (claude-sonnet-4-6 from\n    // packages/core/src/integrations/plugin.ts). Haiku was tried for latency\n    // but hallucinated URLs/IDs after delegated call-agent results\n    // (e.g. inventing `https://slides.workspace.com/deck/builder-io-deck-2024`).\n  });\n\n  return plugin(nitroApp);\n};\n\nexport default dispatchIntegrationsPlugin;\n"]}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/dispatch",
-  "version": "0.2.3",
+  "version": "0.2.5",
   "type": "module",
   "description": "Dispatch — workspace control plane for agent-native apps. Vault, integrations, destinations, scheduled jobs, and cross-app delegation, shipped as a single drop-in package.",
   "license": "MIT",
@@ -97,7 +97,7 @@
     "typescript": "^6.0.3",
     "vite": "8.0.3",
     "vitest": "^4.1.5",
-    "@agent-native/core": "0.9.1"
+    "@agent-native/core": "0.11.4"
   },
   "scripts": {
     "build": "tsc && tsc-alias --resolve-full-paths",

package/src/actions/start-workspace-app-creation.ts

@@ -5,7 +5,7 @@ import { startWorkspaceAppCreation } from "../server/lib/app-creation-store.js";
 
 export default defineAction({
   description:
-    "Start creating a new workspace app from Dispatch. In local dev this returns a code-agent prompt; in production it creates a Builder branch when a Builder project is configured.",
+    "Start creating a new workspace app from Dispatch when the request truly needs its own app. In local dev this returns a code-agent prompt; in production it creates a Builder branch when a Builder project is configured. The result must be a separate workspace app under apps/<app-id>, not a new route or file in apps/starter.",
   schema: z.object({
     prompt: z.string().min(1).describe("The user's app creation request"),
     appId: z

package/src/components/agents-panel.tsx

@@ -1,4 +1,4 @@
-import { useRef, useState } from "react";
+import { useRef, useState, type FormEvent } from "react";
 import { Button } from "@/components/ui/button";
 import { Input } from "@/components/ui/input";
 import {
@@ -27,6 +27,48 @@ export interface ConnectedAgent {
   scope?: "shared" | "personal";
 }
 
+type AgentFormErrors = Partial<Record<"name" | "url" | "form", string>>;
+
+function slugifyAgentName(value: string): string {
+  return value
+    .trim()
+    .toLowerCase()
+    .replace(/[^a-z0-9]+/g, "-")
+    .replace(/^-+|-+$/g, "");
+}
+
+function validateAgentForm(name: string, url: string): AgentFormErrors {
+  const errors: AgentFormErrors = {};
+  const trimmedName = name.trim();
+  const trimmedUrl = url.trim();
+
+  if (!trimmedName) {
+    errors.name = "Agent name is required.";
+  } else if (!slugifyAgentName(trimmedName)) {
+    errors.name = "Agent name must include at least one letter or number.";
+  }
+
+  if (!trimmedUrl) {
+    errors.url = "Agent endpoint URL is required.";
+  } else {
+    try {
+      const parsed = new URL(trimmedUrl);
+      if (parsed.protocol !== "https:" && parsed.protocol !== "http:") {
+        errors.url = "Use an http:// or https:// endpoint URL.";
+      } else if (!parsed.hostname) {
+        errors.url = "Enter a complete endpoint URL with a host.";
+      } else if (parsed.username || parsed.password) {
+        errors.url = "Do not include credentials in the endpoint URL.";
+      }
+    } catch {
+      errors.url =
+        "Enter a valid endpoint URL, such as https://app.example.com.";
+    }
+  }
+
+  return errors;
+}
+
 export function AgentsPanel({
   agents,
   onRefresh,
@@ -38,6 +80,7 @@ export function AgentsPanel({
   const [url, setUrl] = useState("");
   const [description, setDescription] = useState("");
   const [saving, setSaving] = useState(false);
+  const [errors, setErrors] = useState<AgentFormErrors>({});
   const nameRef = useRef<HTMLInputElement>(null);
 
   const customAgents = agents.filter((agent) => agent.source === "custom");
@@ -46,12 +89,17 @@ export function AgentsPanel({
   );
   const builtinAgents = agents.filter((agent) => agent.source === "builtin");
 
-  const handleAdd = async () => {
+  const handleAdd = async (event?: FormEvent<HTMLFormElement>) => {
+    event?.preventDefault();
     const trimmedName = name.trim();
     const trimmedUrl = url.trim();
-    if (!trimmedName || !trimmedUrl) return;
+    const nextErrors = validateAgentForm(trimmedName, trimmedUrl);
+    if (Object.keys(nextErrors).length > 0) {
+      setErrors(nextErrors);
+      return;
+    }
 
-    const id = trimmedName.toLowerCase().replace(/[^a-z0-9-]/g, "-");
+    const id = slugifyAgentName(trimmedName);
     const agentJson = JSON.stringify(
       {
         id,
@@ -79,9 +127,21 @@ export function AgentsPanel({
         setName("");
         setUrl("");
         setDescription("");
+        setErrors({});
         onRefresh();
         nameRef.current?.focus();
+      } else {
+        setErrors({
+          form: `Could not add agent. Request failed with ${res.status}.`,
+        });
       }
+    } catch (error) {
+      setErrors({
+        form:
+          error instanceof Error
+            ? error.message
+            : "Could not add agent. Please try again.",
+      });
     } finally {
       setSaving(false);
     }
@@ -230,31 +290,66 @@ export function AgentsPanel({
           <p className="mt-1 text-xs leading-relaxed text-muted-foreground">
             Add another A2A-compatible app by saving its agent endpoint here.
           </p>
-          <div className="mt-4 space-y-3">
-            <Input
-              ref={nameRef}
-              value={name}
-              onChange={(event) => setName(event.target.value)}
-              placeholder="Name"
-            />
-            <Input
-              value={url}
-              onChange={(event) => setUrl(event.target.value)}
-              placeholder="https://app.example.com"
-            />
+          <form className="mt-4 space-y-3" onSubmit={handleAdd} noValidate>
+            <div className="space-y-1.5">
+              <Input
+                ref={nameRef}
+                value={name}
+                onChange={(event) => {
+                  setName(event.target.value);
+                  setErrors((current) => ({ ...current, name: undefined }));
+                }}
+                placeholder="Name"
+                aria-invalid={Boolean(errors.name)}
+                aria-describedby={
+                  errors.name ? "external-agent-name-error" : undefined
+                }
+              />
+              {errors.name ? (
+                <p
+                  id="external-agent-name-error"
+                  className="text-xs font-medium text-destructive"
+                >
+                  {errors.name}
+                </p>
+              ) : null}
+            </div>
+            <div className="space-y-1.5">
+              <Input
+                value={url}
+                onChange={(event) => {
+                  setUrl(event.target.value);
+                  setErrors((current) => ({ ...current, url: undefined }));
+                }}
+                placeholder="https://app.example.com"
+                aria-invalid={Boolean(errors.url)}
+                aria-describedby={
+                  errors.url ? "external-agent-url-error" : undefined
+                }
+              />
+              {errors.url ? (
+                <p
+                  id="external-agent-url-error"
+                  className="text-xs font-medium text-destructive"
+                >
+                  {errors.url}
+                </p>
+              ) : null}
+            </div>
             <Input
               value={description}
               onChange={(event) => setDescription(event.target.value)}
               placeholder="Description (optional)"
             />
-            <Button
-              className="w-full"
-              onClick={handleAdd}
-              disabled={!name.trim() || !url.trim() || saving}
-            >
+            {errors.form ? (
+              <p className="text-xs font-medium text-destructive">
+                {errors.form}
+              </p>
+            ) : null}
+            <Button type="submit" className="w-full" disabled={saving}>
               {saving ? "Saving..." : "Add agent"}
             </Button>
-          </div>
+          </form>
         </div>
       </div>
     </section>

package/src/components/create-app-popover.tsx

@@ -73,6 +73,7 @@ function buildAppCreationPrompt(input: {
 
   return [
     `Create a new agent-native app in this workspace.`,
+    `This is a new workspace app request, not a feature request for the current app.`,
     ``,
     `Suggested app name: ${input.appId} (you may adjust the slug if it conflicts)`,
     `User prompt: ${input.prompt.trim()}`,
@@ -80,6 +81,7 @@ function buildAppCreationPrompt(input: {
     ``,
     `Pick a starter template that fits the user's prompt — analytics, calendar, content, design, dispatch, forms, mail, slides, videos, clips, or starter when none of the others fit.`,
     `Use the workspace app layout: create it under apps/${input.appId}, mount it at /${input.appId}, keep it on the shared workspace database/hosting model, and avoid table-name collisions by namespacing any new domain tables to the app.`,
+    `Do not satisfy this 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.`,
     keyList
       ? `After the app exists, grant the selected Dispatch vault keys to appId "${input.appId}" and sync them once the app server is available. Treat these as requested grants, not active grants before creation succeeds.`
       : `Do not grant any Dispatch vault keys unless the user asks later.`,

package/src/lib/overview-chat.spec.ts

@@ -0,0 +1,48 @@
+import { beforeEach, describe, expect, it, vi } from "vitest";
+
+const frameState = vi.hoisted(() => ({ inBuilderFrame: false }));
+const sendToAgentChatMock = vi.hoisted(() => vi.fn(() => "chat-tab"));
+
+vi.mock("@agent-native/core/client", () => ({
+  isInBuilderFrame: () => frameState.inBuilderFrame,
+  sendToAgentChat: sendToAgentChatMock,
+}));
+
+const { submitOverviewPrompt } = await import("./overview-chat.js");
+
+describe("submitOverviewPrompt", () => {
+  beforeEach(() => {
+    frameState.inBuilderFrame = false;
+    sendToAgentChatMock.mockClear();
+  });
+
+  it("sends overview prompts to a new local agent tab outside Builder", () => {
+    const tabId = submitOverviewPrompt(" build a metrics app ", "auto");
+
+    expect(tabId).toBe("chat-tab");
+    expect(sendToAgentChatMock).toHaveBeenCalledWith({
+      message: "build a metrics app",
+      submit: true,
+      newTab: true,
+      model: "auto",
+    });
+  });
+
+  it("routes overview prompts to Builder chat inside Builder", () => {
+    frameState.inBuilderFrame = true;
+
+    const tabId = submitOverviewPrompt("ship the onboarding flow", "auto");
+
+    expect(tabId).toBe("chat-tab");
+    expect(sendToAgentChatMock).toHaveBeenCalledWith({
+      message: "ship the onboarding flow",
+      submit: true,
+      type: "code",
+    });
+  });
+
+  it("ignores empty prompts", () => {
+    expect(submitOverviewPrompt("   ", "auto")).toBeNull();
+    expect(sendToAgentChatMock).not.toHaveBeenCalled();
+  });
+});

package/src/lib/overview-chat.ts

@@ -0,0 +1,24 @@
+import { isInBuilderFrame, sendToAgentChat } from "@agent-native/core/client";
+
+export function submitOverviewPrompt(
+  message: string,
+  selectedModel?: string | null,
+): string | null {
+  const trimmed = message.trim();
+  if (!trimmed) return null;
+
+  if (isInBuilderFrame()) {
+    return sendToAgentChat({
+      message: trimmed,
+      submit: true,
+      type: "code",
+    });
+  }
+
+  return sendToAgentChat({
+    message: trimmed,
+    submit: true,
+    newTab: true,
+    model: selectedModel || undefined,
+  });
+}

package/src/routes/pages/overview.tsx

@@ -2,7 +2,6 @@ import { useEffect, useMemo, useState } from "react";
 import { Link } from "react-router";
 import {
   PromptComposer,
-  sendToAgentChat,
   useActionQuery,
   useChatModels,
   agentNativePath,
@@ -34,6 +33,7 @@ import {
   TooltipContent,
   TooltipTrigger,
 } from "@/components/ui/tooltip";
+import { submitOverviewPrompt } from "@/lib/overview-chat";
 
 interface IntegrationStatus {
   platform: string;
@@ -99,17 +99,12 @@ function HomeChatPanel() {
   const { selectedModel } = useChatModels();
 
   const send = (message: string) => {
-    sendToAgentChat({
-      message,
-      submit: true,
-      newTab: true,
-      model: selectedModel || undefined,
-    });
+    submitOverviewPrompt(message, selectedModel);
   };
 
   return (
     <section className="px-2 py-6 sm:py-10">
-      <div className="mx-auto w-full max-w-2xl space-y-5">
+      <div className="mx-auto w-full max-w-2xl space-y-8">
         <h1 className="text-center text-2xl font-semibold tracking-tight text-foreground sm:text-3xl">
           What should we do next?
         </h1>

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

@@ -6,6 +6,7 @@ import {
   getBuilderBranchProjectId,
   getRequestContext,
   isIntegrationCallerRequest,
+  resolveBuilderBranchProjectId,
   resolveBuilderCredentials,
   runBuilderAgent,
 } from "@agent-native/core/server";
@@ -596,6 +597,7 @@ export async function listWorkspaceApps(
 
 export async function getAppCreationSettings(): Promise<AppCreationSettings> {
   const envBuilderProjectId = getEnvBuilderProjectId();
+  const resolvedBuilderProjectId = await resolveBuilderBranchProjectId();
   const raw = await readSettingsRecord();
   const savedBuilderProjectId =
     typeof raw?.builderProjectId === "string" && raw.builderProjectId.trim()
@@ -605,7 +607,9 @@ export async function getAppCreationSettings(): Promise<AppCreationSettings> {
   const enableBuilder =
     process.env.ENABLE_BUILDER === "true" || process.env.ENABLE_BUILDER === "1";
   const effectiveBuilderProjectId =
-    builderProjectId || (enableBuilder ? getBuilderBranchProjectId() : null);
+    builderProjectId ||
+    resolvedBuilderProjectId ||
+    (enableBuilder ? getBuilderBranchProjectId() : null);
 
   return {
     builderProjectId: effectiveBuilderProjectId,

package/src/server/plugins/integrations.ts

@@ -20,7 +20,8 @@ When a user asks for something:
 - If it belongs to analytics, content, slides, videos, etc., delegate via call-agent — do not re-implement the domain logic in dispatch.
 - 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 a new workspace app or agent, call start-workspace-app-creation with their prompt. In this codebase, "agent" and "app" are synonyms — every agent-native app is an agent, so "build me an agent" and "build me an app" mean the same thing. Route both to start-workspace-app-creation. If the request is too vague to produce an app, ask one concise follow-up. If the action returns mode "builder", reply with the Builder branch URL. 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.
+- 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 the user explicitly asks for a new app or workspace app, call start-workspace-app-creation with their prompt. 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>, and making it appear in the workspace apps list. 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.
 - Keep responses concise and operational — messaging platforms have character limits.
 - Use markdown sparingly (bold and lists are fine, avoid complex formatting).