@lobehub/chat 1.111.1 → 1.111.2

package/.cursor/rules/code-review.mdc

@@ -26,28 +26,11 @@ Gather the modified code and context. Please strictly follow the process below:
 
 ### Code Style
 
-read [typescript.mdc](mdc:.cursor/rules/typescript.mdc) to learn the project's code style.
-
-- Ensure JSDoc comments accurately reflect the implementation; update them when needed.
-- Look for opportunities to simplify or modernize code with the latest JavaScript/TypeScript features.
-- Prefer `async`/`await` over callbacks or chained `.then` promises.
-- Use consistent, descriptive naming—avoid obscure abbreviations.
-- Replace magic numbers or strings with well-named constants.
-- Use semantically meaningful variable, function, and class names.
-- Ignore purely formatting issues and other autofixable lint problems.
+read [typescript.mdc](mdc:.cursor/rules/typescript.mdc) for the consolidated project code style and optimization rules.
 
 ### Code Optimization
 
-- Prefer `for…of` loops to index-based `for` loops when feasible.
-- Decide whether callbacks should be **debounced** or **throttled**.
-- Use components from `@lobehub/ui`, Ant Design, or the existing design system instead of raw HTML tags (e.g., `Button` vs. `button`).
-- reuse npm packages already installed (e.g., `lodash/omit`) rather than reinventing the wheel.
-- Design for dark mode and mobile responsiveness:
-  - Use the `antd-style` token system instead of hard-coded colors.
-  - Select the proper component variants.
-- Performance considerations:
-  - Where safe, convert sequential async flows to concurrent ones with `Promise.all`, `Promise.race`, etc.
-  - Query only the required columns from a database rather than selecting entire rows.
+The optimization checklist has been consolidated into [typescript.mdc](mdc:.cursor/rules/typescript.mdc): loops, debouncing/throttling, design system components, theming tokens, concurrency with `Promise.*`, minimal DB column selection, and package reuse.
 
 ### Obvious Bugs
 

package/.cursor/rules/cursor-ux.mdc

@@ -30,75 +30,3 @@ alwaysApply: true
   - Good: `git show commit_hash -- file.txt | cat`
   - Good: `git log --oneline | cat`
   - Reason: Some git commands use pagers by default, which may prevent output from being captured properly
-
-## Mermaid Diagram Generation: Strict Syntax Validation Checklist
-
-Before producing any Mermaid diagram, you **must** compare your final code line-by-line against every rule in the following checklist to ensure 100% compliance. **This is a hard requirement and takes precedence over other stylistic suggestions.** Please follow these action steps:
-
-1.  Plan the Mermaid diagram logic in your mind.
-2.  Write the Mermaid code.
-3.  **Carefully review your code line-by-line against the entire checklist below.**
-4.  Fix any aspect of your code that doesn't comply.
-5.  Use the `validateMermaid` tool to check your code for syntax errors. Only proceed if validation passes.
-6.  Output the final, compliant, and copy-ready Mermaid code block.
-7.  Immediately after the Mermaid code block, output:  
-    I have checked that the Mermaid syntax fully complies with the validation checklist.
-
----
-
-### Checklist Details
-
-#### Rule 1: Edge Labels – Must Be Plain Text Only
-
-> **Essence:** Anything inside `|...|` must contain pure, unformatted text. Absolutely NO Markdown, list markers, or parentheses/brackets allowed—these often cause rendering failures.
-
-- **✅ Do:** `A -->|Process plain text data| B`
-- **❌ Don't:** `A -->|1. Ordered list item| B` (No numbered lists)
-- **❌ Don't:** `CC --"1. fetch('/api/...')"--> API` (No square brackets)
-- **❌ Don't:** `A -->|- Unordered list item| B` (No hyphen lists)
-- **❌ Don't:** `A -->|Transform (important)| B` (No parentheses)
-- **❌ Don't:** `A -->|Transform [important]| B` (No square brackets)
-
-#### Rule 2: Node Definition – Handle Special Characters with Care
-
-> **Essence:** When node text or subgraph titles contain special characters like `()` or `[]`, wrap the text in quotes to avoid conflicts with Mermaid shape syntax.
-
-- **When your node text includes parentheses (e.g., 'React (JSX)'):**
-  - **✅ Do:** `I_REACT["<b>React component (JSX)</b>"]` (Quotes wrap all text)
-  - **❌ Don't:** `I_REACT(<b>React component (JSX)</b>)` (Wrong, Mermaid parses this as a shape)
-  - **❌ Don't:** `subgraph Plugin Features (Plugins)` (Wrong, subgraph titles with parentheses must also be wrapped in quotes)
-
-#### Rule 3: Double Quotes in Text – Must Be Escaped
-
-> **Essence:** Use `&quot;` for double quotes **inside node text**.
-
-- **✅ Do:** `A[This node contains &quot;quotes&quot;]`
-- **❌ Don't:** `A[This node contains "quotes"]`
-
-#### Rule 4: All Formatting Must Use HTML Tags (NOT Markdown!)
-
-> **Essence:** For newlines, bold, and other text formatting in nodes, use HTML tags only. Markdown is not supported.
-
-- **✅ Do (robust):** `A["<b>Bold</b> and <code>code</code><br>This is a new line"]`
-- **❌ Don't (not rendered):** `C["# This is a heading"]`
-- **❌ Don't (not rendered):** ``C["`const` means constant"]``
-- **⚠️ Warning (unreliable):** `B["Markdown **bold** might sometimes work but DON'T rely on it"]`
-
-#### Rule 5: No HTML Tags for Participants and Message Labels (Sequence Diagrams)
-
-> **Important Addition:**  
-> In Mermaid sequence diagrams, you MUST NOT use any HTML tags (such as `<b>`, `<code>`, etc.) in:
->
-> - `participant` display names (`as` part)
-> - Message labels (the text after `:` in diagram flows)
->
-> These tags are generally not rendered—they may appear as-is or cause compatibility issues.
-
-- **✅ Do:** `participant A as Client`
-- **❌ Don't:** `participant A as <b>Client</b>`
-- **✅ Do:** `A->>B: 1. Establish connection`
-- **❌ Don't:** `A->>B: 1. <code>Establish connection</code>`
-
----
-
-**Validate each Mermaid code block by running it through the `validateMermaid` tool before delivering your output!**

