@agent-native/dispatch 0.41.1-nightly-20261104110058 → 0.42.0

package/dist/server/lib/app-roles.d.ts

@@ -1,3 +1,5 @@
 import type { ActionRunContext } from "@agent-native/core/action";
 export declare function authorizeDispatchAdmin(_args: unknown, ctx?: ActionRunContext): Promise<void>;
+/** Organization owners and admins only; Dispatch admin roles do not count. */
+export declare function authorizeOrgOwnerOrAdmin(_args: unknown, ctx?: ActionRunContext): Promise<void>;
 //# sourceMappingURL=app-roles.d.ts.map

package/dist/server/lib/app-roles.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"app-roles.d.ts","sourceRoot":"","sources":["../../../src/server/lib/app-roles.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,2BAA2B,CAAC;AAwBlE,wBAAsB,sBAAsB,CAC1C,KAAK,EAAE,OAAO,EACd,GAAG,CAAC,EAAE,gBAAgB,GACrB,OAAO,CAAC,IAAI,CAAC,CAoCf"}
+{"version":3,"file":"app-roles.d.ts","sourceRoot":"","sources":["../../../src/server/lib/app-roles.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,2BAA2B,CAAC;AAiElE,wBAAsB,sBAAsB,CAC1C,KAAK,EAAE,OAAO,EACd,GAAG,CAAC,EAAE,gBAAgB,GACrB,OAAO,CAAC,IAAI,CAAC,CAUf;AAED,8EAA8E;AAC9E,wBAAsB,wBAAwB,CAC5C,KAAK,EAAE,OAAO,EACd,GAAG,CAAC,EAAE,gBAAgB,GACrB,OAAO,CAAC,IAAI,CAAC,CAWf"}

package/dist/server/lib/app-roles.js

@@ -8,14 +8,18 @@ function getDispatchAccess() {
         allowOrgAdmins: true,
     }));
 }
