@agent-native/dispatch 0.0.0-beta-20260819155526

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

@@ -0,0 +1,43 @@
+import { describe, expect, it, vi } from "vitest";
+
+const mocks = vi.hoisted(() => ({
+  createAgentChatPlugin: vi.fn((options: Record<string, unknown>) => options),
+}));
+
+vi.mock("@agent-native/core/server", () => ({
+  createAgentChatPlugin: mocks.createAgentChatPlugin,
+}));
+
+vi.mock("@agent-native/core/org", () => ({
+  getOrgContext: vi.fn(),
+}));
+
+vi.mock("../../actions/index.js", () => ({
+  dispatchActions: {},
+}));
+
+describe("Dispatch agent chat plugin", () => {
+  it("opts delegated work into the durable background run contract", async () => {
+    await import("./agent-chat.js");
+
+    expect(mocks.createAgentChatPlugin).toHaveBeenCalledWith(
+      expect.objectContaining({
+        appId: "dispatch",
+        durableBackgroundRuns: true,
+        initialToolNames: expect.arrayContaining([
+          "list-workspace-apps",
+          "update-workspace-app-metadata",
+        ]),
+        mcp: {
+          connectorCatalog: expect.arrayContaining([
+            "start-workspace-app-creation",
+          ]),
+        },
+        actionRoutePublicPaths: ["/_agent-native/actions/list-workspace-apps"],
+        actionRouteAuth: expect.objectContaining({
+          resolveCaller: expect.any(Function),
+        }),
+      }),
+    );
+  });
+});

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

