@lobehub/chat 0.147.4 → 0.147.5

package/CHANGELOG.md

@@ -2,6 +2,31 @@
 
 # Changelog
 
+### [Version 0.147.5](https://github.com/lobehub/lobe-chat/compare/v0.147.4...v0.147.5)
+
+<sup>Released on **2024-04-11**</sup>
+
+#### 🐛 Bug Fixes
+
+- **misc**: Fix only search topics in current session.
+
+<br/>
+
+<details>
+<summary><kbd>Improvements and Fixes</kbd></summary>
+
+#### What's fixed
+
+- **misc**: Fix only search topics in current session, closes [#1834](https://github.com/lobehub/lobe-chat/issues/1834) ([9fdcfa4](https://github.com/lobehub/lobe-chat/commit/9fdcfa4))
+
+</details>
+
+<div align="right">
+
+[![](https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square)](#readme-top)
+
+</div>
+
 ### [Version 0.147.4](https://github.com/lobehub/lobe-chat/compare/v0.147.3...v0.147.4)
 
 <sup>Released on **2024-04-11**</sup>

package/docs/self-hosting/advanced/authentication.mdx

@@ -24,11 +24,11 @@ LobeChat supports the configuration of external identity verification services f
 
 Currently supported identity verification services include:
 
-- [Auth0](/en/docs/self-hosting/advanced/sso-providers/auth0)
-- [Microsoft Entra ID](/en/docs/self-hosting/advanced/sso-providers/microsoft-entra-id)
-- [Authentik](/en/docs/self-hosting/advanced/sso-providers/authentik)
-- [Github](/en/docs/self-hosting/advanced/sso-providers/github)
-- [ZITADEL](/en/docs/self-hosting/advanced/sso-providers/zitadel)
+- [Auth0](/docs/self-hosting/advanced/sso-providers/auth0)
+- [Microsoft Entra ID](/docs/self-hosting/advanced/sso-providers/microsoft-entra-id)
+- [Authentik](/docs/self-hosting/advanced/sso-providers/authentik)
+- [Github](/docs/self-hosting/advanced/sso-providers/github)
+- [ZITADEL](/docs/self-hosting/advanced/sso-providers/zitadel)
 
 Click on the links to view the corresponding platform's configuration documentation.
 

package/docs/self-hosting/advanced/authentication.zh-CN.mdx

@@ -20,11 +20,11 @@ LobeChat 支持配置外部身份验证服务，供企业 / 组织内部使用
 
 目前支持的身份验证服务有：
 
-- [Auth0](/zh/docs/self-hosting/advanced/sso-providers/auth0)
-- [Microsoft Entra ID](/zh/docs/self-hosting/advanced/sso-providers/microsoft-entra-id)
-- [Authentik](/zh/docs/self-hosting/advanced/sso-providers/authentik)
-- [Github](/zh/docs/self-hosting/advanced/sso-providers/github)
-- [ZITADEL](/zh/docs/self-hosting/advanced/sso-providers/zitadel)
+- [Auth0](/docs/self-hosting/advanced/sso-providers/auth0)
+- [Microsoft Entra ID](/docs/self-hosting/advanced/sso-providers/microsoft-entra-id)
+- [Authentik](/docs/self-hosting/advanced/sso-providers/authentik)
+- [Github](/docs/self-hosting/advanced/sso-providers/github)
+- [ZITADEL](/docs/self-hosting/advanced/sso-providers/zitadel)
 
 点击链接可以查看对应平台的配置文档。
 

package/docs/self-hosting/advanced/sso-providers/auth0.mdx

@@ -86,7 +86,7 @@ When deploying LobeChat, you need to configure the following environment variabl
 | `NEXTAUTH_URL` | Optional | The URL is used to specify the callback address for the execution of OAuth authentication in Auth.js. It needs to be set only when the default address is incorrect. `https://example.com/api/auth` |
 
   <Callout type={'tip'}>
-    You can refer to the related variable details at [📘Environment Variables](/en/docs/self-hosting/environment-variable#auth0).
+    You can refer to the related variable details at [📘Environment Variables](/docs/self-hosting/environment-variable#auth0).
 
 </Callout>
 </Steps>

package/docs/self-hosting/advanced/sso-providers/auth0.zh-CN.mdx

@@ -81,7 +81,7 @@ http(s)://your-domain/api/auth/callback/auth0
 | `NEXTAUTH_URL` | 可选 | 该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，当默认生成的重定向地址发生不正确时才需要设置。`https://example.com/api/auth` |
 
   <Callout type={'tip'}>
-    前往 [📘 环境变量](/zh/docs/self-hosting/environment-variable#auth0) 可查阅相关变量详情。
+    前往 [📘 环境变量](/docs/self-hosting/environment-variable#auth0) 可查阅相关变量详情。
 
 </Callout>
 </Steps>

package/docs/self-hosting/advanced/sso-providers/authentik.mdx

@@ -64,7 +64,7 @@ When deploying LobeChat, you need to configure the following environment variabl
 | `NEXTAUTH_URL` | Optional | This URL is used to specify the callback address for Auth.js when performing OAuth authentication. It only needs to be set when the default generated redirect address is incorrect. `https://example.com/api/auth` |
 
   <Callout type={'tip'}>
-    Go to  Environment Variables: /en/docs/self-hosting/environment-variable#Authentik for details about the variables.
+    Go to  Environment Variables: /docs/self-hosting/environment-variable#Authentik for details about the variables.
 
 </Callout>
 </Steps>

package/docs/self-hosting/advanced/sso-providers/authentik.zh-CN.mdx

@@ -59,7 +59,7 @@ https://your-domain/api/auth/callback/authentik
 | `NEXTAUTH_URL` | 可选 | 该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，当默认生成的重定向地址发生不正确时才需要设置。`https://example.com/api/auth` |
 
   <Callout type={'tip'}>
-    前往 [📘 环境变量](/zh/docs/self-hosting/environment-variable#Authentik) 可查阅相关变量详情。
+    前往 [📘 环境变量](/docs/self-hosting/environment-variable#Authentik) 可查阅相关变量详情。
 
 </Callout>
 </Steps>

package/docs/self-hosting/advanced/sso-providers/github.mdx

@@ -91,7 +91,7 @@ When deploying LobeChat, you need to configure the following environment variabl
 | `NEXTAUTH_URL` | Optional | This URL is used to specify the callback address for Auth.js when performing OAuth authentication. Only set it if the default generated redirect address is incorrect. `https://example.com/api/auth` |
 
 <Callout type={'tip'}>
-  Go to [📘 Environment Variables](/en/docs/self-hosting/environment-variable#Github) for detailed
+  Go to [📘 Environment Variables](/docs/self-hosting/environment-variable#Github) for detailed
   information on these variables.
 </Callout>
 </Steps>

package/docs/self-hosting/advanced/sso-providers/github.zh-CN.mdx

@@ -87,7 +87,7 @@ tags:
 | `NEXTAUTH_URL` | 可选 | 该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，当默认生成的重定向地址发生不正确时才需要设置。`https://example.com/api/auth` |
 
   <Callout type={'tip'}>
-    前往 [📘 环境变量](/zh/docs/self-hosting/environment-variable#Github) 可查阅相关变量详情。
+    前往 [📘 环境变量](/docs/self-hosting/environment-variable#Github) 可查阅相关变量详情。
 
 </Callout>
 </Steps>

package/docs/self-hosting/advanced/sso-providers/microsoft-entra-id.mdx

@@ -82,7 +82,7 @@ When deploying LobeChat, you need to configure the following environment variabl
 
 <Callout type={'tip'}>
   You can refer to [📘 environment
-  variables](/en/docs/self-hosting/environment-variable#microsoft-entra-id) for details on related
+  variables](/docs/self-hosting/environment-variable#microsoft-entra-id) for details on related
   variables.
 </Callout>
 

package/docs/self-hosting/advanced/sso-providers/microsoft-entra-id.zh-CN.mdx

@@ -78,7 +78,7 @@ https://your-domain/api/auth/callback/azure-ad
 | `NEXTAUTH_URL` | 可选 | 该 URL 用于指定 Auth.js 在执行 OAuth 验证时的回调地址，当默认生成的重定向地址发生不正确时才需要设置。`https://example.com/api/auth` |
 
   <Callout type={'tip'}>
-    前往 [📘 环境变量](/zh/docs/self-hosting/environment-variable#microsoft-entra-id) 可查阅相关变量详情。
+    前往 [📘 环境变量](/docs/self-hosting/environment-variable#microsoft-entra-id) 可查阅相关变量详情。
 
 </Callout>
 </Steps>

package/docs/self-hosting/advanced/sso-providers/zitadel.mdx

@@ -99,7 +99,7 @@ When deploying LobeChat, you need to configure the following environment variabl
 | `NEXTAUTH_URL` | Optional | The URL is used to specify the callback address for the execution of OAuth authentication in Auth.js. It needs to be set only when the default address is incorrect. `https://example.com/api/auth` |
 
   <Callout type={'tip'}>
-    You can refer to the related variable details at [📘Environment Variables](/en/docs/self-hosting/environment-variables/auth#zitadel).
+    You can refer to the related variable details at [📘Environment Variables](/docs/self-hosting/environment-variables/auth#zitadel).
 
 </Callout>
 </Steps>

package/docs/self-hosting/advanced/sso-providers/zitadel.zh-CN.mdx

@@ -95,7 +95,7 @@ http(s)://your-domain/api/auth/callback/zitadel
 | `NEXTAUTH_URL` | 可选 | 该 URL 用于指定 Auth.js 中执行 OAuth 认证的回调地址。仅当默认地址不正确时才需要设置。`https://example.com/api/auth` |
 
   <Callout type={'tip'}>
-    您可以在 [📘 环境变量](/zh/docs/self-hosting/environment-variables/auth#zitadel) 中查看相关变量的详细信息。
+    您可以在 [📘 环境变量](/docs/self-hosting/environment-variables/auth#zitadel) 中查看相关变量的详细信息。
 
 </Callout>
 </Steps>

package/docs/self-hosting/examples/ollama.zh-CN.mdx

@@ -30,7 +30,7 @@ docker run -d -p 3210:3210 -e OLLAMA_PROXY_URL=http://host.docker.internal:11434
 
 接下来，你就可以使用 LobeChat 与本地 LLM 对话了。
 
-关于在 LobeChat 中使用 Ollama 的更多信息，请查阅 [Ollama 使用](/zh/docs/usage/providers/ollama)。
+关于在 LobeChat 中使用 Ollama 的更多信息，请查阅 [Ollama 使用](/docs/usage/providers/ollama)。
 
 ## 非本地访问 Ollama
 

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

@@ -15,7 +15,8 @@ tags:
 # Docker Compose Deployment Guide
 
 <div style={{display:"flex", gap: 4}}>
-  [![][docker-release-shield]][docker-release-link]
+
+[![][docker-release-shield]][docker-release-link]
 
 [![][docker-size-shield]][docker-size-link]
 
@@ -26,29 +27,29 @@ tags:
 We provide a [Docker image][docker-release-link] for deploying the LobeChat service on your private device.
 
 <Steps>
-	
+
 ### Install Docker Container Environment
 
 (Skip this step if already installed)
 
 <Tabs items={['Ubuntu', 'CentOS']}>
-   
+
 <Tab>
-	
-  ```fish
-  $ apt install docker.io
-  ```
-	
+
+```fish
+$ apt install docker.io
+```
+
 </Tab>
 
 <Tab>
-	
+
 ```fish
 $ yum install docker
 ```
-	
+
 </Tab>
-	
+
 </Tabs>
 
 ### Run Docker Compose Deployment Command

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

@@ -12,7 +12,8 @@ tags:
 # Docker Compose 部署指引
 
 <div style={{display:"flex", gap: 4}}>
-  [![][docker-release-shield]][docker-release-link]
+
+[![][docker-release-shield]][docker-release-link]
 
 [![][docker-size-shield]][docker-size-link]
 
@@ -23,7 +24,8 @@ tags:
 我们提供了 [Docker 镜像][docker-release-link]，供你在自己的私有设备上部署 LobeChat 服务。
 
 <Steps>
-  ### 安装 Docker 容器环境
+
+### 安装 Docker 容器环境
 
 （如果已安装，请跳过此步）
 
@@ -55,16 +57,16 @@ $ yum install docker
 version: '3.8'
 
 services:
-  lobe-chat:
-    image: lobehub/lobe-chat
-    container_name: lobe-chat
-    restart: always
-    ports:
-      - '3210:3210'
-    environment:
-      OPENAI_API_KEY: sk-xxxx
-      OPENAI_PROXY_URL: https://api-proxy.com/v1
-      ACCESS_CODE: lobe66
+lobe-chat:
+image: lobehub/lobe-chat
+container_name: lobe-chat
+restart: always
+ports:
+- '3210:3210'
+environment:
+OPENAI_API_KEY: sk-xxxx
+OPENAI_PROXY_URL: https://api-proxy.com/v1
+ACCESS_CODE: lobe66
 ```
 
 运行以下命令启动 Lobe Chat 服务：
@@ -81,48 +83,48 @@ $ docker-compose up -d
 #!/bin/bash
 # auto-update-lobe-chat.sh
 
-# 设置代理（可选）
+# Set proxy (optional)
 export https_proxy=http://127.0.0.1:7890 http_proxy=http://127.0.0.1:7890 all_proxy=socks5://127.0.0.1:7890
 
-# 拉取最新的镜像并将输出存储在变量中
+# Pull the latest image and store the output in a variable
 output=$(docker pull lobehub/lobe-chat:latest 2>&1)
 
-# 检查拉取命令是否成功执行
+# Check if the pull command was executed successfully
 if [ $? -ne 0 ]; then
-  exit 1
+exit 1
 fi
 
-# 检查输出中是否包含特定的字符串
+# Check if the output contains a specific string
 echo "$output" | grep -q "Image is up to date for lobehub/lobe-chat:latest"
 
-# 如果镜像已经是最新的，则不执行任何操作
+# If the image is already up to date, do nothing
 if [ $? -eq 0 ]; then
-  exit 0
+exit 0
 fi
 
 echo "Detected Lobe-Chat update"
 
-# 删除旧的容器
+# Remove the old container
 echo "Removed: $(docker rm -f Lobe-Chat)"
 
-# 也许需要先进入 `docker-compose.yml` 所在的目录
+# You may need to navigate to the directory where `docker-compose.yml` is located first
 # cd /path/to/docker-compose-folder
 
-# 运行新的容器
+# Run the new container
 echo "Started: $(docker-compose up)"
 
-# 打印更新的时间和版本
+# Print the update time and version
 echo "Update time: $(date)"
 echo "Version: $(docker inspect lobehub/lobe-chat:latest | grep 'org.opencontainers.image.version' | awk -F'"' '{print $4}')"
 
-# 清理不再使用的镜像
+# Clean up unused images
 docker images | grep 'lobehub/lobe-chat' | grep -v 'latest' | awk '{print $3}' | xargs -r docker rmi > /dev/null 2>&1
 echo "Removed old images."
 ```
 
-此脚本亦可以在 Crontab 中使用，但请确认你的 Crontab 可以找到正确的 Docker 命令。建议使用绝对路径。
+This script can also be used in Crontab, but ensure that your Crontab can find the correct Docker command. It is recommended to use absolute paths.
 
-配置 Crontab，每 5 分钟执行一次脚本：
+Configure Crontab to execute the script every 5 minutes:
 
 ```bash
 */5 * * * * /path/to/auto-update-lobe-chat.sh >> /path/to/auto-update-lobe-chat.log 2>&1

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

@@ -64,7 +64,7 @@ Command explanation:
 
 - Replace `sk-xxxx` in the above command with your OpenAI API Key.
 
-- For the complete list of environment variables supported by LobeChat, please refer to the [Environment Variables](/zh/docs/self-hosting/environment-ariable) section.
+- For the complete list of environment variables supported by LobeChat, please refer to the [Environment Variables](/docs/self-hosting/environment-ariable) section.
 
 <Callout type="tip">
   Since the official Docker image build takes about half an hour, if you see the "update available"

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

@@ -63,7 +63,7 @@ $ docker run -d -p 3210:3210 \
 - 使用你的 OpenAI API Key 替换上述命令中的 `sk-xxxx`
 
 <Callout type={'tip'}>
-  LobeChat 支持的完整环境变量列表请参考 [📘 环境变量](/zh/docs/self-hosting/environment-variables) 部分
+  LobeChat 支持的完整环境变量列表请参考 [📘 环境变量](/docs/self-hosting/environment-variables) 部分
 </Callout>
 
 <Callout>

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

@@ -92,7 +92,7 @@ Taking OpenAI as an example, the environment variables you need to add are as fo
 
 <Callout type={'tip'}>
   For a complete list of environment variables supported by LobeChat, please refer to the [📘
-  Environment Variables](/en/docs/self-hosting/environment-variables)
+  Environment Variables](/docs/self-hosting/environment-variables)
 </Callout>
 
 Afteradding the variables, finally click "Deploy lobe-chat" to enter the deployment phase

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

@@ -86,7 +86,7 @@ tags:
 | `OPENAI_PROXY_URL` | 可选 | 如果你手动配置了 OpenAI 接口代理，可以使用此配置项来覆盖默认的 OpenAI API 请求基础 URL | `https://aihubmix.com/v1` ，默认值：`https://api.openai.com/v1` |
 
 <Callout type={'tip'}>
-  LobeChat 支持的完整环境变量列表请参考 [📘 环境变量](/zh/docs/self-hosting/environment-variables) 部分
+  LobeChat 支持的完整环境变量列表请参考 [📘 环境变量](/docs/self-hosting/environment-variables) 部分
 </Callout>
 
 添加完成后，最后点击「Deploy lobe-chat」 进入部署阶段。

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

@@ -41,7 +41,7 @@ Vercel's assigned domain DNS may be polluted in some regions, so binding a custo
 If you have deployed your project using the one-click deployment steps mentioned above, you may find that you are always prompted with "updates available." This is because Vercel creates a new project for you by default instead of forking this project, which causes the inability to accurately detect updates.
 
 <Callout>
-  We recommend following the [Self-Hosting Upstream Sync](/zh/docs/self-hosting/upstream-sync) steps to
+  We recommend following the [Self-Hosting Upstream Sync](/docs/self-hosting/upstream-sync) steps to
   Redeploy.
 </Callout>
 

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

@@ -40,7 +40,7 @@ Vercel 分配的域名 DNS 在某些区域被污染了，绑定自定义域名
 如果你根据上述中的一键部署步骤部署了自己的项目，你可能会发现总是被提示 “有可用更新”。这是因为 Vercel 默认为你创建新项目而非 fork 本项目，这将导致无法准确检测更新。
 
 <Callout>
-  我们建议按照 [📘 LobeChat 自部署保持更新](/zh/docs/self-hosting/advanced/upstream-sync) 步骤重新部署。
+  我们建议按照 [📘 LobeChat 自部署保持更新](/docs/self-hosting/advanced/upstream-sync) 步骤重新部署。
 </Callout>
 
 [deploy-button-image]: https://vercel.com/button

package/docs/usage/agents/custom-agent.mdx

@@ -52,7 +52,7 @@ When you need to handle specific tasks, you need to consider creating a custom a
 If you want to understand Prompt writing tips and common model parameter settings, you can continue to view:
 
 <Cards>
-  <Card href={'/en/docs/usage/agents/prompt'} title={'Prompt User Guide'} />
+  <Card href={'/docs/usage/agents/prompt'} title={'Prompt User Guide'} />
 
-  <Card href={'/en/docs/usage/agents/model'} title={'Large Language Model User Guide'} />
+  <Card href={'/docs/usage/agents/model'} title={'Large Language Model User Guide'} />
 </Cards>

package/docs/usage/agents/custom-agent.zh-CN.mdx

@@ -47,7 +47,7 @@ tags:
 如果你希望理解 Prompt 编写技巧和常见的模型参数设置，可以继续查看：
 
 <Cards>
-  <Card href={'/zh/docs/usage/agents/prompt'} title={'Prompt 使用指南'} />
+  <Card href={'/docs/usage/agents/prompt'} title={'Prompt 使用指南'} />
 
-  <Card href={'/zh/docs/usage/agents/model'} title={'大语言模型使用指南'} />
+  <Card href={'/docs/usage/agents/model'} title={'大语言模型使用指南'} />
 </Cards>

package/docs/usage/features/multi-ai-providers.mdx

@@ -55,4 +55,4 @@ At the same time, we are also planning to support more model service providers,
   src={'https://github.com/lobehub/lobe-chat/assets/28616219/ca9a21bc-ea6c-4c90-bf4a-fa53b4fb2b5c'}
 />
 
-To meet the specific needs of users, LobeChat also supports the use of local models based on [Ollama](https://ollama.ai), allowing users to flexibly use their own or third-party models. For more details, see [Local Model Support](/en/docs/usage/features/local-llm).
+To meet the specific needs of users, LobeChat also supports the use of local models based on [Ollama](https://ollama.ai), allowing users to flexibly use their own or third-party models. For more details, see [Local Model Support](/docs/usage/features/local-llm).

package/docs/usage/features/multi-ai-providers.zh-CN.mdx

@@ -55,4 +55,4 @@ tags:
   src={'https://github.com/lobehub/lobe-chat/assets/28616219/ca9a21bc-ea6c-4c90-bf4a-fa53b4fb2b5c'}
 />
 
-为了满足特定用户的需求，LobeChat 还基于 [Ollama](https://ollama.ai) 支持了本地模型的使用，让用户能够更灵活地使用自己的或第三方的模型，详见 [本地模型支持](/zh/docs/usage/features/local-llm)。
+为了满足特定用户的需求，LobeChat 还基于 [Ollama](https://ollama.ai) 支持了本地模型的使用，让用户能够更灵活地使用自己的或第三方的模型，详见 [本地模型支持](/docs/usage/features/local-llm)。

package/docs/usage/features/plugin-system.mdx

@@ -52,7 +52,7 @@ Learn more about [plugin usage](/en-US/usage/plugins/basic) by checking it out.
 
 <Callout>
   If you are interested in plugin development, please refer to our [📘 Plugin Development
-  Guide](/en/docs/usage/plugins/development) in the Wiki.
+  Guide](/docs/usage/plugins/development) in the Wiki.
 </Callout>
 
 - [lobe-chat-plugins][lobe-chat-plugins]: This is the plugin index for LobeChat. It retrieves the list of plugins from the index.json of this repository and displays them to the users.

package/docs/usage/features/plugin-system.zh-CN.mdx

@@ -27,7 +27,7 @@ LobeChat 的插件生态系统是其核心功能的重要扩展，它极大地
 
 此外，这些插件不仅局限于新闻聚合，还可以扩展到其他实用的功能，如快速检索文档、生成图片、获取 Bilibili 、Steam 等各种平台数据，以及与其他各式各样的第三方服务交互。
 
-通过查看 [插件使用](/zh/docs/usage/plugins/basic) 了解更多。
+通过查看 [插件使用](/docs/usage/plugins/basic) 了解更多。
 
 <Callout type={'tip'}>
   为了帮助开发者更好地参与到这个生态中来，我们在提供了全面的开发资源。这包括详尽的组件开发文档、功能齐全的软件开发工具包（SDK），以及样板示例，这些都是为了简化开发过程，降低开发者的入门门槛。
@@ -40,7 +40,7 @@ LobeChat 的插件生态系统是其核心功能的重要扩展，它极大地
 ## 插件生态体系
 
 <Callout>
-  如果你对插件开发感兴趣，请在 Wiki 中查阅我们的 [📘 插件开发指南](/zh/docs/usage/plugins/development)。
+  如果你对插件开发感兴趣，请在 Wiki 中查阅我们的 [📘 插件开发指南](/docs/usage/plugins/development)。
 </Callout>
 
 - [lobe-chat-plugins][lobe-chat-plugins]：这是 LobeChat 的插件索引。它从该仓库的 index.json 中获取插件列表并显示给用户。

package/docs/usage/plugins/custom-plugin.mdx

@@ -34,4 +34,4 @@ If you want to try installing custom plugins on your own, you can use the follow
 
 ## Developing Custom Plugins
 
-If you wish to develop a LobeChat plugin on your own, feel free to refer to the [Plugin Development Guide](/en/docs/usage/plugins/development) to expand the possibilities of your AI assistant!
+If you wish to develop a LobeChat plugin on your own, feel free to refer to the [Plugin Development Guide](/docs/usage/plugins/development) to expand the possibilities of your AI assistant!

package/docs/usage/plugins/custom-plugin.zh-CN.mdx

@@ -32,4 +32,4 @@ tags:
 
 ## 开发自定义插件
 
-如果你希望自行开发一个 LobeChat 的插件，欢迎查阅 [插件开发指南](/zh/docs/usage/plugins/development) 以扩展你的 AI 智能助手的可能性边界！
+如果你希望自行开发一个 LobeChat 的插件，欢迎查阅 [插件开发指南](/docs/usage/plugins/development) 以扩展你的 AI 智能助手的可能性边界！

package/docs/usage/providers/ollama/gemma.mdx

@@ -27,7 +27,7 @@ This document will guide you on how to use Google Gemma in LobeChat:
 <Steps>
   ### Install Ollama locally
 
-First, you need to install Ollama. For the installation process, please refer to the [Ollama usage documentation](/en/docs/usage/providers/ollama).
+First, you need to install Ollama. For the installation process, please refer to the [Ollama usage documentation](/docs/usage/providers/ollama).
 
 ### Pull Google Gemma model to local using Ollama
 
@@ -59,7 +59,7 @@ In the session page, open the model panel and then select the Gemma model.
 
   <Callout type={'info'}>
     If you do not see the Ollama provider in the model selection panel, please refer to [Integrating
-    with Ollama](/en/docs/self-hosting/examples/ollama) to learn how to enable the Ollama provider in
+    with Ollama](/docs/self-hosting/examples/ollama) to learn how to enable the Ollama provider in
     LobeChat.
 
 </Callout>

package/docs/usage/providers/ollama/gemma.zh-CN.mdx

@@ -27,7 +27,7 @@ tags:
 <Steps>
   ### 本地安装 Ollama
 
-首先，你需要安装 Ollama，安装过程请查阅 [Ollama 使用文件](/zh/docs/usage/providers/ollama)。
+首先，你需要安装 Ollama，安装过程请查阅 [Ollama 使用文件](/docs/usage/providers/ollama)。
 
 ### 用 Ollama 拉取 Google Gemma 模型到本地
 
@@ -59,7 +59,7 @@ ollama pull gemma
 
   <Callout type={'info'}>
     如果你没有在模型选择面板中看到 Ollama 服务商，请查阅 [与 Ollama
-    集成](/zh/docs/self-hosting/examples/ollama) 了解如何在 LobeChat 中开启 Ollama 服务商。
+    集成](/docs/self-hosting/examples/ollama) 了解如何在 LobeChat 中开启 Ollama 服务商。
 
 </Callout>
 </Steps>

package/docs/usage/providers/ollama/qwen.mdx

@@ -26,7 +26,7 @@ Now, through the integration of LobeChat and [Ollama](https://ollama.com/), you
 <Steps>
   ## Local Installation of Ollama
 
-First, you need to install Ollama. For the installation process, please refer to the [Ollama Usage Document](/en/docs/usage/providers/ollama).
+First, you need to install Ollama. For the installation process, please refer to the [Ollama Usage Document](/docs/usage/providers/ollama).
 
 ## Pull the Qwen Model to Local with Ollama
 
@@ -61,7 +61,7 @@ In the LobeChat conversation page, open the model selection panel, and then sele
 />
 
   <Callout type={'info'}>
-    If you do not see the Ollama provider in the model selection panel, please refer to [Integration with Ollama](/en/docs/self-hosting/examples/ollama) to learn how to enable the Ollama provider in LobeChat.
+    If you do not see the Ollama provider in the model selection panel, please refer to [Integration with Ollama](/docs/self-hosting/examples/ollama) to learn how to enable the Ollama provider in LobeChat.
 
 </Callout>
 </Steps>

package/docs/usage/providers/ollama/qwen.zh-CN.mdx

@@ -28,7 +28,7 @@ tags:
 <Steps>
   ### 本地安装 Ollama
 
-首先，你需要安装 Ollama，安装过程请查阅 [Ollama 使用文件](/zh/docs/usage/providers/ollama)。
+首先，你需要安装 Ollama，安装过程请查阅 [Ollama 使用文件](/docs/usage/providers/ollama)。
 
 ### 用 Ollama 拉取 Qwen 模型到本地
 
@@ -58,7 +58,7 @@ ollama pull qwen:14b
 
   <Callout type={'info'}>
     如果你没有在模型选择面板中看到 Ollama 服务商，请查阅 [与 Ollama
-    集成](/zh/docs/self-hosting/examples/ollama) 了解如何在 LobeChat 中开启 Ollama 服务商。
+    集成](/docs/self-hosting/examples/ollama) 了解如何在 LobeChat 中开启 Ollama 服务商。
 
 </Callout>
 </Steps>

package/docs/usage/providers/ollama.mdx

@@ -76,7 +76,7 @@ Next, you can start conversing with the local LLM using LobeChat.
 />
 
   <Callout type={'info'}>
-    You can visit [Integrating with Ollama](/en/docs/self-hosting/examples/ollama) to learn how to deploy
+    You can visit [Integrating with Ollama](/docs/self-hosting/examples/ollama) to learn how to deploy
     LobeChat to meet the integration requirements with Ollama.
 
 </Callout>

package/docs/usage/providers/ollama.zh-CN.mdx

@@ -76,7 +76,7 @@ Ollama 支持多种模型，你可以在 [Ollama Library](https://ollama.com/lib
 />
 
   <Callout type={'info'}>
-    你可以前往 [与 Ollama 集成](/zh/docs/self-hosting/examples/ollama) 了解如何部署 LobeChat ，以满足与 Ollama 的集成需求。
+    你可以前往 [与 Ollama 集成](/docs/self-hosting/examples/ollama) 了解如何部署 LobeChat ，以满足与 Ollama 的集成需求。
 
 </Callout>
 </Steps>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lobehub/chat",
-  "version": "0.147.4",
+  "version": "0.147.5",
   "description": "Lobe Chat - an open-source, high-performance chatbot 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/src/app/chat/features/TopicListContent/TopicSearchBar/index.tsx

@@ -1,4 +1,5 @@
 import { SearchBar } from '@lobehub/ui';
+import { useUnmount } from 'ahooks';
 import { useResponsive } from 'antd-style';
 import { memo, useState } from 'react';
 import { useTranslation } from 'react-i18next';
@@ -10,11 +11,12 @@ const TopicSearchBar = memo<{ onClear?: () => void }>(({ onClear }) => {
 
   const [keywords, setKeywords] = useState('');
   const { mobile } = useResponsive();
+  const [activeSessionId, useSearchTopics] = useChatStore((s) => [s.activeId, s.useSearchTopics]);
 
-  const useSearchTopics = useChatStore((s) => s.useSearchTopics);
-
-  useSearchTopics(keywords);
-
+  useSearchTopics(keywords, activeSessionId);
+  useUnmount(() => {
+    useChatStore.setState({ isSearchingTopic: false });
+  });
   return (
     <SearchBar
       autoFocus

package/src/database/models/__tests__/topic.test.ts

@@ -11,11 +11,11 @@ import { CreateTopicParams, QueryTopicParams, TopicModel } from '../topic';
 
 describe('TopicModel', () => {
   let topicData: CreateTopicParams;
-
+  const currentSessionId = 'session1';
   beforeEach(() => {
     // Set up topic data with the correct structure
     topicData = {
-      sessionId: 'session1',
+      sessionId: currentSessionId,
       title: 'Test Topic',
       favorite: false,
     };
@@ -484,7 +484,7 @@ describe('TopicModel', () => {
   });
 
   describe('queryByKeyword', () => {
-    it('should query topics by keyword', async () => {
+    it('should query global topics by keyword', async () => {
       // Create a topic with a unique title
       const uniqueTitle = 'Unique Title';
       await TopicModel.create({ ...topicData, title: uniqueTitle });
@@ -496,5 +496,28 @@ describe('TopicModel', () => {
       expect(topics).toHaveLength(1);
       expect(topics[0].title).toBe(uniqueTitle);
     });
+    it('should query topics in current session by keyword', async () => {
+      // Create a topic with a unique title
+      const uniqueTitle = 'Unique Title';
+      await TopicModel.create({ ...topicData, title: uniqueTitle });
+
+      // Query topics by the unique title
+      const topics = await TopicModel.queryByKeyword(uniqueTitle, currentSessionId);
+
+      // Verify the correct topic is queried
+      expect(topics).toHaveLength(1);
+      expect(topics[0].title).toBe(uniqueTitle);
+    });
+    it('should not query any topic in other session by keyword', async () => {
+      // Create a topic with a unique title
+      const uniqueTitle = 'Unique Title';
+      await TopicModel.create({ ...topicData, title: uniqueTitle });
+
+      // Query topics by the unique title
+      const topics = await TopicModel.queryByKeyword(uniqueTitle, 'session-id-2');
+
+      // Verify the correct topic is queried
+      expect(topics).toHaveLength(0);
+    });
   });
 });

package/src/database/models/topic.ts

@@ -53,20 +53,25 @@ class _TopicModel extends BaseModel {
   /**
    * Query topics by keyword in title, message content, or translated content
    * @param keyword The keyword to search for
+   * @param sessionId The currently activated session id.
    */
-  async queryByKeyword(keyword: string): Promise<ChatTopic[]> {
+  async queryByKeyword(keyword: string, sessionId?: string): Promise<ChatTopic[]> {
     if (!keyword) return [];
 
     console.time('queryTopicsByKeyword');
     const keywordLowerCase = keyword.toLowerCase();
 
     // Find topics with matching title
-    const matchingTopicsPromise = this.table
+    const queryTable = sessionId ? this.table.where('sessionId').equals(sessionId) : this.table;
+    const matchingTopicsPromise = queryTable
       .filter((topic) => topic.title.toLowerCase().includes(keywordLowerCase))
       .toArray();
 
     // Find messages with matching content or translate.content
-    const matchingMessagesPromise = this.db.messages
+    const queryMessages = sessionId
+      ? this.db.messages.where('sessionId').equals(sessionId)
+      : this.db.messages;
+    const matchingMessagesPromise = queryMessages
       .filter((message) => {
         // check content
         if (message.content.toLowerCase().includes(keywordLowerCase)) return true;

package/src/services/__tests__/topic.test.ts

@@ -204,16 +204,16 @@ describe('TopicService', () => {
   });
 
   describe('searchTopics', () => {
-    it('should return topics that match the keyword', async () => {
+    it('should return all topics that match the keyword', async () => {
       // Setup
       const keyword = 'search';
       (TopicModel.queryByKeyword as Mock).mockResolvedValue(mockTopics);
 
       // Execute
-      const result = await topicService.searchTopics(keyword);
+      const result = await topicService.searchTopics(keyword, undefined);
 
       // Assert
-      expect(TopicModel.queryByKeyword).toHaveBeenCalledWith(keyword);
+      expect(TopicModel.queryByKeyword).toHaveBeenCalledWith(keyword, undefined);
       expect(result).toBe(mockTopics);
     });
   });

package/src/services/topic.ts

@@ -48,8 +48,8 @@ class TopicService {
     return TopicModel.queryAll();
   }
 
-  async searchTopics(keyword: string) {
-    return TopicModel.queryByKeyword(keyword);
+  async searchTopics(keyword: string, sessionId?: string) {
+    return TopicModel.queryByKeyword(keyword, sessionId);
   }
 
   async duplicateTopic(id: string, newTitle?: string) {

package/src/store/chat/slices/topic/action.ts

@@ -43,7 +43,7 @@ export interface ChatTopicAction {
   updateTopicLoading: (id?: string) => void;
   updateTopicTitle: (id: string, title: string) => Promise<void>;
   useFetchTopics: (sessionId: string) => SWRResponse<ChatTopic[]>;
-  useSearchTopics: (keywords?: string) => SWRResponse<ChatTopic[]>;
+  useSearchTopics: (keywords?: string, sessionId?: string) => SWRResponse<ChatTopic[]>;
 }
 
 export const chatTopic: StateCreator<
@@ -154,10 +154,11 @@ export const chatTopic: StateCreator<
         },
       },
     ),
-  useSearchTopics: (keywords) =>
+  useSearchTopics: (keywords, sessionId) =>
     useSWR<ChatTopic[]>(
-      [SWR_USE_SEARCH_TOPIC, keywords],
-      ([, keywords]: [string, string]) => topicService.searchTopics(keywords),
+      [SWR_USE_SEARCH_TOPIC, keywords, sessionId],
+      ([, keywords, sessionId]: [string, string, string]) =>
+        topicService.searchTopics(keywords, sessionId),
       {
         onSuccess: (data) => {
           set({ searchTopics: data }, false, n('useSearchTopics(success)', { keywords }));