package/.cursor/rules/project-introduce.mdc

@@ -43,16 +43,16 @@ The project uses the following technologies:
 
 Note: All tools and libraries used are the latest versions. The application only needs to be compatible with the latest browsers;
 
-## Often used npm scripts
+## Often used npm scripts and commands
 
 ```bash
+# !: don't  any build script to check weather code can work after modify
 # type check
-bun type-check
+bun run type-check
 
 # install dependencies
 pnpm install
 
-# !: don't  any build script to check weather code can work after modify
+# run tests
+npx vitest run --config vitest.config.ts '[file-path-pattern]'
 ```
-
-check [testing guide](./testing-guide/testing-guide.mdc) to learn test scripts.

package/.cursor/rules/react-component.mdc

@@ -3,6 +3,7 @@ description:
 globs: *.tsx
 alwaysApply: false
 ---
+
 # react component 编写指南
 
 - 如果要写复杂样式的话用 antd-style ，简单的话可以用 style 属性直接写内联样式
@@ -20,18 +21,20 @@ import { useTheme } from 'antd-style';
 
 const MyComponent = () => {
   const theme = useTheme();
-  
+
   return (
-    <div style={{ 
-      color: theme.colorPrimary,
-      backgroundColor: theme.colorBgContainer,
-      padding: theme.padding,
-      borderRadius: theme.borderRadius
-    }}>
+    <div
+      style={{
+        color: theme.colorPrimary,
+        backgroundColor: theme.colorBgContainer,
+        padding: theme.padding,
+        borderRadius: theme.borderRadius,
+      }}
+    >
       使用主题 token 的组件
     </div>
   );
-}
+};
 ```
 
 #### 使用 antd-style 的 createStyles
@@ -53,13 +56,13 @@ const useStyles = createStyles(({ css, token }) => {
     content: css`
       font-size: ${token.fontSize}px;
       line-height: ${token.lineHeight};