@@ -0,0 +1,99 @@
+import { getOrgContext } from "@agent-native/core/org";
+import { createAgentChatPlugin } from "@agent-native/core/server";
+
+import { dispatchActions } from "../../actions/index.js";
+import {
+  workspaceAppActionRouteAuth,
+  WORKSPACE_APPS_ACTION_PATH,
+} from "../lib/workspace-app-action-auth.js";
+
+const INITIAL_TOOL_NAMES = [
+  "view-screen",
+  "list-workspace-apps",
+  "update-workspace-app-metadata",
+  "list-connected-agents",
+  "ask_app",
+  "open_app",
+  "list-workspace-resources",
+  "create-workspace-resource",
+  "update-workspace-resource",
+  "import-agent",
+  "import-agent-pack",
+  "list-agent-pack",
+  "connect-external-agent",
+  "list-vault-secrets",
+  "request-vault-secret",
+  "create-vault-secret",
+  "list-destinations",
+  "upsert-destination",
+  "list-dreams",
+  "start-workspace-app-creation",
+  "list-available-workspace-templates",
+  "provider-api-catalog",
+  "provider-api-docs",
+  "provider-api-request",
+  "query-staged-dataset",
+  "navigate",
+];
+
+export default createAgentChatPlugin({
+  appId: "dispatch",
+  durableBackgroundRuns: true,
+  initialToolNames: INITIAL_TOOL_NAMES,
+  mcp: {
+    connectorCatalog: [
+      "resolve-integration-source-context",
+      "start-workspace-app-creation",
+    ],
+  },
+  // Without this, AGENT_ORG_ID is never set on agent action calls and every
+  // row written through the frontend (vault secrets, destinations, workspace
+  // resources) lands with org_id=NULL — breaking data isolation across orgs.
+  resolveOrgId: async (event) => {
+    const ctx = await getOrgContext(event);
+    return ctx.orgId;
+  },
+  // Read actions directly from the package's own action map rather than from
+  // a build-time-generated `.generated/actions-registry.ts` (the latter is a
+  // template-only construct that the Vite plugin emits next to actions/).
+  actions: dispatchActions,
+  actionRouteAuth: workspaceAppActionRouteAuth,
+  actionRoutePublicPaths: [WORKSPACE_APPS_ACTION_PATH],
+  codeExecution: { production: "sandboxed" },
+  systemPrompt: `You are the central dispatch for this workspace.
+
+Default posture:
+- Treat Slack and Telegram as shared entrypoints into the workspace.
+- Heavily delegate domain work to specialized agents through A2A when another app owns the job.
+- Keep durable memory and operating instructions in resources rather than ephemeral chat.
+- Prefer replying in the current external thread unless the user explicitly asks you to send to a saved destination.
+
+Use the standard workspace primitives:
+- Read and update resources like AGENTS.md, LEARNINGS.md, jobs/*.md, agents/*.md, and remote-agents/*.json when appropriate.
+- Use recurring jobs for scheduled behavior.
+- Use custom agent profiles in agents/*.md for local spawned work and remote-agents/*.json for remote A2A apps.
+- For a Claude-style Markdown or JSON agent setup, use import-agent so the
+  profile is normalized into agents/<slug>.md. Never import credentials, hooks,
+  shell commands, or local environment settings.
+- For a folder of agent instructions, references, or skills, use
+  import-agent-pack. It preserves the text files under agents/<slug>/ and
+  creates the normalized profile alongside them. Use list-agent-pack to inspect
+  the pack before editing or handing it off to an app.
+- For an existing HTTP/A2A endpoint, use connect-external-agent and let the
+  normal A2A/MCP connection flow handle authentication.
+- You receive a compact available-apps block with sibling workspace app names and descriptions. Use it to pick the right A2A target, and call list-connected-agents or tool-search only when you need fresh details.
+- Hosted/connected A2A neighbors such as Analytics and Content come from the available-apps context or list-connected-agents. list-workspace-apps only inventories apps mounted inside this workspace deployment; never use a missing row there to conclude that a connected agent is unavailable.
+- When answering whether a mounted workspace app exposes an agent card or A2A endpoint, 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.
+- When a user asks to rename an existing workspace app or change its Dispatch title/description, call update-workspace-app-metadata with the existing appId from list-workspace-apps. This is a metadata-only edit — never call start-workspace-app-creation, which creates a new app and Builder branch.
+- When an explicit app-creation request already includes a source brief or a concrete repeatable workflow, call start-workspace-app-creation without asking non-blocking product or UX questions. Choose recommended defaults, let the Builder handoff record assumptions, and ask only for authorization, credentials, a destructive action, an ambiguous target workspace, or a genuinely missing workflow.
+- If the chat 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 "Chat", "Starter", "Blank app", or "New app" UI behind.
+- 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.
+- Integration grants are not provider capability limits. For ad hoc provider inspection, querying, reporting, or troubleshooting, call provider-api-catalog/provider-api-docs, then provider-api-request against the provider's real HTTP API. Use connectionId for a specific shared grant and accountId for a specific OAuth account. Never expose secret values or silently widen app access while doing this.
+- For broad provider searches, joins, classification, corpus counts, or absence claims, fetch every relevant page or an explicitly bounded cohort, stage/save large responses with stageAs/saveToFile/fetchAllPages, and reduce them with query-staged-dataset or run-code. Report source, filters, row counts, pagination, truncation, failed pages, and uncovered gaps.
+
+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.
+- Keep responses concise and operational.
+- Avoid inventing integrations or destinations that are not configured yet.`,
+});

package/src/server/plugins/auth.spec.ts

@@ -0,0 +1,45 @@
+import { beforeEach, describe, expect, it, vi } from "vitest";
+
+const mocks = vi.hoisted(() => ({
+  authPlugin: vi.fn(),
+  createAuthPlugin: vi.fn(),
+  getDispatchConfig: vi.fn(),
+}));
+
+vi.mock("@agent-native/core/server", () => ({
+  createAuthPlugin: mocks.createAuthPlugin,
+}));
+
+vi.mock("../index.js", () => ({
+  getDispatchConfig: mocks.getDispatchConfig,
+}));
+
+describe("dispatchAuthPlugin", () => {
+  beforeEach(() => {
+    vi.resetModules();
+    mocks.authPlugin.mockReset();
+    mocks.createAuthPlugin.mockReset();
+    mocks.createAuthPlugin.mockReturnValue(mocks.authPlugin);
+    mocks.getDispatchConfig.mockReset();
+  });
+
+  it("installs template public routes on the primary auth guard", async () => {
+    const { default: dispatchAuthPlugin } = await import("./auth.js");
+    const nitroApp = {};
+    const publicPaths = [
+      "/_agent-native/identity/authorize",
+      "/_agent-native/org/apps",
+    ];
+
+    mocks.getDispatchConfig.mockReturnValue({
+      auth: { googleOnly: true, publicPaths },
+    });
+    await dispatchAuthPlugin(nitroApp);
+
+    expect(mocks.createAuthPlugin).toHaveBeenCalledOnce();
+    expect(mocks.createAuthPlugin).toHaveBeenCalledWith(
+      expect.objectContaining({ googleOnly: true, publicPaths }),
+    );
+    expect(mocks.authPlugin).toHaveBeenCalledWith(nitroApp);
+  });
+});

