@lobehub/lobehub 2.0.5 → 2.0.7

package/.eslintrc.js

@@ -20,6 +20,7 @@ config.rules['unicorn/no-array-for-each'] = 0;
 config.rules['unicorn/prefer-number-properties'] = 0;
 config.rules['unicorn/prefer-query-selector'] = 0;
 config.rules['unicorn/no-array-callback-reference'] = 0;
+config.rules['@typescript-eslint/no-use-before-define'] = 0;
 // FIXME: Linting error in src/app/[variants]/(main)/chat/features/Migration/DBReader.ts, the fundamental solution should be upgrading typescript-eslint
 config.rules['@typescript-eslint/no-useless-constructor'] = 0;
 config.rules['@next/next/no-img-element'] = 0;

package/CHANGELOG.md

@@ -2,6 +2,56 @@
 
 # Changelog
 
+### [Version 2.0.7](https://github.com/lobehub/lobe-chat/compare/v2.0.6...v2.0.7)
+
+<sup>Released on **2026-01-28**</sup>
+
+#### 🐛 Bug Fixes
+
+- **model-runtime**: Include tool_calls in speed metrics & add getActiveTraceId.
+
+<br/>
+
+<details>
+<summary><kbd>Improvements and Fixes</kbd></summary>
+
+#### What's fixed
+
+- **model-runtime**: Include tool_calls in speed metrics & add getActiveTraceId, closes [#11927](https://github.com/lobehub/lobe-chat/issues/11927) ([b24da44](https://github.com/lobehub/lobe-chat/commit/b24da44))
+
+</details>
+
+<div align="right">
+
+[![](https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square)](#readme-top)
+
+</div>
+
+### [Version 2.0.6](https://github.com/lobehub/lobe-chat/compare/v2.0.5...v2.0.6)
+
+<sup>Released on **2026-01-27**</sup>
+
+#### 🐛 Bug Fixes
+
+- **misc**: The klavis in onboarding connect timeout fixed.
+
+<br/>
+
+<details>
+<summary><kbd>Improvements and Fixes</kbd></summary>
+
+#### What's fixed
+
+- **misc**: The klavis in onboarding connect timeout fixed, closes [#11918](https://github.com/lobehub/lobe-chat/issues/11918) ([bc165be](https://github.com/lobehub/lobe-chat/commit/bc165be))
+
+</details>
+
+<div align="right">
+
+[![](https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square)](#readme-top)
+
+</div>
+
 ### [Version 2.0.5](https://github.com/lobehub/lobe-chat/compare/v2.0.4...v2.0.5)
 
 <sup>Released on **2026-01-27**</sup>

package/changelog/v2.json

@@ -1,4 +1,18 @@
 [
+  {
+    "children": {},
+    "date": "2026-01-28",
+    "version": "2.0.7"
+  },
+  {
+    "children": {
+      "fixes": [
+        "The klavis in onboarding connect timeout fixed."
+      ]
+    },
+    "date": "2026-01-27",
+    "version": "2.0.6"
+  },
   {
     "children": {
       "fixes": [

package/docs/self-hosting/advanced/auth/clerk-to-betterauth.mdx

@@ -63,6 +63,8 @@ For small self-hosted deployments, the simplest approach is to let users reset t
 
    Remove Clerk variables and add Better Auth variables:
 
+   <GenerateSecret envName="AUTH_SECRET" />
+
    ```bash
    # Remove these
    # NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=xxx

package/docs/self-hosting/advanced/auth/clerk-to-betterauth.zh-CN.mdx

@@ -61,6 +61,8 @@ tags:
 
    移除 Clerk 变量并添加 Better Auth 变量：
 
+   <GenerateSecret envName="AUTH_SECRET" />
+
    ```bash
    # 移除这些
    # NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=xxx

package/docs/self-hosting/advanced/auth/nextauth-to-betterauth.mdx

@@ -116,6 +116,8 @@ For small self-hosted deployments, the simplest approach is to let users re-logi
 
    Remove NextAuth variables and add Better Auth variables:
 
+   <GenerateSecret envName="AUTH_SECRET" />
+
    ```bash
    # Remove these
    # NEXT_AUTH_SECRET=xxx

package/docs/self-hosting/advanced/auth/nextauth-to-betterauth.zh-CN.mdx

@@ -111,6 +111,8 @@ Better Auth 支持更多功能，以下是新增的环境变量：
 
    移除 NextAuth 变量并添加 Better Auth 变量：
 
+   <GenerateSecret envName="AUTH_SECRET" />
+
    ```bash
    # 移除这些
    # NEXT_AUTH_SECRET=xxx

package/docs/self-hosting/platform/docker.mdx

@@ -58,6 +58,12 @@ Here is the process for deploying the LobeHub server database version on a Linux
 
   ### Create a file named `lobe-chat.env` to store environment variables:
 
+  Click the buttons below to generate required secrets:
+
+  <GenerateSecret envName="KEY_VAULTS_SECRET" />
+
+  <GenerateSecret envName="AUTH_SECRET" />
+
   ```shell
   # Website domain
   APP_URL=https://your-prod-domain.com

package/docs/self-hosting/platform/docker.zh-CN.mdx

@@ -54,6 +54,12 @@ tags:
 
   ### 创建名为 `lobe-chat.env` 文件用于存放环境变量：
 
+  点击下方按钮生成所需密钥：
+
+  <GenerateSecret envName="KEY_VAULTS_SECRET" />
+
+  <GenerateSecret envName="AUTH_SECRET" />
+
   ```shell
   # 网站域名
   APP_URL=https://your-prod-domain.com

package/docs/self-hosting/platform/vercel.mdx

@@ -114,55 +114,6 @@ The server-side database needs to be paired with a user authentication service t
   <Callout type={'info'}>
     For advanced features like SSO providers, magic link login, and email verification, see [Authentication Service](/docs/self-hosting/advanced/auth).
   </Callout>
-
-  ### Add Public and Private Key Environment Variables in Vercel
-
-  In Vercel's deployment environment variables, add the `NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY` and `CLERK_SECRET_KEY` environment variables. You can click on "API Keys" in the menu, then copy the corresponding values and paste them into Vercel's environment variables.
-
-  <Image alt={'Find the corresponding public and private key environment variables in Clerk'} src={'/blog/assets28616219/89883703-7a1a-4a11-b944-5d804544e57c.webp'} />
-
-  The environment variables required for this step are as follows:
-
-  ```shell
-  NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=pk_live_xxxxxxxxxxx
-  CLERK_SECRET_KEY=sk_live_xxxxxxxxxxxxxxxxxxxxxx
-  ```
-
-  Add the above variables to Vercel:
-
-  <Image alt={'Add Clerk public and private key environment variables in Vercel'} src={'/blog/assets28616219/2bfa13df-6e20-4768-97c0-4dad06c85a2f.webp'} />
-
-  ### Create and Configure Webhook in Clerk
-
-  Since we let Clerk fully handle user authentication and management, we need Clerk to notify our application and store data in the database when there are changes in the user's lifecycle (create, update, delete). We achieve this requirement through the Webhook provided by Clerk.
-
-  We need to add an endpoint in Clerk's Webhooks to inform Clerk to send notifications to this endpoint when a user's information changes.
-
-  <Image alt={'Add Webhooks endpoint in Clerk'} src={'/blog/assets28616219/f50f47fb-5e8e-4930-bf4e-8cf6f5b8afb9.webp'} />
-
-  Fill in the endpoint with the URL of your Vercel project, such as `https://your-project.vercel.app/api/webhooks/clerk`. Then, subscribe to events by checking the three user events (`user.created`, `user.deleted`, `user.updated`), and click create.
-
-  <Callout type={'warning'}>
-    The `https://` in the URL is essential to maintain the integrity of the URL.
-  </Callout>
-
-  <Image alt={'Configure URL and user events when adding Clerk Webhooks'} src={'/blog/assets28616219/0249ea56-ab17-4aa9-a56c-9ebd556c2645.webp'} />
-
-  ### Add Webhook Secret to Vercel Environment Variables
-
-  After creation, you can find the secret of this Webhook in the bottom right corner:
-
-  <Image alt={'View Clerk Webhooks secret'} src={'/blog/assets28616219/fab4abb2-584b-49de-9340-813382951635.webp'} />
-
-  The environment variable corresponding to this secret is `CLERK_WEBHOOK_SECRET`:
-
-  ```shell
-  CLERK_WEBHOOK_SECRET=whsec_xxxxxxxxxxxxxxxxxxxxxx
-  ```
-
-  Add it to Vercel's environment variables:
-
-  <Image alt={'Add Clerk Webhooks secret in Vercel'} src={'/blog/assets28616219/5fdc9479-007f-46ab-9d6e-a9603e949116.webp'} />
 </Steps>
 
 By completing these steps, you have successfully configured the authentication service. Next, we will configure the S3 storage service.

package/docs/self-hosting/platform/vercel.zh-CN.mdx

@@ -114,53 +114,6 @@ tags:
   <Callout type={'info'}>
     如需 SSO 登录、魔法链接登录、邮箱验证等高级功能，请参阅 [身份验证服务](/zh/docs/self-hosting/advanced/auth)。
   </Callout>
-
-  ### 在 Vercel 中添加公、私钥环境变量
-
-  在 Vercel 的部署环境变量中，添加 `NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY` 和 `CLERK_SECRET_KEY` 环境变量。你可以在菜单中点击「API Keys」，然后复制对应的值填入 Vercel 的环境变量中。
-
-  <Image alt={'在 Clerk 中找到对应的公私钥环境变量'} src={'/blog/assets28616219/89883703-7a1a-4a11-b944-5d804544e57c.webp'} />
-
-  此步骤所需的环境变量如下：
-
-  ```shell
-  NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=pk_live_xxxxxxxxxxx
-  CLERK_SECRET_KEY=sk_live_xxxxxxxxxxxxxxxxxxxxxx
-  ```
-
-  添加上述变量到 Vercel 中：
-
-  <Image alt={'在 Vercel 中添加 Clerk 公私钥环境变量'} src={'/blog/assets28616219/2bfa13df-6e20-4768-97c0-4dad06c85a2f.webp'} />
-
-  ### 在 Clerk 中创建并配置 Webhook
-
-  由于我们让 Clerk 完全接管用户鉴权与管理，因此我们需要在 Clerk 用户生命周期变更时（创建、更新、删除）中通知我们的应用并存储落库。我们通过 Clerk 提供的 Webhook 来实现这一诉求。
-
-  我们需要在 Clerk 的 Webhooks 中添加一个端点（Endpoint），告诉 Clerk 当用户发生变更时，向这个端点发送通知。
-
-  <Image alt={'Clerk 添加 Webhooks 端点'} src={'/blog/assets28616219/f50f47fb-5e8e-4930-bf4e-8cf6f5b8afb9.webp'} />
-
-  在 endpoint 中填写你的 Vercel 项目的 URL，如 `https://your-project.vercel.app/api/webhooks/clerk`。然后在订阅事件（Subscribe to events）中，勾选 user 的三个事件（`user.created` 、`user.deleted`、`user.updated`），然后点击创建。
-
-  <Callout type={'warning'}>URL 的`https://`不可缺失，须保持 URL 的完整性</Callout>
-
-  <Image alt={'添加 Clerk Webhooks 时，配置 URL 和用户事件'} src={'/blog/assets28616219/0249ea56-ab17-4aa9-a56c-9ebd556c2645.webp'} />
-
-  ### 将 Webhook 秘钥添加到 Vercel 环境变量
-
-  创建完毕后，可以在右下角找到该 Webhook 的秘钥：
-
-  <Image alt={'查看 Clerk Webhooks 秘钥'} src={'/blog/assets28616219/fab4abb2-584b-49de-9340-813382951635.webp'} />
-
-  这个秘钥所对应的环境变量名为 `CLERK_WEBHOOK_SECRET`：
-
-  ```shell
-  CLERK_WEBHOOK_SECRET=whsec_xxxxxxxxxxxxxxxxxxxxxx
-  ```
-
-  将其添加到 Vercel 的环境变量中：
-
-  <Image alt={'在 Vercel 中 添加 Clerk Webhooks 秘钥'} src={'/blog/assets28616219/5fdc9479-007f-46ab-9d6e-a9603e949116.webp'} />
 </Steps>
 
 这样，你已经成功配置了身份验证服务。接下来我们将配置 S3 存储服务。

package/docs/self-hosting/start.mdx

@@ -16,24 +16,4 @@ tags:
 
 LobeHub supports various deployment platforms, including Vercel, Docker, and Docker Compose. You can choose a deployment platform that suits you to build your own Lobe Chat.
 
-## Quick Deployment
-
-For users who are new to LobeHub, we recommend using the client-side database mode for quick deployment. The advantage of this mode is that deployment can be quickly completed with just one command/button, making it easy for you to quickly get started and experience LobeHub.
-
-You can follow the guide below for quick deployment of LobeHub:
-
 <PlatformCards urlPrefix={'platform'} />
-
-<Callout>
-  In the client-side database mode, data is stored locally on the user's device, without
-  cross-device synchronization, and does not support advanced features such as file uploads and
-  knowledge base.
-</Callout>
-
-## Advanced Mode: Server-Side Database
-
-For users who are already familiar with LobeHub or need cross-device synchronization, you can deploy a version with a server-side database to access a more complete and powerful LobeHub.
-
-<Cards>
-  <Card href={'/docs/self-hosting/server-database'} title={'Server-Side Database Deployment Guide'} />
-</Cards>

package/docs/self-hosting/start.zh-CN.mdx

@@ -20,22 +20,4 @@ tags:
 
 LobeHub 支持多种部署平台，包括 Vercel、Docker、 Docker Compose 、阿里云计算巢 和腾讯轻量云 等，你可以选择适合自己的部署平台进行部署，构建属于自己的 Lobe Chat。
 
-## 快速部署
-
-对于第一次了解 LobeHub 的用户，我们推荐使用客户端数据库的模式快速部署，该模式的优势是一行指令 / 一个按钮即可快捷完成部署，便于你快速上手与体验 LobeHub。
-
-你可以通过以下指南快速部署 LobeHub：
-
 <PlatformCards urlPrefix={'platform'} />
-
-<Callout>
-  客户端数据库模式下数据均保留在用户本地，不会跨多端同步，也不支持文件上传、知识库等进阶功能。
-</Callout>
-
-## 进阶模式：服务端数据库
-
-针对已经了解 LobeHub 的用户，或需要多端同步的用户，可以自行部署带有服务端数据库的版本，进而获得更完整、功能更强大的 LobeHub。
-
-<Cards rows={1}>
-  <Card href={'/zh/docs/self-hosting/server-database'} title={'服务端数据库部署指南'} />
-</Cards>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lobehub/lobehub",
-  "version": "2.0.5",
+  "version": "2.0.7",
   "description": "LobeHub - an open-source,comprehensive AI Agent framework that supports speech synthesis, multimodal, and extensible Function Call plugin system. Supports one-click free deployment of your private ChatGPT/LLM web application.",
   "keywords": [
     "framework",

package/packages/database/src/repositories/aiInfra/index.test.ts

@@ -2,6 +2,7 @@ import type {
   AiProviderDetailItem,
   AiProviderListItem,
   AiProviderRuntimeConfig,
+  AiProviderRuntimeState,
   EnabledProvider,
 } from '@lobechat/types';
 import { AiProviderModelListItem, EnabledAiModel, ExtendParamsType } from 'model-bank';
@@ -1774,4 +1775,55 @@ describe('AiInfraRepos', () => {
       });
     });
   });
+
+  describe('AiInfraRepos.tryMatchingProviderFrom', () => {
+    const createRuntimeState = (models: EnabledAiModel[]): AiProviderRuntimeState => ({
+      enabledAiModels: models,
+      enabledAiProviders: [],
+      enabledChatAiProviders: [],
+      enabledImageAiProviders: [],
+      runtimeConfig: {},
+    });
+
+    it('prefers provider order when multiple providers have model', async () => {
+      const runtimeState = createRuntimeState([
+        { abilities: {}, enabled: true, id: 'm-1', type: 'chat', providerId: 'provider-b' },
+        { abilities: {}, enabled: true, id: 'm-1', type: 'chat', providerId: 'provider-a' },
+      ]);
+
+      const providerId = await AiInfraRepos.tryMatchingProviderFrom(runtimeState, {
+        modelId: 'm-1',
+        preferredProviders: ['provider-b', 'provider-a'],
+      });
+
+      expect(providerId).toBe('provider-b');
+    });
+
+    it('ignores disabled models when matching', async () => {
+      const runtimeState = createRuntimeState([
+        { abilities: {}, enabled: false, id: 'm-1', type: 'chat', providerId: 'provider-disabled' },
+        { abilities: {}, enabled: true, id: 'm-1', type: 'chat', providerId: 'provider-a' },
+      ]);
+
+      const providerId = await AiInfraRepos.tryMatchingProviderFrom(runtimeState, {
+        modelId: 'm-1',
+        preferredProviders: ['provider-disabled', 'provider-a'],
+      });
+
+      expect(providerId).toBe('provider-a');
+    });
+
+    it('falls back to provided fallback provider when no match', async () => {
+      const warnSpy = vi.spyOn(console, 'warn').mockImplementation(() => {});
+      const runtimeState = createRuntimeState([]);
+
+      const providerId = await AiInfraRepos.tryMatchingProviderFrom(runtimeState, {
+        modelId: 'm-1',
+        fallbackProvider: 'provider-fallback',
+      });
+
+      expect(providerId).toBe('provider-fallback');
+      warnSpy.mockRestore();
+    });
+  });
 });

package/packages/database/src/repositories/aiInfra/index.ts

@@ -24,6 +24,8 @@ import { LobeChatDatabase } from '../../type';
 
 type DecryptUserKeyVaults = (encryptKeyVaultsStr: string | null) => Promise<any>;
 
+const normalizeProvider = (provider: string) => provider.toLowerCase();
+
 /**
  * Provider-level search defaults (only used when built-in models don't provide settings.searchImpl and settings.searchProvider)
  * Note: Not stored in DB, only injected during read
@@ -282,6 +284,107 @@ export class AiInfraRepos {
     };
   };
 
+  /**
+   * Resolve the best provider for a given model.
+   *
+   * Matching pipeline:
+   * 1) Build a map of provider -> enabled model ids (disabled models are ignored).
+   * 2) Walk providers in priority order: preferred providers (if any) -> explicit fallback provider -> remaining providers that have enabled models.
+   * 3) For each provider, look for an exact modelId match or any preferred model alias.
+   * 4) If nothing matches, fall back to the configured provider (with a warning) or throw when no fallback exists.
+   *
+   * Handles:
+   * - Preferred provider ordering (case-insensitive).
+   * - Preferred model aliases.
+   * - Disabled models are skipped.
+   * - Missing matches: falls back when possible, otherwise surfaces an error.
+   *
+   * Edge cases to note:
+   * - If preferredProviders are set, non-preferred providers are skipped unless they are also the explicit fallback.
+   * - If fallbackProvider lacks enabled models, it is still returned (caller should ensure runtimeConfig has credentials).
+   */
+  static async tryMatchingProviderFrom(
+    runtimeState: AiProviderRuntimeState,
+    options: {
+      fallbackProvider?: string;
+      label?: string;
+      modelId: string;
+      preferredModels?: string[];
+      preferredProviders?: string[];
+    },
+  ): Promise<string> {
+    const { modelId, fallbackProvider, preferredModels, preferredProviders, label } = options;
+
+    // Build a map of provider -> enabled model ids for quick membership checks; skip disabled models entirely
+    const providerModels = runtimeState.enabledAiModels.reduce<Record<string, Set<string>>>(
+      (acc, model) => {
+        if (model.enabled === false) return acc;
+
+        const providerId = normalizeProvider(model.providerId);
+        acc[providerId] = acc[providerId] || new Set<string>();
+        acc[providerId].add(model.id);
+
+        return acc;
+      },
+      {},
+    );
+
+    // Normalize preferred providers so ordering is stable and comparisons are case-insensitive
+    const normalizedPreferredProviders = (preferredProviders || [])
+      .map(normalizeProvider)
+      .filter(Boolean);
+
+    // Provider search pipeline:
+    // 1) iterate preferred providers (if given)
+    // 2) fall back to the explicitly configured fallback provider
+    // 3) consider any provider that has enabled models
+    const providerOrder = Array.from(
+      new Set(
+        [
+          ...normalizedPreferredProviders,
+          fallbackProvider ? normalizeProvider(fallbackProvider) : undefined,
+          ...Object.keys(providerModels),
+        ].filter(Boolean) as string[],
+      ),
+    );
+
+    // Candidate models include the requested modelId plus any preferred model aliases
+    const modelTargets = new Set([modelId, ...(preferredModels || [])]);
+
+    for (const providerId of providerOrder) {
+      // If preferred providers are specified, skip non-preferred providers unless they are the explicit fallback
+      if (
+        normalizedPreferredProviders.length > 0 &&
+        providerId !== normalizeProvider(fallbackProvider || '') &&
+        !normalizedPreferredProviders.includes(providerId)
+      ) {
+        continue;
+      }
+
+      const models = providerModels[providerId];
+      if (!models) {
+        continue;
+      }
+
+      // Accept the first provider in order whose enabled models contain either the requested id or any preferred alias
+      const match = Array.from(modelTargets).find((target) => models.has(target));
+      if (match) {
+        return providerId;
+      }
+    }
+
+    if (fallbackProvider) {
+      console.warn(
+        `[ai-infra] no enabled provider found for ${label || 'model'} "${modelId}" (preferred ${preferredProviders}), falling back to server-configured provider "${fallbackProvider}".`,
+      );
+      return normalizeProvider(fallbackProvider);
+    }
+
+    throw new Error(
+      `Unable to resolve provider for ${label || 'model'} "${modelId}". Check preferred providers/models configuration.`,
+    );
+  }
+
   getAiProviderModelList = async (
     providerId: string,
     options?: {

package/packages/model-runtime/src/core/streams/protocol.ts

@@ -472,12 +472,14 @@ export const createTokenSpeedCalculator = (
     // - text/reasoning: standard text output events
     // - content_part/reasoning_part: multimodal output events used by Gemini 3+ models
     //   which emit structured parts instead of plain text events
+    // - tool_calls: function calling output events
     if (
       !outputStartAt &&
       (chunk.type === 'text' ||
         chunk.type === 'reasoning' ||
         chunk.type === 'content_part' ||
-        chunk.type === 'reasoning_part')
+        chunk.type === 'reasoning_part' ||
+        chunk.type === 'tool_calls')
     ) {
       outputStartAt = Date.now();
     }

package/src/app/(backend)/api/workflows/memory-user-memory/pipelines/persona/update-writing/route.ts

@@ -8,39 +8,39 @@ import {
 } from '@/server/services/memory/userMemory/persona/service';
 
 const workflowPayloadSchema = z.object({
-  userId: z.string().optional(),
   userIds: z.array(z.string()).optional(),
 });
 
 export const { POST } = serve(async (context) => {
-  const payload = workflowPayloadSchema.parse(context.requestPayload || {});
+  const payload = await context.run('memory:pipelines:persona:update-writing:parse-payload', () =>
+    workflowPayloadSchema.parse(context.requestPayload || {}),
+  );
   const db = await getServerDB();
 
-  const userIds = Array.from(
-    new Set([...(payload.userIds || []), ...(payload.userId ? [payload.userId] : [])]),
-  ).filter(Boolean);
-
+  const userIds = Array.from(new Set(payload.userIds || [])).filter(Boolean);
   if (userIds.length === 0) {
-    return { message: 'userId or userIds is required', processedUsers: 0 };
+    throw new Error('No user IDs provided for persona update.');
   }
 
   const service = new UserPersonaService(db);
-  const results = [];
 
-  for (const userId of userIds) {
-    const context = await buildUserPersonaJobInput(db, userId);
-    const result = await service.composeWriting({ ...context, userId });
-    results.push({
-      diffId: result.diff?.id,
-      documentId: result.document.id,
-      userId,
-      version: result.document.version,
-    });
-  }
+  await Promise.all(
+    userIds.map(async (userId) =>
+      context.run(`memory:pipelines:persona:update-writing:users:${userId}`, async () => {
+        const context = await buildUserPersonaJobInput(db, userId);
+        const result = await service.composeWriting({ ...context, userId });
+        return {
+          diffId: result.diff?.id,
+          documentId: result.document.id,
+          userId,
+          version: result.document.version,
+        };
+      }),
+    ),
+  );
 
   return {
     message: 'User persona processed via workflow.',
     processedUsers: userIds.length,
-    results,
   };
 });

package/src/app/[variants]/(main)/agent/features/Conversation/AgentWelcome/ToolAuthAlert.tsx

@@ -104,7 +104,7 @@ const KlavisToolAuthItem = memo<KlavisToolAuthItemProps>(({ tool, onAuthComplete
         try {
           await refreshKlavisServerTools(identifier);
         } catch (error) {
-          console.error('[Klavis] Failed to check auth status:', error);
+          console.debug('[Klavis] Polling check (expected during auth):', error);
         }
       }, POLL_INTERVAL_MS);
 
@@ -129,7 +129,8 @@ const KlavisToolAuthItem = memo<KlavisToolAuthItemProps>(({ tool, onAuthComplete
               windowCheckIntervalRef.current = null;
             }
             oauthWindowRef.current = null;
-            refreshKlavisServerTools(identifier);
+            // Start polling after window closes
+            startFallbackPolling(identifier);
           }
         } catch {
           if (windowCheckIntervalRef.current) {

package/src/app/[variants]/(main)/settings/skill/features/KlavisSkillItem.tsx

@@ -120,7 +120,7 @@ const KlavisSkillItem = memo<KlavisSkillItemProps>(({ serverType, server }) => {
         try {
           await refreshKlavisServerTools(serverName);
         } catch (error) {
-          console.error('[Klavis] Failed to check auth status:', error);
+          console.debug('[Klavis] Polling check (expected during auth):', error);
         }
       }, POLL_INTERVAL_MS);
 
@@ -145,8 +145,8 @@ const KlavisSkillItem = memo<KlavisSkillItemProps>(({ serverType, server }) => {
               windowCheckIntervalRef.current = null;
             }
             oauthWindowRef.current = null;
-            await refreshKlavisServerTools(serverName);
-            setIsWaitingAuth(false);
+            // Start polling after window closes
+            startFallbackPolling(serverName);
           }
         } catch {
           console.log('[Klavis] COOP blocked window.closed access, falling back to polling');