@agentforge-io/core 0.2.0 → 1.0.0

package/dist/services/agent.service.d.ts

@@ -29,6 +29,18 @@ export interface AgentRecord {
     mcpServers?: McpServerConfig[];
     metadata?: Record<string, unknown>;
     isActive?: boolean;
+    /**
+     * When set, connector tools (Gmail, Drive, ...) are resolved against
+     * this user's OAuth authorizations instead of the caller's. Used by
+     * public-chat agents — a visitor's browser session can leverage the
+     * agent owner's authorized connectors without exposing the owner's
+     * identity in the conversation record.
+     *
+     * Leave undefined for personal agents where the caller owns the
+     * connectors themselves; in that case the SDK falls back to the
+     * caller's userId, preserving the original behavior.
+     */
+    connectorOwnerUserId?: string;
 }
 /**
  * Host-supplied resolver for per-tenant agent configurations. The SDK never

package/dist/services/agent.service.js

@@ -157,7 +157,11 @@ class AgentService {
             role: 'user',
             content: params.content,
         });
-        const extraTools = await this.resolveExtraTools(params.userId);
+        // Connector tools follow `agent.connectorOwnerUserId` when the
+        // resolved agent declares one (e.g. a public-chat agent reusing the
+        // owner's Gmail authorization); otherwise they fall back to the
+        // caller's userId, which is the historical personal-agent path.
+        const extraTools = await this.resolveExtraTools(agent.connectorOwnerUserId ?? params.userId);
         const response = await this.runner.run(agent, messages, {
             userId: params.userId,
             conversationId: params.conversationId,
@@ -217,7 +221,10 @@ class AgentService {
         });
         let fullContent = '';
         let finalUsage = { inputTokens: 0, outputTokens: 0, totalTokens: 0 };
-        const extraTools = await this.resolveExtraTools(params.userId);
+        // Same precedence as sendMessage — agent.connectorOwnerUserId takes
+        // priority so a public-chat agent always uses the owner's connector
+        // toolbelt regardless of which visitor session is streaming.
+        const extraTools = await this.resolveExtraTools(agent.connectorOwnerUserId ?? params.userId);
         for await (const chunk of this.runner.stream(agent, messages, {
             userId: params.userId,
             conversationId: params.conversationId,
@@ -325,5 +332,6 @@ function toAgentDefinition(record) {
         tools: record.tools,
         mcpServers: record.mcpServers,
         metadata: record.metadata,
+        connectorOwnerUserId: record.connectorOwnerUserId,
     };
 }

package/dist/types/config.types.d.ts

@@ -94,6 +94,15 @@ export interface AgentDefinition {
     requiredPlan?: string[];
     /** Custom metadata */
     metadata?: Record<string, unknown>;
+    /**
+     * When set, connector tools (Gmail, Drive, ...) are resolved against
+     * this user's OAuth authorizations instead of the caller's. Lets a
+     * public-chat agent reuse the agent owner's authorized connectors
+     * while keeping the conversation scoped to the visitor. Leave
+     * undefined for personal agents — the SDK falls back to the caller's
+     * userId, preserving the original behavior.
+     */
+    connectorOwnerUserId?: string;
 }
 /**
  * Configuration for an MCP server the runtime should connect to.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agentforge-io/core",
-  "version": "0.2.0",
+  "version": "1.0.0",
   "description": "Framework-free AI runtime SDK. Owns: agent loop (Anthropic), conversations, tools, streaming, agent-job queue, SdkHooks. Identity, billing, infra (email/uploads/secrets) live in the host's modules — not here.",
   "license": "MIT",
   "main": "dist/index.js",