package/src/server/plugins/auth.ts

@@ -0,0 +1,36 @@
+import { createAuthPlugin } from "@agent-native/core/server";
+
+import { getDispatchConfig } from "../index.js";
+
+const DEFAULT_MARKETING = {
+  appName: "Dispatch",
+  tagline:
+    "Your AI agent manages secrets, orchestrates other agents, and routes messages across your workspace.",
+  features: [
+    "Centralized vault for secrets with granular per-app grants",
+    "Cross-agent orchestration and delegation to specialist apps",
+    "Slack and Telegram routing with approval workflows",
+  ],
+} as const;
+
+/**
+ * Defer config + plugin construction until the Nitro plugin actually fires.
+ * This way `setupDispatch(config)` can run after plugin module-load order
+ * (Nitro doesn't guarantee load order across plugin files) and still feed
+ * `googleOnly` / `marketing` into `createAuthPlugin`.
+ */
+const dispatchAuthPlugin = async (nitroApp: any) => {
+  const { auth: authConfig = {} } = getDispatchConfig();
+  const googleOnly = authConfig.googleOnly ?? false;
+  const marketing =
+    (authConfig.marketing as Record<string, unknown> | undefined) ??
+    DEFAULT_MARKETING;
+  const plugin = createAuthPlugin({
+    googleOnly,
+    marketing: marketing as any,
+    publicPaths: authConfig.publicPaths,
+  });
+  return plugin(nitroApp);
+};
+
+export default dispatchAuthPlugin;

package/src/server/plugins/core-routes.ts

@@ -0,0 +1,29 @@
+import {
+  createCoreRoutesPlugin,
+  getH3App,
+  type NitroPluginDef,
+} from "@agent-native/core/server";
+
+import { WORKSPACE_APP_CHAT_PROXY_PREFIX } from "../../shared/workspace-app-chat.js";
+import { envKeys } from "../lib/env-config.js";
+import { registerDispatchOnboardingSteps } from "../lib/onboarding-steps.js";
+import { createWorkspaceAppChatProxyHandler } from "../lib/workspace-app-chat-proxy.js";
+
+// Register before the core plugin so "create your first app" (order 5) appears
+// above the auto-generated Slack/Telegram steps (order 60). Idempotent.
+registerDispatchOnboardingSteps();
+
+const corePlugin = createCoreRoutesPlugin({ envKeys });
+
+const dispatchCoreRoutesPlugin: NitroPluginDef = (nitroApp) => {
+  const coreInit = corePlugin(nitroApp);
+  // `getH3App` installs the framework CSRF middleware on its first call for
+  // this app, so any route registered through it is already behind that check.
+  getH3App(nitroApp).use(
+    WORKSPACE_APP_CHAT_PROXY_PREFIX,
+    createWorkspaceAppChatProxyHandler(),
+  );
+  return coreInit;
+};
+
+export default dispatchCoreRoutesPlugin;

package/src/server/plugins/db.ts

@@ -0,0 +1,20 @@
+import { runMigrations } from "@agent-native/core/db";
+
+import { dispatchMigrations } from "../../db/migrations.js";
+import { scheduleVaultBootResync } from "../lib/vault-boot-resync.js";
+
+export const runDispatchMigrations = runMigrations(dispatchMigrations, {
+  table: "dispatch_migrations",
+});
+
+/**
+ * Run dispatch's own migrations first (this is what guarantees
+ * `vault_secrets` exists), then kick off the vault boot resync. The resync
+ * itself waits several more seconds before touching the DB — see
+ * vault-boot-resync.ts — so this ordering is a belt-and-suspenders
+ * guarantee, not a hard dependency.
+ */
+export default async (nitroApp: any) => {
+  await runDispatchMigrations(nitroApp);
+  scheduleVaultBootResync();
+};