-    `
+    `,
   };
 });
 
 const Card: FC<CardProps> = ({ title, content }) => {
   const { styles } = useStyles();
-  
+
   return (
     <Flexbox className={styles.container}>
       <div className={styles.title}>{title}</div>
@@ -74,80 +77,96 @@ const Card: FC<CardProps> = ({ title, content }) => {
 请注意使用下面的 token 而不是 css 字面值。可以访问 https://ant.design/docs/react/customize-theme-cn 了解所有 token
 
 - 动画类
-    - token.motionDurationMid
-    - token.motionEaseInOut
+  - token.motionDurationMid
+  - token.motionEaseInOut
 - 包围盒属性
-    - token.paddingSM
-    - token.marginLG
-
+  - token.paddingSM
+  - token.marginLG
 
 ## Lobe UI 包含的组件
 
 - 不知道 @lobehub/ui 的组件怎么用，有哪些属性，就自己搜下这个项目其它地方怎么用的，不要瞎猜，大部分组件都是在 antd 的基础上扩展了属性
 - 具体用法不懂可以联网搜索，例如 ActionIcon 就爬取 https://ui.lobehub.com/components/action-icon
+- 可以阅读 node_modules/@lobehub/ui/es/index.js 了解有哪些组件，每个组件的属性是什么
 
 - General
-  ActionIcon
-  ActionIconGroup
-  Block
-  Button
-  Icon
+  - ActionIcon
+  - ActionIconGroup
+  - Block
+  - Button
+  - DownloadButton
+  - Icon
 - Data Display
-  Avatar
-  Collapse
-  FileTypeIcon
-  FluentEmoji
-  GuideCard
-  Highlighter
-  Hotkey
-  Image
-  List
-  Markdown
-  MaterialFileTypeIcon
-  Mermaid
-  Segmented
-  Snippet
-  SortableList
-  Tag
-  Tooltip
-  Video
+  - Avatar
+  - AvatarGroup
+  - GroupAvatar
+  - Collapse
+  - FileTypeIcon
+  - FluentEmoji
+  - GuideCard
+  - Highlighter
+  - Hotkey
+  - Image
+  - List
+  - Markdown
+  - SearchResultCards
+  - MaterialFileTypeIcon
+  - Mermaid
+  - Typography
+  - Text
+  - Segmented
+  - Snippet
+  - SortableList
+  - Tag
+  - Tooltip
+  - Video
 - Data Entry
-  AutoComplete
-  CodeEditor
-  ColorSwatches
-  CopyButton
-  DatePicker
-  EditableText
-  EmojiPicker
-  Form
-  FormModal
-  HotkeyInput
-  ImageSelect
-  Input
-  SearchBar
-  Select
-  SliderWithInput
-  ThemeSwitch
+  - AutoComplete
+  - CodeEditor
+  - ColorSwatches
+  - CopyButton
+  - DatePicker
+  - EditableText
+  - EmojiPicker
+  - Form
+  - FormModal
+  - HotkeyInput
+  - ImageSelect
+  - Input
+  - SearchBar
+  - Select
+  - SliderWithInput
+  - ThemeSwitch
 - Feedback
-  Alert
-  Drawer
-  Modal
+  - Alert
+  - Drawer
+  - Modal
 - Layout
-  DraggablePanel
-  Footer
-  Grid
-  Header
-  Layout
-  MaskShadow
-  ScrollShadow
+  - DraggablePanel
+  - DraggablePanelBody
+  - DraggablePanelContainer
+  - DraggablePanelFooter
+  - DraggablePanelHeader
+  - Footer
+  - Grid
+  - Header
+  - Layout
+  - LayoutFooter
+  - LayoutHeader
+  - LayoutMain
+  - LayoutSidebar
+  - LayoutSidebarInner
+  - LayoutToc
+  - MaskShadow
+  - ScrollShadow
 - Navigation
-  Burger
-  Dropdown
-  Menu
-  SideNav
-  Tabs
-  Toc
+  - Burger
+  - Dropdown
+  - Menu
+  - SideNav
+  - Tabs
+  - Toc
 - Theme
-  ConfigProvider
-  FontLoader
-  ThemeProvider
+  - ConfigProvider
+  - FontLoader
+  - ThemeProvider

package/.cursor/rules/rules-attach.mdc

@@ -4,82 +4,49 @@ globs:
 alwaysApply: true
 ---
 
-# LobeChat Cursor Rules System Guide
+# 📋 Available Rules Index
 
-This document explains how the LobeChat project's Cursor rules system works and serves as an index for manually accessible rules.
-
-## 🎯 Core Principle
-
-**All rules are equal** - there are no priorities or "recommendations" between different rule sources. You should follow all applicable rules simultaneously.
-
-## 📚 Four Ways to Access Rules
-
-### 1. **Always Applied Rules** - `always_applied_workspace_rules`
-
-- **What**: Core project guidelines that are always active
-- **Content**: Project tech stack, basic coding standards, output formatting rules
-- **Access**: No tools needed - automatically provided in every conversation
-
-### 2. **Dynamic Context Rules** - `cursor_rules_context`
-
-- **What**: Rules automatically matched based on files referenced in the conversation
-- **Trigger**: Only when user **explicitly @ mentions files** or **opens files in Cursor**
-- **Content**: May include brief descriptions or full rule content, depending on relevance
-- **Access**: No tools needed - automatically updated when files are referenced
-
-### 3. **Agent Requestable Rules** - `agent_requestable_workspace_rules`
-
-- **What**: Detailed operational guides that can be requested on-demand
-- **Access**: Use `fetch_rules` tool with rule names
-- **Examples**: `debug`, `i18n/i18n`, `code-review`
-
-### 4. **Manual Rules Index** - This file + `read_file`
-
-- **What**: Additional rules not covered by the above mechanisms
-- **Why needed**: Cursor's rule system only supports "agent request" or "auto attach" modes
-- **Access**: Use `read_file` tool to read specific `.mdc` files
-
-## 🔧 When to Use `read_file` for Rules
-
-Use `read_file` to access rules from the index below when:
+The following rules are available via `read_file` from the `.cursor/rules/` directory:
 
-1. **Gap identification**: You determine a rule is needed for the current task
-2. **No auto-trigger**: The rule isn't provided in `cursor_rules_context` (because relevant files weren't @ mentioned)
-3. **Not agent-requestable**: The rule isn't available via `fetch_rules`
+## General
 
-## 📋 Available Rules Index
+- `project-introduce.mdc` – Project description and tech stack
+- `cursor-rules.mdc` – Cursor rules authoring and optimization guide
+- `code-review.mdc` – How to code review
 
-The following rules are available via `read_file` from the `.cursor/rules/` directory:
+## Backend
 
 - `backend-architecture.mdc` – Backend layer architecture and design guidelines
 - `define-database-model.mdc` – Database model definition guidelines
 - `drizzle-schema-style-guide.mdc` – Style guide for defining Drizzle ORM schemas
+
+## Frontend
+
 - `react-component.mdc` – React component style guide and conventions
-- `testing-guide.mdc` – Comprehensive testing guide for Vitest environment
+- `i18n.mdc` – Internationalization guide using react-i18next
 - `typescript.mdc` – TypeScript code style guide
+- `packages/react-layout-kit.mdc` – Usage guide for react-layout-kit
+
+## State Management
+
 - `zustand-action-patterns.mdc` – Recommended patterns for organizing Zustand actions
 - `zustand-slice-organization.mdc` – Best practices for structuring Zustand slices
 
-## ❌ Common Misunderstandings to Avoid
-
-1. **"Priority confusion"**: There's no hierarchy between rule sources - they're complementary, not competitive
-2. **"Dynamic expectations"**: `cursor_rules_context` only updates when you @ files - it won't automatically include rules for tasks you're thinking about
-3. **"Tool redundancy"**: Each access method serves a different purpose - they're not alternatives to choose from
+## Desktop (Electron)
 
-## 🛠️ Practical Workflow
+- `desktop-feature-implementation.mdc` – Implementing new Electron desktop features
+- `desktop-controller-tests.mdc` – Desktop controller unit testing guide
+- `desktop-local-tools-implement.mdc` – Workflow to add new desktop local tools
+- `desktop-menu-configuration.mdc` – Desktop menu configuration guide
+- `desktop-window-management.mdc` – Desktop window management guide
 
-```
-1. Start with always_applied_workspace_rules (automatic)
-2. Check cursor_rules_context for auto-matched rules (automatic)
-3. If you need specific guides: fetch_rules (manual)
-4. If you identify gaps: consult this index → read_file (manual)
-```
+## Debugging
 
-## Example Decision Flow
+- `debug.mdc` – General debugging guide
+- `debug-usage.mdc` – Using the debug package and namespace conventions
 
-**Scenario**: Working on a new Zustand store slice
+## Testing
 
-1. Follow always_applied_workspace_rules ✅
-2. If store files were @ mentioned → use cursor_rules_context rules ✅
-3. Need detailed Zustand guidance → `read_file('.cursor/rules/zustand-slice-organization.mdc')` ✅
-4. All rules apply simultaneously - no conflicts ✅
+- `testing-guide/testing-guide.mdc` – Comprehensive testing guide for Vitest
+- `testing-guide/electron-ipc-test.mdc` – Electron IPC interface testing strategy
+- `testing-guide/db-model-test.mdc` – Database Model testing guide

package/.cursor/rules/system-role.mdc

@@ -6,38 +6,26 @@ alwaysApply: true
 
 ## System Role
 
-You are an expert in full-stack Web development, proficient in JavaScript, TypeScript, CSS, React, Node.js, Next.js, Postgresql, all kinds of network protocols.
+You are an expert in full-stack Web development, proficient in JavaScript, TypeScript, CSS, React, Node.js, Next.js, Postgresql, Redis, S3, all kinds of network protocols.
 
-You are an expert in LLM and Ai art. In Ai image generation, you are proficient in Stable Diffusion and ComfyUI's architectural principles, workflows, model structures, parameter configurations, training methods, and inference optimization.
+You are an LLM expert, you are familiar with all kinds of LLM models, ai agents, ai workflow, prompt engineering and context engineering.
+
+You are an expert in Ai art. In Ai image generation, you are proficient in Stable Diffusion and ComfyUI's architectural principles, workflows, model structures, parameter configurations, training methods, and inference optimization.
 
 You are an expert in UI/UX design, proficient in web interaction patterns, responsive design, accessibility, and user behavior optimization. You excel at improving user retention and paid conversion rates through various interaction details.
 
 ## Problem Solving
 
-- Before formulating any response, you must first gather context by using tools like codebase_search, grep_search, file_search, web_search, fetch_rules, context7, and read_file to avoid making assumptions.
 - When modifying existing code, clearly describe the differences and reasons for the changes
 - Provide alternative solutions that may be better overall or superior in specific aspects
 - Provide optimization suggestions for deprecated API usage
 - Cite sources whenever possible at the end, not inline
 - When you provide multiple solutions, provide the recommended solution first, and note it as `Recommended`
-- Express uncertainty when there might not be a correct answer
-- Admit when you don't know something instead of guessing
+- Express uncertainty when there might not be a correct answer, instead of take action by guessing and assuming
 
 ## Code Implementation
 
-- Write correct, up-to-date, bug-free, fully functional, secure, maintainable and efficient code
-- First, think step-by-step: describe your plan in detailed pseudocode before implementation
-- Confirm the plan before writing code
 - Focus on maintainable over being performant
-- Leave NO TODOs, placeholders, or missing pieces
-- Be sure to reference file names
-- When you notice I have manually modified the code, that was definitely on purpose and do not revert them
-- If documentation links or required files are missing, ask for them before proceeding with the task rather than making assumptions
-- If you're unable to access or retrieve content from websites, please inform me immediately and request the specific information needed rather than making assumptions
-- You can use emojis, npm packages like `chalk`/`chalk-animation`/`terminal-link`/`gradient-string`/`log-symbols`/`boxen`/`consola`/`@clack/prompts` to create beautiful terminal output
-- Don't run `tsc --noEmit` to check ts syntax error, because our project is very large and the validate very slow
-
-## Some logging rules
-
-- Never log user private information like api key, etc
-- Don't use `import { log } from 'debug'` to log messages, because it will directly log the message to the console.
+- Be sure to reference file path
+- If doc links or required files are missing, ask for them before proceeding with the task rather than making assumptions
+- If you're unable to get valid result when using tools, please clearly state in the output

package/.cursor/rules/typescript.mdc

@@ -1,21 +1,62 @@
 ---
-description: 
+description: TypeScript code style and optimization guidelines
 globs: *.ts,*.tsx,*.mts
 alwaysApply: false
 ---
 
-TypeScript Code Style Guide:
+# TypeScript Code Style Guide
+
+## Types and Type Safety
 
 - Avoid explicit type annotations when TypeScript can infer types.
-- Avoid defining `any` type variables (e.g., `let a: number;` instead of `let a;`).
-- Use the most accurate type possible (e.g., use `Record<PropertyKey, unknown>` instead of `object`).
-- Prefer `interface` over `type` (e.g., define react component props).
-- Use `as const satisfies XyzInterface` instead of `as const` when suitable
-- import index.ts module(directory module) like `@/db/index` instead of `@/db`
-- Instead of calling Date.now() multiple times, assign it to a constant once and reuse it. This ensures consistency and improves readability
-- Always refactor repeated logic into a reusable function
-- Don't remove meaningful code comments, be sure to keep original comments when providing applied code
-- Update the code comments when needed after you modify the related code
-- Please respect my prettier preferences when you provide code
-- Prefer object destructuring when accessing and using properties
-- Prefer async version api than sync version, eg: use readFile from 'fs/promises' instead of 'fs'
+- Avoid implicitly `any` variables; explicitly type when necessary (e.g., `let a: number` instead of `let a`).
+- Use the most accurate type possible (e.g., prefer `Record<PropertyKey, unknown>` over `object`).
+- Prefer `interface` over `type` for object shapes (e.g., React component props). Keep `type` for unions, intersections, and utility types.
+- Prefer `as const satisfies XyzInterface` over plain `as const` when suitable.
+
+## Imports and Modules
+
+- When importing a directory module, prefer the explicit index path like `@/db/index` instead of `@/db`.
+
+## Asynchronous Patterns and Concurrency
+
+- Prefer `async`/`await` over callbacks or chained `.then` promises.
+- Prefer async APIs over sync ones (avoid `*Sync`).
+- Prefer promise-based variants (e.g., `import { readFile } from 'fs/promises'`) over callback-based APIs from `fs`.
+- Where safe, convert sequential async flows to concurrent ones with `Promise.all`, `Promise.race`, etc.
+
+## Code Structure and Readability
+
+- Refactor repeated logic into reusable functions.
+- Prefer object destructuring when accessing and using properties.
+- Use consistent, descriptive naming; avoid obscure abbreviations.
+- Use semantically meaningful variable, function, and class names.
+- Replace magic numbers or strings with well-named constants.
+- Keep meaningful code comments; do not remove them when applying edits. Update comments when behavior changes.
+- Ensure JSDoc comments accurately reflect the implementation.
+- Look for opportunities to simplify or modernize code with the latest JavaScript/TypeScript features where it improves clarity.
+- Defer formatting to tooling; ignore purely formatting-only issues and autofixable lint problems.
+- Respect project Prettier settings.
+
+## UI and Theming
+
+- Use components from `@lobehub/ui`, Ant Design, or existing design system components instead of raw HTML tags (e.g., `Button` vs. `button`).
+- Design for dark mode and mobile responsiveness:
+  - Use the `antd-style` token system instead of hard-coded colors.
+  - Select appropriate component variants.
+
+## Performance
+
+- Prefer `for…of` loops to index-based `for` loops when feasible.
+- Decide whether callbacks should be debounced or throttled based on UX and performance needs.
+- Reuse existing npm packages rather than reinventing the wheel (e.g., `lodash-es/omit`).
+- Query only the required columns from a database rather than selecting entire rows.
+
+## Time and Consistency
+
+- Instead of calling `Date.now()` multiple times, assign it to a constant once and reuse it to ensure consistency and improve readability.
+
+## Some logging rules
+
+- Never log user private information like api key, etc
+- Don't use `import { log } from 'debug'` to log messages, because it will directly log the message to the console.

package/CHANGELOG.md

@@ -2,6 +2,31 @@
 
 # Changelog
 
+### [Version 1.111.2](https://github.com/lobehub/lobe-chat/compare/v1.111.1...v1.111.2)
+
+<sup>Released on **2025-08-08**</sup>
+
+#### ♻ Code Refactoring
+
+- **pricing**: Introduce new pricing system.
+
+<br/>
+
+<details>
+<summary><kbd>Improvements and Fixes</kbd></summary>
+
+#### Code refactoring
+
+- **pricing**: Introduce new pricing system, closes [#8681](https://github.com/lobehub/lobe-chat/issues/8681) ([96b7508](https://github.com/lobehub/lobe-chat/commit/96b7508))
+
+</details>
+
+<div align="right">
+
+[![](https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square)](#readme-top)
+
+</div>
+
 ### [Version 1.111.1](https://github.com/lobehub/lobe-chat/compare/v1.111.0...v1.111.1)
 
 <sup>Released on **2025-08-08**</sup>

package/changelog/v1.json

@@ -1,4 +1,9 @@
 [
+  {
+    "children": {},
+    "date": "2025-08-08",
+    "version": "1.111.2"
+  },
   {
     "children": {
       "improvements": [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lobehub/chat",
-  "version": "1.111.1",
+  "version": "1.111.2",
   "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",