@agent-native/core 0.144.3 → 0.145.0

package/dist/framework-tools.js

@@ -0,0 +1,114 @@
+import { normalizeDatabaseToolsMode, } from "./scripts/db/tool-mode.js";
+/**
+ * Optional framework tool groups an app can turn off through `frameworkTools`.
+ *
+ * Each name is also stamped onto the group's actions as
+ * `ActionEntry.frameworkGroup`. That tag is what lets a single filter subtract a
+ * group from every agent tool surface at once: `agent-chat-plugin.ts` spreads
+ * these registries at thirteen separate composition sites (interactive chat,
+ * dev, MCP-full, A2A, background jobs, triggers), and a per-site condition would
+ * be the same omission waiting to happen thirteen times.
+ *
+ * The tag has a second job: framework-tagged actions are excluded from the
+ * DEFAULT first-request tool list, so an app pays for the ~40 kit schemas only
+ * when it names them in `initialToolNames`. They stay in the searchable registry
+ * either way.
+ */
+export const FRAMEWORK_TOOL_GROUPS = [
+    "sharing",
+    "review",
+    "history",
+    "featureFlags",
+    "localization",
+    "audit",
+    "contextXray",
+    "userProfile",
+    "automation",
+    "docs",
+    "resources",
+    "web",
+    "workspaceApps",
+    "chat",
+    "email",
+];
+function normalizeFrameworkToolsConfig(config) {
+    if (config === "minimal")
+        return { option: {}, minimal: true };
+    if (!config || typeof config !== "object") {
+        return { option: {}, minimal: false };
+    }
+    const { preset, ...option } = config;
+    return { option, minimal: preset === "minimal" };
+}
+function conflict(key, legacyKey, legacyValue, nestedValue) {
+    throw new Error(`[agent-native] Conflicting agent-chat options: \`${legacyKey}: ${JSON.stringify(legacyValue)}\` ` +
+        `and \`frameworkTools.${key}: ${JSON.stringify(nestedValue)}\` disagree. ` +
+        `Remove the deprecated \`${legacyKey}\` and keep \`frameworkTools.${key}\`.`);
+}
+/**
+ * Resolve the public option surface into one shape the plugin threads inward.
+ *
+ * Legacy `databaseTools` / `extensionTools` remain accepted for one minor. When
+ * both forms are present and disagree we throw at plugin init rather than
+ * picking a winner: an app that boots with a tool surface nobody chose is how a
+ * "why can't the agent see db-query" report ends up unexplainable.
+ */
+export function resolveFrameworkTools(input) {
+    const { option, minimal } = normalizeFrameworkToolsConfig(input?.frameworkTools);
+    const legacyDatabase = input?.databaseTools;
+    if (legacyDatabase !== undefined) {
+        if (option.database !== undefined &&
+            normalizeDatabaseToolsMode(legacyDatabase) !==
+                normalizeDatabaseToolsMode(option.database)) {
+            conflict("database", "databaseTools", legacyDatabase, option.database);
+        }
+        console.warn("[agent-native] `databaseTools` is deprecated — use `frameworkTools: { database: … }`.");
+    }
+    const legacyExtensions = input?.extensionTools;
+    if (legacyExtensions !== undefined) {
+        if (option.extensions !== undefined &&
+            (legacyExtensions === true) !== (option.extensions === true)) {
+            conflict("extensions", "extensionTools", legacyExtensions, option.extensions);
+        }
+        console.warn("[agent-native] `extensionTools` is deprecated — use `frameworkTools: { extensions: … }`.");
+    }
+    const database = option.database ?? legacyDatabase ?? (minimal ? "off" : undefined);
+    const extensions = option.extensions ?? legacyExtensions ?? false;
+    const disabledGroups = new Set();
+    for (const group of FRAMEWORK_TOOL_GROUPS) {
+        const explicit = option[group];
+        if (explicit === false || (explicit === undefined && minimal)) {
+            disabledGroups.add(group);
+        }
+    }
+    return {
+        database,
+        extensions,
+        disabledGroups,
+        isEnabled: (group) => !disabledGroups.has(group),
+    };
+}
+/**
+ * Drop every action belonging to a disabled group. Returns the input untouched
+ * when nothing is disabled so the default path allocates nothing.
+ */
+export function filterFrameworkToolGroups(actions, disabledGroups) {
+    if (disabledGroups.size === 0)
+        return actions;
+    return Object.fromEntries(Object.entries(actions).filter(([, entry]) => entry.frameworkGroup === undefined ||
+        !disabledGroups.has(entry.frameworkGroup)));
+}
+/** True for actions the framework contributes rather than the app's own. */
+export function isFrameworkGroupedAction(entry) {
+    return entry.frameworkGroup !== undefined;
+}
+/**
+ * Whether a group is live, for prompt builders that only receive the disabled
+ * set. Prompt text and tool schemas must agree: a prompt that names a tool the
+ * request does not carry makes the model try it, fail, and often report the
+ * capability as nonexistent — so every block naming a group's tool by name has
+ * to be gated on the same set that gates the registry.
+ */
+export function frameworkGroupEnabled(disabledGroups, group) {
+    return !disabledGroups?.has(group);
+}