package/src/server/plugins/integrations.ts

@@ -0,0 +1,82 @@
+import { createIntegrationsPlugin } from "@agent-native/core/server";
+
+import { dispatchActions } from "../../actions/index.js";
+import { getDispatchConfig } from "../index.js";
+import {
+  beforeDispatchProcess,
+  resolveDispatchExecutionContext,
+} from "../lib/dispatch-integrations.js";
+
+const dispatchIntegrationActions = {
+  ...dispatchActions,
+  // Messaging integrations should use the core call-agent tool for cross-app
+  // delegation because it queues A2A continuations when serverless budgets are
+  // tight. The MCP-facing ask_app action is still available outside this path.
+  ask_app: {
+    ...dispatchActions.ask_app,
+    agentTool: false,
+  },
+};
+
+const DISPATCH_INTEGRATION_SYSTEM_PROMPT = `You are the central dispatch for this workspace, responding via a messaging platform integration (Slack, Telegram, email, etc.).
+
+Default posture:
+- Treat Slack, Telegram, and email as shared entrypoints into the workspace.
+- 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), 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.
+- Hosted/connected A2A neighbors such as Analytics and Content come from the available-apps context or list-connected-agents. list-workspace-apps only inventories apps mounted inside this workspace deployment; never use a missing row there to conclude that a connected agent is unavailable.
+- When asked whether a mounted workspace app exposes an agent card or A2A endpoint, 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, 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.
+- Integration grants are not provider capability limits. For ad hoc provider inspection, querying, reporting, or troubleshooting, call provider-api-catalog/provider-api-docs, then provider-api-request against the provider's real HTTP API. Use connectionId for a specific shared grant and accountId for a specific OAuth account. Never expose secret values or silently widen app access while doing this.
+- 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.
+
+When a user asks for something:
+- If it belongs to analytics, content, slides, clips, assets, etc., delegate via call-agent — do not re-implement the domain logic in dispatch.
+- Synthetic uptime, health-check, and URL-availability monitors belong to Analytics, even when the monitored target is another app such as Clips. Delegate creation to Analytics and relay its exact monitor URL. Dispatch-native recurring jobs are for reminders, digests, and agent workflows, not HTTP uptime probes.
+- Route by the requested artifact type, not by organization-specific names stored in code. For structured records, databases, tables, queues, boards, and intake forms, resolve the owning app and canonical destination from loaded workspace instructions/resources plus discovered app capabilities; do not assume Content, a database ID, schema, owner, or required fields. Visual designs, mockups, wireframes, screens, and interfaces belong to Design. A trusted Required target agent hint in integration context is authoritative.
+- When delegating structured intake to the resolved owning app, preserve the exact Source thread URL and the workspace instruction context, inspect the destination's current required fields, ask only for missing values, submit once, verify the saved record, and return the exact link.
+- In messaging integrations, use call-agent for cross-app delegation; do not use ask_app.
+- 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 user asks to rename an existing workspace app or change its Dispatch title/description, call update-workspace-app-metadata with the existing appId from list-workspace-apps. Do not call start-workspace-app-creation for a metadata-only edit because that starts a new app and Builder branch.
+- 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 app from that template.
+- If the chat 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 "Chat", "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/chat or another existing app unless the user explicitly asks to modify that existing app. When the prompt contains a source brief or concrete repeatable workflow, choose recommended defaults and do not ask non-blocking product or UX questions; ask only for authorization, credentials, a destructive action, an ambiguous target workspace, or a genuinely missing workflow. 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 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. Dispatch reuses the connected workspace Builder project or provisions it through the Builder Projects API when an organization owner/admin starts the first app; members need an owner/admin to configure the project first. Do not ask the user to use Builder org/beta settings. If it returns mode "builder-unavailable", the action also returns a \`reason\` code plus a user-facing \`message\` and (for some reasons) an operator-facing \`detail\`. Relay the \`message\` to the user as-is; only surface \`detail\` when the user is clearly an operator debugging the deployment (e.g. troubleshooting a broken Builder connection for the workspace), never as routine detail for an end user.
+- 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).
+- If a task requires many steps, summarize what you did rather than streaming every detail.`;
+
+/**
+ * Defer plugin construction until the Nitro plugin actually fires so the
+ * config-aware system prompt resolves AFTER `setupDispatch(config)` has
+ * stamped the active config (plugin module load order is not guaranteed).
+ */
+const dispatchIntegrationsPlugin = async (nitroApp: any) => {
+  const { integrations = {} } = getDispatchConfig();
+  const promptOverride = integrations.systemPrompt;
+  const systemPrompt =
+    typeof promptOverride === "string"
+      ? promptOverride
+      : typeof promptOverride === "function"
+        ? promptOverride(DISPATCH_INTEGRATION_SYSTEM_PROMPT)
+        : DISPATCH_INTEGRATION_SYSTEM_PROMPT;
+
+  const plugin = createIntegrationsPlugin({
+    appId: "dispatch",
+    actions: dispatchIntegrationActions,
+    resolveExecutionContext: resolveDispatchExecutionContext,
+    beforeProcess: beforeDispatchProcess,
+    systemPrompt,
+    // Inherit the framework default (claude-sonnet-4-6 from
+    // packages/core/src/integrations/plugin.ts). Haiku was tried for latency
+    // but hallucinated URLs/IDs after delegated call-agent results
+    // (e.g. inventing `https://slides.workspace.com/deck/builder-io-deck-2024`).
+  });
+
+  return plugin(nitroApp);
+};
+
+export default dispatchIntegrationsPlugin;

