@agent-native/dispatch 0.13.13 → 0.14.1

package/dist/server/plugins/integrations.js

@@ -1,7 +1,7 @@
 import { createIntegrationsPlugin } from "@agent-native/core/server";
 import { dispatchActions } from "../../actions/index.js";
 import { getDispatchConfig } from "../index.js";
-import { beforeDispatchProcess, resolveDispatchOwner, } from "../lib/dispatch-integrations.js";
+import { beforeDispatchProcess, resolveDispatchExecutionContext, } from "../lib/dispatch-integrations.js";
 const dispatchIntegrationActions = {
     ...dispatchActions,
     // Messaging integrations should use the core call-agent tool for cross-app
@@ -26,6 +26,9 @@ Default posture:
 
 When a user asks for something:
 - If it belongs to analytics, content, slides, clips, assets, etc., delegate via call-agent — do not re-implement the domain logic in dispatch.
+- Synthetic uptime, health-check, and URL-availability monitors belong to Analytics, even when the monitored target is another app such as Clips. Delegate creation to Analytics and relay its exact monitor URL. Dispatch-native recurring jobs are for reminders, digests, and agent workflows, not HTTP uptime probes.
+- Route by the requested artifact type, not by organization-specific names stored in code. For structured records, databases, tables, queues, boards, and intake forms, resolve the owning app and canonical destination from loaded workspace instructions/resources plus discovered app capabilities; do not assume Content, a database ID, schema, owner, or required fields. Visual designs, mockups, wireframes, screens, and interfaces belong to Design. A trusted Required target agent hint in integration context is authoritative.
+- When delegating structured intake to the resolved owning app, preserve the exact Source thread URL and the workspace instruction context, inspect the destination's current required fields, ask only for missing values, submit once, verify the saved record, and return the exact link.
 - In messaging integrations, use call-agent for cross-app delegation; do not use ask_app.
 - After call-agent returns an answer, RELAY IT DIRECTLY to the user with at most a one-line preface — do not rephrase, summarize, or add commentary. The downstream agent already crafted the answer; your job is delivery, not editing. This minimizes round-trips and keeps the user-visible reply fast.
 - Exception: if the downstream agent reports a missing model/provider credential, do not name exact env vars, Vault keys, tokens, or secrets. Say the target app needs an LLM connection and recommend connecting Builder/managed LLM for that app; keep bring-your-own provider keys as a secondary option only if the user asks.
@@ -53,7 +56,7 @@ const dispatchIntegrationsPlugin = async (nitroApp) => {
     const plugin = createIntegrationsPlugin({
         appId: "dispatch",
         actions: dispatchIntegrationActions,
-        resolveOwner: resolveDispatchOwner,
+        resolveExecutionContext: resolveDispatchExecutionContext,
         beforeProcess: beforeDispatchProcess,
         systemPrompt,
         // Inherit the framework default (claude-sonnet-4-6 from

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,oBAAoB,GACrB,MAAM,iCAAiC,CAAC;AAEzC,MAAM,0BAA0B,GAAG;IACjC,GAAG,eAAe;IAClB,2EAA2E;IAC3E,6EAA6E;IAC7E,6EAA6E;IAC7E,OAAO,EAAE;QACP,GAAG,eAAe,CAAC,OAAO;QAC1B,SAAS,EAAE,KAAK;KACjB;CACF,CAAC;AAEF,MAAM,kCAAkC,GAAG;;;;;;;;;;;;;;;;;;;;;;;;4FAwBiD,CAAC;AAE7F;;;;GAIG;AACH,MAAM,0BAA0B,GAAG,KAAK,EAAE,QAAa,EAAE,EAAE;IACzD,MAAM,EAAE,YAAY,GAAG,EAAE,EAAE,GAAG,iBAAiB,EAAE,CAAC;IAClD,MAAM,cAAc,GAAG,YAAY,CAAC,YAAY,CAAC;IACjD,MAAM,YAAY,GAChB,OAAO,cAAc,KAAK,QAAQ;QAChC,CAAC,CAAC,cAAc;QAChB,CAAC,CAAC,OAAO,cAAc,KAAK,UAAU;YACpC,CAAC,CAAC,cAAc,CAAC,kCAAkC,CAAC;YACpD,CAAC,CAAC,kCAAkC,CAAC;IAE3C,MAAM,MAAM,GAAG,wBAAwB,CAAC;QACtC,KAAK,EAAE,UAAU;QACjB,OAAO,EAAE,0BAA0B;QACnC,YAAY,EAAE,oBAAoB;QAClC,aAAa,EAAE,qBAAqB;QACpC,YAAY;QACZ,wDAAwD;QACxD,yEAAyE;QACzE,+DAA+D;QAC/D,6EAA6E;KAC9E,CAAC,CAAC;IAEH,OAAO,MAAM,CAAC,QAAQ,CAAC,CAAC;AAC1B,CAAC,CAAC;AAEF,eAAe,0BAA0B,CAAC","sourcesContent":["import { createIntegrationsPlugin } from \"@agent-native/core/server\";\n\nimport { dispatchActions } from \"../../actions/index.js\";\nimport { getDispatchConfig } from \"../index.js\";\nimport {\n  beforeDispatchProcess,\n  resolveDispatchOwner,\n} from \"../lib/dispatch-integrations.js\";\n\nconst dispatchIntegrationActions = {\n  ...dispatchActions,\n  // Messaging integrations should use the core call-agent tool for cross-app\n  // delegation because it queues A2A continuations when serverless budgets are\n  // tight. The MCP-facing ask_app action is still available outside this path.\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. Apps you can delegate to include slides (decks/presentations), analytics (data/dashboards), content (docs/articles), forms (form builder), clips (screen recordings), design (visual designs), and assets (brand libraries plus generated images/videos).\n- Use the available-apps prompt context first, then list-connected-agents when you need fresh details, to see what agents are available before assuming a request must be handled locally.\n- When asked whether workspace apps expose agent cards or A2A endpoints, call list-workspace-apps with includeAgentCards=true. Without that probe, missing agent-card fields mean unchecked, not unavailable.\n- 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- 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 connecting Builder/managed LLM for that app; keep bring-your-own provider keys as a secondary option only if the user asks.\n- If the user asks to create, build, make, scaffold, or generate an \"agent\" from Dispatch chat or by tagging @agent-native in Slack, email, or Telegram, first classify the ask. If it is a simple Dispatch-native behavior like a reminder, digest, monitor, routing rule, saved instruction, or recurring workflow, create or update the recurring job/resource/destination in Dispatch. If it is a robust unique product or teammate that needs its own UI, data model, actions, integrations, or domain workflow, treat it as a new workspace app and call start-workspace-app-creation.\n- If a new-app prompt asks for access to Mail, Calendar, Analytics, Brain, Assets, or similar first-party app data/agents, keep using the existing hosted/connected app and A2A path. Do not ask Builder to scaffold those apps as children of the new app unless the user explicitly asks for a customized fork/copy.\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. If the request is too vague to classify, ask one concise follow-up. If the action returns mode \"builder\", reply with the Builder branch URL; Builder is responsible for creating the separate workspace app under apps/<app-id>, mounting it at /<app-id>, ensuring apps/<app-id>/package.json exists with name/displayName and description so Dispatch discovers it, using relative /<app-id> links instead of hardcoded localhost/dev ports, and preserving APP_BASE_PATH/VITE_APP_BASE_PATH via appBasePath() in the React Router client entry. The new app lives at the workspace root /<app-id>, NOT under /dispatch/<app-id>, /apps/<app-id>, or any other Dispatch tab — when telling the user where to find it, link to /<app-id> only. There is no separate workspace app registry to edit. If it returns mode \"local-agent\", tell the user it is ready for the local code agent and include the returned app path/prompt summary. If it returns mode \"coming-soon\", say this requires a code change and they can edit locally or use Builder.io to edit this code in the cloud and continue customizing the app any way they like; do not send them to Builder org/beta settings. If it returns mode \"builder-unavailable\", report the action's message exactly enough to preserve the missing identity/credential detail.\n- For digests, reminders, or saved behavior, prefer recurring jobs, resources, or destinations over chat replies.\n- Keep responses concise and operational — messaging platforms have character limits.\n- Use markdown sparingly (bold and lists are fine, avoid complex formatting).\n- If a task requires many steps, summarize what you did rather than streaming every detail.`;\n\n/**\n * Defer plugin construction until the Nitro plugin actually fires so the\n * config-aware system prompt resolves AFTER `setupDispatch(config)` has\n * stamped the active config (plugin module load order is not guaranteed).\n */\nconst dispatchIntegrationsPlugin = async (nitroApp: any) => {\n  const { integrations = {} } = getDispatchConfig();\n  const promptOverride = integrations.systemPrompt;\n  const systemPrompt =\n    typeof promptOverride === \"string\"\n      ? promptOverride\n      : typeof promptOverride === \"function\"\n        ? promptOverride(DISPATCH_INTEGRATION_SYSTEM_PROMPT)\n        : DISPATCH_INTEGRATION_SYSTEM_PROMPT;\n\n  const plugin = createIntegrationsPlugin({\n    appId: \"dispatch\",\n    actions: dispatchIntegrationActions,\n    resolveOwner: resolveDispatchOwner,\n    beforeProcess: beforeDispatchProcess,\n    systemPrompt,\n    // Inherit the framework default (claude-sonnet-4-6 from\n    // packages/core/src/integrations/plugin.ts). Haiku was tried for latency\n    // but hallucinated URLs/IDs after delegated call-agent results\n    // (e.g. inventing `https://slides.workspace.com/deck/builder-io-deck-2024`).\n  });\n\n  return plugin(nitroApp);\n};\n\nexport default dispatchIntegrationsPlugin;\n"]}
+{"version":3,"file":"integrations.js","sourceRoot":"","sources":["../../../src/server/plugins/integrations.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,wBAAwB,EAAE,MAAM,2BAA2B,CAAC;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,2EAA2E;IAC3E,6EAA6E;IAC7E,6EAA6E;IAC7E,OAAO,EAAE;QACP,GAAG,eAAe,CAAC,OAAO;QAC1B,SAAS,EAAE,KAAK;KACjB;CACF,CAAC;AAEF,MAAM,kCAAkC,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;4FA2BiD,CAAC;AAE7F;;;;GAIG;AACH,MAAM,0BAA0B,GAAG,KAAK,EAAE,QAAa,EAAE,EAAE;IACzD,MAAM,EAAE,YAAY,GAAG,EAAE,EAAE,GAAG,iBAAiB,EAAE,CAAC;IAClD,MAAM,cAAc,GAAG,YAAY,CAAC,YAAY,CAAC;IACjD,MAAM,YAAY,GAChB,OAAO,cAAc,KAAK,QAAQ;QAChC,CAAC,CAAC,cAAc;QAChB,CAAC,CAAC,OAAO,cAAc,KAAK,UAAU;YACpC,CAAC,CAAC,cAAc,CAAC,kCAAkC,CAAC;YACpD,CAAC,CAAC,kCAAkC,CAAC;IAE3C,MAAM,MAAM,GAAG,wBAAwB,CAAC;QACtC,KAAK,EAAE,UAAU;QACjB,OAAO,EAAE,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  // Messaging integrations should use the core call-agent tool for cross-app\n  // delegation because it queues A2A continuations when serverless budgets are\n  // tight. The MCP-facing ask_app action is still available outside this path.\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. Apps you can delegate to include slides (decks/presentations), analytics (data/dashboards), content (docs/articles), forms (form builder), clips (screen recordings), design (visual designs), and assets (brand libraries plus generated images/videos).\n- Use the available-apps prompt context first, then list-connected-agents when you need fresh details, to see what agents are available before assuming a request must be handled locally.\n- When asked whether workspace apps expose agent cards or A2A endpoints, call list-workspace-apps with includeAgentCards=true. Without that probe, missing agent-card fields mean unchecked, not unavailable.\n- 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 connecting Builder/managed LLM for that app; keep bring-your-own provider keys as a secondary option only if the user asks.\n- If the user asks to create, build, make, scaffold, or generate an \"agent\" from Dispatch chat or by tagging @agent-native in Slack, email, or Telegram, first classify the ask. If it is a simple Dispatch-native behavior like a reminder, digest, monitor, routing rule, saved instruction, or recurring workflow, create or update the recurring job/resource/destination in Dispatch. If it is a robust unique product or teammate that needs its own UI, data model, actions, integrations, or domain workflow, treat it as a new workspace app and call start-workspace-app-creation.\n- If a new-app prompt asks for access to Mail, Calendar, Analytics, Brain, Assets, or similar first-party app data/agents, keep using the existing hosted/connected app and A2A path. Do not ask Builder to scaffold those apps as children of the new app unless the user explicitly asks for a customized fork/copy.\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. If the request is too vague to classify, ask one concise follow-up. If the action returns mode \"builder\", reply with the Builder branch URL; Builder is responsible for creating the separate workspace app under apps/<app-id>, mounting it at /<app-id>, ensuring apps/<app-id>/package.json exists with name/displayName and description so Dispatch discovers it, using relative /<app-id> links instead of hardcoded localhost/dev ports, and preserving APP_BASE_PATH/VITE_APP_BASE_PATH via appBasePath() in the React Router client entry. The new app lives at the workspace root /<app-id>, NOT under /dispatch/<app-id>, /apps/<app-id>, or any other Dispatch tab — when telling the user where to find it, link to /<app-id> only. There is no separate workspace app registry to edit. If it returns mode \"local-agent\", tell the user it is ready for the local code agent and include the returned app path/prompt summary. If it returns mode \"coming-soon\", say this requires a code change and they can edit locally or use Builder.io to edit this code in the cloud and continue customizing the app any way they like; do not send them to Builder org/beta settings. If it returns mode \"builder-unavailable\", report the action's message exactly enough to preserve the missing identity/credential detail.\n- For digests, reminders, or saved behavior, prefer recurring jobs, resources, or destinations over chat replies.\n- Keep responses concise and operational — messaging platforms have character limits.\n- Use markdown sparingly (bold and lists are fine, avoid complex formatting).\n- If a task requires many steps, summarize what you did rather than streaming every detail.`;\n\n/**\n * Defer plugin construction until the Nitro plugin actually fires so the\n * config-aware system prompt resolves AFTER `setupDispatch(config)` has\n * stamped the active config (plugin module load order is not guaranteed).\n */\nconst dispatchIntegrationsPlugin = async (nitroApp: any) => {\n  const { integrations = {} } = getDispatchConfig();\n  const promptOverride = integrations.systemPrompt;\n  const systemPrompt =\n    typeof promptOverride === \"string\"\n      ? promptOverride\n      : typeof promptOverride === \"function\"\n        ? promptOverride(DISPATCH_INTEGRATION_SYSTEM_PROMPT)\n        : DISPATCH_INTEGRATION_SYSTEM_PROMPT;\n\n  const plugin = createIntegrationsPlugin({\n    appId: \"dispatch\",\n    actions: 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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/dispatch",
-  "version": "0.13.13",
+  "version": "0.14.1",
   "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": {
@@ -94,7 +94,7 @@
     "typescript-7": "npm:typescript@^7.0.2",
     "vite": "8.1.0",
     "vitest": "^4.1.5",
-    "@agent-native/core": "0.92.1"
+    "@agent-native/core": "0.94.0"
   },
   "peerDependencies": {
     "@agent-native/core": ">=0.8.0",

package/src/actions/navigate.ts

@@ -27,7 +27,7 @@ export default defineAction({
       .string()
       .optional()
       .describe(
-        "Named dispatch view to navigate to. Built-in views include chat, overview, apps, metrics, new-app, vault, integrations, messaging, workspace, agents, destinations, identities, approvals, automations, audit, thread-debug, dreams, and team. Generated Dispatch extension tabs can also use their nav item id.",
+        "Named dispatch view to navigate to. Built-in views include chat, overview, apps, operations (or monitoring, observability, database), metrics, new-app, vault, integrations, messaging, workspace, agents, destinations, identities, approvals, automations, audit, thread-debug, dreams, and team. Generated Dispatch extension tabs can also use their nav item id.",
       ),
     path: z.string().optional().describe("URL path to navigate to"),
     threadId: z

package/src/actions/provider-api-audit.spec.ts

@@ -0,0 +1,52 @@
+import { describe, expect, it } from "vitest";
+
+import {
+  buildProviderApiAuditSummary,
+  sanitizeProviderApiAuditPath,
+} from "./provider-api-audit.js";
+
+describe("provider API audit summaries", () => {
+  it("redacts every query value from relative and absolute request paths", () => {
+    expect(
+      sanitizeProviderApiAuditPath(
+        "/v1/resources?api_key=secret-example&cursor=page-example",
+      ),
+    ).toBe("/v1/resources?api_key=[redacted]&cursor=[redacted]");
+    expect(
+      sanitizeProviderApiAuditPath(
+        "https://api.example.test/download?X-Amz-Signature=signed-example&part=1",
+      ),
+    ).toBe(
+      "https://api.example.test/download?X-Amz-Signature=[redacted]&part=[redacted]",
+    );
+  });
+
+  it("redacts credential-named and opaque path segments", () => {
+    expect(
+      sanitizeProviderApiAuditPath(
+        "/hooks/token/secret-example-value/callback/api_key=another-example",
+      ),
+    ).toBe("/hooks/token/[redacted]/callback/api_key=[redacted]");
+    expect(
+      sanitizeProviderApiAuditPath(
+        "/download/0123456789abcdef0123456789abcdef/file",
+      ),
+    ).toBe("/download/[redacted]/file");
+  });
+
+  it("drops fragments and keeps explicit query arguments out of summaries", () => {
+    const summary = buildProviderApiAuditSummary({
+      method: "get",
+      provider: "example",
+      path: "/records?filter=customer-example#secret-example-fragment",
+      query: { api_key: "query-secret-example" },
+    } as Parameters<typeof buildProviderApiAuditSummary>[0] & {
+      query: unknown;
+    });
+
+    expect(summary).toBe("GET example /records?filter=[redacted]");
+    expect(summary).not.toContain("customer-example");
+    expect(summary).not.toContain("secret-example");
+    expect(summary).not.toContain("query-secret-example");
+  });
+});

package/src/actions/provider-api-audit.ts

@@ -0,0 +1,88 @@
+const REDACTED = "[redacted]";
+
+const CREDENTIAL_NAME =
+  /^(?:api[-_]?key|access[-_]?token|auth(?:orization)?|bearer|credential|password|secret|signature|sig|token|x-amz-credential|x-amz-signature)$/i;
+
+function decodePathSegment(segment: string): string {
+  try {
+    return decodeURIComponent(segment);
+  } catch {
+    return segment;
+  }
+}
+
+function looksLikeCredentialValue(segment: string): boolean {
+  const value = decodePathSegment(segment);
+  if (/^eyJ[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+$/.test(value)) {
+    return true;
+  }
+  if (
+    /^(?:sk|pk|rk|ghp|github_pat|xox[baprs]|ya29|AIza)[-_][A-Za-z0-9_-]+$/i.test(
+      value,
+    )
+  ) {
+    return true;
+  }
+  return value.length >= 32 && /^[A-Za-z0-9._~-]+$/.test(value);
+}
+
+function sanitizePathname(pathname: string): string {
+  let redactNext = false;
+  return pathname
+    .split("/")
+    .map((segment) => {
+      if (!segment) return segment;
+      const decoded = decodePathSegment(segment);
+      if (redactNext) {
+        redactNext = false;
+        return REDACTED;
+      }
+
+      const assignment = decoded.match(/^([^=:]+)([=:])(.+)$/);
+      if (assignment && CREDENTIAL_NAME.test(assignment[1]!)) {
+        return `${assignment[1]}${assignment[2]}${REDACTED}`;
+      }
+      if (CREDENTIAL_NAME.test(decoded)) {
+        redactNext = true;
+        return segment;
+      }
+      return looksLikeCredentialValue(segment) ? REDACTED : segment;
+    })
+    .join("/");
+}
+
+function sanitizeQuery(search: string): string {
+  if (!search) return "";
+  const redacted = Array.from(new URLSearchParams(search).keys(), (key) => {
+    const safeKey = encodeURIComponent(key.slice(0, 100));
+    return `${safeKey}=${REDACTED}`;
+  });
+  return redacted.length > 0 ? `?${redacted.join("&")}` : "";
+}
+
+export function sanitizeProviderApiAuditPath(path: unknown): string {
+  const raw = String(path ?? "");
+  const withoutFragment = raw.split("#", 1)[0] ?? "";
+
+  try {
+    const url = new URL(withoutFragment);
+    return `${url.protocol}//${url.host}${sanitizePathname(url.pathname)}${sanitizeQuery(url.search)}`;
+  } catch {
+    const queryIndex = withoutFragment.indexOf("?");
+    const pathname =
+      queryIndex >= 0 ? withoutFragment.slice(0, queryIndex) : withoutFragment;
+    const search = queryIndex >= 0 ? withoutFragment.slice(queryIndex + 1) : "";
+    return `${sanitizePathname(pathname)}${sanitizeQuery(search)}`;
+  }
+}
+
+export function buildProviderApiAuditSummary(args: {
+  method?: unknown;
+  provider?: unknown;
+  path?: unknown;
+}): string {
+  const method = String(args.method || "GET").toUpperCase();
+  const provider = String(args.provider ?? "");
+  const path = sanitizeProviderApiAuditPath(args.path);
+  return `${method} ${provider} ${path}`.slice(0, 200);
+}

package/src/actions/provider-api-request.ts

@@ -7,6 +7,7 @@ import {
   DISPATCH_APP_ID,
   executeProviderApiRequest,
 } from "../server/lib/provider-api.js";
+import { buildProviderApiAuditSummary } from "./provider-api-audit.js";
 
 const MethodSchema = z.enum(["GET", "POST", "PUT", "PATCH", "DELETE", "HEAD"]);
 
@@ -197,6 +198,15 @@ export default defineAction({
       ),
   }),
   http: false,
+  audit: {
+    recordInputs: false,
+    target: (args) => ({
+      type: "provider-api",
+      id: String(args.provider),
+      visibility: "private",
+    }),
+    summary: (args) => buildProviderApiAuditSummary(args),
+  },
   run: async (args) => {
     if (args.stageAs) {
       const ctx = getCredentialContext();

package/src/actions/send-platform-message.spec.ts

@@ -0,0 +1,108 @@
+import { beforeEach, describe, expect, it, vi } from "vitest";
+
+const mocks = vi.hoisted(() => ({
+  getInstallation: vi.fn(),
+  resolveTokenBundle: vi.fn(),
+  resolveSecret: vi.fn(),
+  sendMessageToTarget: vi.fn(),
+  getDestinationById: vi.fn(),
+  slackAdapter: vi.fn(),
+}));
+
+vi.mock("@agent-native/core/integrations", () => ({
+  listIntegrationInstallations: mocks.getInstallation,
+  resolveIntegrationTokenBundle: mocks.resolveTokenBundle,
+}));
+
+vi.mock("@agent-native/core/server", () => ({
+  getRequestUserEmail: () => "member@example.com",
+  getRequestOrgId: () => "org-a",
+  resolveSecret: mocks.resolveSecret,
+  isEmailConfigured: vi.fn(),
+  slackAdapter: mocks.slackAdapter,
+  telegramAdapter: vi.fn(),
+  emailAdapter: vi.fn(),
+}));
+
+vi.mock("../server/lib/dispatch-store.js", () => ({
+  getDestinationById: mocks.getDestinationById,
+}));
+
+const action = (await import("./send-platform-message.js")).default;
+
+describe("send-platform-message tenant scoping", () => {
+  beforeEach(() => {
+    vi.clearAllMocks();
+    mocks.getDestinationById.mockResolvedValue(null);
+    mocks.resolveSecret.mockResolvedValue(null);
+    mocks.slackAdapter.mockImplementation(
+      (options: { resolveBotToken: () => Promise<string | undefined> }) => ({
+        formatAgentResponse: (text: string) => ({
+          text,
+          platformContext: {},
+        }),
+        sendMessageToTarget: async (...args: unknown[]) => {
+          expect(await options.resolveBotToken()).toBe("own-managed-token");
+          return mocks.sendMessageToTarget(...args);
+        },
+      }),
+    );
+  });
+
+  it("resolves and uses only the caller org's Slack installation", async () => {
+    mocks.getInstallation.mockResolvedValue([
+      {
+        id: "installation-a",
+        installationKey: "team:T1:app:A1",
+        teamId: "T1",
+        enterpriseId: null,
+      },
+    ]);
+    mocks.resolveTokenBundle.mockResolvedValue({
+      accessToken: "own-managed-token",
+    });
+
+    await action.run(
+      {
+        platform: "slack",
+        destination: "C1",
+        tenantId: "T1",
+        text: "hello",
+      },
+      {} as never,
+    );
+
+    expect(mocks.getInstallation).toHaveBeenCalledWith(
+      {
+        userEmail: "member@example.com",
+        orgId: "org-a",
+      },
+      "slack",
+    );
+    expect(mocks.resolveTokenBundle).toHaveBeenCalledWith(
+      "slack",
+      "team:T1:app:A1",
+    );
+    expect(mocks.sendMessageToTarget).toHaveBeenCalledOnce();
+  });
+
+  it("does not use another org's managed installation", async () => {
+    mocks.getInstallation.mockResolvedValue([]);
+
+    await expect(
+      action.run(
+        {
+          platform: "slack",
+          destination: "C1",
+          tenantId: "T-other",
+          text: "hello",
+        },
+        {} as never,
+      ),
+    ).rejects.toThrow("That Slack workspace is not connected");
+
+    expect(mocks.resolveTokenBundle).not.toHaveBeenCalled();
+    expect(mocks.slackAdapter).not.toHaveBeenCalled();
+    expect(mocks.sendMessageToTarget).not.toHaveBeenCalled();
+  });
+});

package/src/actions/send-platform-message.ts

@@ -1,5 +1,11 @@
 import { defineAction } from "@agent-native/core";
 import {
+  listIntegrationInstallations,
+  resolveIntegrationTokenBundle,
+} from "@agent-native/core/integrations";
+import {
+  getRequestOrgId,
+  getRequestUserEmail,
   slackAdapter,
   telegramAdapter,
   emailAdapter,
@@ -8,21 +14,52 @@ import {
 } from "@agent-native/core/server";
 import { z } from "zod";
 
-import {
-  getDestinationById,
-  recordAudit,
-} from "../server/lib/dispatch-store.js";
+import { getDestinationById } from "../server/lib/dispatch-store.js";
 
-function getAdapter(platform: "slack" | "telegram" | "email") {
+function getAdapter(
+  platform: "slack" | "telegram" | "email",
+  slackToken?: string,
+) {
   if (platform === "email") return emailAdapter();
-  return platform === "slack" ? slackAdapter() : telegramAdapter();
+  return platform === "slack"
+    ? slackAdapter({ resolveBotToken: async () => slackToken })
+    : telegramAdapter();
 }
 
 async function assertOutboundConfigured(
   platform: "slack" | "telegram" | "email",
-) {
-  if (platform === "slack" && !(await resolveSecret("SLACK_BOT_TOKEN"))) {
-    throw new Error("Slack outbound messaging is not configured");
+  tenantId?: string,
+): Promise<string | undefined> {
+  if (platform === "slack") {
+    const userEmail = getRequestUserEmail();
+    if (!userEmail) throw new Error("An authenticated user is required");
+    const installations = tenantId
+      ? await listIntegrationInstallations(
+          { userEmail, orgId: getRequestOrgId() ?? null },
+          "slack",
+        )
+      : [];
+    const installation =
+      installations.find(
+        (candidate) =>
+          candidate.teamId === tenantId || candidate.enterpriseId === tenantId,
+      ) ?? null;
+    const managed = installation
+      ? await resolveIntegrationTokenBundle(
+          "slack",
+          installation.installationKey,
+        )
+      : null;
+    const token =
+      managed?.accessToken ?? (await resolveSecret("SLACK_BOT_TOKEN"));
+    if (!token) {
+      throw new Error(
+        tenantId
+          ? "That Slack workspace is not connected"
+          : "Select a Slack workspace for managed outbound messaging",
+      );
+    }
+    return token;
   }
   if (platform === "telegram" && !(await resolveSecret("TELEGRAM_BOT_TOKEN"))) {
     throw new Error("Telegram outbound messaging is not configured");
@@ -45,9 +82,29 @@ export default defineAction({
     destinationId: z.string().optional().describe("Saved destination id"),
     destination: z.string().optional().describe("Raw platform destination id"),
     threadRef: z.string().optional().describe("Optional thread reference"),
+    tenantId: z
+      .string()
+      .optional()
+      .describe("Slack workspace/team id for managed installations"),
     text: z.string().describe("Message to send"),
   }),
-  run: async ({ platform, destinationId, destination, threadRef, text }) => {
+  audit: {
+    recordInputs: false,
+    target: (args) => ({
+      type: "destination",
+      id: args.destinationId || args.destination || "unknown",
+      visibility: "private",
+    }),
+    summary: (args) => `Sent proactive ${args.platform || "saved"} message`,
+  },
+  run: async ({
+    platform,
+    destinationId,
+    destination,
+    threadRef,
+    tenantId,
+    text,
+  }) => {
     const saved = destinationId
       ? await getDestinationById(destinationId)
       : null;
@@ -63,9 +120,12 @@ export default defineAction({
       throw new Error("A platform and destination are required");
     }
 
-    await assertOutboundConfigured(resolvedPlatform);
+    const slackToken = await assertOutboundConfigured(
+      resolvedPlatform,
+      tenantId,
+    );
 
-    const adapter = getAdapter(resolvedPlatform);
+    const adapter = getAdapter(resolvedPlatform, slackToken);
     if (!adapter.sendMessageToTarget) {
       throw new Error(
         `Platform ${resolvedPlatform} does not support proactive outbound messaging`,
@@ -76,19 +136,7 @@ export default defineAction({
       destination: resolvedDestination,
       threadRef: resolvedThreadRef,
       label: saved?.name || undefined,
-    });
-
-    await recordAudit({
-      action: "message.sent",
-      targetType: "destination",
-      targetId: destinationId || resolvedDestination,
-      summary: `Sent proactive ${resolvedPlatform} message${saved?.name ? ` to ${saved.name}` : ""}`,
-      metadata: {
-        platform: resolvedPlatform,
-        destination: resolvedDestination,
-        threadRef: resolvedThreadRef,
-        text,
-      },
+      tenantId,
     });
 
     return {

package/src/actions/view-screen.ts

@@ -90,6 +90,17 @@ export default defineAction({
       screen.connectedAgents = connectedAgents;
       screen.mcpAppAccess = mcpAccess;
     }
+    if (navigation?.view === "operations") {
+      const nav = navigation as { operationsView?: string };
+      screen.operatorConsole = {
+        view: nav.operationsView === "database" ? "database" : "monitoring",
+        monitoring:
+          "The shared observability dashboard provides traces, conversations, evaluations, experiments, and feedback.",
+        database:
+          "The shared database admin is available in Code mode for table browsing and SQL inspection.",
+        relatedTools: ["thread-debug", "audit", "destinations", "automations"],
+      };
+    }
     if (
       navigation?.view === "overview" ||
       navigation?.view === "metrics" ||