package/dist/mcp/screen-memory-stdio.d.ts

@@ -137,13 +137,13 @@ export declare function screenMemoryMcpToolDefinitions(): ({
     inputSchema: {
         type: string;
         properties: {
+            count?: undefined;
             query?: undefined;
             minutes?: undefined;
             limit?: undefined;
             clientHint?: undefined;
             timestamp?: undefined;
             chapterId?: undefined;
-            count?: undefined;
             startAt?: undefined;
             endAt?: undefined;
             reason?: undefined;
@@ -159,6 +159,7 @@ export declare function screenMemoryMcpToolDefinitions(): ({
     inputSchema: {
         type: string;
         properties: {
+            count?: undefined;
             query: {
                 type: string;
                 description: string;
@@ -174,7 +175,6 @@ export declare function screenMemoryMcpToolDefinitions(): ({
             clientHint?: undefined;
             timestamp?: undefined;
             chapterId?: undefined;
-            count?: undefined;
             startAt?: undefined;
             endAt?: undefined;
             reason?: undefined;
@@ -190,6 +190,7 @@ export declare function screenMemoryMcpToolDefinitions(): ({
     inputSchema: {
         type: string;
         properties: {
+            count?: undefined;
             minutes: {
                 type: string;
                 description: string;
@@ -199,7 +200,6 @@ export declare function screenMemoryMcpToolDefinitions(): ({
             clientHint?: undefined;
             timestamp?: undefined;
             chapterId?: undefined;
-            count?: undefined;
             startAt?: undefined;
             endAt?: undefined;
             reason?: undefined;
@@ -216,6 +216,7 @@ export declare function screenMemoryMcpToolDefinitions(): ({
         type: string;
         required: string[];
         properties: {
+            count?: undefined;
             query: {
                 type: string;
                 description: string;
@@ -234,7 +235,6 @@ export declare function screenMemoryMcpToolDefinitions(): ({
             };
             timestamp?: undefined;
             chapterId?: undefined;
-            count?: undefined;
             startAt?: undefined;
             endAt?: undefined;
             reason?: undefined;
@@ -250,6 +250,7 @@ export declare function screenMemoryMcpToolDefinitions(): ({
         type: string;
         required: string[];
         properties: {
+            count?: undefined;
             query?: undefined;
             minutes?: undefined;
             limit?: undefined;
@@ -263,7 +264,6 @@ export declare function screenMemoryMcpToolDefinitions(): ({
                 description: string;
             };
             chapterId?: undefined;
-            count?: undefined;
             startAt?: undefined;
             endAt?: undefined;
             includeMicrophone?: undefined;
@@ -314,13 +314,13 @@ export declare function screenMemoryMcpToolDefinitions(): ({
         type: string;
         required: string[];
         properties: {
+            count?: undefined;
             query?: undefined;
             minutes?: undefined;
             limit?: undefined;
             clientHint?: undefined;
             timestamp?: undefined;
             chapterId?: undefined;
-            count?: undefined;
             startAt: {
                 type: string;
                 description: string;
@@ -349,13 +349,13 @@ export declare function screenMemoryMcpToolDefinitions(): ({
         type: string;
         required: string[];
         properties: {
+            count?: undefined;
             query?: undefined;
             minutes?: undefined;
             limit?: undefined;
             clientHint?: undefined;
             timestamp?: undefined;
             chapterId?: undefined;
-            count?: undefined;
             startAt?: undefined;
             endAt?: undefined;
             reason?: undefined;

package/dist/notifications/routes.d.ts

@@ -16,18 +16,18 @@ export declare function createNotificationsHandler(): import("h3").EventHandlerW
     error?: undefined;
     ok?: undefined;
 } | {
+    count?: undefined;
     updated: number;
     error?: undefined;
     ok?: undefined;
-    count?: undefined;
 } | {
+    count?: undefined;
     updated?: undefined;
     error: string;
     ok?: undefined;
-    count?: undefined;
 } | {
+    count?: undefined;
     updated?: undefined;
-    ok: boolean;
     error?: undefined;
-    count?: undefined;
+    ok: boolean;
 }>>;

package/dist/observability/routes.d.ts

@@ -42,22 +42,22 @@ export declare function createObservabilityHandler(): import("h3").EventHandlerW
     avgEvalScore: number;
 } | {
     error?: undefined;
+    ok?: undefined;
     summary: import("./types.js").TraceSummary;
     spans: import("./types.js").TraceSpan[];
     id?: undefined;
-    ok?: undefined;
 } | {
     error?: undefined;
+    ok?: undefined;
     summary?: undefined;
     spans?: undefined;
     id: string;
-    ok?: undefined;
 } | {
+    ok?: undefined;
     summary?: undefined;
     spans?: undefined;
     id?: undefined;
     error: any;
-    ok?: undefined;
 } | {
     error?: undefined;
     summary?: undefined;

package/dist/progress/routes.d.ts

@@ -15,6 +15,6 @@ export declare function createProgressHandler(): import("h3").EventHandlerWithFe
     error: string;
     ok?: undefined;
 } | {
-    ok: boolean;
     error?: undefined;
+    ok: boolean;
 }>>;

package/dist/provider-api/actions/custom-provider-registration.d.ts

@@ -75,7 +75,6 @@ export declare function createCustomProviderRegistrationAction<TSchema extends Z
         user: "user";
     }>>;
 }, z.core.$strip>>, {
-    id?: undefined;
     deleted?: undefined;
     found?: undefined;
     providers: {
@@ -90,16 +89,17 @@ export declare function createCustomProviderRegistrationAction<TSchema extends Z
     count: number;
     provider?: undefined;
     registered?: undefined;
+    id?: undefined;
     label?: undefined;
     message?: undefined;
 } | {
-    id?: undefined;
     deleted?: undefined;
     providers?: undefined;
     count?: undefined;
     found: boolean;
     provider: import("../custom-registry.js").CustomProviderConfig;
     registered?: undefined;
+    id?: undefined;
     label?: undefined;
     message?: undefined;
 } | {

package/dist/resources/handlers.d.ts

@@ -48,8 +48,8 @@ export declare function handleUpdateResource(event: any): Promise<import("./stor
 }>;
 /** DELETE /_agent-native/resources/:id — delete a resource */
 export declare function handleDeleteResource(event: any): Promise<{
-    error: string;
     ok?: undefined;
+    error: string;
 } | {
     error?: undefined;
     ok: boolean;

package/dist/secrets/routes.d.ts

@@ -34,16 +34,16 @@ export declare function createListSecretsHandler(): import("h3").EventHandlerWit
 /** POST /_agent-native/secrets/:key — write a secret. */
 export declare function createWriteSecretHandler(): import("h3").EventHandlerWithFetch<import("h3").EventHandlerRequest, Promise<{
     error: string;
-    status?: undefined;
     ok?: undefined;
+    status?: undefined;
 } | {
     ok: boolean;
     status: string;
     error?: undefined;
 } | {
+    ok?: undefined;
     error: string;
     removed?: undefined;
-    ok?: undefined;
 } | {
     ok: boolean;
     removed: boolean;
@@ -54,9 +54,9 @@ export declare function createWriteSecretHandler(): import("h3").EventHandlerWit
  * or the current stored value without changing anything.
  */
 export declare function createTestSecretHandler(): import("h3").EventHandlerWithFetch<import("h3").EventHandlerRequest, Promise<{
+    ok?: undefined;
     error: string;
     note?: undefined;
-    ok?: undefined;
 } | {
     ok: boolean;
     note?: undefined;

package/dist/server/action-discovery.d.ts

@@ -26,6 +26,7 @@
  * ```
  */
 import type { ActionEntry } from "../agent/production-agent.js";
+import type { FrameworkToolGroup } from "../framework-tools.js";
 /**
  * Register a map of actions contributed by a published package.
  *
@@ -80,6 +81,32 @@ export declare function loadActionsFromStaticRegistry(modules: Record<string, un
  *   passing to `createAgentChatPlugin({ actions })`.
  */
 export declare function autoDiscoverActions(from: string): Promise<Record<string, ActionEntry>>;
+/**
+ * Which `frameworkTools` switch owns each framework action kit.
+ *
+ * The group is stamped onto the entry as `frameworkGroup`, which is what lets
+ * one filter subtract a whole kit from every agent tool surface at once — the
+ * plugin spreads these registries at thirteen composition sites, and a
+ * per-site condition would be the same omission waiting to happen thirteen
+ * times. The tag also keeps these ~45 schemas out of the DEFAULT first-request
+ * tool list; they stay reachable through `tool-search`.
+ *
+ * Anything absent from this map is always-on and must be listed in
+ * `ALWAYS_ON_CORE_ACTIONS` instead. `action-discovery.spec.ts` fails when a new
+ * core action appears in neither, so "always-on" stays a decision someone made
+ * rather than the default that happens when a map goes un-updated.
+ */
+export declare const CORE_ACTION_GROUPS: Record<string, FrameworkToolGroup>;
+/**
+ * Core actions with no `frameworkTools` switch, and why:
+ *
+ * - `upload-image` is load-bearing for ordinary work.
+ * - The email catalog is mounted everywhere on purpose so Dispatch can ask any
+ *   app what it sends without that app opting in (see its comment below). It is
+ *   a read surface, not the `email` group's send capability.
+ * - MCP tools and org service tokens are already governed by `disableMcp`.
+ */
+export declare const ALWAYS_ON_CORE_ACTIONS: ReadonlySet<string>;
 export declare function mergeCoreSharingActions(registry: Record<string, ActionEntry>): Promise<void>;
 /** @deprecated Use `autoDiscoverActions` instead */
 export declare const autoDiscoverScripts: typeof autoDiscoverActions;

package/dist/server/action-discovery.js

@@ -497,6 +497,92 @@ export async function autoDiscoverActions(from) {
     }
     return registry;
 }
+/**
+ * Which `frameworkTools` switch owns each framework action kit.
+ *
+ * The group is stamped onto the entry as `frameworkGroup`, which is what lets
+ * one filter subtract a whole kit from every agent tool surface at once — the
+ * plugin spreads these registries at thirteen composition sites, and a
+ * per-site condition would be the same omission waiting to happen thirteen
+ * times. The tag also keeps these ~45 schemas out of the DEFAULT first-request
+ * tool list; they stay reachable through `tool-search`.
+ *
+ * Anything absent from this map is always-on and must be listed in
+ * `ALWAYS_ON_CORE_ACTIONS` instead. `action-discovery.spec.ts` fails when a new
+ * core action appears in neither, so "always-on" stays a decision someone made
+ * rather than the default that happens when a map goes un-updated.
+ */
+export const CORE_ACTION_GROUPS = {
+    "share-resource": "sharing",
+    "unshare-resource": "sharing",
+    "list-resource-shares": "sharing",
+    "set-resource-visibility": "sharing",
+    "create-agent-resource-link": "sharing",
+    "get-feature-flags": "featureFlags",
+    "list-feature-flags": "featureFlags",
+    "set-feature-flag": "featureFlags",
+    "list-recurring-jobs": "automation",
+    "manage-recurring-job": "automation",
+    "run-automation-now": "automation",
+    "list-automation-runs": "automation",
+    "list-automations": "automation",
+    "manage-automation": "automation",
+    "context-manifest-get": "contextXray",
+    "context-preview-get": "contextXray",
+    "context-pin": "contextXray",
+    "context-evict": "contextXray",
+    "context-restore": "contextXray",
+    "context-report": "contextXray",
+    "get-localization-preference": "localization",
+    "set-localization-preference": "localization",
+    // Profile, credentials, and appearance share one switch: an app that hides
+    // its profile surface from the agent hides password management with it.
+    "get-user-profile": "userProfile",
+    "update-user-profile": "userProfile",
+    "get-auth-methods": "userProfile",
+    "set-password": "userProfile",
+    "change-password": "userProfile",
+    "change-appearance": "userProfile",
+    "list-audit-events": "audit",
+    "get-audit-event": "audit",
+    "export-audit-events": "audit",
+    "create-resource-version": "history",
+    "list-resource-versions": "history",
+    "get-resource-version": "history",
+    "restore-resource-version": "history",
+    "list-resource-history": "history",
+    "list-review-comments": "review",
+    "create-review-comment": "review",
+    "reply-review-comment": "review",
+    "resolve-review-thread": "review",
+    "delete-review-comment": "review",
+    "consume-review-feedback": "review",
+    "get-review-feedback": "review",
+    "set-review-status": "review",
+    "send-review-thread-to-agent": "review",
+};
+/**
+ * Core actions with no `frameworkTools` switch, and why:
+ *
+ * - `upload-image` is load-bearing for ordinary work.
+ * - The email catalog is mounted everywhere on purpose so Dispatch can ask any
+ *   app what it sends without that app opting in (see its comment below). It is
+ *   a read surface, not the `email` group's send capability.
+ * - MCP tools and org service tokens are already governed by `disableMcp`.
+ */
+export const ALWAYS_ON_CORE_ACTIONS = new Set([
+    "upload-image",
+    "list-transactional-emails",
+    "render-transactional-email-preview",
+    "list-email-log",
+    "list-email-activity",
+    "list-email-engagement",
+    "create-org-service-token",
+    "list-org-service-tokens",
+    "revoke-org-service-token",
+    "list-mcp-tools",
+    "call-mcp-tool",
+]);
 export async function mergeCoreSharingActions(registry) {
     const entries = [
         ["share-resource", () => import("../sharing/actions/share-resource.js")],
@@ -732,6 +818,9 @@ export async function mergeCoreSharingActions(registry) {
                     // actions' `toolCallable: false` (audit-H5) is dropped and the
                     // tools-iframe bridge 403 in action-routes.ts never fires.
                     ...preserveActionFlags(def),
+                    ...(CORE_ACTION_GROUPS[name]
+                        ? { frameworkGroup: CORE_ACTION_GROUPS[name] }
+                        : {}),
                 };
             }
         }

package/dist/server/agent-chat/action-filters-a2a.d.ts

@@ -117,5 +117,16 @@ export declare function createA2AEngineToolSurface(availableTools: EngineTool[],
     tools: EngineTool[];
     availableTools: EngineTool[];
 };
+/**
+ * The first-request tool catalog: an explicit `initialToolNames` verbatim, or
+ * the app's OWN actions by default.
+ *
+ * "Its own actions" excludes the framework kits. They arrive in this same
+ * registry through `autoDiscoverActions` -> `mergeCoreSharingActions`, so the
+ * plain `Object.keys` default promoted ~45 sharing/review/history/flag schemas
+ * into every app's first request whether or not the app had those surfaces. They
+ * remain in `availableTools` and are still found by `tool-search`; an app that
+ * wants one on turn one names it in `initialToolNames`.
+ */
 export declare function resolveInitialToolNames(templateActions: Record<string, ActionEntry>, configured?: string[]): string[];
 export {};

package/dist/server/agent-chat/action-filters-a2a.js

@@ -5,6 +5,7 @@ import { resolveMainChatMaxOutputTokens } from "../../agent/engine/output-tokens
 import { filterInitialEngineTools, resolveAgentRequestReasoningEffort, } from "../../agent/production-agent.js";
 import { runAgentLoopDirectWithSoftTimeout } from "../../agent/run-loop-with-resume.js";
 import { resolveRunSoftTimeoutMs } from "../../agent/run-manager.js";
+import { isFrameworkGroupedAction } from "../../framework-tools.js";
 import { isAuthenticatedReadAction, isAutoReadExcludedActionName, } from "../../mcp/build-server.js";
 import { withConfiguredAppBasePath } from "../app-base-path.js";
 // ---------------------------------------------------------------------------
@@ -389,6 +390,21 @@ export function createA2AEngineToolSurface(availableTools, initialToolNames) {
         availableTools,
     };
 }
+/**
+ * The first-request tool catalog: an explicit `initialToolNames` verbatim, or
+ * the app's OWN actions by default.
+ *
+ * "Its own actions" excludes the framework kits. They arrive in this same
+ * registry through `autoDiscoverActions` -> `mergeCoreSharingActions`, so the
+ * plain `Object.keys` default promoted ~45 sharing/review/history/flag schemas
+ * into every app's first request whether or not the app had those surfaces. They
+ * remain in `availableTools` and are still found by `tool-search`; an app that
+ * wants one on turn one names it in `initialToolNames`.
+ */
 export function resolveInitialToolNames(templateActions, configured) {
-    return configured ?? Object.keys(templateActions);
+    if (configured)
+        return configured;
+    return Object.entries(templateActions)
+        .filter(([, entry]) => !isFrameworkGroupedAction(entry))
+        .map(([name]) => name);
 }

package/dist/server/agent-chat/framework-prompts.d.ts

@@ -1,4 +1,5 @@
 import type { ActionEntry } from "../../agent/production-agent.js";
+import type { FrameworkToolGroup } from "../../framework-tools.js";
 import type { DatabaseToolsOption } from "../../scripts/db/tool-mode.js";
 import { type PromptExamples } from "../prompts/index.js";
 import { resolveInitialToolNames } from "./action-filters-a2a.js";
@@ -15,6 +16,7 @@ import { createDataWidgetActionEntries } from "./context-tools.js";
 export declare function buildFrameworkPrompts(examples?: PromptExamples, options?: {
     databaseTools?: DatabaseToolsOption;
     extensionTools?: boolean;
+    disabledFrameworkGroups?: ReadonlySet<FrameworkToolGroup>;
 }): {
     FRAMEWORK_CORE: string;
     FRAMEWORK_CORE_COMPACT: string;

package/dist/server/agent-chat/plugin-options.d.ts

@@ -1,6 +1,7 @@
 import type { ActionEntry } from "../../agent/production-agent.js";
 import type { AgentLoopFinalResponseGuard } from "../../agent/production-agent.js";
 import type { AgentChatAttachment, AgentChatReference, MentionProvider } from "../../agent/types.js";
+import type { FrameworkToolsConfig } from "../../framework-tools.js";
 import type { ExternalAgentPolicy } from "../../mcp/external-agent-policy.js";
 import type { DatabaseToolsOption } from "../../scripts/db/tool-mode.js";
 import type { PromptExamples } from "../prompts/index.js";
@@ -236,6 +237,29 @@ export interface AgentChatPluginOptions {
      * Defaults to `false`.
      */
     nativeActionsInDev?: boolean;
+    /**
+     * Which of the framework's OWN agent tools this app exposes — raw SQL,
+     * extensions, sharing, review comments, version history, feature flags,
+     * localization, audit, context X-Ray, profile, automations, docs, resources,
+     * web, cross-app delegation, chat, email.
+     *
+     * Every group defaults to today's behavior, so omitting this leaves the tool
+     * surface unchanged. `"minimal"` (or `{ preset: "minimal" }`) turns them all
+     * off for voice-first and single-purpose apps; an explicit group key wins over
+     * the preset.
+     *
+     * Disabling a group removes it from the AGENT surfaces only — chat, MCP, A2A,
+     * background runs. The matching HTTP action routes stay mounted because the UI
+     * reaches them through client hooks. Weigh the parity cost first: the
+     * framework's contract is that anything the UI can do, the agent can do, so
+     * `sharing: false` alongside a visible `ShareButton` is a deliberate break and
+     * only makes sense when the app has no such surface.
+     *
+     * Independent of this option, framework tools are no longer promoted into the
+     * first model request by default — they are reachable through `tool-search`,
+     * or by naming them in `initialToolNames`.
+     */
+    frameworkTools?: FrameworkToolsConfig;
     /**
      * Expose raw SQL/native database tools to the app agent.
      *
@@ -244,6 +268,9 @@ export interface AgentChatPluginOptions {
      * `true`) to expose `db-exec`/`db-patch` for scoped raw SQL maintenance.
      * Set to `"off"` (also `false`) for chat-first apps that want agents to use
      * typed actions only.
+     *
+     * @deprecated Use `frameworkTools: { database: … }`. Still honored for one
+     * minor; setting both to conflicting values throws at plugin init.
      */
     databaseTools?: DatabaseToolsOption;
     /**
@@ -252,6 +279,9 @@ export interface AgentChatPluginOptions {
      * false. Set to true for apps that intentionally let the LLM create or
      * manage sandboxed extension mini-apps. Core extension routes may still be
      * mounted for compatibility and app-owned surfaces.
+     *
+     * @deprecated Use `frameworkTools: { extensions: … }`. Still honored for one
+     * minor; setting both to conflicting values throws at plugin init.
      */
     extensionTools?: boolean;
     /**

package/dist/server/agent-chat/prompt-resources.d.ts

@@ -1,3 +1,4 @@
+import { type FrameworkToolGroup } from "../../framework-tools.js";
 import type { ContextGovernanceTier, ContextManifestSourceRef, ContextSystemProvenance } from "../../shared/context-xray.js";
 export declare const COMPACT_PROMPT_RESOURCE_MAX_CHARS = 6000;
 export interface PromptContextProviderContext {
@@ -89,4 +90,6 @@ export declare function resourceScopeForOwner(owner: string, currentOwner?: stri
  * AGENTS.md and restarting the server is all it takes; Vite HMR invalidates
  * the bundle in dev so changes land instantly.
  */
-export declare function loadResourcesForPrompt(owner: string, compact?: boolean, selfAppId?: string, orgId?: string | null): Promise<string>;
+export declare function loadResourcesForPrompt(owner: string, compact?: boolean, selfAppId?: string, orgId?: string | null, opts?: {
+    disabledFrameworkGroups?: ReadonlySet<FrameworkToolGroup>;
+}): Promise<string>;

package/dist/server/agent-chat/prompt-resources.js

@@ -1,3 +1,4 @@
+import { frameworkGroupEnabled, } from "../../framework-tools.js";
 import { getFrontmatterValue, getSkillNameFromPath, parseFrontmatter, } from "../../resources/metadata.js";
 import { ensurePersonalDefaults, organizationIdFromResourceOwner, resourceGet, resourceGetByPath, resourceList, resourceListAccessible, SHARED_OWNER, sharedResourceOwner, WORKSPACE_OWNER, } from "../../resources/store.js";
 import { discoverAgents } from "../agent-discovery.js";
@@ -600,7 +601,7 @@ async function loadResourceIndexForPrompt(owner, scope) {
  * AGENTS.md and restarting the server is all it takes; Vite HMR invalidates
  * the bundle in dev so changes land instantly.
  */
-export async function loadResourcesForPrompt(owner, compact = false, selfAppId, orgId = getRequestOrgId() ?? null) {
+export async function loadResourcesForPrompt(owner, compact = false, selfAppId, orgId = getRequestOrgId() ?? null, opts) {
     await ensurePersonalDefaults(owner);
     const sections = [];
     const addSection = (content, governance = "inherited") => {
@@ -774,7 +775,12 @@ export async function loadResourcesForPrompt(owner, compact = false, selfAppId,
         orgId,
     }));
     try {
-        const agents = (await discoverAgents(selfAppId)).slice(0, 30);
+        // Both tools this block names by name come from the `workspaceApps` group.
+        // With that group off there is no `call-agent` to delegate through, so the
+        // block would only teach a capability the request cannot carry.
+        const agents = frameworkGroupEnabled(opts?.disabledFrameworkGroups, "workspaceApps")
+            ? (await discoverAgents(selfAppId)).slice(0, 30)
+            : [];
         if (agents.length > 0) {
             const lines = agents.map((agent) => `- ${agent.name} (${agent.id}) — ${agent.description || "Connected A2A app"}`);
             // Nothing else in the prompt or the initial tool surface tells the agent