package/src/shared/app-roles.ts

@@ -0,0 +1,8 @@
+import type { AppRolesDescriptor } from "@agent-native/core/client/org";
+
+export const dispatchAccessDescriptor = {
+  appId: "dispatch",
+  roles: ["admin"] as const,
+  roleLabels: { admin: "Dispatch admin" },
+  label: "Dispatch access",
+} satisfies AppRolesDescriptor<"admin">;

package/src/shared/chat-first-pane.ts

@@ -0,0 +1,7 @@
+/**
+ * Application-state key holding the workspace app the chat-first shell has on
+ * screen. In chat-first mode the app opens as a surface tab while the route
+ * stays on /chat, so this key is the only signal that names the open app.
+ * Written by the layout, read by view-screen — keep them on this one constant.
+ */
+export const CHAT_FIRST_PANE_STATE_KEY = "chat-first-pane";

package/src/shared/feature-flags.ts

@@ -0,0 +1,20 @@
+import { defineFeatureFlag } from "@agent-native/core/feature-flags/registry";
+
+/**
+ * Browser-only rollout for app-scoped sessions in Dispatch panes. The server
+ * action checks this flag too; the client hook only selects the presentation
+ * path and keeps the legacy embed route available while the flag is off.
+ */
+export const DISPATCH_WORKSPACE_SSO_FLAG = defineFeatureFlag({
+  key: "dispatch.workspace-sso",
+  displayName: "Dispatch workspace sign-in",
+  description:
+    "Let Dispatch use the signed-in workspace identity for exact registered app panes.",
+});
+
+export const DISPATCH_WORKSPACE_APP_LIST_FLAG = defineFeatureFlag({
+  key: "dispatch.workspace-app-list",
+  displayName: "Workspace app list",
+  description:
+    "Show apps from the signed-in workspace in native desktop and mobile app lists.",
+});

package/src/shared/workspace-app-chat.ts