-export async function authorizeDispatchAdmin(_args, ctx) {
+/**
+ * The caller's active membership in the request org, or null when there is no
+ * org to check (a user without one, or standalone Dispatch with no org tables).
+ */
+async function requireActiveMembership(ctx, action) {
     const email = ctx?.userEmail !== undefined ? ctx.userEmail : getRequestUserEmail();
     const orgId = ctx?.orgId !== undefined ? ctx.orgId : getRequestOrgId();
     if (!email?.trim()) {
-        throw new ForbiddenError("Dispatch administration requires an authenticated user.");
+        throw new ForbiddenError(`${action} requires an authenticated user.`);
     }
     if (!orgId?.trim())
-        return;
+        return null;
     let membership;
     try {
         membership = await validateFederatedOrganizationMembershipForCurrentRequest({
@@ -26,16 +30,31 @@ export async function authorizeDispatchAdmin(_args, ctx) {
     catch (error) {
         if (isMissingOrganizationTableError(error) &&
             isStandaloneDispatchRuntime()) {
-            return;
+            return null;
         }
         throw error;
     }
     if (!membership.active) {
-        throw new ForbiddenError("Dispatch administration requires active organization membership.");
+        throw new ForbiddenError(`${action} requires active organization membership.`);
     }
+    return { email, orgId, role: membership.role };
+}
+export async function authorizeDispatchAdmin(_args, ctx) {
+    const membership = await requireActiveMembership(ctx, "Dispatch administration");
+    if (!membership)
+        return;
     await getDispatchAccess().assertPermission(["administer"], {
-        userEmail: email,
-        orgId,
+        userEmail: membership.email,
+        orgId: membership.orgId,
     });
 }
+/** Organization owners and admins only; Dispatch admin roles do not count. */
+export async function authorizeOrgOwnerOrAdmin(_args, ctx) {
+    const membership = await requireActiveMembership(ctx, "This organization setting");
+    if (!membership)
+        return;
+    if (membership.role !== "owner" && membership.role !== "admin") {
+        throw new ForbiddenError("Only organization owners and admins can change this setting.");
+    }
+}
 //# sourceMappingURL=app-roles.js.map

package/dist/server/lib/app-roles.js.map

@@ -1 +1 @@
-{"version":3,"file":"app-roles.js","sourceRoot":"","sources":["../../../src/server/lib/app-roles.ts"],"names":[],"mappings":"AACA,OAAO,EACL,cAAc,EACd,+BAA+B,EAC/B,2BAA2B,EAE3B,wDAAwD,GACzD,MAAM,wBAAwB,CAAC;AAChC,OAAO,EACL,eAAe,EACf,mBAAmB,GACpB,MAAM,2BAA2B,CAAC;AACnC,OAAO,EAAE,cAAc,EAAE,MAAM,4BAA4B,CAAC;AAE5D,OAAO,EAAE,wBAAwB,EAAE,MAAM,2BAA2B,CAAC;AAErE,IAAI,cAA2D,CAAC;AAEhE,SAAS,iBAAiB;IACxB,OAAO,CAAC,cAAc,KAAK,cAAc,CAAC,wBAAwB,EAAE;QAClE,cAAc,EAAE,IAAI;KACrB,CAAC,CAAC,CAAC;AACN,CAAC;AAED,MAAM,CAAC,KAAK,UAAU,sBAAsB,CAC1C,KAAc,EACd,GAAsB;IAEtB,MAAM,KAAK,GACT,GAAG,EAAE,SAAS,KAAK,SAAS,CAAC,CAAC,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC,CAAC,mBAAmB,EAAE,CAAC;IACvE,MAAM,KAAK,GAAG,GAAG,EAAE,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,GAAG,CAAC,KAAK,CAAC,CAAC,CAAC,eAAe,EAAE,CAAC;IACvE,IAAI,CAAC,KAAK,EAAE,IAAI,EAAE,EAAE,CAAC;QACnB,MAAM,IAAI,cAAc,CACtB,yDAAyD,CAC1D,CAAC;IACJ,CAAC;IACD,IAAI,CAAC,KAAK,EAAE,IAAI,EAAE;QAAE,OAAO;IAC3B,IAAI,UAAU,CAAC;IACf,IAAI,CAAC;QACH,UAAU,GAAG,MAAM,wDAAwD,CACzE;YACE,KAAK;YACL,KAAK;SACN,CACF,CAAC;IACJ,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACf,IACE,+BAA+B,CAAC,KAAK,CAAC;YACtC,2BAA2B,EAAE,EAC7B,CAAC;YACD,OAAO;QACT,CAAC;QACD,MAAM,KAAK,CAAC;IACd,CAAC;IACD,IAAI,CAAC,UAAU,CAAC,MAAM,EAAE,CAAC;QACvB,MAAM,IAAI,cAAc,CACtB,kEAAkE,CACnE,CAAC;IACJ,CAAC;IACD,MAAM,iBAAiB,EAAE,CAAC,gBAAgB,CAAC,CAAC,YAAY,CAAC,EAAE;QACzD,SAAS,EAAE,KAAK;QAChB,KAAK;KACN,CAAC,CAAC;AACL,CAAC","sourcesContent":["import type { ActionRunContext } from \"@agent-native/core/action\";\nimport {\n  defineAppRoles,\n  isMissingOrganizationTableError,\n  isStandaloneDispatchRuntime,\n  type AppRoles,\n  validateFederatedOrganizationMembershipForCurrentRequest,\n} from \"@agent-native/core/org\";\nimport {\n  getRequestOrgId,\n  getRequestUserEmail,\n} from \"@agent-native/core/server\";\nimport { ForbiddenError } from \"@agent-native/core/sharing\";\n\nimport { dispatchAccessDescriptor } from \"../../shared/app-roles.js\";\n\nlet dispatchAccess: AppRoles<\"admin\", \"administer\"> | undefined;\n\nfunction getDispatchAccess(): AppRoles<\"admin\", \"administer\"> {\n  return (dispatchAccess ??= defineAppRoles(dispatchAccessDescriptor, {\n    allowOrgAdmins: true,\n  }));\n}\n\nexport async function authorizeDispatchAdmin(\n  _args: unknown,\n  ctx?: ActionRunContext,\n): Promise<void> {\n  const email =\n    ctx?.userEmail !== undefined ? ctx.userEmail : getRequestUserEmail();\n  const orgId = ctx?.orgId !== undefined ? ctx.orgId : getRequestOrgId();\n  if (!email?.trim()) {\n    throw new ForbiddenError(\n      \"Dispatch administration requires an authenticated user.\",\n    );\n  }\n  if (!orgId?.trim()) return;\n  let membership;\n  try {\n    membership = await validateFederatedOrganizationMembershipForCurrentRequest(\n      {\n        orgId,\n        email,\n      },\n    );\n  } catch (error) {\n    if (\n      isMissingOrganizationTableError(error) &&\n      isStandaloneDispatchRuntime()\n    ) {\n      return;\n    }\n    throw error;\n  }\n  if (!membership.active) {\n    throw new ForbiddenError(\n      \"Dispatch administration requires active organization membership.\",\n    );\n  }\n  await getDispatchAccess().assertPermission([\"administer\"], {\n    userEmail: email,\n    orgId,\n  });\n}\n"]}
+{"version":3,"file":"app-roles.js","sourceRoot":"","sources":["../../../src/server/lib/app-roles.ts"],"names":[],"mappings":"AACA,OAAO,EACL,cAAc,EACd,+BAA+B,EAC/B,2BAA2B,EAG3B,wDAAwD,GACzD,MAAM,wBAAwB,CAAC;AAChC,OAAO,EACL,eAAe,EACf,mBAAmB,GACpB,MAAM,2BAA2B,CAAC;AACnC,OAAO,EAAE,cAAc,EAAE,MAAM,4BAA4B,CAAC;AAE5D,OAAO,EAAE,wBAAwB,EAAE,MAAM,2BAA2B,CAAC;AAErE,IAAI,cAA2D,CAAC;AAEhE,SAAS,iBAAiB;IACxB,OAAO,CAAC,cAAc,KAAK,cAAc,CAAC,wBAAwB,EAAE;QAClE,cAAc,EAAE,IAAI;KACrB,CAAC,CAAC,CAAC;AACN,CAAC;AAED;;;GAGG;AACH,KAAK,UAAU,uBAAuB,CACpC,GAAiC,EACjC,MAAc;IAEd,MAAM,KAAK,GACT,GAAG,EAAE,SAAS,KAAK,SAAS,CAAC,CAAC,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC,CAAC,mBAAmB,EAAE,CAAC;IACvE,MAAM,KAAK,GAAG,GAAG,EAAE,KAAK,KAAK,SAAS,CAAC,CAAC,CAAC,GAAG,CAAC,KAAK,CAAC,CAAC,CAAC,eAAe,EAAE,CAAC;IACvE,IAAI,CAAC,KAAK,EAAE,IAAI,EAAE,EAAE,CAAC;QACnB,MAAM,IAAI,cAAc,CAAC,GAAG,MAAM,kCAAkC,CAAC,CAAC;IACxE,CAAC;IACD,IAAI,CAAC,KAAK,EAAE,IAAI,EAAE;QAAE,OAAO,IAAI,CAAC;IAChC,IAAI,UAAU,CAAC;IACf,IAAI,CAAC;QACH,UAAU,GAAG,MAAM,wDAAwD,CACzE;YACE,KAAK;YACL,KAAK;SACN,CACF,CAAC;IACJ,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACf,IACE,+BAA+B,CAAC,KAAK,CAAC;YACtC,2BAA2B,EAAE,EAC7B,CAAC;YACD,OAAO,IAAI,CAAC;QACd,CAAC;QACD,MAAM,KAAK,CAAC;IACd,CAAC;IACD,IAAI,CAAC,UAAU,CAAC,MAAM,EAAE,CAAC;QACvB,MAAM,IAAI,cAAc,CACtB,GAAG,MAAM,2CAA2C,CACrD,CAAC;IACJ,CAAC;IACD,OAAO,EAAE,KAAK,EAAE,KAAK,EAAE,IAAI,EAAE,UAAU,CAAC,IAAI,EAAE,CAAC;AACjD,CAAC;AAED,MAAM,CAAC,KAAK,UAAU,sBAAsB,CAC1C,KAAc,EACd,GAAsB;IAEtB,MAAM,UAAU,GAAG,MAAM,uBAAuB,CAC9C,GAAG,EACH,yBAAyB,CAC1B,CAAC;IACF,IAAI,CAAC,UAAU;QAAE,OAAO;IACxB,MAAM,iBAAiB,EAAE,CAAC,gBAAgB,CAAC,CAAC,YAAY,CAAC,EAAE;QACzD,SAAS,EAAE,UAAU,CAAC,KAAK;QAC3B,KAAK,EAAE,UAAU,CAAC,KAAK;KACxB,CAAC,CAAC;AACL,CAAC;AAED,8EAA8E;AAC9E,MAAM,CAAC,KAAK,UAAU,wBAAwB,CAC5C,KAAc,EACd,GAAsB;IAEtB,MAAM,UAAU,GAAG,MAAM,uBAAuB,CAC9C,GAAG,EACH,2BAA2B,CAC5B,CAAC;IACF,IAAI,CAAC,UAAU;QAAE,OAAO;IACxB,IAAI,UAAU,CAAC,IAAI,KAAK,OAAO,IAAI,UAAU,CAAC,IAAI,KAAK,OAAO,EAAE,CAAC;QAC/D,MAAM,IAAI,cAAc,CACtB,8DAA8D,CAC/D,CAAC;IACJ,CAAC;AACH,CAAC","sourcesContent":["import type { ActionRunContext } from \"@agent-native/core/action\";\nimport {\n  defineAppRoles,\n  isMissingOrganizationTableError,\n  isStandaloneDispatchRuntime,\n  type AppRoles,\n  type OrgRole,\n  validateFederatedOrganizationMembershipForCurrentRequest,\n} from \"@agent-native/core/org\";\nimport {\n  getRequestOrgId,\n  getRequestUserEmail,\n} from \"@agent-native/core/server\";\nimport { ForbiddenError } from \"@agent-native/core/sharing\";\n\nimport { dispatchAccessDescriptor } from \"../../shared/app-roles.js\";\n\nlet dispatchAccess: AppRoles<\"admin\", \"administer\"> | undefined;\n\nfunction getDispatchAccess(): AppRoles<\"admin\", \"administer\"> {\n  return (dispatchAccess ??= defineAppRoles(dispatchAccessDescriptor, {\n    allowOrgAdmins: true,\n  }));\n}\n\n/**\n * The caller's active membership in the request org, or null when there is no\n * org to check (a user without one, or standalone Dispatch with no org tables).\n */\nasync function requireActiveMembership(\n  ctx: ActionRunContext | undefined,\n  action: string,\n): Promise<{ email: string; orgId: string; role: OrgRole } | null> {\n  const email =\n    ctx?.userEmail !== undefined ? ctx.userEmail : getRequestUserEmail();\n  const orgId = ctx?.orgId !== undefined ? ctx.orgId : getRequestOrgId();\n  if (!email?.trim()) {\n    throw new ForbiddenError(`${action} requires an authenticated user.`);\n  }\n  if (!orgId?.trim()) return null;\n  let membership;\n  try {\n    membership = await validateFederatedOrganizationMembershipForCurrentRequest(\n      {\n        orgId,\n        email,\n      },\n    );\n  } catch (error) {\n    if (\n      isMissingOrganizationTableError(error) &&\n      isStandaloneDispatchRuntime()\n    ) {\n      return null;\n    }\n    throw error;\n  }\n  if (!membership.active) {\n    throw new ForbiddenError(\n      `${action} requires active organization membership.`,\n    );\n  }\n  return { email, orgId, role: membership.role };\n}\n\nexport async function authorizeDispatchAdmin(\n  _args: unknown,\n  ctx?: ActionRunContext,\n): Promise<void> {\n  const membership = await requireActiveMembership(\n    ctx,\n    \"Dispatch administration\",\n  );\n  if (!membership) return;\n  await getDispatchAccess().assertPermission([\"administer\"], {\n    userEmail: membership.email,\n    orgId: membership.orgId,\n  });\n}\n\n/** Organization owners and admins only; Dispatch admin roles do not count. */\nexport async function authorizeOrgOwnerOrAdmin(\n  _args: unknown,\n  ctx?: ActionRunContext,\n): Promise<void> {\n  const membership = await requireActiveMembership(\n    ctx,\n    \"This organization setting\",\n  );\n  if (!membership) return;\n  if (membership.role !== \"owner\" && membership.role !== \"admin\") {\n    throw new ForbiddenError(\n      \"Only organization owners and admins can change this setting.\",\n    );\n  }\n}\n"]}

package/dist/server/lib/hosted-apps-settings-schema.d.ts

@@ -0,0 +1,6 @@
+import { z } from "zod";
+/** Result of the get/set hosted-apps actions. */
+export declare const hostedAppsSettingsViewSchema: z.ZodObject<{
+    showHostedApps: z.ZodBoolean;
+}, z.core.$strip>;
+//# sourceMappingURL=hosted-apps-settings-schema.d.ts.map

package/dist/server/lib/hosted-apps-settings-schema.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"hosted-apps-settings-schema.d.ts","sourceRoot":"","sources":["../../../src/server/lib/hosted-apps-settings-schema.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB,iDAAiD;AACjD,eAAO,MAAM,4BAA4B;;iBAEvC,CAAC"}

package/dist/server/lib/hosted-apps-settings-schema.js

@@ -0,0 +1,6 @@
+import { z } from "zod";
+/** Result of the get/set hosted-apps actions. */
+export const hostedAppsSettingsViewSchema = z.object({
+    showHostedApps: z.boolean(),
+});
+//# sourceMappingURL=hosted-apps-settings-schema.js.map

package/dist/server/lib/hosted-apps-settings-schema.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"hosted-apps-settings-schema.js","sourceRoot":"","sources":["../../../src/server/lib/hosted-apps-settings-schema.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB,iDAAiD;AACjD,MAAM,CAAC,MAAM,4BAA4B,GAAG,CAAC,CAAC,MAAM,CAAC;IACnD,cAAc,EAAE,CAAC,CAAC,OAAO,EAAE;CAC5B,CAAC,CAAC","sourcesContent":["import { z } from \"zod\";\n\n/** Result of the get/set hosted-apps actions. */\nexport const hostedAppsSettingsViewSchema = z.object({\n  showHostedApps: z.boolean(),\n});\n"]}

package/dist/server/lib/hosted-apps-settings.d.ts

@@ -0,0 +1,27 @@
+import { ActionContractError } from "@agent-native/core/action";
+import { type DiscoveredAgent } from "@agent-native/core/server/agent-discovery";
+export declare const HOSTED_APPS_SETTINGS_KEY = "dispatch-hosted-apps-settings";
+export interface HostedAppsSettings {
+    showHostedApps: boolean;
+}
+export declare class InvalidHostedAppsSettingsError extends ActionContractError {
+    constructor();
+}
+/**
+ * Built-in catalog apps this workspace offers. A mounted workspace app with a
+ * built-in's id is a workspace app; the built-in config never applies to it.
+ */
+export declare function listHostedApps(): Promise<DiscoveredAgent[]>;
+/**
+ * The stored setting. An unreadable value is `invalid` and hides hosted apps,
+ * so it cannot fail the app lists or agent context; Settings reports it.
+ */
+export declare function readHostedAppsSettings(): Promise<HostedAppsSettings & {
+    invalid: boolean;
+}>;
+export declare function setHostedAppsSettings(next: HostedAppsSettings): Promise<HostedAppsSettings>;
+/** Hides hosted apps from Dispatch's lists and agent context when off. */
+export declare function hideHostedAppsWhenOff<T extends {
+    id: string;
+}>(agents: T[]): Promise<T[]>;
+//# sourceMappingURL=hosted-apps-settings.d.ts.map

package/dist/server/lib/hosted-apps-settings.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"hosted-apps-settings.d.ts","sourceRoot":"","sources":["../../../src/server/lib/hosted-apps-settings.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,mBAAmB,EAAE,MAAM,2BAA2B,CAAC;AAKhE,OAAO,EAIL,KAAK,eAAe,EACrB,MAAM,2CAA2C,CAAC;AAUnD,eAAO,MAAM,wBAAwB,kCAAkC,CAAC;AAExE,MAAM,WAAW,kBAAkB;IACjC,cAAc,EAAE,OAAO,CAAC;CACzB;AAID,qBAAa,8BAA+B,SAAQ,mBAAmB;IACrE,cAMC;CACF;AAED;;;GAGG;AACH,wBAAsB,cAAc,IAAI,OAAO,CAAC,eAAe,EAAE,CAAC,CAQjE;AASD;;;GAGG;AACH,wBAAsB,sBAAsB,IAAI,OAAO,CACrD,kBAAkB,GAAG;IAAE,OAAO,EAAE,OAAO,CAAA;CAAE,CAC1C,CAaA;AAED,wBAAsB,qBAAqB,CACzC,IAAI,EAAE,kBAAkB,GACvB,OAAO,CAAC,kBAAkB,CAAC,CAe7B;AAED,0EAA0E;AAC1E,wBAAsB,qBAAqB,CAAC,CAAC,SAAS;IAAE,EAAE,EAAE,MAAM,CAAA;CAAE,EAClE,MAAM,EAAE,CAAC,EAAE,GACV,OAAO,CAAC,CAAC,EAAE,CAAC,CAKd"}

package/dist/server/lib/hosted-apps-settings.js

@@ -0,0 +1,72 @@
+import { ActionContractError } from "@agent-native/core/action";
+import { getRequestOrgId, getRequestUserEmail, } from "@agent-native/core/server";
+import { getBuiltinAgents, loadWorkspaceAppsManifest, normalizeAgentId, } from "@agent-native/core/server/agent-discovery";
+import { getOrgSetting, getUserSetting, putOrgSetting, putUserSetting, } from "@agent-native/core/settings";
+import { HOSTED_APPS_SETTINGS_INVALID_ERROR_CODE } from "../../shared/hosted-apps-settings.js";
+export const HOSTED_APPS_SETTINGS_KEY = "dispatch-hosted-apps-settings";
+// A contract error, so its code reaches Settings, which offers the save that
+// repairs it; a bare error would arrive as an anonymous 500.
+export class InvalidHostedAppsSettingsError extends ActionContractError {
+    constructor() {
+        super(`Stored ${HOSTED_APPS_SETTINGS_KEY} is not { showHostedApps: boolean }. Save the Agent-Native.com hosted apps setting again to repair it.`, { errorCode: HOSTED_APPS_SETTINGS_INVALID_ERROR_CODE, statusCode: 409 });
+        this.name = "InvalidHostedAppsSettingsError";
+    }
+}
+/**
+ * Built-in catalog apps this workspace offers. A mounted workspace app with a
+ * built-in's id is a workspace app; the built-in config never applies to it.
+ */
+export async function listHostedApps() {
+    const workspaceApps = await loadWorkspaceAppsManifest();
+    const workspaceIds = new Set((workspaceApps ?? []).map((app) => normalizeAgentId(app.id)));
+    return getBuiltinAgents("dispatch").filter((agent) => !workspaceIds.has(agent.id));
+}
+function hostedAppsSettingsScope() {
+    const orgId = getRequestOrgId();
+    if (orgId)
+        return { scope: "org", scopeId: orgId };
+    const email = getRequestUserEmail();
+    return email ? { scope: "user", scopeId: email } : null;
+}
+/**
+ * The stored setting. An unreadable value is `invalid` and hides hosted apps,
+ * so it cannot fail the app lists or agent context; Settings reports it.
+ */
+export async function readHostedAppsSettings() {
+    const scope = hostedAppsSettingsScope();
+    // No org and no user means there is nowhere the setting could be stored.
+    if (!scope)
+        return { showHostedApps: true, invalid: false };
+    const raw = scope.scope === "org"
+        ? await getOrgSetting(scope.scopeId, HOSTED_APPS_SETTINGS_KEY)
+        : await getUserSetting(scope.scopeId, HOSTED_APPS_SETTINGS_KEY);
+    if (raw === null)
+        return { showHostedApps: true, invalid: false };
+    if (typeof raw.showHostedApps !== "boolean") {
+        return { showHostedApps: false, invalid: true };
+    }
+    return { showHostedApps: raw.showHostedApps, invalid: false };
+}
+export async function setHostedAppsSettings(next) {
+    const scope = hostedAppsSettingsScope();
+    if (!scope) {
+        throw Object.assign(new Error("Sign in to change the Agent-Native.com hosted apps setting."), { statusCode: 401 });
+    }
+    const value = { showHostedApps: next.showHostedApps };
+    if (scope.scope === "org") {
+        await putOrgSetting(scope.scopeId, HOSTED_APPS_SETTINGS_KEY, value);
+    }
+    else {
+        await putUserSetting(scope.scopeId, HOSTED_APPS_SETTINGS_KEY, value);
+    }
+    return value;
+}
+/** Hides hosted apps from Dispatch's lists and agent context when off. */
+export async function hideHostedAppsWhenOff(agents) {
+    const { showHostedApps } = await readHostedAppsSettings();
+    if (showHostedApps)
+        return agents;
+    const hostedIds = new Set((await listHostedApps()).map((app) => app.id));
+    return agents.filter((agent) => !hostedIds.has(agent.id));
+}
+//# sourceMappingURL=hosted-apps-settings.js.map

package/dist/server/lib/hosted-apps-settings.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"hosted-apps-settings.js","sourceRoot":"","sources":["../../../src/server/lib/hosted-apps-settings.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,mBAAmB,EAAE,MAAM,2BAA2B,CAAC;AAChE,OAAO,EACL,eAAe,EACf,mBAAmB,GACpB,MAAM,2BAA2B,CAAC;AACnC,OAAO,EACL,gBAAgB,EAChB,yBAAyB,EACzB,gBAAgB,GAEjB,MAAM,2CAA2C,CAAC;AACnD,OAAO,EACL,aAAa,EACb,cAAc,EACd,aAAa,EACb,cAAc,GACf,MAAM,6BAA6B,CAAC;AAErC,OAAO,EAAE,uCAAuC,EAAE,MAAM,sCAAsC,CAAC;AAE/F,MAAM,CAAC,MAAM,wBAAwB,GAAG,+BAA+B,CAAC;AAMxE,6EAA6E;AAC7E,6DAA6D;AAC7D,MAAM,OAAO,8BAA+B,SAAQ,mBAAmB;IACrE;QACE,KAAK,CACH,UAAU,wBAAwB,wGAAwG,EAC1I,EAAE,SAAS,EAAE,uCAAuC,EAAE,UAAU,EAAE,GAAG,EAAE,CACxE,CAAC;QACF,IAAI,CAAC,IAAI,GAAG,gCAAgC,CAAC;IAC/C,CAAC;CACF;AAED;;;GAGG;AACH,MAAM,CAAC,KAAK,UAAU,cAAc;IAClC,MAAM,aAAa,GAAG,MAAM,yBAAyB,EAAE,CAAC;IACxD,MAAM,YAAY,GAAG,IAAI,GAAG,CAC1B,CAAC,aAAa,IAAI,EAAE,CAAC,CAAC,GAAG,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,gBAAgB,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC,CAC7D,CAAC;IACF,OAAO,gBAAgB,CAAC,UAAU,CAAC,CAAC,MAAM,CACxC,CAAC,KAAK,EAAE,EAAE,CAAC,CAAC,YAAY,CAAC,GAAG,CAAC,KAAK,CAAC,EAAE,CAAC,CACvC,CAAC;AACJ,CAAC;AAED,SAAS,uBAAuB;IAC9B,MAAM,KAAK,GAAG,eAAe,EAAE,CAAC;IAChC,IAAI,KAAK;QAAE,OAAO,EAAE,KAAK,EAAE,KAAc,EAAE,OAAO,EAAE,KAAK,EAAE,CAAC;IAC5D,MAAM,KAAK,GAAG,mBAAmB,EAAE,CAAC;IACpC,OAAO,KAAK,CAAC,CAAC,CAAC,EAAE,KAAK,EAAE,MAAe,EAAE,OAAO,EAAE,KAAK,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC;AACnE,CAAC;AAED;;;GAGG;AACH,MAAM,CAAC,KAAK,UAAU,sBAAsB;IAG1C,MAAM,KAAK,GAAG,uBAAuB,EAAE,CAAC;IACxC,yEAAyE;IACzE,IAAI,CAAC,KAAK;QAAE,OAAO,EAAE,cAAc,EAAE,IAAI,EAAE,OAAO,EAAE,KAAK,EAAE,CAAC;IAC5D,MAAM,GAAG,GACP,KAAK,CAAC,KAAK,KAAK,KAAK;QACnB,CAAC,CAAC,MAAM,aAAa,CAAC,KAAK,CAAC,OAAO,EAAE,wBAAwB,CAAC;QAC9D,CAAC,CAAC,MAAM,cAAc,CAAC,KAAK,CAAC,OAAO,EAAE,wBAAwB,CAAC,CAAC;IACpE,IAAI,GAAG,KAAK,IAAI;QAAE,OAAO,EAAE,cAAc,EAAE,IAAI,EAAE,OAAO,EAAE,KAAK,EAAE,CAAC;IAClE,IAAI,OAAO,GAAG,CAAC,cAAc,KAAK,SAAS,EAAE,CAAC;QAC5C,OAAO,EAAE,cAAc,EAAE,KAAK,EAAE,OAAO,EAAE,IAAI,EAAE,CAAC;IAClD,CAAC;IACD,OAAO,EAAE,cAAc,EAAE,GAAG,CAAC,cAAc,EAAE,OAAO,EAAE,KAAK,EAAE,CAAC;AAChE,CAAC;AAED,MAAM,CAAC,KAAK,UAAU,qBAAqB,CACzC,IAAwB;IAExB,MAAM,KAAK,GAAG,uBAAuB,EAAE,CAAC;IACxC,IAAI,CAAC,KAAK,EAAE,CAAC;QACX,MAAM,MAAM,CAAC,MAAM,CACjB,IAAI,KAAK,CAAC,6DAA6D,CAAC,EACxE,EAAE,UAAU,EAAE,GAAG,EAAE,CACpB,CAAC;IACJ,CAAC;IACD,MAAM,KAAK,GAAG,EAAE,cAAc,EAAE,IAAI,CAAC,cAAc,EAAE,CAAC;IACtD,IAAI,KAAK,CAAC,KAAK,KAAK,KAAK,EAAE,CAAC;QAC1B,MAAM,aAAa,CAAC,KAAK,CAAC,OAAO,EAAE,wBAAwB,EAAE,KAAK,CAAC,CAAC;IACtE,CAAC;SAAM,CAAC;QACN,MAAM,cAAc,CAAC,KAAK,CAAC,OAAO,EAAE,wBAAwB,EAAE,KAAK,CAAC,CAAC;IACvE,CAAC;IACD,OAAO,KAAK,CAAC;AACf,CAAC;AAED,0EAA0E;AAC1E,MAAM,CAAC,KAAK,UAAU,qBAAqB,CACzC,MAAW;IAEX,MAAM,EAAE,cAAc,EAAE,GAAG,MAAM,sBAAsB,EAAE,CAAC;IAC1D,IAAI,cAAc;QAAE,OAAO,MAAM,CAAC;IAClC,MAAM,SAAS,GAAG,IAAI,GAAG,CAAC,CAAC,MAAM,cAAc,EAAE,CAAC,CAAC,GAAG,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC,CAAC;IACzE,OAAO,MAAM,CAAC,MAAM,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,CAAC,SAAS,CAAC,GAAG,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC,CAAC;AAC5D,CAAC","sourcesContent":["import { ActionContractError } from \"@agent-native/core/action\";\nimport {\n  getRequestOrgId,\n  getRequestUserEmail,\n} from \"@agent-native/core/server\";\nimport {\n  getBuiltinAgents,\n  loadWorkspaceAppsManifest,\n  normalizeAgentId,\n  type DiscoveredAgent,\n} from \"@agent-native/core/server/agent-discovery\";\nimport {\n  getOrgSetting,\n  getUserSetting,\n  putOrgSetting,\n  putUserSetting,\n} from \"@agent-native/core/settings\";\n\nimport { HOSTED_APPS_SETTINGS_INVALID_ERROR_CODE } from \"../../shared/hosted-apps-settings.js\";\n\nexport const HOSTED_APPS_SETTINGS_KEY = \"dispatch-hosted-apps-settings\";\n\nexport interface HostedAppsSettings {\n  showHostedApps: boolean;\n}\n\n// A contract error, so its code reaches Settings, which offers the save that\n// repairs it; a bare error would arrive as an anonymous 500.\nexport class InvalidHostedAppsSettingsError extends ActionContractError {\n  constructor() {\n    super(\n      `Stored ${HOSTED_APPS_SETTINGS_KEY} is not { showHostedApps: boolean }. Save the Agent-Native.com hosted apps setting again to repair it.`,\n      { errorCode: HOSTED_APPS_SETTINGS_INVALID_ERROR_CODE, statusCode: 409 },\n    );\n    this.name = \"InvalidHostedAppsSettingsError\";\n  }\n}\n\n/**\n * Built-in catalog apps this workspace offers. A mounted workspace app with a\n * built-in's id is a workspace app; the built-in config never applies to it.\n */\nexport async function listHostedApps(): Promise<DiscoveredAgent[]> {\n  const workspaceApps = await loadWorkspaceAppsManifest();\n  const workspaceIds = new Set(\n    (workspaceApps ?? []).map((app) => normalizeAgentId(app.id)),\n  );\n  return getBuiltinAgents(\"dispatch\").filter(\n    (agent) => !workspaceIds.has(agent.id),\n  );\n}\n\nfunction hostedAppsSettingsScope() {\n  const orgId = getRequestOrgId();\n  if (orgId) return { scope: \"org\" as const, scopeId: orgId };\n  const email = getRequestUserEmail();\n  return email ? { scope: \"user\" as const, scopeId: email } : null;\n}\n\n/**\n * The stored setting. An unreadable value is `invalid` and hides hosted apps,\n * so it cannot fail the app lists or agent context; Settings reports it.\n */\nexport async function readHostedAppsSettings(): Promise<\n  HostedAppsSettings & { invalid: boolean }\n> {\n  const scope = hostedAppsSettingsScope();\n  // No org and no user means there is nowhere the setting could be stored.\n  if (!scope) return { showHostedApps: true, invalid: false };\n  const raw =\n    scope.scope === \"org\"\n      ? await getOrgSetting(scope.scopeId, HOSTED_APPS_SETTINGS_KEY)\n      : await getUserSetting(scope.scopeId, HOSTED_APPS_SETTINGS_KEY);\n  if (raw === null) return { showHostedApps: true, invalid: false };\n  if (typeof raw.showHostedApps !== \"boolean\") {\n    return { showHostedApps: false, invalid: true };\n  }\n  return { showHostedApps: raw.showHostedApps, invalid: false };\n}\n\nexport async function setHostedAppsSettings(\n  next: HostedAppsSettings,\n): Promise<HostedAppsSettings> {\n  const scope = hostedAppsSettingsScope();\n  if (!scope) {\n    throw Object.assign(\n      new Error(\"Sign in to change the Agent-Native.com hosted apps setting.\"),\n      { statusCode: 401 },\n    );\n  }\n  const value = { showHostedApps: next.showHostedApps };\n  if (scope.scope === \"org\") {\n    await putOrgSetting(scope.scopeId, HOSTED_APPS_SETTINGS_KEY, value);\n  } else {\n    await putUserSetting(scope.scopeId, HOSTED_APPS_SETTINGS_KEY, value);\n  }\n  return value;\n}\n\n/** Hides hosted apps from Dispatch's lists and agent context when off. */\nexport async function hideHostedAppsWhenOff<T extends { id: string }>(\n  agents: T[],\n): Promise<T[]> {\n  const { showHostedApps } = await readHostedAppsSettings();\n  if (showHostedApps) return agents;\n  const hostedIds = new Set((await listHostedApps()).map((app) => app.id));\n  return agents.filter((agent) => !hostedIds.has(agent.id));\n}\n"]}

package/dist/server/plugins/agent-chat.js

@@ -1,6 +1,7 @@
 import { getOrgContext } from "@agent-native/core/org";
-import { createAgentChatPlugin, getBuilderWorkspaceUrl, } from "@agent-native/core/server";
+import { createAgentChatPlugin, getBuilderWorkspaceUrl, registerAgentContextAgentFilter, } from "@agent-native/core/server";
 import { dispatchActions } from "../../actions/index.js";
+import { hideHostedAppsWhenOff } from "../lib/hosted-apps-settings.js";
 import { workspaceAppActionRouteAuth, WORKSPACE_APP_CLAIM_ACTION_PATH, WORKSPACE_APPS_ACTION_PATH, } from "../lib/workspace-app-action-auth.js";
 const INITIAL_TOOL_NAMES = [
     "view-screen",
@@ -31,6 +32,7 @@ const INITIAL_TOOL_NAMES = [
     "query-staged-dataset",
     "navigate",
 ];
+registerAgentContextAgentFilter("dispatch", hideHostedAppsWhenOff);
 export default createAgentChatPlugin({
     appId: "dispatch",
     connectApps: true,
@@ -79,11 +81,12 @@ Use the standard workspace primitives:
 - 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 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 keep the configureClientRouterBasename() call in app/entry.client.tsx so the app hydrates at /<app-id>. 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.
+- Treat the apps in the available-apps context as existing neighbors available through links and A2A. 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.
+- Owners and admins can hide Agent-Native.com hosted apps for the organization with set-hosted-apps-settings; get-hosted-apps-settings reads it. When hidden they are left out of available-apps and list-connected-agents marks them hiddenFromLaunchers, but call-agent by name still reaches them.
 - 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.
 - Use list-dispatch-usage-metrics only for this workspace's own members' agent/LLM usage and spend, or aggregate adoption of an accessible workspace app. For agent/LLM usage or spend, call it with scope=workspace and the requested sinceDays; it reports workspace-member usage only. For app adoption, call it with scope=app and appId; app creators can see aggregate daily/weekly active users and tracked actions for their own app, while organization owners/admins can inspect any accessible app. App scope omits individual users and prompt previews. External customer, account, or company usage, credits, activity, or product data belongs to the relevant app: use its identity in <relevant-apps> when clear, or call describe-workspace-apps with a query when ownership is unclear. Do not use this action for external customer/account/company data.

package/dist/server/plugins/agent-chat.js.map

@@ -1 +1 @@
-{"version":3,"file":"agent-chat.js","sourceRoot":"","sources":["../../../src/server/plugins/agent-chat.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,MAAM,wBAAwB,CAAC;AACvD,OAAO,EACL,qBAAqB,EACrB,sBAAsB,GACvB,MAAM,2BAA2B,CAAC;AAEnC,OAAO,EAAE,eAAe,EAAE,MAAM,wBAAwB,CAAC;AACzD,OAAO,EACL,2BAA2B,EAC3B,+BAA+B,EAC/B,0BAA0B,GAC3B,MAAM,qCAAqC,CAAC;AAE7C,MAAM,kBAAkB,GAAG;IACzB,aAAa;IACb,qBAAqB;IACrB,+BAA+B;IAC/B,uBAAuB;IACvB,SAAS;IACT,UAAU;IACV,0BAA0B;IAC1B,2BAA2B;IAC3B,2BAA2B;IAC3B,cAAc;IACd,mBAAmB;IACnB,iBAAiB;IACjB,wBAAwB;IACxB,oBAAoB;IACpB,sBAAsB;IACtB,qBAAqB;IACrB,mBAAmB;IACnB,oBAAoB;IACpB,aAAa;IACb,8BAA8B;IAC9B,6BAA6B;IAC7B,oCAAoC;IACpC,sBAAsB;IACtB,mBAAmB;IACnB,sBAAsB;IACtB,sBAAsB;IACtB,UAAU;CACX,CAAC;AAEF,eAAe,qBAAqB,CAAC;IACnC,KAAK,EAAE,UAAU;IACjB,WAAW,EAAE,IAAI;IACjB,qBAAqB,EAAE,IAAI;IAC3B,gBAAgB,EAAE,kBAAkB;IACpC,GAAG,EAAE;QACH,eAAe,EAAE,IAAI;QACrB,gBAAgB,EAAE;YAChB,oCAAoC;YACpC,8BAA8B;YAC9B,6BAA6B;SAC9B;KACF;IACD,YAAY,EAAE,KAAK,EAAE,KAAK,EAAE,EAAE;QAC5B,MAAM,GAAG,GAAG,MAAM,aAAa,CAAC,KAAK,CAAC,CAAC;QACvC,OAAO,GAAG,CAAC,KAAK,CAAC;IACnB,CAAC;IACD,OAAO,EAAE,eAAe;IACxB,eAAe,EAAE,2BAA2B;IAC5C,sBAAsB,EAAE;QACtB,0BAA0B;QAC1B,+BAA+B;KAChC;IACD,aAAa,EAAE,EAAE,UAAU,EAAE,WAAW,EAAE;IAC1C,YAAY,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6EAoC6D,sBAAsB,EAAE,EAAE;CACtG,CAAC,CAAC;AAEH;;;GAGG;AACH,SAAS,sBAAsB;IAC7B,MAAM,GAAG,GAAG,sBAAsB,EAAE,CAAC;IACrC,IAAI,CAAC,GAAG;QAAE,OAAO,EAAE,CAAC;IACpB,OAAO;;2JAEkJ,GAAG,sCAAsC,CAAC;AACrM,CAAC","sourcesContent":["import { getOrgContext } from \"@agent-native/core/org\";\nimport {\n  createAgentChatPlugin,\n  getBuilderWorkspaceUrl,\n} from \"@agent-native/core/server\";\n\nimport { dispatchActions } from \"../../actions/index.js\";\nimport {\n  workspaceAppActionRouteAuth,\n  WORKSPACE_APP_CLAIM_ACTION_PATH,\n  WORKSPACE_APPS_ACTION_PATH,\n} from \"../lib/workspace-app-action-auth.js\";\n\nconst INITIAL_TOOL_NAMES = [\n  \"view-screen\",\n  \"list-workspace-apps\",\n  \"update-workspace-app-metadata\",\n  \"list-connected-agents\",\n  \"ask_app\",\n  \"open_app\",\n  \"list-workspace-resources\",\n  \"create-workspace-resource\",\n  \"update-workspace-resource\",\n  \"import-agent\",\n  \"import-agent-pack\",\n  \"list-agent-pack\",\n  \"connect-external-agent\",\n  \"list-vault-secrets\",\n  \"request-vault-secret\",\n  \"create-vault-secret\",\n  \"list-destinations\",\n  \"upsert-destination\",\n  \"list-dreams\",\n  \"start-workspace-app-creation\",\n  \"list-dispatch-usage-metrics\",\n  \"list-available-workspace-templates\",\n  \"provider-api-catalog\",\n  \"provider-api-docs\",\n  \"provider-api-request\",\n  \"query-staged-dataset\",\n  \"navigate\",\n];\n\nexport default createAgentChatPlugin({\n  appId: \"dispatch\",\n  connectApps: true,\n  durableBackgroundRuns: true,\n  initialToolNames: INITIAL_TOOL_NAMES,\n  mcp: {\n    appApprovalPage: true,\n    connectorCatalog: [\n      \"resolve-integration-source-context\",\n      \"start-workspace-app-creation\",\n      \"list-dispatch-usage-metrics\",\n    ],\n  },\n  resolveOrgId: async (event) => {\n    const ctx = await getOrgContext(event);\n    return ctx.orgId;\n  },\n  actions: dispatchActions,\n  actionRouteAuth: workspaceAppActionRouteAuth,\n  actionRoutePublicPaths: [\n    WORKSPACE_APPS_ACTION_PATH,\n    WORKSPACE_APP_CLAIM_ACTION_PATH,\n  ],\n  codeExecution: { production: \"sandboxed\" },\n  systemPrompt: `You are the central dispatch for this workspace.\n\nDefault posture:\n- Treat Slack and Telegram as shared entrypoints into the workspace.\n- Heavily delegate domain work to specialized agents through A2A when another app owns the job.\n- Keep durable memory and operating instructions in resources rather than ephemeral chat.\n- Prefer replying in the current external thread unless the user explicitly asks you to send to a saved destination.\n\nUse the standard workspace primitives:\n- Read and update resources like AGENTS.md, LEARNINGS.md, jobs/*.md, agents/*.md, and remote-agents/*.json when appropriate.\n- Use recurring jobs for scheduled behavior.\n- Use custom agent profiles in agents/*.md for local spawned work and remote-agents/*.json for remote A2A apps.\n- For a Claude-style Markdown or JSON agent setup, use import-agent so the\n  profile is normalized into agents/<slug>.md. Never import credentials, hooks,\n  shell commands, or local environment settings.\n- For a folder of agent instructions, references, or skills, use\n  import-agent-pack. It preserves the text files under agents/<slug>/ and\n  creates the normalized profile alongside them. Use list-agent-pack to inspect\n  the pack before editing or handing it off to an app.\n- For an existing HTTP/A2A endpoint, use connect-external-agent and let the\n  normal A2A/MCP connection flow handle authentication.\n- 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.\n- 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.\n- 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.\n- 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.\n- 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.\n- 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.\n- 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.\n- 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.\n- 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.\n- 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.\n- Use list-dispatch-usage-metrics only for this workspace's own members' agent/LLM usage and spend, or aggregate adoption of an accessible workspace app. For agent/LLM usage or spend, call it with scope=workspace and the requested sinceDays; it reports workspace-member usage only. For app adoption, call it with scope=app and appId; app creators can see aggregate daily/weekly active users and tracked actions for their own app, while organization owners/admins can inspect any accessible app. App scope omits individual users and prompt previews. External customer, account, or company usage, credits, activity, or product data belongs to the relevant app: use its identity in <relevant-apps> when clear, or call describe-workspace-apps with a query when ownership is unclear. Do not use this action for external customer/account/company data.\n\nWhen a user asks for something like a digest, reminder, routing rule, or saved behavior:\n- First decide whether it should be a resource, a recurring job, a destination, or a delegated task.\n- Keep responses concise and operational.\n- Avoid inventing integrations or destinations that are not configured yet.${builderManagedAppsNote()}`,\n});\n\n/**\n * A Builder-linked workspace builds its apps in Builder; app-creation actions\n * return a link there, and the agent should offer it rather than retry.\n */\nfunction builderManagedAppsNote(): string {\n  const url = getBuilderWorkspaceUrl();\n  if (!url) return \"\";\n  return `\n\nThis workspace is managed in Builder. Never create, scaffold, remix, or install workspace apps from here. When someone asks for a new app, point them to ${url} and tell them to use New app there.`;\n}\n"]}
+{"version":3,"file":"agent-chat.js","sourceRoot":"","sources":["../../../src/server/plugins/agent-chat.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,MAAM,wBAAwB,CAAC;AACvD,OAAO,EACL,qBAAqB,EACrB,sBAAsB,EACtB,+BAA+B,GAChC,MAAM,2BAA2B,CAAC;AAEnC,OAAO,EAAE,eAAe,EAAE,MAAM,wBAAwB,CAAC;AACzD,OAAO,EAAE,qBAAqB,EAAE,MAAM,gCAAgC,CAAC;AACvE,OAAO,EACL,2BAA2B,EAC3B,+BAA+B,EAC/B,0BAA0B,GAC3B,MAAM,qCAAqC,CAAC;AAE7C,MAAM,kBAAkB,GAAG;IACzB,aAAa;IACb,qBAAqB;IACrB,+BAA+B;IAC/B,uBAAuB;IACvB,SAAS;IACT,UAAU;IACV,0BAA0B;IAC1B,2BAA2B;IAC3B,2BAA2B;IAC3B,cAAc;IACd,mBAAmB;IACnB,iBAAiB;IACjB,wBAAwB;IACxB,oBAAoB;IACpB,sBAAsB;IACtB,qBAAqB;IACrB,mBAAmB;IACnB,oBAAoB;IACpB,aAAa;IACb,8BAA8B;IAC9B,6BAA6B;IAC7B,oCAAoC;IACpC,sBAAsB;IACtB,mBAAmB;IACnB,sBAAsB;IACtB,sBAAsB;IACtB,UAAU;CACX,CAAC;AAEF,+BAA+B,CAAC,UAAU,EAAE,qBAAqB,CAAC,CAAC;AAEnE,eAAe,qBAAqB,CAAC;IACnC,KAAK,EAAE,UAAU;IACjB,WAAW,EAAE,IAAI;IACjB,qBAAqB,EAAE,IAAI;IAC3B,gBAAgB,EAAE,kBAAkB;IACpC,GAAG,EAAE;QACH,eAAe,EAAE,IAAI;QACrB,gBAAgB,EAAE;YAChB,oCAAoC;YACpC,8BAA8B;YAC9B,6BAA6B;SAC9B;KACF;IACD,YAAY,EAAE,KAAK,EAAE,KAAK,EAAE,EAAE;QAC5B,MAAM,GAAG,GAAG,MAAM,aAAa,CAAC,KAAK,CAAC,CAAC;QACvC,OAAO,GAAG,CAAC,KAAK,CAAC;IACnB,CAAC;IACD,OAAO,EAAE,eAAe;IACxB,eAAe,EAAE,2BAA2B;IAC5C,sBAAsB,EAAE;QACtB,0BAA0B;QAC1B,+BAA+B;KAChC;IACD,aAAa,EAAE,EAAE,UAAU,EAAE,WAAW,EAAE;IAC1C,YAAY,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;6EAqC6D,sBAAsB,EAAE,EAAE;CACtG,CAAC,CAAC;AAEH;;;GAGG;AACH,SAAS,sBAAsB;IAC7B,MAAM,GAAG,GAAG,sBAAsB,EAAE,CAAC;IACrC,IAAI,CAAC,GAAG;QAAE,OAAO,EAAE,CAAC;IACpB,OAAO;;2JAEkJ,GAAG,sCAAsC,CAAC;AACrM,CAAC","sourcesContent":["import { getOrgContext } from \"@agent-native/core/org\";\nimport {\n  createAgentChatPlugin,\n  getBuilderWorkspaceUrl,\n  registerAgentContextAgentFilter,\n} from \"@agent-native/core/server\";\n\nimport { dispatchActions } from \"../../actions/index.js\";\nimport { hideHostedAppsWhenOff } from \"../lib/hosted-apps-settings.js\";\nimport {\n  workspaceAppActionRouteAuth,\n  WORKSPACE_APP_CLAIM_ACTION_PATH,\n  WORKSPACE_APPS_ACTION_PATH,\n} from \"../lib/workspace-app-action-auth.js\";\n\nconst INITIAL_TOOL_NAMES = [\n  \"view-screen\",\n  \"list-workspace-apps\",\n  \"update-workspace-app-metadata\",\n  \"list-connected-agents\",\n  \"ask_app\",\n  \"open_app\",\n  \"list-workspace-resources\",\n  \"create-workspace-resource\",\n  \"update-workspace-resource\",\n  \"import-agent\",\n  \"import-agent-pack\",\n  \"list-agent-pack\",\n  \"connect-external-agent\",\n  \"list-vault-secrets\",\n  \"request-vault-secret\",\n  \"create-vault-secret\",\n  \"list-destinations\",\n  \"upsert-destination\",\n  \"list-dreams\",\n  \"start-workspace-app-creation\",\n  \"list-dispatch-usage-metrics\",\n  \"list-available-workspace-templates\",\n  \"provider-api-catalog\",\n  \"provider-api-docs\",\n  \"provider-api-request\",\n  \"query-staged-dataset\",\n  \"navigate\",\n];\n\nregisterAgentContextAgentFilter(\"dispatch\", hideHostedAppsWhenOff);\n\nexport default createAgentChatPlugin({\n  appId: \"dispatch\",\n  connectApps: true,\n  durableBackgroundRuns: true,\n  initialToolNames: INITIAL_TOOL_NAMES,\n  mcp: {\n    appApprovalPage: true,\n    connectorCatalog: [\n      \"resolve-integration-source-context\",\n      \"start-workspace-app-creation\",\n      \"list-dispatch-usage-metrics\",\n    ],\n  },\n  resolveOrgId: async (event) => {\n    const ctx = await getOrgContext(event);\n    return ctx.orgId;\n  },\n  actions: dispatchActions,\n  actionRouteAuth: workspaceAppActionRouteAuth,\n  actionRoutePublicPaths: [\n    WORKSPACE_APPS_ACTION_PATH,\n    WORKSPACE_APP_CLAIM_ACTION_PATH,\n  ],\n  codeExecution: { production: \"sandboxed\" },\n  systemPrompt: `You are the central dispatch for this workspace.\n\nDefault posture:\n- Treat Slack and Telegram as shared entrypoints into the workspace.\n- Heavily delegate domain work to specialized agents through A2A when another app owns the job.\n- Keep durable memory and operating instructions in resources rather than ephemeral chat.\n- Prefer replying in the current external thread unless the user explicitly asks you to send to a saved destination.\n\nUse the standard workspace primitives:\n- Read and update resources like AGENTS.md, LEARNINGS.md, jobs/*.md, agents/*.md, and remote-agents/*.json when appropriate.\n- Use recurring jobs for scheduled behavior.\n- Use custom agent profiles in agents/*.md for local spawned work and remote-agents/*.json for remote A2A apps.\n- For a Claude-style Markdown or JSON agent setup, use import-agent so the\n  profile is normalized into agents/<slug>.md. Never import credentials, hooks,\n  shell commands, or local environment settings.\n- For a folder of agent instructions, references, or skills, use\n  import-agent-pack. It preserves the text files under agents/<slug>/ and\n  creates the normalized profile alongside them. Use list-agent-pack to inspect\n  the pack before editing or handing it off to an app.\n- For an existing HTTP/A2A endpoint, use connect-external-agent and let the\n  normal A2A/MCP connection flow handle authentication.\n- 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.\n- 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.\n- 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.\n- 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 keep the configureClientRouterBasename() call in app/entry.client.tsx so the app hydrates at /<app-id>. There is no separate workspace app registry to edit.\n- 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.\n- 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.\n- 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.\n- Treat the apps in the available-apps context as existing neighbors available through links and A2A. 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.\n- Owners and admins can hide Agent-Native.com hosted apps for the organization with set-hosted-apps-settings; get-hosted-apps-settings reads it. When hidden they are left out of available-apps and list-connected-agents marks them hiddenFromLaunchers, but call-agent by name still reaches them.\n- 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.\n- 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.\n- Use list-dispatch-usage-metrics only for this workspace's own members' agent/LLM usage and spend, or aggregate adoption of an accessible workspace app. For agent/LLM usage or spend, call it with scope=workspace and the requested sinceDays; it reports workspace-member usage only. For app adoption, call it with scope=app and appId; app creators can see aggregate daily/weekly active users and tracked actions for their own app, while organization owners/admins can inspect any accessible app. App scope omits individual users and prompt previews. External customer, account, or company usage, credits, activity, or product data belongs to the relevant app: use its identity in <relevant-apps> when clear, or call describe-workspace-apps with a query when ownership is unclear. Do not use this action for external customer/account/company data.\n\nWhen a user asks for something like a digest, reminder, routing rule, or saved behavior:\n- First decide whether it should be a resource, a recurring job, a destination, or a delegated task.\n- Keep responses concise and operational.\n- Avoid inventing integrations or destinations that are not configured yet.${builderManagedAppsNote()}`,\n});\n\n/**\n * A Builder-linked workspace builds its apps in Builder; app-creation actions\n * return a link there, and the agent should offer it rather than retry.\n */\nfunction builderManagedAppsNote(): string {\n  const url = getBuilderWorkspaceUrl();\n  if (!url) return \"\";\n  return `\n\nThis workspace is managed in Builder. Never create, scaffold, remix, or install workspace apps from here. When someone asks for a new app, point them to ${url} and tell them to use New app there.`;\n}\n"]}

package/dist/server/plugins/integrations.js

@@ -17,7 +17,7 @@ Default posture:
 - Use relevant-apps prompt profiles first, then list-connected-agents when you need fresh details. If that context is absent or does not list the needed capability, search with describe-workspace-apps query="<capability>" before assuming a request must be handled locally.
 - Hosted/connected A2A neighbors such as Analytics and Content come from the relevant-apps context or list-connected-agents. If neither identifies the needed capability, use describe-workspace-apps before concluding a connected agent is unavailable. 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.
+- Treat the apps in the relevant-apps context as existing neighbors available through links and A2A. 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.
@@ -32,9 +32,9 @@ When a user asks for something:
 - 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 using 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 a new-app prompt asks for access to Mail, Calendar, Analytics, Brain, Assets, or similar first-party app data/agents, keep using the existing app through A2A. 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. If it returns mode "app-id-taken", the app id is already in use: \`conflict\` is "registered" for a live app or "pending" for a creation in flight, and \`owner\` names who started it. Relay the \`message\` and propose a different app id; never retry the same id.
+- 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 keeping the configureClientRouterBasename() call in app/entry.client.tsx. 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. If it returns mode "app-id-taken", the app id is already in use: \`conflict\` is "registered" for a live app or "pending" for a creation in flight, and \`owner\` names who started it. Relay the \`message\` and propose a different app id; never retry the same id.
 - 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).

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;AAErE,OAAO,EAAE,eAAe,EAAE,MAAM,wBAAwB,CAAC;AACzD,OAAO,EAAE,iBAAiB,EAAE,MAAM,aAAa,CAAC;AAChD,OAAO,EACL,qBAAqB,EACrB,+BAA+B,GAChC,MAAM,iCAAiC,CAAC;AAEzC,MAAM,0BAA0B,GAAG;IACjC,GAAG,eAAe;IAClB,OAAO,EAAE;QACP,GAAG,eAAe,CAAC,OAAO;QAC1B,SAAS,EAAE,KAAK;KACjB;CACF,CAAC;AAEF,MAAM,kCAAkC,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;4FA6BiD,CAAC;AAE7F,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,0BAA0B;QACnC,uBAAuB,EAAE,+BAA+B;QACxD,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\";\n\nimport { dispatchActions } from \"../../actions/index.js\";\nimport { getDispatchConfig } from \"../index.js\";\nimport {\n  beforeDispatchProcess,\n  resolveDispatchExecutionContext,\n} from \"../lib/dispatch-integrations.js\";\n\nconst dispatchIntegrationActions = {\n  ...dispatchActions,\n  ask_app: {\n    ...dispatchActions.ask_app,\n    agentTool: false,\n  },\n};\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.\n- Use relevant-apps prompt profiles first, then list-connected-agents when you need fresh details. If that context is absent or does not list the needed capability, search with describe-workspace-apps query=\"<capability>\" before assuming a request must be handled locally.\n- Hosted/connected A2A neighbors such as Analytics and Content come from the relevant-apps context or list-connected-agents. If neither identifies the needed capability, use describe-workspace-apps before concluding a connected agent is unavailable. 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.\n- 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.\n- 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.\n- 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.\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, clips, assets, etc., delegate via call-agent — do not re-implement the domain logic in dispatch.\n- 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.\n- 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.\n- 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.\n- In messaging integrations, use call-agent for cross-app delegation; do not use ask_app.\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 using 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 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.\n- 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.\n- 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.\n- 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. If it returns mode \"app-id-taken\", the app id is already in use: \\`conflict\\` is \"registered\" for a live app or \"pending\" for a creation in flight, and \\`owner\\` names who started it. Relay the \\`message\\` and propose a different app id; never retry the same id.\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\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: dispatchIntegrationActions,\n    resolveExecutionContext: resolveDispatchExecutionContext,\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;AAErE,OAAO,EAAE,eAAe,EAAE,MAAM,wBAAwB,CAAC;AACzD,OAAO,EAAE,iBAAiB,EAAE,MAAM,aAAa,CAAC;AAChD,OAAO,EACL,qBAAqB,EACrB,+BAA+B,GAChC,MAAM,iCAAiC,CAAC;AAEzC,MAAM,0BAA0B,GAAG;IACjC,GAAG,eAAe;IAClB,OAAO,EAAE;QACP,GAAG,eAAe,CAAC,OAAO;QAC1B,SAAS,EAAE,KAAK;KACjB;CACF,CAAC;AAEF,MAAM,kCAAkC,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;4FA6BiD,CAAC;AAE7F,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,0BAA0B;QACnC,uBAAuB,EAAE,+BAA+B;QACxD,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\";\n\nimport { dispatchActions } from \"../../actions/index.js\";\nimport { getDispatchConfig } from \"../index.js\";\nimport {\n  beforeDispatchProcess,\n  resolveDispatchExecutionContext,\n} from \"../lib/dispatch-integrations.js\";\n\nconst dispatchIntegrationActions = {\n  ...dispatchActions,\n  ask_app: {\n    ...dispatchActions.ask_app,\n    agentTool: false,\n  },\n};\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.\n- Use relevant-apps prompt profiles first, then list-connected-agents when you need fresh details. If that context is absent or does not list the needed capability, search with describe-workspace-apps query=\"<capability>\" before assuming a request must be handled locally.\n- Hosted/connected A2A neighbors such as Analytics and Content come from the relevant-apps context or list-connected-agents. If neither identifies the needed capability, use describe-workspace-apps before concluding a connected agent is unavailable. 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.\n- 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.\n- Treat the apps in the relevant-apps context as existing neighbors available through links and A2A. 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.\n- 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.\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, clips, assets, etc., delegate via call-agent — do not re-implement the domain logic in dispatch.\n- 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.\n- 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.\n- 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.\n- In messaging integrations, use call-agent for cross-app delegation; do not use ask_app.\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 using 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 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.\n- 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 app through A2A. 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.\n- 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.\n- 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 keeping the configureClientRouterBasename() call in app/entry.client.tsx. 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. If it returns mode \"app-id-taken\", the app id is already in use: \\`conflict\\` is \"registered\" for a live app or \"pending\" for a creation in flight, and \\`owner\\` names who started it. Relay the \\`message\\` and propose a different app id; never retry the same id.\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\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: dispatchIntegrationActions,\n    resolveExecutionContext: resolveDispatchExecutionContext,\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/dist/shared/hosted-apps-settings.d.ts

@@ -0,0 +1,3 @@
+/** The stored setting is not `{ showHostedApps: boolean }`; saving repairs it. */
+export declare const HOSTED_APPS_SETTINGS_INVALID_ERROR_CODE = "dispatch_hosted_apps_settings_invalid";
+//# sourceMappingURL=hosted-apps-settings.d.ts.map

package/dist/shared/hosted-apps-settings.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"hosted-apps-settings.d.ts","sourceRoot":"","sources":["../../src/shared/hosted-apps-settings.ts"],"names":[],"mappings":"AAAA,kFAAkF;AAClF,eAAO,MAAM,uCAAuC,0CACX,CAAC"}

package/dist/shared/hosted-apps-settings.js

@@ -0,0 +1,3 @@
+/** The stored setting is not `{ showHostedApps: boolean }`; saving repairs it. */
+export const HOSTED_APPS_SETTINGS_INVALID_ERROR_CODE = "dispatch_hosted_apps_settings_invalid";
+//# sourceMappingURL=hosted-apps-settings.js.map

package/dist/shared/hosted-apps-settings.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"hosted-apps-settings.js","sourceRoot":"","sources":["../../src/shared/hosted-apps-settings.ts"],"names":[],"mappings":"AAAA,kFAAkF;AAClF,MAAM,CAAC,MAAM,uCAAuC,GAClD,uCAAuC,CAAC","sourcesContent":["/** The stored setting is not `{ showHostedApps: boolean }`; saving repairs it. */\nexport const HOSTED_APPS_SETTINGS_INVALID_ERROR_CODE =\n  \"dispatch_hosted_apps_settings_invalid\";\n"]}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/dispatch",
-  "version": "0.41.1-nightly-20261104110058",
+  "version": "0.42.0",
   "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.",
   "homepage": "https://github.com/BuilderIO/agent-native#readme",
   "bugs": {
@@ -90,7 +90,7 @@
     "tailwind-merge": "^3.5.0",
     "vaul": "^1.1.2",
     "zod": "^4.3.6",
-    "@agent-native/toolkit": "0.224.0-nightly-20261104110058"
+    "@agent-native/toolkit": "0.224.0"
   },
   "devDependencies": {
     "@react-router/dev": "^8.1.0",
@@ -104,10 +104,10 @@
     "typescript-7": "npm:typescript@^7.0.2",
     "vite": "8.1.0",
     "vitest": "^4.1.5",
-    "@agent-native/core": "0.224.0-nightly-20261104110058"
+    "@agent-native/core": "0.224.0"
   },
   "peerDependencies": {
-    "@agent-native/core": "0.224.0-nightly-20261104110058",
+    "@agent-native/core": ">=0.224.0-0",
     "react": ">=19.2.7",
     "react-dom": ">=19.2.7",
     "react-router": ">=8"

package/src/actions/get-hosted-apps-settings.ts

@@ -0,0 +1,29 @@
+import { defineAction, fail } from "@agent-native/core/action";
+import { getRequestUserEmail } from "@agent-native/core/server";
+import { z } from "zod";
+
+import { hostedAppsSettingsViewSchema } from "../server/lib/hosted-apps-settings-schema.js";
+import {
+  InvalidHostedAppsSettingsError,
+  readHostedAppsSettings,
+} from "../server/lib/hosted-apps-settings.js";
+
+export default defineAction({
+  description:
+    "Read whether this organization shows Agent-Native.com hosted apps (built-in apps such as Mail or Analytics) in Dispatch app lists and agent context. When showHostedApps is false they are hidden; call-agent by name still reaches them. list-connected-agents lists them, marked hiddenFromLaunchers while hidden.",
+  schema: z.object({}),
+  outputSchema: hostedAppsSettingsViewSchema,
+  http: { method: "GET" },
+  readOnly: true,
+  run: async () => {
+    if (!getRequestUserEmail()) {
+      fail("Sign in to read the Agent-Native.com hosted apps setting.", {
+        errorCode: "dispatch_user_identity_missing",
+        statusCode: 401,
+      });
+    }
+    const { showHostedApps, invalid } = await readHostedAppsSettings();
+    if (invalid) throw new InvalidHostedAppsSettingsError();
+    return { showHostedApps };
+  },
+});

package/src/actions/hosted-apps-settings.spec.ts

@@ -0,0 +1,100 @@
+import { beforeEach, describe, expect, it, vi } from "vitest";
+
+const mocks = vi.hoisted(() => ({
+  authorizeOrgOwnerOrAdmin: vi.fn(),
+  email: vi.fn<() => string | undefined>(() => "member@example.test"),
+  readHostedAppsSettings: vi.fn(),
+  setHostedAppsSettings: vi.fn(),
+  recordAudit: vi.fn(),
+}));
+
+vi.mock("@agent-native/core/server", () => ({
+  getRequestUserEmail: () => mocks.email(),
+}));
+
+vi.mock("../server/lib/app-roles.js", () => ({
+  authorizeOrgOwnerOrAdmin: mocks.authorizeOrgOwnerOrAdmin,
+}));
+
+vi.mock("../server/lib/dispatch-store.js", () => ({
+  recordAudit: mocks.recordAudit,
+}));
+
+vi.mock("../server/lib/hosted-apps-settings.js", async (importOriginal) => ({
+  InvalidHostedAppsSettingsError: (
+    await importOriginal<
+      typeof import("../server/lib/hosted-apps-settings.js")
+    >()
+  ).InvalidHostedAppsSettingsError,
+  HOSTED_APPS_SETTINGS_KEY: "dispatch-hosted-apps-settings",
+  readHostedAppsSettings: mocks.readHostedAppsSettings,
+  setHostedAppsSettings: mocks.setHostedAppsSettings,
+}));
+
+const getAction = (await import("./get-hosted-apps-settings.js")).default;
+const setAction = (await import("./set-hosted-apps-settings.js")).default;
+
+describe("hosted apps settings actions", () => {
+  beforeEach(() => {
+    vi.clearAllMocks();
+    mocks.email.mockReturnValue("member@example.test");
+    mocks.readHostedAppsSettings.mockResolvedValue({
+      showHostedApps: false,
+      invalid: false,
+    });
+    mocks.setHostedAppsSettings.mockImplementation(async (value) => value);
+    mocks.authorizeOrgOwnerOrAdmin.mockResolvedValue(undefined);
+  });
+
+  it("lets any signed-in member read the setting", async () => {
+    await expect(getAction.run({})).resolves.toEqual({
+      showHostedApps: false,
+    });
+    expect(mocks.authorizeOrgOwnerOrAdmin).not.toHaveBeenCalled();
+  });
+
+  it("refuses to read without a signed-in user", async () => {
+    mocks.email.mockReturnValue(undefined);
+    await expect(getAction.run({})).rejects.toThrow("Sign in");
+    expect(mocks.readHostedAppsSettings).not.toHaveBeenCalled();
+  });
+
+  it("reports an invalid stored value with the code Settings repairs from", async () => {
+    mocks.readHostedAppsSettings.mockResolvedValue({
+      showHostedApps: false,
+      invalid: true,
+    });
+    await expect(getAction.run({})).rejects.toMatchObject({
+      errorCode: "dispatch_hosted_apps_settings_invalid",
+      statusCode: 409,
+    });
+  });
+
+  it("denies callers who are not org owners or admins before writing", async () => {
+    mocks.authorizeOrgOwnerOrAdmin.mockRejectedValue(
+      Object.assign(new Error("Only organization owners and admins"), {
+        statusCode: 403,
+      }),
+    );
+    await expect(setAction.run({ showHostedApps: false })).rejects.toThrow(
+      "Only organization owners and admins",
+    );
+    expect(mocks.setHostedAppsSettings).not.toHaveBeenCalled();
+    expect(mocks.recordAudit).not.toHaveBeenCalled();
+  });
+
+  it("writes, records the change in Dispatch's audit log, and returns the read shape", async () => {
+    await expect(setAction.run({ showHostedApps: false })).resolves.toEqual({
+      showHostedApps: false,
+    });
+    expect(mocks.setHostedAppsSettings).toHaveBeenCalledWith({
+      showHostedApps: false,
+    });
+    expect(mocks.recordAudit).toHaveBeenCalledWith(
+      expect.objectContaining({
+        targetId: "dispatch-hosted-apps-settings",
+        summary: "Hid Agent-Native.com hosted apps",
+      }),
+    );
+  });
+});