@@ -0,0 +1,45 @@
+/**
+ * Route contract for the Dispatch → workspace app agent-chat proxy.
+ *
+ * When an app is open in Dispatch, its chat rail must talk to that app's own
+ * agent (its tools, its AGENTS.md and skills, its org resources, its dev-mode
+ * surface) instead of to Dispatch's agent. The rail points `apiUrl` at this
+ * Dispatch-side prefix and the server forwards the whole agent-chat subtree to
+ * the app's `/_agent-native/agent-chat`, exactly as the Desktop loopback relay
+ * does. Shared so the browser can build the URL without importing server code.
+ */
+
+export const WORKSPACE_APP_CHAT_PROXY_PREFIX =
+  "/_agent-native/workspace-app-chat";
+
+/** Dispatch-relative base URL the chat rail uses as its `apiUrl`. */
+export function workspaceAppChatProxyPath(appId: string): string {
+  return `${WORKSPACE_APP_CHAT_PROXY_PREFIX}/${encodeURIComponent(appId.trim())}`;
+}
+
+/**
+ * Split `/<appId>[/rest]` off a request that already matched the prefix.
+ * Returns null when there is no app segment, so the route fails loudly instead
+ * of proxying to an unresolved target.
+ */
+export function parseWorkspaceAppChatProxyPath(
+  pathname: string,
+): { appId: string; targetSubPath: string } | null {
+  const index = pathname.indexOf(WORKSPACE_APP_CHAT_PROXY_PREFIX);
+  if (index < 0) return null;
+  const rest = pathname.slice(index + WORKSPACE_APP_CHAT_PROXY_PREFIX.length);
+  if (!rest.startsWith("/")) return null;
+  const segments = rest.slice(1).split("/");
+  const rawAppId = segments.shift() ?? "";
+  let appId: string;
+  try {
+    appId = decodeURIComponent(rawAppId).trim();
+  } catch {
+    // coercion-ok: malformed percent-encoding names no workspace app.
+    return null;
+  }
+  if (!appId) return null;
+  const targetSubPath = segments.length > 0 ? `/${segments.join("/")}` : "";
+  if (targetSubPath.includes("..")) return null;
+  return { appId, targetSubPath };
+}

package/src/shared/workspace-sso.ts

@@ -0,0 +1,173 @@
+import { DISPATCH_WORKSPACE_SSO_FLAG } from "./feature-flags.js";
+
+export { DISPATCH_WORKSPACE_SSO_FLAG };
+
+/** Exact first-party origins. Never replace this with a suffix or wildcard. */
+export const CANONICAL_WORKSPACE_SSO_APP_ORIGINS = {
+  analytics: "https://analytics.agent-native.com",
+  assets: "https://assets.agent-native.com",
+  brain: "https://brain.agent-native.com",
+  calendar: "https://calendar.agent-native.com",
+  chat: "https://chat.agent-native.com",
+  clips: "https://clips.agent-native.com",
+  content: "https://content.agent-native.com",
+  crm: "https://crm.agent-native.com",
+  design: "https://design.agent-native.com",
+  dispatch: "https://dispatch.agent-native.com",
+  forms: "https://forms.agent-native.com",
+  macros: "https://macros.agent-native.com",
+  mail: "https://mail.agent-native.com",
+  plan: "https://plan.agent-native.com",
+  slides: "https://slides.agent-native.com",
+  tasks: "https://tasks.agent-native.com",
+} as const;
+
+export const WORKSPACE_SSO_CALLBACK_PATH =
+  "/_agent-native/identity/callback" as const;
+
+const CONTROL_CHARS = /[\u0000-\u001f\u007f]/;
+const APP_ID = /^[a-z0-9](?:[a-z0-9-]*[a-z0-9])?$/;
+const CLIENT_ID = /^[A-Za-z0-9][A-Za-z0-9._:-]{0,127}$/;
+const LOCALHOST_HOSTS = new Set(["localhost", "127.0.0.1", "[::1]", "::1"]);
+
+export interface WorkspaceSsoAppRegistration {
+  appId: string;
+  clientId: string;
+  origin: string;
+  callbackPath: typeof WORKSPACE_SSO_CALLBACK_PATH;
+}
+
+export function exactWorkspaceSsoOrigin(raw: unknown): string | null {
+  if (typeof raw !== "string" || !raw || CONTROL_CHARS.test(raw)) return null;
+  try {
+    const url = new URL(raw);
+    if (
+      url.protocol !== "https:" &&
+      !(url.protocol === "http:" && LOCALHOST_HOSTS.has(url.hostname))
+    ) {
+      return null;
+    }
+    if (
+      url.username ||
+      url.password ||
+      url.pathname !== "/" ||
+      url.search ||
+      url.hash
+    ) {
+      return null;
+    }
+    return url.origin;
+  } catch {
+    // coercion-ok: malformed registry origins are rejected as absent.
+    return null;
+  }
+}
+
+/**
+ * Parse the same additive custom registry used by browser identity SSO. The
+ * raw value is passed in so this shared module stays safe to import in the
+ * browser bundle.
+ */
+export function parseWorkspaceSsoAppRegistrations(
+  raw: unknown,
+): WorkspaceSsoAppRegistration[] {
+  if (typeof raw !== "string" || !raw.trim()) return [];
+  let value: unknown;
+  try {
+    value = JSON.parse(raw);
+  } catch {
+    // coercion-ok: malformed custom registry data must fail closed.
+    return [];
+  }
+  if (!Array.isArray(value)) return [];
+
+  const registrations: WorkspaceSsoAppRegistration[] = [];
+  const seen = new Set<string>();
+  for (const entry of value) {
+    if (!entry || typeof entry !== "object") continue;
+    const candidate = entry as Record<string, unknown>;
+    const appId = candidate.appId;
+    const clientId = candidate.clientId;
+    const origin = exactWorkspaceSsoOrigin(candidate.origin);
+    if (
+      typeof appId !== "string" ||
+      !APP_ID.test(appId) ||
+      typeof clientId !== "string" ||
+      !CLIENT_ID.test(clientId) ||
+      !origin ||
+      candidate.callbackPath !== WORKSPACE_SSO_CALLBACK_PATH ||
+      !Array.isArray(candidate.capabilities) ||
+      !candidate.capabilities.includes("identity-sso") ||
+      seen.has(appId) ||
+      Object.prototype.hasOwnProperty.call(
+        CANONICAL_WORKSPACE_SSO_APP_ORIGINS,
+        appId,
+      )
+    ) {
+      continue;
+    }
+    seen.add(appId);
+    registrations.push({
+      appId,
+      clientId,
+      origin,
+      callbackPath: WORKSPACE_SSO_CALLBACK_PATH,
+    });
+  }
+  return registrations;
+}
+
+function appOrigin(rawUrl: unknown): string | null {
+  if (typeof rawUrl !== "string" || !rawUrl.trim()) return null;
+  try {
+    const url = new URL(rawUrl.trim());
+    return url.protocol === "http:" || url.protocol === "https:"
+      ? url.origin
+      : null;
+  } catch {
+    // coercion-ok: malformed app metadata is not eligible for workspace SSO.
+    return null;
+  }
+}
+
+function isLoopbackOrigin(origin: string): boolean {
+  try {
+    return LOCALHOST_HOSTS.has(new URL(origin).hostname);
+  } catch {
+    // coercion-ok: only a previously parsed origin reaches this helper.
+    return false;
+  }
+}
+
+/**
+ * Keep the server-side app catalog and the browser's action choice on the
+ * same exact-origin rules. `registryRaw` is deliberately supplied by the
+ * caller so this shared module never reads process or browser environment.
+ */
+export function isWorkspaceSsoAppUrl(
+  app: { id: string; url?: unknown },
+  options: { nodeEnv?: string; registryRaw?: unknown } = {},
+): boolean {
+  const origin = appOrigin(app.url);
+  if (!origin) return false;
+
+  const appId = app.id.trim().toLowerCase();
+  const canonicalOrigin =
+    CANONICAL_WORKSPACE_SSO_APP_ORIGINS[
+      appId as keyof typeof CANONICAL_WORKSPACE_SSO_APP_ORIGINS
+    ];
+  if (canonicalOrigin === origin) return true;
+
+  if (
+    options.nodeEnv !== "production" &&
+    canonicalOrigin &&
+    isLoopbackOrigin(origin)
+  ) {
+    return true;
+  }
+
+  return parseWorkspaceSsoAppRegistrations(options.registryRaw).some(
+    (registration) =>
+      registration.appId === appId && registration.origin === origin,
+  );
+}