feat: add loading back

fix: test mobile
fix: try to fixed
2026-06-14 11:40:07 +00:00 · 2025-11-17 17:20:03 +08:00 · 2025-11-17 16:33:16 +08:00 · 2025-11-17 16:11:20 +08:00 · 2025-11-17 15:38:29 +08:00 · 2025-11-17 15:16:37 +08:00
5964 changed files with 762001 additions and 149074 deletions
@@ -0,0 +1,38 @@
+---
+allowed-tools: Bash(gh issue view:*), Bash(gh search:*), Bash(gh issue list:*), Bash(gh api:*), Bash(gh issue comment:*)
+description: Find duplicate GitHub issues
+---
+
+Find up to 3 likely duplicate issues for a given GitHub issue.
+
+To do this, follow these steps precisely:
+
+1. Use an agent to check if the Github issue (a) is closed, (b) does not need to be deduped (eg. because it is broad product feedback without a specific solution, or positive feedback), or (c) already has a duplicates comment that you made earlier. If so, do not proceed.
+2. Use an agent to view a Github issue, and ask the agent to return a summary of the issue
+3. Then, launch 5 parallel agents to search Github for duplicates of this issue, using diverse keywords and search approaches, using the summary from #1
+4. Next, feed the results from #1 and #2 into another agent, so that it can filter out false positives, that are likely not actually duplicates of the original issue. If there are no duplicates remaining, do not proceed.
+5. Finally, comment back on the issue with a list of up to three duplicate issues (or zero, if there are no likely duplicates)
+
+Notes (be sure to tell this to your agents, too):
+
+- Use `gh` to interact with Github, rather than web fetch
+- Do not use other tools, beyond `gh` (eg. don't use other MCP servers, file edit, etc.)
+- Make a todo list first
+- For your comment, follow the following format precisely (assuming for this example that you found 3 suspected duplicates):
+
+---
+
+Found 3 possible duplicate issues:
+
+1. <link to issue>
+2. <link to issue>
+3. <link to issue>
+
+This issue will be automatically closed as a duplicate in 3 days.
+
+- If your issue is a duplicate, please close it and 👍 the existing issue instead
+- To prevent auto-closure, add a comment or 👎 this comment
+
+> 🤖 Generated with Claude Code
+
+---
@@ -0,0 +1,228 @@
+# Auto Testing Coverage Assistant
+
+You are an auto testing assistant. Your task is to add unit tests to improve code coverage in the codebase.
+
+## Target Directories
+
+Prioritize modules with business logic:
+
+- apps/desktop/src/core/
+- apps/desktop/src/modules/
+- apps/desktop/src/controllers/
+- apps/desktop/src/services/
+- packages/\*/src/
+- src/services/
+- src/store/
+- src/server/routers/
+- src/server/services/
+- src/server/modules/
+- src/libs/
+- src/utils/
+
+**Do NOT test**:
+
+- UI components (\*.tsx React components)
+- Test files themselves
+- Generated files
+- Configuration files
+- Type definition files
+
+## Workflow
+
+### 1. Select a Module to Process
+
+**Selection Strategy**:
+
+- Randomly pick ONE module from the target directories
+- Prioritize modules that:
+  - Have significant business logic
+  - Have no or minimal test coverage
+  - Already have example test files (easier to follow patterns)
+  - Are large modules with complex logic
+
+**Module granularity examples**:
+
+- A single package: `packages/database/src/models`
+- A desktop module: `apps/desktop/src/modules/auth`
+- A service directory: `src/services/user`
+- A store slice: `src/store/chat`
+
+**Special handling**:
+
+- If a directory has NO tests but needs coverage → create ONE example test file
+- If a directory already has some tests → expand coverage to untested functions/classes
+- Focus on directories with existing test examples (follow their patterns)
+
+### 2. Analyze Module Structure
+
+Before writing tests:
+
+- Identify core business logic functions/classes
+- Check for existing test files and patterns
+- Determine testing approach based on module type:
+  - Database models → test CRUD operations
+  - Services → test business logic flows
+  - Controllers → test request handling
+  - Store slices → test state mutations and actions
+  - Utils → test utility functions with edge cases
+
+### 3. Write Unit Tests
+
+**Testing Guidelines**:
+
+- Follow existing test patterns in the codebase
+- Use Vitest as the testing framework
+- Focus on business logic, not UI rendering
+- Write comprehensive tests covering:
+  - Happy path scenarios
+  - Edge cases
+  - Error handling
+  - Input validation
+- Use descriptive test names: `describe()` and `it()` blocks
+- Mock external dependencies appropriately
+- Keep tests isolated and independent
+
+**Test File Naming**:
+
+- Place test files next to source files: `filename.test.ts`
+- Or in `__tests__` directory: `__tests__/filename.test.ts`
+
+**Example Test Structure**:
+
+```typescript
+import { describe, it, expect, vi, beforeEach } from 'vitest';
+import { functionToTest } from './module';
+
+describe('ModuleName', () => {
+  describe('functionName', () => {
+    it('should handle normal case correctly', () => {
+      // Arrange
+      const input = 'test';
+
+      // Act
+      const result = functionToTest(input);
+
+      // Assert
+      expect(result).toBe('expected');
+    });
+
+    it('should handle edge case', () => {
+      // Test edge case
+    });
+
+    it('should throw error on invalid input', () => {
+      // Test error handling
+    });
+  });
+});
+```
+
+### 4. Run Tests and Fix Issues
+
+**CRITICAL**: Tests MUST pass before submitting!
+
+- Run tests using the appropriate command:
+  - Web: `bunx vitest run --silent='passed-only' '[file-path-pattern]'`
+  - Packages: `cd packages/[name] && bunx vitest run --silent='passed-only' '[file-path-pattern]'`
+- Wrap file paths in single quotes
+- Fix any failing tests
+- Ensure all tests pass before proceeding
+
+**If tests fail**:
+
+- Debug and fix the test logic
+- Check mocks and dependencies
+- Verify test isolation
+- If unable to fix after 2 attempts, skip this module and document the issue
+
+### 5. Create Pull Request
+
+- Create a new branch: `automatic/add-tests-[module-name]-[date]`
+- Commit changes with message format:
+  ```
+  ✅ test: add unit tests for [module-name]
+  ```
+- Push the branch
+- Create a PR with:
+
+  - Title: `✅ test: add unit tests for [module-name]`
+  - Body following this template:
+
+  ```markdown
+  ## Summary
+
+  - Added unit tests for `[module-name]`
+  - Total test files added/modified: [number]
+  - Test cases added: [number]
+  - Coverage focus: [brief description of what was tested]
+
+  ## Changes
+
+  - [ ] All tests pass successfully
+  - [ ] Business logic coverage improved
+  - [ ] Edge cases and error handling covered
+  - [ ] Tests follow existing patterns
+
+  ## Module Processed
+
+  `[module-path]`
+
+  ## Test Coverage
+
+  - Functions tested: [list key functions]
+  - Coverage type: [unit/integration]
+  - Test approach: [brief description]
+
+  ---
+  🤖 Generated with [Claude Code](https://claude.com/claude-code)
+  ```
+
+## Important Rules
+
+- **DO** focus on business logic testing only
+- **DO** ensure all tests pass before creating PR
+- **DO** follow existing test patterns in the codebase
+- **DO** write descriptive test names and comments
+- **DO** test edge cases and error scenarios
+- **DO NOT** test UI components (\*.tsx)
+- **DO NOT** create tests that will fail
+- **DO NOT** modify production code unless absolutely necessary for testability
+- **DO NOT** exceed 45 minutes of workflow time
+- **DO NOT** create tests for generated or configuration files
+
+## Module Selection Examples
+
+**Good choices**:
+
+- `packages/database/src/models/` - Core CRUD operations
+- `src/services/user/client.ts` - User service business logic
+- `apps/desktop/src/modules/auth/` - Authentication logic
+- `src/store/chat/slices/message/` - Message state management
+- `src/server/services/` - Backend service logic
+
+**Bad choices**:
+
+- `src/components/` - UI components (avoid)
+- `src/app/` - Next.js pages (avoid)
+- `src/styles/` - Styling files (avoid)
+- Configuration files (avoid)
+
+## Testing Best Practices
+
+1. **Arrange-Act-Assert** pattern
+2. **Mock external dependencies** (APIs, databases, file system)
+3. **Test one thing per test case**
+4. **Use descriptive test names**
+5. **Keep tests fast and isolated**
+6. **Follow DRY principle with beforeEach/afterEach**
+7. **Test behavior, not implementation**
+
+## Example Modules with Test Patterns
+
+Look for existing test files to understand patterns:
+
+- `packages/database/src/models/**/*.test.ts` - Database testing patterns
+- `apps/desktop/src/controllers/**/*.test.ts` - Controller testing patterns
+- `src/services/**/*.test.ts` - Service testing patterns
+
+Follow their structure and conventions when adding new tests.
@@ -0,0 +1,253 @@
+# Issue Triage Guide
+
+This guide is used for batch triaging GitHub issues - analyzing issues and applying appropriate labels.
+
+## Workflow
+
+For EACH issue, follow these steps:
+
+### Step 1: Get Available Labels (run once per batch)
+
+```bash
+gh label list --json name,description --limit 300
+```
+
+### Step 2: Get Issue Details
+
+For each issue number, run:
+
+```bash
+gh issue view [ISSUE_NUMBER] --json number,title,body,labels,comments
+```
+
+### Step 3: Analyze and Select Labels
+
+Extract information from the issue template and content:
+
+#### Template Fields Mapping
+
+- 📦 Platform field → `platform:web/desktop/mobile`
+- 💻 Operating System → `os:windows/macos/linux/ios`
+- 🌐 Browser → `device:pc/mobile`
+- 📦 Deployment mode → `deployment:server/client/pglite`
+- Platform (hosting) → `hosting:cloud/self-host/vercel/zeabur/railway`
+
+#### Provider Detection
+
+**IMPORTANT**: Always check issue title and body for provider mentions!
+
+**Official Providers** (check for these keywords in title/body):
+
+- `openai`, `gpt` → `provider:openai`
+- `gemini` → `provider:gemini`
+- `claude`, `anthropic` → `provider:claude`
+- `deepseek` → `provider:deepseek`
+- `google` → `provider:google`
+- `ollama` → `provider:ollama`
+- `azure` → `provider:azure`
+- `bedrock` → `provider:bedrock`
+- `vertex` → `provider:vertex`
+- `groq`, `grok` → `provider:groq`
+- `mistral` → `provider:mistral`
+- `moonshot` → `provider:moonshot`
+- `zhipu` → `provider:zhipu`
+- `minimax` → `provider:minimax`
+- `doubao` → `provider:doubao`
+
+**Third-party Aggregation Providers**:
+
+- `aihubmix`, `AIHubMix`, `AIHUBMIX` → `provider:aihubmix`
+- Check environment variables like `AIHUBMIX_*` in issue body
+
+**Multiple Providers**: If issue mentions multiple providers, add ALL applicable provider labels.
+
+### Label Categories
+
+#### a) Issue Type (select ONE if applicable)
+
+- `💄 Design` - UI/UX design issues
+- `📝 Documentation` - Documentation improvements
+- `⚡️ Performance` - Performance optimization
+
+#### b) Priority (select ONE if applicable)
+
+- `priority:high` - Critical issues, data loss, security, maintainer mentions "urgent"/"serious"/"critical"
+- `priority:medium` - Important issues affecting multiple users, significant functionality impact
+- `priority:low` - Nice to have, minor issues, edge cases
+
+**Priority Guidelines**:
+
+- Set `priority:high` for: data loss, authentication failures, deployment blockers, critical bugs
+- Set `priority:medium` for: feature bugs affecting multiple users, workflow issues
+- Set `priority:low` for: cosmetic issues, feature requests, configuration questions
+
+#### c) Platform (select ALL applicable)
+
+- `platform:web`
+- `platform:desktop`
+- `platform:mobile`
+
+#### d) Device (for platform:web, select ONE)
+
+- `device:pc`
+- `device:mobile`
+
+#### e) Operating System (select ALL applicable)
+
+- `os:windows`
+- `os:macos`
+- `os:linux`
+- `os:ios`
+- `os:android`
+
+#### f) Hosting Platform (select ONE)
+
+- `hosting:cloud` - Official LobeHub Cloud
+- `hosting:self-host` - Self-hosted deployment
+- `hosting:vercel` - Vercel deployment
+- `hosting:zeabur` - Zeabur deployment
+- `hosting:railway` - Railway deployment
+
+#### g) Deployment Mode (select ONE if mentioned)
+
+- `deployment:server` - Server-side database mode
+- `deployment:client` - Client-side database mode
+- `deployment:pglite` - PGLite mode
+
+**Additional deployment tags**:
+
+- `docker` - If using Docker deployment
+- `electron` - If desktop/Electron specific
+
+#### h) Model Provider (select ALL applicable)
+
+See "Provider Detection" section above for complete list.
+
+**IMPORTANT**: Always scan issue title and body for provider keywords!
+
+#### i) Feature/Component (select ALL applicable)
+
+Core Features:
+
+- `feature:settings` - Settings and configuration
+- `feature:agent` - Agent/Assistant functionality
+- `feature:topic` - Topic/Conversation management
+- `feature:marketplace` - Agent marketplace
+
+File & Knowledge:
+
+- `feature:files` - File upload/management
+- `feature:knowledge-base` - Knowledge base and RAG
+- `feature:export` - Export functionality
+
+Model Capabilities:
+
+- `feature:streaming` - Streaming responses
+- `feature:tool` - Tool calling
+- `feature:vision` - Vision/multimodal capabilities
+- `feature:image` - AI image generation
+- `feature:dalle` - DALL-E specific
+- `feature:tts` - Text-to-speech
+
+Technical:
+
+- `feature:api` - Backend API
+- `feature:auth` - Authentication/authorization
+- `feature:sync` - Cloud sync functionality
+- `feature:search` - Search functionality
+- `feature:mcp` - MCP integration
+- `feature:editor` - Lobe Editor
+- `feature:markdown` - Markdown rendering
+- `feature:thread` - Thread/Subtopic functionality
+
+Collaboration:
+
+- `feature:group-chat` - Group chat functionality
+- `feature:memory` - Memory feature
+- `feature:team-workspace` - Team workspace
+
+#### j) Workflow/Status
+
+- `Duplicate` - Only if duplicate of an OPEN issue (mention issue number)
+- `needs-reproduction` - Cannot reproduce, needs more information
+- `good-first-issue` - Good for first-time contributors
+- `🤔 Need Reproduce` - Needs reproduction steps
+
+### Step 4: Apply Labels
+
+Add labels (comma-separated, no spaces after commas):
+
+```bash
+gh issue edit [ISSUE_NUMBER] --add-label "label1,label2,label3"
+```
+
+Remove "unconfirm" label if adding other labels:
+
+```bash
+gh issue edit [ISSUE_NUMBER] --remove-label "unconfirm"
+```
+
+**Important**: Combine both commands when possible for efficiency.
+
+### Step 5: Log Summary
+
+For each issue, provide reasoning (2-4 sentences):
+
+- Labels applied and why
+- Key factors from issue template/comments
+- Provider detection reasoning (if applicable)
+
+## Important Rules
+
+1. **Read Carefully**: Read issue template fields AND issue body/title for complete context
+2. **Provider Detection**: ALWAYS check title and body for provider keywords (including aihubmix, etc.)
+3. **Multiple Categories**: Use ALL applicable labels from different categories
+4. **Label Prefixes**: Always use proper prefixes (`feature:`, `provider:`, `os:`, `platform:`, etc.)
+5. **Maintainer Comments**: Check maintainer comments for priority/status hints
+6. **No Comments**: Only apply labels, DO NOT post comments to issues
+7. **Batch Efficiency**: Process issues in parallel when possible
+
+## Common Patterns
+
+### Provider in Environment Variables
+
+If issue body contains `AIHUBMIX_*`, add `provider:aihubmix`
+
+### Multiple Provider Issues
+
+If comparing providers (e.g., "works with OpenAI but not Gemini"), add both provider labels
+
+### Desktop Issues
+
+Desktop issues often need: `platform:desktop`, `electron`, specific `os:*`, and `deployment:client` or `deployment:server`
+
+### Knowledge Base Issues
+
+Usually need: `feature:knowledge-base`, often with `feature:files`, may need `provider:*` for embedding models
+
+### Tool Calling Issues
+
+Usually need: `feature:tool`, specific `provider:*`, may need `feature:mcp` if MCP-related
+
+### Streaming Issues
+
+Usually need: `feature:streaming`, specific `provider:*`, check for timeout/performance issues
+
+## Example Triage
+
+**Issue #8850**: "aihubmix 的优惠 app 没有生效"
+
+**Analysis**:
+
+- Title contains "aihubmix" → `provider:aihubmix`
+- Template shows: Windows, Chrome, Docker, Client mode
+- About API discount codes not working
+
+**Labels Applied**:
+
+```bash
+gh issue edit 8850 --add-label "provider:aihubmix,platform:web,os:windows,deployment:client,hosting:self-host,docker"
+gh issue edit 8850 --remove-label "unconfirm"
+```
+
+**Reasoning**: AIHubMix provider discount feature not working. Client mode deployment on Windows with Docker. Provider detection from title keyword "aihubmix".
@@ -0,0 +1,135 @@
+# Team Assignment Guide
+
+## Quick Reference by Name
+
+- **@arvinxx**: Last resort only, mention for priority:high issues, tool calling , mcp
+- **@canisminor1990**: Design, UI components, editor
+- **@tjx666**: Image/video generation, vision, cloud, documentation, TTS
+- **@ONLY-yours**: Performance, streaming, settings, general bugs, web platform, marketplace
+- **@RiverTwilight**: Knowledge base, files (KB-related), group chat
+- **@nekomeowww**: Memory, backend, deployment, DevOps
+- **@sudongyuer**: Mobile app (React Native)
+- **@sxjeru**: Model providers and configuration
+- **@cy948**: Auth Modules
+- **@rdmclin2**: Team workspace
+
+Quick reference for assigning issues based on labels.
+
+## Label to Team Member Mapping
+
+### Provider Labels (provider:\*)
+
+| Label            | Owner   | Notes                                        |
+| ---------------- | ------- | -------------------------------------------- |
+| All `provider:*` | @sxjeru | Model configuration and provider integration |
+
+### Platform Labels (platform:\*)
+
+| Label              | Owner       | Notes                                  |
+| ------------------ | ----------- | -------------------------------------- |
+| `platform:mobile`  | @sudongyuer | React Native mobile app                |
+| `platform:desktop` | @ONLY-yours | Electron desktop client (general)      |
+| `platform:web`     | @ONLY-yours | Web platform (unless specific feature) |
+
+### Feature Labels (feature:\*)
+
+| Label                    | Owner           | Notes                                                                   |
+| ------------------------ | --------------- | ----------------------------------------------------------------------- |
+| `feature:image`          | @tjx666         | AI image generation                                                     |
+| `feature:dalle`          | @tjx666         | DALL-E related                                                          |
+| `feature:vision`         | @tjx666         | Vision/multimodal generation                                            |
+| `feature:knowledge-base` | @RiverTwilight  | Knowledge base and RAG                                                  |
+| `feature:files`          | @RiverTwilight  | File upload/management (when KB-related)<br>@ONLY-yours (general files) |
+| `feature:editor`         | @canisminor1990 | Lobe Editor                                                             |
+| `feature:auth`           | @cy948          | Authentication/authorization                                            |
+| `feature:api`            | @nekomeowww     | Backend API                                                             |
+| `feature:streaming`      | @arvinxx        | Streaming response                                                      |
+| `feature:settings`       | @ONLY-yours     | Settings and configuration                                              |
+| `feature:agent`          | @ONLY-yours     | Agent/Assistant                                                         |
+| `feature:topic`          | @ONLY-yours     | Topic/Conversation management                                           |
+| `feature:thread`         | @arvinxx        | Thread/Subtopic                                                         |
+| `feature:marketplace`    | @ONLY-yours     | Agent marketplace                                                       |
+| `feature:tool`           | @arvinxx        | Tool calling                                                            |
+| `feature:mcp`            | @arvinxx        | MCP integration                                                         |
+| `feature:search`         | @ONLY-yours     | Search functionality                                                    |
+| `feature:tts`            | @tjx666         | Text-to-speech                                                          |
+| `feature:export`         | @ONLY-yours     | Export functionality                                                    |
+| `feature:group-chat`     | @RiverTwilight  | Group chat functionality                                                |
+| `feature:memory`         | @nekomeowww     | Memory feature                                                          |
+| `feature:team-workspace` | @rdmclin2       | Team workspace application                                              |
+
+### Deployment Labels (deployment:\*)
+
+| Label              | Owner       | Notes                      |
+| ------------------ | ----------- | -------------------------- |
+| All `deployment:*` | @nekomeowww | Server/client/pglite modes |
+
+### Hosting Labels (hosting:\*)
+
+| Label               | Owner       | Notes                  |
+| ------------------- | ----------- | ---------------------- |
+| `hosting:cloud`     | @tjx666     | Official LobeHub Cloud |
+| `hosting:self-host` | @nekomeowww | Self-hosting issues    |
+| `hosting:vercel`    | @nekomeowww | Vercel deployment      |
+| `hosting:zeabur`    | @nekomeowww | Zeabur deployment      |
+| `hosting:railway`   | @nekomeowww | Railway deployment     |
+
+### Issue Type Labels
+
+| Label              | Owner                | Notes                        |
+| ------------------ | -------------------- | ---------------------------- |
+| 💄 Design          | @canisminor1990      | Design and styling           |
+| 📝 Documentation   | @tjx666              | Documentation                |
+| ⚡️ Performance     | @ONLY-yours          | Performance optimization     |
+| 🐛 Bug             | (depends on feature) | Assign based on other labels |
+| 🌠 Feature Request | (depends on feature) | Assign based on other labels |
+
+## Assignment Rules
+
+### Priority Order (apply in order)
+
+1. **Specific feature owner** - e.g., `feature:knowledge-base` → @RiverTwilight
+2. **Platform owner** - e.g., `platform:mobile` → @sudongyuer
+3. **Provider owner** - e.g., `provider:*` → @sxjeru
+4. **Component owner** - e.g., 💄 Design → @canisminor1990
+5. **Infrastructure owner** - e.g., `deployment:*` → @nekomeowww
+6. **General maintainer** - @ONLY-yours for general bugs/issues
+7. **Last resort** - @arvinxx (only if no clear owner)
+
+### Special Cases
+
+**Multiple labels with different owners:**
+
+- Mention the **most specific** feature owner first
+- Mention secondary owners if their input is valuable
+- Example: `feature:knowledge-base` + `deployment:server` → @RiverTwilight (primary), @nekomeowww (secondary)
+
+**Priority:high issues:**
+
+- Mention feature owner + @arvinxx
+- Example: `priority:high` + `feature:image` → @tjx666 @arvinxx
+
+**No clear owner:**
+
+- Assign to @ONLY-yours for general issues
+- Only mention @arvinxx if critical and truly unclear
+
+## Comment Templates
+
+**Single owner:**
+
+```
+@username - This is a [feature/component] issue. Please take a look.
+```
+
+**Multiple owners:**
+
+```
+@primary @secondary - This involves [features]. Please coordinate.
+```
+
+**High priority:**
+
+```
+@owner @arvinxx - High priority [feature] issue.
+```
@@ -0,0 +1,89 @@
+# Code Comment Translation Assistant
+
+You are a code comment translation assistant. Your task is to find non-English comments in the codebase and translate them to English.
+
+## Target Directories
+
+- apps/desktop/src/
+- packages/\*/src/
+- src
+
+## Workflow
+
+### 1. Select a Module to Process
+
+Module granularity examples:
+
+- A single package: `packages/database`
+- A desktop module: `apps/desktop/src/modules/auth`
+- A service directory: `src/services/user`
+
+### 2. Find Non-English Comments
+
+- Search for files containing non-English characters in comments (excluding test files)
+- File types to check: `.ts`, `.tsx`
+- Exclude: `*.test.ts`, `*.test.tsx`, `*.spec.ts`, `*.spec.tsx`, `node_modules`, `dist`, `build`
+
+### 3. Translate Comments
+
+- Translate all non-English comments to English while preserving:
+  - Code functionality (do not change any code)
+  - Comment structure and formatting
+  - JSDoc tags and annotations
+  - Markdown formatting in comments
+- Translation guidelines:
+  - Keep technical terms accurate
+  - Maintain professional tone
+  - Preserve line breaks and indentation
+  - Keep TODO/FIXME/NOTE markers in English
+
+### 4. Limit Changes
+
+- **CRITICAL**: Ensure total changes do not exceed 500 lines
+- If a module would exceed 500 lines, process only part of it
+- Count lines using: `git diff --stat`
+- Stop processing files once approaching the 500-line limit
+
+### 5. Create Pull Request
+
+- Create a new branch: `automatic/translate-comments-[module-name]-[date]`
+- Commit changes with message format:
+  ```
+  🌐 chore: translate non-English comments to English in [module-name]
+  ```
+- Push the branch
+- Create a PR with:
+
+  - Title: `🌐 chore: translate non-English comments to English in [module-name]`
+  - Body following this template:
+
+  ```markdown
+  ## Summary
+
+  - Translated non-English comments to English in `[module-name]`
+  - Total lines changed: [number] lines
+  - Files affected: [number] files
+
+  ## Changes
+
+  - [ ] All non-English comments translated to English
+  - [ ] Code functionality unchanged
+  - [ ] Comment formatting preserved
+
+  ## Module Processed
+
+  `[module-path]`
+
+  ---
+  🤖 Generated with [Claude Code](https://claude.com/claude-code)
+  ```
+
+## Important Rules
+
+- **DO NOT** modify any code logic, only comments
+- **DO NOT** translate non-English strings in code (only comments)
+- **DO NOT** exceed 500 lines of changes in one PR
+- **DO NOT** process test files or generated files
+- **DO** preserve all code formatting and structure
+- **DO** ensure translations are technically accurate
+- **DO** verify changes compile without errors
@@ -0,0 +1,183 @@
+---
+description: Complete guide for adding a new AI provider documentation to LobeChat
+alwaysApply: false
+---
+
+# Adding New AI Provider Documentation
+
+This document provides a step-by-step guide for adding documentation for a new AI provider to LobeChat, based on the complete workflow used for adding providers like BFL (Black Forest Labs) and FAL.
+
+## Overview
+
+Adding a new provider requires creating both user-facing documentation and technical configuration files. The process involves:
+
+1. Creating usage documentation (EN + CN)
+2. Adding environment variable documentation (EN + CN)
+3. Updating Docker configuration files
+4. Updating .env.example file
+5. Preparing image resources
+
+## Step 1: Create Provider Usage Documentation
+
+Create user-facing documentation that explains how to use the new provider.
+
+### Required Files
+
+Create both English and Chinese versions:
+- `docs/usage/providers/{provider-name}.mdx` (English)
+- `docs/usage/providers/{provider-name}.zh-CN.mdx` (Chinese)
+
+### Documentation Structure
+
+Follow the structure and format used in existing provider documentation. For reference, see:
+- `docs/usage/providers/fal.mdx` (English template)
+- `docs/usage/providers/fal.zh-CN.mdx` (Chinese template)
+
+### Key Requirements
+
+- **Images**: Prepare 5-6 screenshots showing the process
+- **Cover Image**: Create or obtain a cover image for the provider
+- **Accurate URLs**: Use real registration and dashboard URLs
+- **Service Type**: Specify whether it's for image generation, text generation, etc.
+- **Pricing Warning**: Include pricing information callout
+
+### Important Notes
+
+- **🔒 API Key Security**: Never include real API keys in documentation. Always use placeholder format (e.g., `bfl-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx`)
+- **🖼️ Image Hosting**: Use LobeHub's CDN for all images: `hub-apac-1.lobeobjects.space`
+
+## Step 2: Update Environment Variables Documentation
+
+Add the new provider's environment variables to the self-hosting documentation.
+
+### Files to Update
+
+- `docs/self-hosting/environment-variables/model-provider.mdx` (English)
+- `docs/self-hosting/environment-variables/model-provider.zh-CN.mdx` (Chinese)
+
+### Content to Add
+
+Add two sections for each provider:
+
+```markdown
+### `{PROVIDER}_API_KEY`
+
+- Type: Required
+- Description: This is the API key you applied for in the {Provider Name} service.
+- Default: -
+- Example: `{api-key-format-example}`
+
+### `{PROVIDER}_MODEL_LIST`
+
+- Type: Optional
+- Description: Used to control the {Provider Name} model list. Use `+` to add a model, `-` to hide a model, and `model_name=display_name` to customize the display name of a model. Separate multiple entries with commas. The definition syntax follows the same rules as other providers' model lists.
+- Default: `-`
+- Example: `-all,+{model-id-1},+{model-id-2}={display-name}`
+
+The above example disables all models first, then enables `{model-id-1}` and `{model-id-2}` (displayed as `{display-name}`).
+
+[model-list]: /docs/self-hosting/advanced/model-list
+```
+
+### Important Notes
+
+- **API Key Format**: Use proper UUID format for examples (e.g., `12345678-1234-1234-1234-123456789abc`)
+- **Real Model IDs**: Use actual model IDs from the codebase, not placeholders
+- **Consistent Naming**: Follow the pattern `{PROVIDER}_API_KEY` and `{PROVIDER}_MODEL_LIST`
+
+## Step 3: Update Docker Configuration Files
+
+Add environment variables to all Docker configuration files to ensure the provider works in containerized deployments.
+
+### Files to Update
+
+All Dockerfile variants must be updated:
+- `Dockerfile`
+- `Dockerfile.database`
+- `Dockerfile.pglite`
+
+### Changes Required
+
+Add the new provider's environment variables at the **end** of the ENV section, just before the final line:
+
+```dockerfile
+# Previous providers...
+    # 302.AI
+    AI302_API_KEY="" AI302_MODEL_LIST="" \
+    # {New Provider 1}
+    {PROVIDER1}_API_KEY="" {PROVIDER1}_MODEL_LIST="" \
+    # {New Provider 2}
+    {PROVIDER2}_API_KEY="" {PROVIDER2}_MODEL_LIST=""
+```
+
+### Important Rules
+
+- **Position**: Add new providers at the **end** of the list
+- **Ordering**: When adding multiple providers, use alphabetical order (e.g., FAL before BFL)
+- **Consistency**: Maintain identical ordering across all Dockerfile variants
+- **Format**: Follow the pattern `{PROVIDER}_API_KEY="" {PROVIDER}_MODEL_LIST="" \`
+
+## Step 4: Update .env.example File
+
+Add example configuration entries to help users understand how to configure the provider locally.
+
+### File to Update
+
+- `.env.example`
+
+### Content to Add
+
+Add new sections before the "Market Service" section:
+
+```bash
+### {Provider Name} ###
+
+# {PROVIDER}_API_KEY={provider-prefix}-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
+```
+
+### Format Guidelines
+
+- **Section Header**: Use `### {Provider Name} ###` format
+- **Commented Example**: Use `#` to comment out the example
+- **Key Format**: Use appropriate prefix for the provider (e.g., `bfl-`, `fal-`, `sk-`)
+- **Position**: Add before the Market Service section
+- **Spacing**: Maintain consistent spacing with existing entries
+
+## Step 5: Image Resources
+
+Prepare all necessary image resources for the documentation.
+
+### Required Images
+
+1. **Cover Image**: Provider logo or branded image
+2. **API Dashboard Screenshots**: 3-4 screenshots showing API key creation process
+3. **LobeChat Configuration Screenshots**: 2-3 screenshots showing provider setup in LobeChat
+
+### Image Guidelines
+
+- **Quality**: Use high-resolution screenshots
+- **Consistency**: Maintain consistent styling across all screenshots
+- **Privacy**: Remove or blur any sensitive information
+- **Format**: Use PNG format for screenshots
+- **Hosting**: Use LobeHub's CDN (`hub-apac-1.lobeobjects.space`) for all images
+
+## Checklist
+
+Before submitting your provider documentation:
+
+- [ ] Created both English and Chinese usage documentation
+- [ ] Added environment variable documentation (EN + CN)
+- [ ] Updated all 3 Dockerfile variants with consistent ordering
+- [ ] Updated .env.example with proper key format
+- [ ] Prepared all required screenshots and images
+- [ ] Used actual model IDs from the codebase
+- [ ] Verified no real API keys are included in documentation
+- [ ] Used LobeHub CDN for all image hosting
+- [ ] Tested the documentation for clarity and accuracy
+
+## Reference
+
+This guide was created based on the implementation of BFL (Black Forest Labs) provider documentation. For a complete example, refer to:
+- Commits: `d2da03e1a` (documentation) and `6a2e95868` (environment variables)
+- Files: `docs/usage/providers/bfl.mdx`, `docs/usage/providers/bfl.zh-CN.mdx`
+- PR: Current branch `tj/feat/bfl-docs`
@@ -0,0 +1,175 @@
+---
+description: Guide for adding environment variables to configure user settings
+alwaysApply: false
+---
+
+# Adding Environment Variable for User Settings
+
+Add server-side environment variables to configure default values for user settings.
+
+**Priority**: User Custom > Server Env Var > Hardcoded Default
+
+## Steps
+
+### 1. Define Environment Variable
+
+Create `src/envs/<domain>.ts`:
+
+```typescript
+import { createEnv } from '@t3-oss/env-nextjs';
+import { z } from 'zod';
+
+export const get<Domain>Config = () => {
+  return createEnv({
+    server: {
+      YOUR_ENV_VAR: z.coerce.number().min(MIN).max(MAX).optional(),
+    },
+    runtimeEnv: {
+      YOUR_ENV_VAR: process.env.YOUR_ENV_VAR,
+    },
+  });
+};
+
+export const <domain>Env = get<Domain>Config();
+```
+
+### 2. Update Type (Optional)
+
+**Skip this step if the domain field already exists in `GlobalServerConfig`.**
+
+Add to `packages/types/src/serverConfig.ts`:
+
+```typescript
+export interface GlobalServerConfig {
+  <domain>?: {
+    <settingName>?: <type>;
+  };
+}
+```
+
+**Prefer reusing existing types** from `packages/types/src/user/settings` with `PartialDeep`:
+
+```typescript
+import { User<Domain>Config } from './user/settings';
+
+export interface GlobalServerConfig {
+  <domain>?: PartialDeep<User<Domain>Config>;
+}
+```
+
+### 3. Assemble Server Config (Optional)
+
+**Skip this step if the domain field already exists in server config.**
+
+In `src/server/globalConfig/index.ts`:
+
+```typescript
+import { <domain>Env } from '@/envs/<domain>';
+import { cleanObject } from '@/utils/object';
+
+export const getServerGlobalConfig = async () => {
+  const config: GlobalServerConfig = {
+    // ...
+    <domain>: cleanObject({
+      <settingName>: <domain>Env.YOUR_ENV_VAR,
+    }),
+  };
+  return config;
+};
+```
+
+If the domain already exists, just add the new field to the existing `cleanObject()`:
+
+```typescript
+<domain>: cleanObject({
+  existingField: <domain>Env.EXISTING_VAR,
+  <settingName>: <domain>Env.YOUR_ENV_VAR, // Add this line
+}),
+```
+
+### 4. Merge to User Store (Optional)
+
+**Skip this step if the domain field already exists in `serverSettings`.**
+
+In `src/store/user/slices/common/action.ts`, add to `serverSettings`:
+
+```typescript
+const serverSettings: PartialDeep<UserSettings> = {
+  defaultAgent: serverConfig.defaultAgent,
+  <domain>: serverConfig.<domain>, // Add this line
+  // ...
+};
+```
+
+### 5. Update .env.example
+
+```bash
+# <Description> (range/options, default: X)
+# YOUR_ENV_VAR=<example>
+```
+
+### 6. Update Documentation
+
+Update both English and Chinese documentation:
+- `docs/self-hosting/environment-variables/basic.mdx`
+- `docs/self-hosting/environment-variables/basic.zh-CN.mdx`
+
+Add new section or subsection with environment variable details (type, description, default, example, range/constraints).
+
+## Type Reuse
+
+**Prefer reusing existing types** from `packages/types/src/user/settings` instead of defining inline types in `serverConfig.ts`.
+
+```typescript
+// ✅ Good - reuse existing type
+import { UserImageConfig } from './user/settings';
+
+export interface GlobalServerConfig {
+  image?: PartialDeep<UserImageConfig>;
+}
+
+// ❌ Bad - inline type definition
+export interface GlobalServerConfig {
+  image?: {
+    defaultImageNum?: number;
+  };
+}
+```
+
+## Example: AI_IMAGE_DEFAULT_IMAGE_NUM
+
+```typescript
+// src/envs/image.ts
+export const getImageConfig = () => {
+  return createEnv({
+    server: {
+      AI_IMAGE_DEFAULT_IMAGE_NUM: z.coerce.number().min(1).max(20).optional(),
+    },
+    runtimeEnv: {
+      AI_IMAGE_DEFAULT_IMAGE_NUM: process.env.AI_IMAGE_DEFAULT_IMAGE_NUM,
+    },
+  });
+};
+
+// packages/types/src/serverConfig.ts
+import { UserImageConfig } from './user/settings';
+
+export interface GlobalServerConfig {
+  image?: PartialDeep<UserImageConfig>;
+}
+
+// src/server/globalConfig/index.ts
+image: cleanObject({
+  defaultImageNum: imageEnv.AI_IMAGE_DEFAULT_IMAGE_NUM,
+}),
+
+// src/store/user/slices/common/action.ts
+const serverSettings: PartialDeep<UserSettings> = {
+  image: serverConfig.image,
+  // ...
+};
+
+// .env.example
+# AI_IMAGE_DEFAULT_IMAGE_NUM=4
+```
+
@@ -0,0 +1,28 @@
+---
+description: cursor rules writing and optimization guide
+globs: 
+alwaysApply: false
+---
+当你编写或修改 Cursor Rule 时，请遵循以下准则：
+
+- 当你知道 rule 的文件名时，使用 `read_file` 而不是 `fetch_rules` 去读取它们，它们都在项目根目录的 `.cursor/rules/` 文件夹下
+
+- 代码示例
+  - 示例应尽量精简，仅保留演示核心
+  - 删除与示例无关的导入/导出语句，但保留必要的导入
+  - 同一文件存在多个示例时，若前文已演示模块导入，后续示例可省略重复导入
+  - 无需书写 `export`
+  - 可省略与演示无关或重复的 props、配置对象属性、try/catch、CSS 等代码
+  - 删除无关注释，保留有助理解的注释
+
+- 格式
+  - 修改前请先确认原始文档语言，并保持一致
+  - 无序列表统一使用 `-`
+  - 列表末尾的句号是多余的
+  - 非必要不使用加粗、行内代码等样式，Rule 主要供 LLM 阅读
+  - 避免中英文逐句对照。若括号内容为示例而非翻译，可保留
+
+- Review
+  - 修正 Markdown 语法问题
+  - 纠正错别字
+  - 指出示例与说明不一致之处
@@ -0,0 +1,25 @@
+---
+globs: packages/database/migrations/**/*
+alwaysApply: false
+---
+
+# Database Migrations Guide
+
+## Defensive Programming - Use Idempotent Clauses
+
+Always use defensive clauses to make migrations idempotent:
+
+```sql
+-- ✅ Good: Idempotent operations
+ALTER TABLE "users" ADD COLUMN IF NOT EXISTS "avatar" text;
+DROP TABLE IF EXISTS "old_table";
+CREATE INDEX IF NOT EXISTS "users_email_idx" ON "users" ("email");
+ALTER TABLE "posts" DROP COLUMN IF EXISTS "deprecated_field";
+
+-- ❌ Bad: Non-idempotent operations
+ALTER TABLE "users" ADD COLUMN "avatar" text;
+DROP TABLE "old_table";
+CREATE INDEX "users_email_idx" ON "users" ("email");
+```
+
+**Important**: After modifying migration SQL (e.g., adding `IF NOT EXISTS` clauses), run `bun run db:generate-client` to update the hash in `packages/database/src/core/migrations.json`.
@@ -0,0 +1,84 @@
+---
+description: 包含添加 console.log 日志请求时
+globs:
+alwaysApply: false
+---
+# Debug 包使用指南
+
+本项目使用 [debug](mdc:https:/github.com/debug-js/debug) 包进行调试日志记录。使用此规则来确保团队成员统一调试日志格式。
+
+## 基本用法
+
+1. 导入 debug 包：
+
+```typescript
+import debug from 'debug';
+```
+
+2. 创建一个命名空间的日志记录器：
+
+```typescript
+// 格式: lobe:[模块]:[子模块]
+const log = debug('lobe-[模块名]:[子模块名]');
+```
+
+3. 使用日志记录器：
+
+```typescript
+log('简单消息');
+log('带变量的消息: %O', object);
+log('格式化数字: %d', number);
+```
+
+## 命名空间约定
+
+- 桌面应用相关: `lobe-desktop:[模块]`
+- 服务端相关: `lobe-server:[模块]`
+- 客户端相关: `lobe-client:[模块]`
+- 路由相关: `lobe-[类型]-router:[模块]`
+
+## 格式说明符
+
+- `%O` - 对象展开（推荐用于复杂对象）
+- `%o` - 对象
+- `%s` - 字符串
+- `%d` - 数字
+
+## 示例
+
+查看 [market/index.ts](mdc:src/server/routers/edge/market/index.ts) 中的使用示例：
+
+```typescript
+import debug from 'debug';
+
+const log = debug('lobe-edge-router:market');
+
+log('getAgent input: %O', input);
+```
+
+## 启用调试
+
+要在开发时启用调试输出，需设置环境变量：
+
+### 在浏览器中
+
+在控制台执行：
+```javascript
+localStorage.debug = 'lobe-*'
+```
+
+### 在 Node.js 环境中
+
+```bash
+DEBUG=lobe-* npm run dev
+# 或者
+DEBUG=lobe-* pnpm dev
+```
+
+### 在 Electron 应用中
+
+可以在主进程和渲染进程启动前设置环境变量：
+
+```typescript
+process.env.DEBUG = 'lobe-*';
+```
@@ -0,0 +1,188 @@
+---
+description: 桌面端测试
+globs:
+alwaysApply: false
+---
+# 桌面端控制器单元测试指南
+
+## 测试框架与目录结构
+
+LobeChat 桌面端使用 Vitest 作为测试框架。控制器的单元测试应放置在对应控制器文件同级的 `__tests__` 目录下，并以原控制器文件名加 `.test.ts` 作为文件名。
+
+```
+apps/desktop/src/main/controllers/
+├── __tests__/
+│   ├── index.test.ts
+│   ├── MenuCtr.test.ts
+│   └── ...
+├── McpCtr.ts
+├── MenuCtr.ts
+└── ...
+```
+
+## 测试文件基本结构
+
+```typescript
+import { beforeEach, describe, expect, it, vi } from 'vitest';
+
+import type { App } from '@/core/App';
+
+import YourController from '../YourControllerName';
+
+// 模拟依赖
+vi.mock('依赖模块', () => ({
+  依赖函数: vi.fn(),
+}));
+
+// 模拟 App 实例
+const mockApp = {
+  // 按需模拟必要的 App 属性和方法
+} as unknown as App;
+
+describe('YourController', () => {
+  let controller: YourController;
+
+  beforeEach(() => {
+    vi.clearAllMocks();
+    controller = new YourController(mockApp);
+  });
+
+  describe('方法名', () => {
+    it('测试场景描述', async () => {
+      // 准备测试数据
+
+      // 执行被测方法
+      const result = await controller.方法名(参数);
+
+      // 验证结果
+      expect(result).toMatchObject(预期结果);
+    });
+  });
+});
+```
+
+## 模拟外部依赖
+
+### 模拟模块函数
+
+```typescript
+const mockFunction = vi.fn();
+
+vi.mock('module-name', () => ({
+  functionName: mockFunction,
+}));
+```
+
+### 模拟 Node.js 核心模块
+
+例如模拟 `child_process.exec` 和 `util.promisify`:
+
+```typescript
+// 存储模拟的 exec 实现
+const mockExecImpl = vi.fn();
+
+// 模拟 child_process.exec
+vi.mock('child_process', () => ({
+  exec: vi.fn((cmd, callback) => {
+    return mockExecImpl(cmd, callback);
+  }),
+}));
+
+// 模拟 util.promisify
+vi.mock('util', () => ({
+  promisify: vi.fn((fn) => {
+    return async (cmd: string) => {
+      return new Promise((resolve, reject) => {
+        mockExecImpl(cmd, (error: Error | null, result: any) => {
+          if (error) reject(error);
+          else resolve(result);
+        });
+      });
+    };
+  }),
+}));
+```
+
+## 编写有效的测试用例
+
+### 测试分类
+
+将测试用例分为不同类别，每个类别测试一个特定场景：
+
+```typescript
+// 成功场景
+it('应该成功完成操作', async () => {});
+
+// 边界条件
+it('应该处理边界情况', async () => {});
+
+// 错误处理
+it('应该优雅地处理错误', async () => {});
+```
+
+### 设置测试数据
+
+```typescript
+// 模拟返回值
+mockExecImpl.mockImplementation((cmd: string, callback: any) => {
+  if (cmd === '命令') {
+    callback(null, { stdout: '成功输出' });
+  } else {
+    callback(new Error('错误信息'), null);
+  }
+});
+```
+
+### 断言
+
+使用 Vitest 的断言函数验证结果：
+
+```typescript
+// 检查基本值
+expect(result.success).toBe(true);
+
+// 检查对象部分匹配
+expect(result.data).toMatchObject({
+  key: 'value',
+});
+
+// 检查数组
+expect(result.items).toHaveLength(2);
+expect(result.items[0].name).toBe('expectedName');
+
+// 检查函数调用
+expect(mockFunction).toHaveBeenCalledWith(expectedArgs);
+expect(mockFunction).toHaveBeenCalledTimes(1);
+```
+
+## 最佳实践
+
+1. **隔离测试**：确保每个测试互不影响，使用 `beforeEach` 重置模拟和状态
+2. **全面覆盖**：测试正常流程、边界条件和错误处理
+3. **清晰命名**：测试名称应清晰描述测试内容和预期结果
+4. **避免测试实现细节**：测试应该关注行为而非实现细节，使代码重构不会破坏测试
+5. **模拟外部依赖**：使用 `vi.mock()` 模拟所有外部依赖，减少测试的不确定性
+
+## 示例：测试 IPC 事件处理方法
+
+```typescript
+it('应该正确处理 IPC 事件', async () => {
+  // 模拟依赖
+  mockSomething.mockReturnValue({ result: 'success' });
+
+  // 调用 IPC 方法
+  const result = await controller.ipcMethodName({
+    param1: 'value1',
+    param2: 'value2',
+  });
+
+  // 验证结果
+  expect(result).toEqual({
+    success: true,
+    data: { result: 'success' },
+  });
+
+  // 验证依赖调用
+  expect(mockSomething).toHaveBeenCalledWith('value1', 'value2');
+});
+```
@@ -0,0 +1,154 @@
+---
+description: 当要做 electron 相关工作时
+globs:
+alwaysApply: false
+---
+**桌面端新功能实现指南**
+
+## 桌面端应用架构概述
+
+LobeChat 桌面端基于 Electron 框架构建，采用主进程-渲染进程架构：
+
+1. **主进程 (Main Process)**：
+   - 位置：`apps/desktop/src/main`
+   - 职责：控制应用生命周期、系统API交互、窗口管理、后台服务
+
+2. **渲染进程 (Renderer Process)**：
+   - 复用 Web 端代码，位于 `src` 目录
+   - 通过 IPC 与主进程通信
+
+3. **预加载脚本 (Preload)**：
+   - 位置：`apps/desktop/src/preload`
+   - 职责：安全地暴露主进程功能给渲染进程
+
+## 添加新桌面端功能流程
+
+### 1. 确定功能需求与设计
+
+首先确定新功能的需求和设计，包括：
+- 功能描述和用例
+- 是否需要系统级API（如文件系统、网络等）
+- UI/UX设计（如必要）
+- 与现有功能的交互方式
+
+### 2. 在主进程中实现核心功能
+
+1. **创建控制器 (Controller)**
+   - 位置：`apps/desktop/src/main/controllers/`
+   - 示例：创建 `NewFeatureCtr.ts`
+   - 规范：按 `_template.ts` 模板格式实现
+   - 注册：在 `apps/desktop/src/main/controllers/index.ts` 导出
+
+2. **定义 IPC 事件处理器**
+   - 使用 `@ipcClientEvent('eventName')` 装饰器注册事件处理函数
+   - 处理函数应接收前端传递的参数并返回结果
+   - 处理可能的错误情况
+
+3. **实现业务逻辑**
+   - 可能需要调用 Electron API 或 Node.js 原生模块
+   - 对于复杂功能，可以创建专门的服务类 (`services/`)
+
+### 3. 定义 IPC 通信类型
+
+1. **在共享类型定义中添加新类型**
+   - 位置：`packages/electron-client-ipc/src/types.ts`
+   - 添加参数类型接口（如 `NewFeatureParams`）
+   - 添加返回结果类型接口（如 `NewFeatureResult`）
+
+### 4. 在渲染进程实现前端功能
+
+1. **创建服务层**
+   - 位置：`src/services/electron/`
+   - 添加服务方法调用 IPC
+   - 使用 `dispatch` 或 `invoke` 函数
+
+   ```typescript
+   // src/services/electron/newFeatureService.ts
+   import { dispatch } from '@lobechat/electron-client-ipc';
+   import { NewFeatureParams } from 'types';
+
+   export const newFeatureService = async (params: NewFeatureParams) => {
+     return dispatch('newFeatureEventName', params);
+   };
+   ```
+
+2. **实现 Store Action**
+   - 位置：`src/store/`
+   - 添加状态更新逻辑和错误处理
+
+3. **添加 UI 组件**
+   - 根据需要在适当位置添加UI组件
+   - 通过 Store 或 Service 层调用功能
+
+### 5. 如果是新增内置工具，遵循工具实现流程
+
+参考 [desktop-local-tools-implement.mdc](mdc:desktop-local-tools-implement.mdc) 了解更多关于添加内置工具的详细步骤。
+
+### 6. 添加测试
+
+1. **单元测试**
+   - 位置：`apps/desktop/src/main/controllers/__tests__/`
+   - 测试主进程组件功能
+
+2. **集成测试**
+   - 测试 IPC 通信和功能完整流程
+
+## 最佳实践
+
+1. **安全性考虑**
+   - 谨慎处理用户数据和文件系统访问
+   - 适当验证和清理输入数据
+   - 限制暴露给渲染进程的API范围
+
+2. **性能优化**
+   - 对于耗时操作，考虑使用异步方法
+   - 大型数据传输考虑分批处理
+
+3. **用户体验**
+   - 为长时间操作添加进度指示
+   - 提供适当的错误反馈
+   - 考虑操作的可撤销性
+
+4. **代码组织**
+   - 遵循项目现有的命名和代码风格约定
+   - 为新功能添加适当的文档和注释
+   - 功能模块化，避免过度耦合
+
+## 示例：实现系统通知功能
+
+```typescript
+// apps/desktop/src/main/controllers/NotificationCtr.ts
+import { BrowserWindow, Notification } from 'electron';
+import { ipcClientEvent } from 'electron-client-ipc';
+
+interface ShowNotificationParams {
+  title: string;
+  body: string;
+}
+
+export class NotificationCtr {
+  @ipcClientEvent('showNotification')
+  async handleShowNotification({ title, body }: ShowNotificationParams) {
+    try {
+      if (!Notification.isSupported()) {
+        return { success: false, error: 'Notifications not supported' };
+      }
+
+      const notification = new Notification({
+        title,
+        body,
+      });
+
+      notification.show();
+
+      return { success: true };
+    } catch (error) {
+      console.error('Failed to show notification:', error);
+      return {
+        success: false,
+        error: error instanceof Error ? error.message : 'Unknown error'
+      };
+    }
+  }
+}
+```
@@ -0,0 +1,80 @@
+---
+description:
+globs:
+alwaysApply: false
+---
+**新增桌面端工具流程:**
+
+1.  **定义工具接口 (Manifest):**
+    *   **文件:** `src/tools/[tool_category]/index.ts` (例如: `src/tools/local-files/index.ts`)
+    *   **操作:**
+        *   在 `ApiName` 对象（例如 `LocalFilesApiName`）中添加一个新的、唯一的 API 名称。
+        *   在 `Manifest` 对象（例如 `LocalFilesManifest`）的 `api` 数组中，新增一个对象来定义新工具的接口。
+        *   **关键字段:**
+            *   `name`: 使用上一步定义的 API 名称。
+            *   `description`: 清晰描述工具的功能，供 Agent 理解和向用户展示。
+            *   `parameters`: 使用 JSON Schema 定义工具所需的输入参数。
+                *   `type`: 通常是 'object'。
+                *   `properties`: 定义每个参数的名称、`description`、`type` (string, number, boolean, array, etc.)，使用英文。
+                *   `required`: 一个字符串数组，列出必须提供的参数名称。
+
+2.  **定义相关类型:**
+    *   **文件 1:** `packages/electron-client-ipc/src/types.ts` (或类似的共享 IPC 类型文件)
+        *   **操作:** 定义传递给 IPC 事件的参数类型接口 (例如: `RenameLocalFileParams`, `MoveLocalFileParams`)。确保与 Manifest 中定义的 `parameters` 一致。
+    *   **文件 2:** `src/tools/[tool_category]/type.ts` (例如: `src/tools/local-files/type.ts`)
+        *   **操作:** 定义此工具执行后，存储在前端 Zustand Store 中的状态类型接口 (例如: `LocalRenameFileState`, `LocalMoveFileState`)。这通常包含操作结果（成功/失败）、错误信息以及相关数据（如旧路径、新路径等）。
+
+3.  **实现前端状态管理 (Store Action):**
+    *   **文件:** `src/store/chat/slices/builtinTool/actions/[tool_category].ts` (例如: `src/store/chat/slices/builtinTool/actions/localFile.ts`)
+    *   **操作:**
+        *   导入在步骤 2 中定义的 IPC 参数类型和状态类型。
+        *   在 Action 接口 (例如: `LocalFileAction`) 中添加新 Action 的方法签名，使用对应的 IPC 参数类型。
+        *   在 `createSlice` (例如: `localFileSlice`) 中实现该 Action 方法：
+            *   接收 `id` (消息 ID) 和 `params` (符合 IPC 参数类型)。
+            *   设置加载状态 (`toggleLocalFileLoading(id, true)`)。
+            *   调用对应的 `Service` 层方法 (见步骤 4)，传递 `params`。
+            *   使用 `try...catch` 处理 `Service` 调用可能发生的错误。
+            *   **成功时:**
+                *   调用 `updatePluginState(id, {...})` 更新插件状态，使用步骤 2 中定义的状态类型。
+                *   调用 `internal_updateMessageContent(id, JSON.stringify({...}))` 更新消息内容，通常包含成功确认信息。
+            *   **失败时:**
+                *   记录错误 (`console.error`)。
+                *   调用 `updatePluginState(id, {...})` 更新插件状态，包含错误信息。
+                *   调用 `internal_updateMessagePluginError(id, {...})` 设置消息的错误状态。
+                *   调用 `internal_updateMessageContent(id, JSON.stringify({...}))` 更新消息内容，包含错误信息。
+            *   在 `finally` 块中取消加载状态 (`toggleLocalFileLoading(id, false)`)。
+            *   返回操作是否成功 (`boolean`)。
+
+4.  **实现 Service 层 (调用 IPC):**
+    *   **文件:** `src/services/electron/[tool_category]Service.ts` (例如: `src/services/electron/localFileService.ts`)
+    *   **操作:**
+        *   导入在步骤 2 中定义的 IPC 参数类型。
+        *   添加一个新的 `async` 方法，方法名通常与 Action 名称对应 (例如: `renameLocalFile`)。
+        *   方法接收 `params` (符合 IPC 参数类型)。
+        *   使用从 `@lobechat/electron-client-ipc` 导入的 `dispatch` (或 `invoke`) 函数，调用与 Manifest 中 `name` 字段匹配的 IPC 事件名称，并将 `params` 传递过去。
+        *   定义方法的返回类型，通常是 `Promise<{ success: boolean; error?: string }>`，与后端 Controller 返回的结构一致。
+
+5.  **实现后端逻辑 (Controller / IPC Handler):**
+    *   **文件:** `apps/desktop/src/main/controllers/[ToolName]Ctr.ts` (例如: `apps/desktop/src/main/controllers/LocalFileCtr.ts`)
+    *   **操作:**
+        *   导入 Node.js 相关模块 (`fs`, `path` 等) 和 IPC 相关依赖 (`ipcClientEvent`, 参数类型等)。
+        *   添加一个新的 `async` 方法，方法名通常以 `handle` 开头 (例如: `handleRenameFile`)。
+        *   使用 `@ipcClientEvent('yourApiName')` 装饰器将此方法注册为对应 IPC 事件的处理器，确保 `'yourApiName'` 与 Manifest 中的 `name` 和 Service 层调用的事件名称一致。
+        *   方法的参数应解构自 Service 层传递过来的对象，类型与步骤 2 中定义的 IPC 参数类型匹配。
+        *   实现核心业务逻辑：
+            *   进行必要的输入验证。
+            *   执行文件系统操作或其他后端任务 (例如: `fs.promises.rename`)。
+            *   使用 `try...catch` 捕获执行过程中的错误。
+            *   处理特定错误码 (`error.code`) 以提供更友好的错误消息。
+        *   返回一个包含 `success` (boolean) 和可选 `error` (string) 字段的对象。
+
+6.  **更新 Agent 文档 (System Role):**
+    *   **文件:** `src/tools/[tool_category]/systemRole.ts` (例如: `src/tools/local-files/systemRole.ts`)
+    *   **操作:**
+        *   在 `<core_capabilities>` 部分添加新工具的简要描述。
+        *   如果需要，更新 `<workflow>`。
+        *   在 `<tool_usage_guidelines>` 部分为新工具添加详细的使用说明，解释其参数、用途和预期行为。
+        *   如有必要，更新 `<security_considerations>`。
+        *   如有必要（例如工具返回了新的数据结构或路径），更新 `<response_format>` 中的示例。
+
+通过遵循这些步骤，可以系统地将新的桌面端工具集成到 LobeChat 的插件系统中。
@@ -0,0 +1,197 @@
+---
+description:
+globs:
+alwaysApply: false
+---
+**桌面端菜单配置指南**
+
+## 菜单系统概述
+
+LobeChat 桌面应用有三种主要的菜单类型：
+
+1. **应用菜单 (App Menu)**：显示在应用窗口顶部（macOS）或窗口标题栏（Windows/Linux）
+2. **上下文菜单 (Context Menu)**：右键点击时显示的菜单
+3. **托盘菜单 (Tray Menu)**：点击系统托盘图标显示的菜单
+
+## 菜单相关文件结构
+
+```
+apps/desktop/src/main/
+├── menus/                 # 菜单定义
+│   ├── appMenu.ts         # 应用菜单配置
+│   ├── contextMenu.ts     # 上下文菜单配置
+│   └── factory.ts         # 菜单工厂函数
+├── controllers/
+│   ├── MenuCtr.ts         # 菜单控制器
+│   └── TrayMenuCtr.ts     # 托盘菜单控制器
+```
+
+## 菜单配置流程
+
+### 1. 应用菜单配置
+
+应用菜单在 `apps/desktop/src/main/menus/appMenu.ts` 中定义：
+
+1. **导入依赖**
+   ```typescript
+   import { app, BrowserWindow, Menu, MenuItem, MenuItemConstructorOptions } from 'electron';
+   import { is } from 'electron-util';
+   ```
+
+2. **定义菜单项**
+   - 使用 `MenuItemConstructorOptions` 类型定义菜单结构
+   - 每个菜单项可以包含：label, accelerator (快捷键), role, submenu, click 等属性
+
+3. **创建菜单工厂函数**
+   ```typescript
+   export const createAppMenu = (win: BrowserWindow) => {
+     const template = [
+       // 定义菜单项...
+     ];
+
+     return Menu.buildFromTemplate(template);
+   };
+   ```
+
+4. **注册菜单**
+   - 在 `MenuCtr.ts` 控制器中使用 `Menu.setApplicationMenu(menu)` 设置应用菜单
+
+### 2. 上下文菜单配置
+
+上下文菜单通常在特定元素上右键点击时显示：
+
+1. **在主进程中定义菜单模板**
+   ```typescript
+   // apps/desktop/src/main/menus/contextMenu.ts
+   export const createContextMenu = () => {
+     const template = [
+       // 定义菜单项...
+     ];
+
+     return Menu.buildFromTemplate(template);
+   };
+   ```
+
+2. **在适当的事件处理器中显示菜单**
+   ```typescript
+   const menu = createContextMenu();
+   menu.popup();
+   ```
+
+### 3. 托盘菜单配置
+
+托盘菜单在 `TrayMenuCtr.ts` 中配置：
+
+1. **创建托盘图标**
+   ```typescript
+   this.tray = new Tray(trayIconPath);
+   ```
+
+2. **定义托盘菜单**
+   ```typescript
+   const contextMenu = Menu.buildFromTemplate([
+     { label: '显示主窗口', click: this.showMainWindow },
+     { type: 'separator' },
+     { label: '退出', click: () => app.quit() },
+   ]);
+   ```
+
+3. **设置托盘菜单**
+   ```typescript
+   this.tray.setContextMenu(contextMenu);
+   ```
+
+## 多语言支持
+
+为菜单添加多语言支持：
+
+1. **导入本地化工具**
+   ```typescript
+   import { i18n } from '../locales';
+   ```
+
+2. **使用翻译函数**
+   ```typescript
+   const template = [
+     {
+       label: i18n.t('menu.file'),
+       submenu: [
+         { label: i18n.t('menu.new'), click: createNew },
+         // ...
+       ]
+     },
+     // ...
+   ];
+   ```
+
+3. **在语言切换时更新菜单**
+   在 `MenuCtr.ts` 中监听语言变化事件并重新创建菜单
+
+## 添加新菜单项流程
+
+1. **确定菜单位置**
+   - 决定添加到哪个菜单（应用菜单、上下文菜单或托盘菜单）
+   - 确定在菜单中的位置（主菜单项或子菜单项）
+
+2. **定义菜单项**
+   ```typescript
+   const newMenuItem: MenuItemConstructorOptions = {
+     label: '新功能',
+     accelerator: 'CmdOrCtrl+N',
+     click: (_, window) => {
+       // 处理点击事件
+       if (window) window.webContents.send('trigger-new-feature');
+     }
+   };
+   ```
+
+3. **添加到菜单模板**
+   将新菜单项添加到相应的菜单模板中
+
+4. **对于与渲染进程交互的功能**
+   - 使用 `window.webContents.send()` 发送 IPC 消息到渲染进程
+   - 在渲染进程中监听该消息并处理
+
+## 菜单项启用/禁用控制
+
+动态控制菜单项状态：
+
+1. **保存对菜单项的引用**
+   ```typescript
+   this.menuItems = {};
+   const menu = Menu.buildFromTemplate(template);
+   this.menuItems.newFeature = menu.getMenuItemById('new-feature');
+   ```
+
+2. **根据条件更新状态**
+   ```typescript
+   updateMenuState(state) {
+     if (this.menuItems.newFeature) {
+       this.menuItems.newFeature.enabled = state.canUseNewFeature;
+     }
+   }
+   ```
+
+## 最佳实践
+
+1. **使用标准角色**
+   - 尽可能使用 Electron 预定义的角色（如 `role: 'copy'`）以获得本地化和一致的行为
+
+2. **平台特定菜单**
+   - 使用 `process.platform` 检查为不同平台提供不同菜单
+   ```typescript
+   if (process.platform === 'darwin') {
+     template.unshift({ role: 'appMenu' });
+   }
+   ```
+
+3. **快捷键冲突**
+   - 避免与系统快捷键冲突
+   - 使用 `CmdOrCtrl` 代替 `Ctrl` 以支持 macOS 和 Windows/Linux
+
+4. **保持菜单简洁**
+   - 避免过多嵌套的子菜单
+   - 将相关功能分组在一起
+
+5. **添加分隔符**
+   - 使用 `{ type: 'separator' }` 在逻辑上分隔不同组的菜单项
@@ -0,0 +1,296 @@
+---
+description:
+globs:
+alwaysApply: false
+---
+**桌面端窗口管理指南**
+
+## 窗口管理概述
+
+LobeChat 桌面应用使用 Electron 的 `BrowserWindow` 管理应用窗口。主要的窗口管理功能包括：
+
+1. **窗口创建和配置**
+2. **窗口状态管理**（大小、位置、最大化等）
+3. **多窗口协调**
+4. **窗口事件处理**
+
+## 相关文件结构
+
+```
+apps/desktop/src/main/
+├── appBrowsers.ts               # 窗口管理的核心文件
+├── controllers/
+│   └── BrowserWindowsCtr.ts     # 窗口控制器
+└── modules/
+    └── browserWindowManager.ts  # 窗口管理模块
+```
+
+## 窗口管理流程
+
+### 1. 窗口创建
+
+在 `appBrowsers.ts` 或 `BrowserWindowsCtr.ts` 中定义窗口创建逻辑：
+
+```typescript
+export const createMainWindow = () => {
+  const mainWindow = new BrowserWindow({
+    width: 1200,
+    height: 800,
+    minWidth: 600,
+    minHeight: 400,
+    webPreferences: {
+      preload: path.join(__dirname, '../preload/index.js'),
+      contextIsolation: true,
+      nodeIntegration: false,
+    },
+    // 其他窗口配置项...
+  });
+
+  // 加载应用内容
+  if (isDev) {
+    mainWindow.loadURL('http://localhost:3000');
+    mainWindow.webContents.openDevTools();
+  } else {
+    mainWindow.loadFile(path.join(__dirname, '../../renderer/index.html'));
+  }
+
+  return mainWindow;
+};
+```
+
+### 2. 窗口状态管理
+
+实现窗口状态持久化保存和恢复：
+
+1. **保存窗口状态**
+   ```typescript
+   const saveWindowState = (window: BrowserWindow) => {
+     if (!window.isMinimized() && !window.isMaximized()) {
+       const position = window.getPosition();
+       const size = window.getSize();
+
+       settings.set('windowState', {
+         x: position[0],
+         y: position[1],
+         width: size[0],
+         height: size[1],
+       });
+     }
+   };
+   ```
+
+2. **恢复窗口状态**
+   ```typescript
+   const restoreWindowState = (window: BrowserWindow) => {
+     const savedState = settings.get('windowState');
+
+     if (savedState) {
+       window.setBounds({
+         x: savedState.x,
+         y: savedState.y,
+         width: savedState.width,
+         height: savedState.height,
+       });
+     }
+   };
+   ```
+
+3. **监听窗口事件**
+   ```typescript
+   window.on('close', () => saveWindowState(window));
+   window.on('moved', () => saveWindowState(window));
+   window.on('resized', () => saveWindowState(window));
+   ```
+
+### 3. 实现多窗口管理
+
+对于需要多窗口支持的功能：
+
+1. **跟踪窗口**
+   ```typescript
+   export class WindowManager {
+     private windows: Map<string, BrowserWindow> = new Map();
+
+     createWindow(id: string, options: BrowserWindowConstructorOptions) {
+       const window = new BrowserWindow(options);
+       this.windows.set(id, window);
+
+       window.on('closed', () => {
+         this.windows.delete(id);
+       });
+
+       return window;
+     }
+
+     getWindow(id: string) {
+       return this.windows.get(id);
+     }
+
+     getAllWindows() {
+       return Array.from(this.windows.values());
+     }
+   }
+   ```
+
+2. **窗口间通信**
+   ```typescript
+   // 从一个窗口向另一个窗口发送消息
+   sendMessageToWindow(targetWindowId, channel, data) {
+     const targetWindow = this.getWindow(targetWindowId);
+     if (targetWindow) {
+       targetWindow.webContents.send(channel, data);
+     }
+   }
+   ```
+
+### 4. 窗口与渲染进程通信
+
+通过 IPC 实现窗口操作：
+
+1. **在主进程中注册 IPC 处理器**
+   ```typescript
+   // BrowserWindowsCtr.ts
+   @ipcClientEvent('minimizeWindow')
+   handleMinimizeWindow() {
+     const focusedWindow = BrowserWindow.getFocusedWindow();
+     if (focusedWindow) {
+       focusedWindow.minimize();
+     }
+     return { success: true };
+   }
+
+   @ipcClientEvent('maximizeWindow')
+   handleMaximizeWindow() {
+     const focusedWindow = BrowserWindow.getFocusedWindow();
+     if (focusedWindow) {
+       if (focusedWindow.isMaximized()) {
+         focusedWindow.restore();
+       } else {
+         focusedWindow.maximize();
+       }
+     }
+     return { success: true };
+   }
+
+   @ipcClientEvent('closeWindow')
+   handleCloseWindow() {
+     const focusedWindow = BrowserWindow.getFocusedWindow();
+     if (focusedWindow) {
+       focusedWindow.close();
+     }
+     return { success: true };
+   }
+   ```
+
+2. **在渲染进程中调用**
+   ```typescript
+   // src/services/electron/windowService.ts
+   import { dispatch } from '@lobechat/electron-client-ipc';
+
+   export const windowService = {
+     minimize: () => dispatch('minimizeWindow'),
+     maximize: () => dispatch('maximizeWindow'),
+     close: () => dispatch('closeWindow'),
+   };
+   ```
+
+### 5. 自定义窗口控制 (无边框窗口)
+
+对于自定义窗口标题栏：
+
+1. **创建无边框窗口**
+   ```typescript
+   const window = new BrowserWindow({
+     frame: false,
+     titleBarStyle: 'hidden',
+     // 其他选项...
+   });
+   ```
+
+2. **在渲染进程中实现拖拽区域**
+   ```css
+   /* CSS */
+   .titlebar {
+     -webkit-app-region: drag;
+   }
+
+   .titlebar-button {
+     -webkit-app-region: no-drag;
+   }
+   ```
+
+## 最佳实践
+
+1. **性能考虑**
+   - 避免创建过多窗口
+   - 使用 `show: false` 创建窗口，在内容加载完成后再显示，避免白屏
+
+2. **安全性**
+   - 始终设置适当的 `webPreferences` 确保安全
+   ```typescript
+   webPreferences: {
+     preload: path.join(__dirname, '../preload/index.js'),
+     contextIsolation: true,
+     nodeIntegration: false,
+     sandbox: true,
+   }
+   ```
+
+3. **跨平台兼容性**
+   - 考虑不同操作系统的窗口行为差异
+   - 使用 `process.platform` 为不同平台提供特定实现
+
+4. **崩溃恢复**
+   - 监听 `webContents.on('crashed')` 事件处理崩溃
+   - 提供崩溃恢复选项
+
+5. **内存管理**
+   - 确保窗口关闭时清理所有相关资源
+   - 使用 `window.on('closed')` 而不是 `window.on('close')` 进行最终清理
+
+## 示例：创建设置窗口
+
+```typescript
+// apps/desktop/src/main/controllers/BrowserWindowsCtr.ts
+
+@ipcClientEvent('openSettings')
+handleOpenSettings() {
+  // 检查设置窗口是否已经存在
+  if (this.settingsWindow && !this.settingsWindow.isDestroyed()) {
+    // 如果窗口已存在，将其置于前台
+    this.settingsWindow.focus();
+    return { success: true };
+  }
+
+  // 创建新窗口
+  this.settingsWindow = new BrowserWindow({
+    width: 800,
+    height: 600,
+    title: 'Settings',
+    parent: this.mainWindow, // 设置父窗口，使其成为模态窗口
+    modal: true,
+    webPreferences: {
+      preload: path.join(__dirname, '../preload/index.js'),
+      contextIsolation: true,
+      nodeIntegration: false,
+    },
+  });
+
+  // 加载设置页面
+  if (isDev) {
+    this.settingsWindow.loadURL('http://localhost:3000/settings');
+  } else {
+    this.settingsWindow.loadFile(
+      path.join(__dirname, '../../renderer/index.html'),
+      { hash: 'settings' }
+    );
+  }
+
+  // 监听窗口关闭事件
+  this.settingsWindow.on('closed', () => {
+    this.settingsWindow = null;
+  });
+
+  return { success: true };
+}
+```
@@ -0,0 +1,202 @@
+---
+description: 
+globs: src/database/schemas/*
+alwaysApply: false
+---
+# Drizzle ORM Schema Style Guide for lobe-chat
+
+This document outlines the conventions and best practices for defining PostgreSQL Drizzle ORM schemas within the lobe-chat project.
+
+## Configuration
+
+- Drizzle configuration is managed in [drizzle.config.ts](mdc:drizzle.config.ts)
+- Schema files are located in the src/database/schemas/ directory
+- Migration files are output to `src/database/migrations/`
+- The project uses `postgresql` dialect with `strict: true`
+
+## Helper Functions
+
+Commonly used column definitions, especially for timestamps, are centralized in [src/database/schemas/_helpers.ts](mdc:src/database/schemas/_helpers.ts):
+- `timestamptz(name: string)`: Creates a timestamp column with timezone
+- `createdAt()`, `updatedAt()`, `accessedAt()`: Helper functions for standard timestamp columns
+- `timestamps`: An object `{ createdAt, updatedAt, accessedAt }` for easy inclusion in table definitions
+
+## Naming Conventions
+
+- **Table Names**: Use plural snake_case (e.g., `users`, `agents`, `session_groups`)
+- **Column Names**: Use snake_case (e.g., `user_id`, `created_at`, `background_color`)
+
+## Column Definitions
+
+### Primary Keys (PKs)
+- Typically `text('id')` (or `varchar('id')` for some OIDC tables)
+- Often use `.$defaultFn(() => idGenerator('table_name'))` for automatic ID generation with meaningful prefixes
+- **ID Prefix Purpose**: Makes it easy for users and developers to distinguish different entity types at a glance
+- For internal/system tables that users don't need to see, can use `uuid` or auto-increment keys
+- Composite PKs are defined using `primaryKey({ columns: [t.colA, t.colB] })`
+
+### Foreign Keys (FKs)
+- Defined using `.references(() => otherTable.id, { onDelete: 'cascade' | 'set null' | 'no action' })`
+- FK columns are usually named `related_table_singular_name_id` (e.g., `user_id` references `users.id`)
+- Most tables include a `user_id` column referencing `users.id` with `onDelete: 'cascade'`
+
+### Timestamps
+- Consistently use the `...timestamps` spread from [_helpers.ts](mdc:src/database/schemas/_helpers.ts) for `created_at`, `updated_at`, and `accessed_at` columns
+
+### Default Values
+- `.$defaultFn(() => expression)` for dynamic defaults (e.g., `idGenerator()`, `randomSlug()`)
+- `.default(staticValue)` for static defaults (e.g., `boolean('enabled').default(true)`)
+
+### Indexes
+- Defined in the table's second argument: `pgTable('name', {...columns}, (t) => ({ indexName: indexType().on(...) }))`
+- Use `uniqueIndex()` for unique constraints and `index()` for non-unique indexes
+- Naming pattern: `table_name_column(s)_idx` or `table_name_column(s)_unique`
+- Many tables feature a `clientId: text('client_id')` column, often part of a composite unique index with `user_id`
+
+### Data Types
+- Common types: `text`, `varchar`, `jsonb`, `boolean`, `integer`, `uuid`, `pgTable`
+- For `jsonb` fields, specify the TypeScript type using `.$type<MyType>()` for better type safety
+
+## Zod Schemas & Type Inference
+
+- Utilize `drizzle-zod` to generate Zod schemas for validation:
+  - `createInsertSchema(tableName)`
+  - `createSelectSchema(tableName)` (less common)
+- Export inferred types: `export type NewEntity = typeof tableName.$inferInsert;` and `export type EntityItem = typeof tableName.$inferSelect;`
+
+## Relations
+
+- Table relationships are defined centrally in [src/database/schemas/relations.ts](mdc:src/database/schemas/relations.ts) using the `relations()` utility from `drizzle-orm`
+
+## Code Style & Structure
+
+- **File Organization**: Each main database entity typically has its own schema file (e.g., [user.ts](mdc:src/database/schemas/user.ts), [agent.ts](mdc:src/database/schemas/agent.ts))
+- All schemas are re-exported from [src/database/schemas/index.ts](mdc:src/database/schemas/index.ts)
+- **ESLint**: Files often start with `/* eslint-disable sort-keys-fix/sort-keys-fix */`
+- **Comments**: Use JSDoc-style comments to explain the purpose of tables and complex columns, fields that are self-explanatory do not require jsdoc explanations, such as id, user_id, etc.
+
+## Example Pattern
+
+```typescript
+// From src/database/schemas/agent.ts
+export const agents = pgTable(
+  'agents',
+  {
+    id: text('id')
+      .primaryKey()
+      .$defaultFn(() => idGenerator('agents'))
+      .notNull(),
+    slug: varchar('slug', { length: 100 })
+      .$defaultFn(() => randomSlug(4))
+      .unique(),
+    userId: text('user_id')
+      .references(() => users.id, { onDelete: 'cascade' })
+      .notNull(),
+    clientId: text('client_id'),
+    chatConfig: jsonb('chat_config').$type<LobeAgentChatConfig>(),
+    ...timestamps,
+  },
+  // return array instead of object, the object style is deprecated
+  (t) => [
+    uniqueIndex('client_id_user_id_unique').on(t.clientId, t.userId),
+  ],
+);
+
+export const insertAgentSchema = createInsertSchema(agents);
+export type NewAgent = typeof agents.$inferInsert;
+export type AgentItem = typeof agents.$inferSelect;
+```
+
+## Common Patterns
+
+### 1. userId + clientId Pattern (Legacy)
+Some existing tables include both fields for different purposes:
+
+```typescript
+// Example from agents table (legacy pattern)
+userId: text('user_id')
+  .references(() => users.id, { onDelete: 'cascade' })
+  .notNull(),
+clientId: text('client_id'),
+
+// Usually with a composite unique index
+clientIdUnique: uniqueIndex('agents_client_id_user_id_unique').on(t.clientId, t.userId),
+```
+
+- **`userId`**: Server-side user association, ensures data belongs to specific user
+- **`clientId`**: Unique key for import/export operations, supports data migration between instances
+- **Current Status**: New tables should NOT include `clientId` unless specifically needed for import/export functionality
+- **Note**: This pattern is being phased out for new features to simplify the schema
+
+### 2. Junction Tables (Many-to-Many Relationships)
+Use composite primary keys for relationship tables:
+
+```typescript
+// Example: agents_knowledge_bases (from agent.ts)
+export const agentsKnowledgeBases = pgTable(
+  'agents_knowledge_bases',
+  {
+    agentId: text('agent_id').references(() => agents.id, { onDelete: 'cascade' }).notNull(),
+    knowledgeBaseId: text('knowledge_base_id').references(() => knowledgeBases.id, { onDelete: 'cascade' }).notNull(),
+    userId: text('user_id').references(() => users.id, { onDelete: 'cascade' }).notNull(),
+    enabled: boolean('enabled').default(true),
+    ...timestamps,
+  },
+  (t) => [
+    primaryKey({ columns: [t.agentId, t.knowledgeBaseId] }),
+  ],
+);
+```
+
+**Pattern**: `{entity1}Id` + `{entity2}Id` as composite PK, plus `userId` for ownership
+
+### 3. OIDC Tables Special Patterns
+OIDC tables use `varchar` IDs instead of `text` with custom generators:
+
+```typescript
+// Example from oidc.ts
+export const oidcAuthorizationCodes = pgTable('oidc_authorization_codes', {
+  id: varchar('id', { length: 255 }).primaryKey(), // varchar not text
+  data: jsonb('data').notNull(),
+  expiresAt: timestamptz('expires_at').notNull(),
+  // ... other fields
+});
+```
+
+**Reason**: OIDC standards expect specific ID formats and lengths
+
+### 4. File Processing with Async Tasks
+File-related tables reference async task IDs for background processing:
+
+```typescript
+// Example from files table
+export const files = pgTable('files', {
+  // ... other fields
+  chunkTaskId: uuid('chunk_task_id').references(() => asyncTasks.id, { onDelete: 'set null' }),
+  embeddingTaskId: uuid('embedding_task_id').references(() => asyncTasks.id, { onDelete: 'set null' }),
+  // ...
+});
+```
+
+**Purpose**: 
+- Track file chunking progress (breaking files into smaller pieces)
+- Track embedding generation progress (converting text to vectors)
+- Allow querying task status and handling failures
+
+### 5. Slug Pattern (Legacy)
+Some entities include auto-generated slugs - this is legacy code:
+
+```typescript
+slug: varchar('slug', { length: 100 })
+  .$defaultFn(() => randomSlug(4))
+  .unique(),
+
+// Often with composite unique constraint
+slugUserIdUnique: uniqueIndex('slug_user_id_unique').on(t.slug, t.userId),
+```
+
+**Current usage**: Only used to identify default agents/sessions (legacy pattern)
+**Future refactor**: Will likely be replaced with `isDefault: boolean()` field
+**Note**: Avoid using slugs for new features - prefer explicit boolean flags for status tracking
+
+By following these guidelines, maintain consistency, type safety, and maintainability across database schema definitions.
@@ -0,0 +1,35 @@
+---
+description: Explain how group chat works in LobeHub (Multi-agent orchestratoin)
+globs:
+alwaysApply: false
+---
+
+This rule explains how group chat (multi-agent orchestration) works. Not confused with session group, which is a organization method to manage session.
+
+## Key points
+
+- A supervisor will devide who and how will speak next
+- Each agent will speak just like in single chat (if was asked to speak)
+- Not coufused with session group
+
+## Related Files
+
+- src/store/chat/slices/message/supervisor.ts
+- src/store/chat/slices/aiChat/actions/generateAIGroupChat.ts
+- src/prompts/groupChat/index.ts (All prompts here)
+
+## Snippets
+
+```tsx
+// Detect whether in group chat
+const isGroupSession = useSessionStore(sessionSelectors.isCurrentSessionGroupSession);
+
+// Member actions
+const addAgentsToGroup = useChatGroupStore((s) => s.addAgentsToGroup);
+const removeAgentFromGroup = useChatGroupStore((s) => s.removeAgentFromGroup);
+const persistReorder = useChatGroupStore((s) => s.reorderGroupMembers);
+
+// Get group info
+const groupConfig = useChatGroupStore(chatGroupSelectors.currentGroupConfig);
+const currentGroupMemebers = useSessionStore(sessionSelectors.currentGroupAgents);
+```
@@ -0,0 +1,182 @@
+---
+globs: *.tsx
+alwaysApply: false
+---
+# LobeChat Internationalization Guide
+
+## Key Points
+
+- Default language: Chinese (zh-CN) as the source language
+- Supported languages: 18 languages including English, Japanese, Korean, Arabic, etc.
+- Framework: react-i18next with Next.js app router
+- Translation automation: @lobehub/i18n-cli for automatic translation, config file: .i18nrc.js
+- Never manually modify any json file. You can only modify files in `default` folder
+
+## Directory Structure
+
+```
+src/locales/
+├── default/           # Source language files (zh-CN)
+│   ├── index.ts      # Namespace exports
+│   ├── common.ts     # Common translations
+│   ├── chat.ts       # Chat-related translations
+│   ├── setting.ts    # Settings translations
+│   └── ...           # Other namespace files
+└── resources.ts      # Type definitions and language configuration
+
+locales/               # Translation files
+├── en-US/            # English translations
+│   ├── common.json   # Common translations
+│   ├── chat.json     # Chat translations
+│   ├── setting.json  # Settings translations
+│   └── ...           # Other namespace JSON files
+├── ja-JP/            # Japanese translations
+│   ├── common.json
+│   ├── chat.json
+│   └── ...
+└── ...               # Other language folders
+```
+
+## Workflow for Adding New Translations
+
+### 1. Adding New Translation Keys
+
+Step 1: Add translation keys in the corresponding namespace files under src/locales/default directory
+
+```typescript
+// Example: src/locales/default/common.ts
+export default {
+  // ... existing keys
+  newFeature: {
+    title: '新功能标题',
+    description: '功能描述文案',
+    button: '操作按钮',
+  },
+};
+```
+
+Step 2: If creating a new namespace, export it in src/locales/default/index.ts
+
+```typescript
+import newNamespace from './newNamespace';
+
+const resources = {
+  // ... existing namespaces
+  newNamespace,
+} as const;
+```
+
+### 2. Translation Process
+
+Development mode:
+
+Generally, you don't need to help me run the automatic translation tool as it takes a long time. I'll run it myself when needed. However, to see immediate results, you still need to translate `locales/zh-CN/namespace.json` first, no need to translate other languages.
+
+Production mode:
+
+```bash
+# Generate translations for all languages
+npm run i18n
+```
+
+## Usage in Components
+
+### Basic Usage
+
+```tsx
+import { useTranslation } from 'react-i18next';
+
+const MyComponent = () => {
+  const { t } = useTranslation('common');
+
+  return (
+    <div>
+      <h1>{t('newFeature.title')}</h1>
+      <p>{t('newFeature.description')}</p>
+      <button>{t('newFeature.button')}</button>
+    </div>
+  );
+};
+```
+
+### Usage with Parameters
+
+```tsx
+const { t } = useTranslation('common');
+
+<p>{t('welcome.message', { name: 'John' })}</p>;
+
+// Corresponding language file:
+// welcome: { message: 'Welcome {{name}}!' }
+```
+
+### Multiple Namespaces
+
+```tsx
+const { t } = useTranslation(['common', 'chat']);
+
+<button>{t('common:save')}</button>
+<span>{t('chat:typing')}</span>
+```
+
+## Type Safety
+
+The project uses TypeScript to implement type-safe translations, with types automatically generated from src/locales/resources.ts:
+
+```typescript
+import type { DefaultResources, Locales, NS } from '@/locales/resources';
+
+// Available types:
+// - NS: Available namespace keys ('common' | 'chat' | 'setting' | ...)
+// - Locales: Supported language codes ('en-US' | 'zh-CN' | 'ja-JP' | ...)
+
+const namespace: NS = 'common';
+const locale: Locales = 'en-US';
+```
+
+## Best Practices
+
+### 1. Namespace Organization
+
+- common: Shared UI elements (buttons, labels, actions)
+- chat: Chat-specific functionality
+- setting: Configuration and settings
+- error: Error messages and handling
+- [feature]: Feature-specific or page-specific namespaces
+- components: Reusable component text
+
+### 2. Key Naming Conventions
+
+```typescript
+// ✅ Good: Hierarchical structure
+export default {
+  modal: {
+    confirm: {
+      title: '确认操作',
+      message: '确定要执行此操作吗？',
+      actions: {
+        confirm: '确认',
+        cancel: '取消',
+      },
+    },
+  },
+};
+
+// ❌ Avoid: Flat structure
+export default {
+  modalConfirmTitle: '确认操作',
+  modalConfirmMessage: '确定要执行此操作吗？',
+};
+```
+
+## Troubleshooting
+
+### Missing Translation Keys
+
+- Check if the key exists in src/locales/default/namespace.ts
+- Ensure the namespace is correctly imported in the component
+- Ensure new namespaces are exported in src/locales/default/index.ts
+
+- 检查键是否存在于 src/locales/default/namespace.ts 中
+- 确保在组件中正确导入命名空间
+- 确保新命名空间已在 src/locales/default/index.ts 中导出
@@ -0,0 +1,119 @@
+---
+description: react flex layout package `react-layout-kit` usage
+globs: 
+alwaysApply: false
+---
+# React Layout Kit 使用指南
+
+react-layout-kit 是一个功能丰富的 React flex 布局组件库，在 lobe-chat 项目中被广泛使用。以下是重点组件的使用方法：
+
+## Flexbox 组件
+
+Flexbox 是最常用的布局组件，用于创建弹性布局，类似于 CSS 的 display: flex。
+
+### 基本用法
+
+```jsx
+import { Flexbox } from 'react-layout-kit';
+
+// 默认垂直布局
+<Flexbox>
+  <div>子元素1</div>
+  <div>子元素2</div>
+</Flexbox>
+
+// 水平布局
+<Flexbox horizontal>
+  <div>左侧元素</div>
+  <div>右侧元素</div>
+</Flexbox>
+```
+
+### 常用属性
+
+- horizontal: 布尔值，设置为水平方向布局
+- flex: 数值或字符串，控制 flex 属性
+- gap: 数值，设置子元素之间的间距
+- align: 对齐方式，如 'center', 'flex-start' 等
+- justify: 主轴对齐方式，如 'space-between', 'center' 等
+- padding: 内边距值
+- paddingInline: 水平内边距值
+- paddingBlock: 垂直内边距值
+- width/height: 设置宽高，通常用 '100%' 或具体像素值
+- style: 自定义样式对象
+
+### 实际应用示例
+
+```jsx
+// 经典三栏布局
+<Flexbox horizontal height={'100%'} width={'100%'}>
+  {/* 左侧边栏 */}
+  <Flexbox
+    width={260}
+    style={{
+      borderRight: `1px solid ${theme.colorBorderSecondary}`,
+      height: '100%',
+      overflowY: 'auto',
+    }}
+  >
+    <SidebarContent />
+  </Flexbox>
+  
+  {/* 中间内容区 */}
+  <Flexbox flex={1} style={{ height: '100%' }}>
+    {/* 主要内容 */}
+    <Flexbox flex={1} padding={24} style={{ overflowY: 'auto' }}>
+      <MainContent />
+    </Flexbox>
+    
+    {/* 底部区域 */}
+    <Flexbox
+      style={{
+        borderTop: `1px solid ${theme.colorBorderSecondary}`,
+        padding: '16px 24px',
+      }}
+    >
+      <Footer />
+    </Flexbox>
+  </Flexbox>
+</Flexbox>
+```
+
+## Center 组件
+
+Center 是对 Flexbox 的封装，使子元素水平和垂直居中。
+
+### 基本用法
+
+```jsx
+<Center width={'100%'} height={'100%'}>
+  <Content />
+</Center>
+```
+
+Center 组件继承了 Flexbox 的所有属性，同时默认设置了居中对齐。主要用于快速创建居中布局。
+
+### 实际应用示例
+
+```jsx
+// 登录页面居中布局
+<Flexbox height={'100%'} width={'100%'}>
+  <Center height={'100%'} width={'100%'}>
+    <LoginForm />
+  </Center>
+</Flexbox>
+
+// 图标居中显示
+<Center className={styles.icon} flex={'none'} height={40} width={40}>
+  <Icon icon={icon} size={24} />
+</Center>
+```
+
+## 最佳实践
+
+- 使用 flex={1} 让组件填充可用空间
+- 使用 gap 代替传统的 margin 设置元素间距
+- 嵌套 Flexbox 创建复杂布局
+- 设置 overflow: 'auto' 使内容可滚动
+- 使用 horizontal 创建水平布局，默认为垂直布局
+- 与 antd-style 的 useTheme hook 配合使用创建主题响应式的布局
@@ -0,0 +1,36 @@
+---
+alwaysApply: true
+---
+
+## Project Description
+
+You are developing an open-source, modern-design AI chat framework: lobehub(previous lobe-chat).
+
+Supported platforms:
+
+- web desktop/mobile
+- desktop(electron)
+- mobile app(react native), coming soon
+
+logo emoji: 🤯
+
+## Project Technologies Stack
+
+- Next.js 15
+- react 19
+- TypeScript
+- `@lobehub/ui`, antd for component framework
+- antd-style for css-in-js framework
+- lucide-react, `@ant-design/icons` for icons
+- react-layout-kit for flex layout component
+- react-i18next for i18n
+- zustand for state management
+- nuqs for search params management
+- SWR for data fetch
+- aHooks for react hooks library
+- dayjs for time library
+- lodash-es for utility library
+- TRPC for type safe backend
+- PGLite for client DB and Neon PostgreSQL for backend DB
+- Drizzle ORM
+- Vitest for testing
@@ -0,0 +1,122 @@
+---
+description: Project directory structure overview
+alwaysApply: false
+---
+
+# LobeChat Project Structure
+
+## Complete Project Structure
+
+This project uses common monorepo structure. The workspace packages name use `@lobechat/` namespace.
+
+**note**: some not very important files are not shown for simplicity.
+
+```plaintext
+lobe-chat/
+├── apps/
+│   └── desktop/
+├── docs/
+├── locales/
+│   ├── en-US/
+│   └── zh-CN/
+├── packages/
+│   ├── const/
+│   ├── context-engine/
+│   ├── database/
+│   │   ├── src/
+│   │   │   ├── models/
+│   │   │   ├── schemas/
+│   │   │   └── repositories/
+│   ├── model-bank/
+│   │   └── src/
+│   │       └── aiModels/
+│   ├── model-runtime/
+│   │   └── src/
+│   │       ├── core/
+│   │       └── providers/
+│   ├── types/
+│   │   └── src/
+│   │       ├── message/
+│   │       └── user/
+│   └── utils/
+├── public/
+├── scripts/
+├── src/
+│   ├── app/
+│   │   ├── (backend)/
+│   │   │   ├── api/
+│   │   │   │   ├── auth/
+│   │   │   │   └── webhooks/
+│   │   │   ├── middleware/
+│   │   │   ├── oidc/
+│   │   │   ├── trpc/
+│   │   │   └── webapi/
+│   │   │       ├── chat/
+│   │   │       └── tts/
+│   │   ├── [variants]/
+│   │   │   ├── (main)/
+│   │   │   │   ├── chat/
+│   │   │   │   └── settings/
+│   │   │   └── @modal/
+│   │   └── manifest.ts
+│   ├── components/
+│   ├── config/
+│   ├── features/
+│   │   └── ChatInput/
+│   ├── hooks/
+│   ├── layout/
+│   │   ├── AuthProvider/
+│   │   └── GlobalProvider/
+│   ├── libs/
+│   │   └── oidc-provider/
+│   ├── locales/
+│   │   └── default/
+│   ├── server/
+│   │   ├── modules/
+│   │   ├── routers/
+│   │   │   ├── async/
+│   │   │   ├── desktop/
+│   │   │   ├── edge/
+│   │   │   └── lambda/
+│   │   └── services/
+│   ├── services/
+│   │   ├── user/
+│   │   │   ├── client.ts
+│   │   │   └── server.ts
+│   │   └── message/
+│   ├── store/
+│   │   ├── agent/
+│   │   ├── chat/
+│   │   └── user/
+│   ├── styles/
+│   └── utils/
+└── package.json
+```
+
+## Architecture Map
+
+- UI Components: `src/components`, `src/features`
+- Global providers: `src/layout`
+- Zustand stores: `src/store`
+- Client Services: `src/services/` cross-platform services
+  - clientDB: `src/services/<domain>/client.ts`
+  - serverDB: `src/services/<domain>/server.ts`
+- API Routers:
+  - `src/app/(backend)/webapi` (REST)
+  - `src/server/routers/{edge|lambda|async|desktop|tools}` (tRPC)
+- Server:
+  - Services(can access serverDB): `src/server/services` server-used-only services
+  - Modules(can't access db): `src/server/modules` (Server only Third-party Service Module)
+- Database:
+  - Schema (Drizzle): `packages/database/src/schemas`
+  - Model (CRUD): `packages/database/src/models`
+  - Repository (bff-queries): `packages/database/src/repositories`
+- Third-party Integrations: `src/libs` — analytics, oidc etc.
+
+## Data Flow Architecture
+
+- **Web with ClientDB**: React UI → Client Service → Direct Model Access → PGLite (Web WASM)
+- **Web with ServerDB**: React UI → Client Service → tRPC Lambda → Server Services → PostgreSQL (Remote)
+- **Desktop**:
+  - Cloud sync disabled: Electron UI → Client Service → tRPC Lambda → Local Server Services → PGLite (Node WASM)
+  - Cloud sync enabled: Electron UI → Client Service → tRPC Lambda → Cloud Server Services → PostgreSQL (Remote)
@@ -0,0 +1,173 @@
+---
+description: 
+globs: *.tsx
+alwaysApply: false
+---
+
+# react component 编写指南
+
+- 如果要写复杂样式的话用 antd-style ，简单的话可以用 style 属性直接写内联样式
+- 如果需要 flex 布局或者居中布局应该使用 react-layout-kit 的 Flexbox 和 Center 组件
+- 选择组件时优先顺序应该是 src/components > 安装的组件 package > lobe-ui > antd
+- 使用 selector 访问 zustand store 的数据，而不是直接从 store 获取
+
+## antd-style token system
+
+### 访问 token system 的两种方式
+
+#### 使用 antd-style 的 useTheme hook
+
+```tsx
+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,
+      }}
+    >
+      使用主题 token 的组件
+    </div>
+  );
+};
+```
+
+#### 使用 antd-style 的 createStyles
+
+```tsx
+const useStyles = createStyles(({ css, token }) => {
+  return {
+    container: css`
+      background-color: ${token.colorBgContainer};
+      border-radius: ${token.borderRadius}px;
+      padding: ${token.padding}px;
+      color: ${token.colorText};
+    `,
+    title: css`
+      font-size: ${token.fontSizeLG}px;
+      font-weight: ${token.fontWeightStrong};
+      margin-bottom: ${token.marginSM}px;
+    `,
+    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>
+      <div className={styles.content}>{content}</div>
+    </Flexbox>
+  );
+};
+```
+
+### 一些你经常会忘记使用的 token
+
+请注意使用下面的 token 而不是 css 字面值。可以访问 https://ant.design/docs/react/customize-theme-cn 了解所有 token
+
+- 动画类
+  - token.motionDurationMid
+  - token.motionEaseInOut
+- 包围盒属性
+  - 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
+  - DownloadButton
+  - Icon
+- Data Display
+  - 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
+- Feedback
+  - Alert
+  - Drawer
+  - Modal
+- Layout
+  - DraggablePanel
+  - DraggablePanelBody
+  - DraggablePanelContainer
+  - DraggablePanelFooter
+  - DraggablePanelHeader
+  - Footer
+  - Grid
+  - Header
+  - Layout
+  - LayoutFooter
+  - LayoutHeader
+  - LayoutMain
+  - LayoutSidebar
+  - LayoutSidebarInner
+  - LayoutToc
+  - MaskShadow
+  - ScrollShadow
+- Navigation
+  - Burger
+  - Dropdown
+  - Menu
+  - SideNav
+  - Tabs
+  - Toc
+- Theme
+  - ConfigProvider
+  - FontLoader
+  - ThemeProvider
@@ -0,0 +1,43 @@
+---
+description:
+globs:
+alwaysApply: true
+---
+
+# Available project rules index
+
+All following rules are saved under `.cursor/rules/` directory:
+
+## Backend
+
+- `drizzle-schema-style-guide.mdc` – Style guide for defining Drizzle ORM schemas
+
+## Frontend
+
+- `react-component.mdc` – React component style guide and conventions
+- `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
+
+## Desktop (Electron)
+
+- `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
+
+## Debugging
+
+- `debug-usage.mdc` – Using the debug package and namespace conventions
+
+## Testing
+
+- `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
@@ -0,0 +1,455 @@
+---
+globs: src/database/**/*.test.ts
+alwaysApply: false
+---
+
+## 🗃️ 数据库 Model 测试指南
+
+测试 `packages/database` 下的数据库 Model 层。
+
+### 测试环境选择 💡
+
+数据库 Model 层通过环境变量控制数据库类型，在两种测试环境下有不同的数据库后端：客户端环境 (PGLite) 和 服务端环境 (PostgreSQL)
+
+### ⚠️ 双环境验证要求
+
+**对于所有 Model 测试，必须在两个环境下都验证通过**：
+
+#### 完整验证流程
+
+```bash
+# 1. 先在客户端环境测试（快速验证）
+cd packages/database && TEST_SERVER_DB=0 bunx vitest run --silent='passed-only' src/database/models/__tests__/myModel.test.ts
+
+# 2. 再在服务端环境测试（兼容性验证）, 需要设置环境变量 `TEST_SERVER_DB=1`
+cd packages/database && TEST_SERVER_DB=1 bunx vitest run --silent='passed-only' src/database/models/__tests__/myModel.test.ts #
+```
+
+### 创建新 Model 测试的最佳实践 📋
+
+#### 1. 参考现有实现和测试模板
+
+创建新 Model 测试前，**必须先参考现有的实现模式**：
+
+- **Model 实现参考**:
+- **测试模板参考**:
+- **复杂示例参考**:
+
+#### 2. 用户权限检查 - 安全第一 🔒
+
+这是**最关键的安全要求**。所有涉及用户数据的操作都必须包含用户权限检查：
+
+**❌ 错误示例 - 存在安全漏洞**:
+
+```typescript
+// 危险：缺少用户权限检查，任何用户都能操作任何数据
+update = async (id: string, data: Partial<MyModel>) => {
+  return this.db
+    .update(myTable)
+    .set(data)
+    .where(eq(myTable.id, id)) // ❌ 只检查 ID，没有检查 userId
+    .returning();
+};
+```
+
+**✅ 正确示例 - 安全的实现**:
+
+```typescript
+// 安全：必须同时匹配 ID 和 userId
+update = async (id: string, data: Partial<MyModel>) => {
+  return this.db
+    .update(myTable)
+    .set(data)
+    .where(
+      and(
+        eq(myTable.id, id),
+        eq(myTable.userId, this.userId), // ✅ 用户权限检查
+      ),
+    )
+    .returning();
+};
+```
+
+**必须进行用户权限检查的方法**：
+
+- `update()` - 更新操作
+- `delete()` - 删除操作
+- `findById()` - 查找特定记录
+- 任何涉及特定记录的查询或修改操作
+
+#### 3. 测试文件结构和必测场景
+
+**基本测试结构**:
+
+```typescript
+// @vitest-environment node
+describe('MyModel', () => {
+  describe('create', () => {
+    it('should create a new record');
+    it('should handle edge cases');
+  });
+
+  describe('queryAll', () => {
+    it('should return records for current user only');
+    it('should handle empty results');
+  });
+
+  describe('update', () => {
+    it('should update own records');
+    it('should NOT update other users records'); // 🔒 安全测试
+  });
+
+  describe('delete', () => {
+    it('should delete own records');
+    it('should NOT delete other users records'); // 🔒 安全测试
+  });
+
+  describe('user isolation', () => {
+    it('should enforce user data isolation'); // 🔒 核心安全测试
+  });
+});
+```
+
+**必须测试的安全场景** 🔒:
+
+```typescript
+it('should not update records of other users', async () => {
+  // 创建其他用户的记录
+  const [otherUserRecord] = await serverDB
+    .insert(myTable)
+    .values({ userId: 'other-user', data: 'original' })
+    .returning();
+
+  // 尝试更新其他用户的记录
+  const result = await myModel.update(otherUserRecord.id, { data: 'hacked' });
+
+  // 应该返回 undefined 或空数组（因为权限检查失败）
+  expect(result).toBeUndefined();
+
+  // 验证原始数据未被修改
+  const unchanged = await serverDB.query.myTable.findFirst({
+    where: eq(myTable.id, otherUserRecord.id),
+  });
+  expect(unchanged?.data).toBe('original'); // 数据应该保持不变
+});
+```
+
+#### 4. Mock 外部依赖服务
+
+如果 Model 依赖外部服务（如 FileService），需要正确 Mock：
+
+**设置 Mock**:
+
+```typescript
+// 在文件顶部设置 Mock
+const mockGetFullFileUrl = vi.fn();
+vi.mock('@/server/services/file', () => ({
+  FileService: vi.fn().mockImplementation(() => ({
+    getFullFileUrl: mockGetFullFileUrl,
+  })),
+}));
+
+// 在 beforeEach 中重置和配置 Mock
+beforeEach(async () => {
+  vi.clearAllMocks();
+  mockGetFullFileUrl.mockImplementation((url: string) => `https://example.com/${url}`);
+});
+```
+
+**验证 Mock 调用**:
+
+```typescript
+it('should process URLs through FileService', async () => {
+  // ... 测试逻辑
+
+  // 验证 Mock 被正确调用
+  expect(mockGetFullFileUrl).toHaveBeenCalledWith('expected-url');
+  expect(mockGetFullFileUrl).toHaveBeenCalledTimes(1);
+});
+```
+
+#### 5. 数据库状态管理
+
+**正确的数据清理模式**:
+
+```typescript
+const userId = 'test-user';
+const otherUserId = 'other-user';
+
+beforeEach(async () => {
+  // 清理用户表（级联删除相关数据）
+  await serverDB.delete(users);
+
+  // 创建测试用户
+  await serverDB.insert(users).values([{ id: userId }, { id: otherUserId }]);
+});
+
+afterEach(async () => {
+  // 清理测试数据
+  await serverDB.delete(users);
+});
+```
+
+#### 6. 测试数据类型和外键约束处理 ⚠️
+
+**必须使用 Schema 导出的类型**:
+
+```typescript
+// ✅ 正确：使用 schema 导出的类型
+import { NewGeneration, NewGenerationBatch } from '../../schemas';
+
+const testBatch: NewGenerationBatch = {
+  userId,
+  generationTopicId: 'test-topic-id',
+  provider: 'test-provider',
+  model: 'test-model',
+  prompt: 'Test prompt for image generation',
+  width: 1024,
+  height: 1024,
+  config: {
+    /* ... */
+  },
+};
+
+const testGeneration: NewGeneration = {
+  id: 'test-gen-id',
+  generationBatchId: 'test-batch-id',
+  asyncTaskId: null, // 处理外键约束
+  fileId: null, // 处理外键约束
+  seed: 12345,
+  userId,
+};
+```
+
+```typescript
+// ❌ 错误：没有类型声明或使用错误类型
+const testBatch = {
+  // 缺少类型声明
+  generationTopicId: 'test-topic-id',
+  // ...
+};
+
+const testGeneration = {
+  // 缺少类型声明
+  asyncTaskId: 'invalid-uuid', // 外键约束错误
+  fileId: 'non-existent-file', // 外键约束错误
+  // ...
+};
+```
+
+**外键约束处理策略**:
+
+1. **使用 null 值**: 对于可选的外键字段，使用 null 避免约束错误
+2. **创建关联记录**: 如果需要测试关联关系，先创建被引用的记录
+3. **理解约束关系**: 了解哪些字段有外键约束，避免引用不存在的记录
+
+```typescript
+// 外键约束处理示例
+beforeEach(async () => {
+  // 清理数据库
+  await serverDB.delete(users);
+
+  // 创建测试用户
+  await serverDB.insert(users).values([{ id: userId }]);
+
+  // 如果需要测试文件关联，创建文件记录
+  if (needsFileAssociation) {
+    await serverDB.insert(files).values({
+      id: 'test-file-id',
+      userId,
+      name: 'test.jpg',
+      url: 'test-url',
+      size: 1024,
+      fileType: 'image/jpeg',
+    });
+  }
+});
+```
+
+**排序测试的可预测性**:
+
+```typescript
+// ✅ 正确：使用明确的时间戳确保排序结果可预测
+it('should find batches by topic id in correct order', async () => {
+  const oldDate = new Date('2024-01-01T10:00:00Z');
+  const newDate = new Date('2024-01-02T10:00:00Z');
+
+  const batch1 = { ...testBatch, prompt: 'First batch', userId, createdAt: oldDate };
+  const batch2 = { ...testBatch, prompt: 'Second batch', userId, createdAt: newDate };
+
+  await serverDB.insert(generationBatches).values([batch1, batch2]);
+
+  const results = await generationBatchModel.findByTopicId(testTopic.id);
+
+  expect(results[0].prompt).toBe('Second batch'); // 最新优先 (desc order)
+  expect(results[1].prompt).toBe('First batch');
+});
+```
+
+```typescript
+// ❌ 错误：依赖数据库的默认时间戳，结果不可预测
+it('should find batches by topic id', async () => {
+  const batch1 = { ...testBatch, prompt: 'First batch', userId };
+  const batch2 = { ...testBatch, prompt: 'Second batch', userId };
+
+  await serverDB.insert(generationBatches).values([batch1, batch2]);
+
+  // 插入顺序和数据库时间戳可能不一致，导致测试不稳定
+  const results = await generationBatchModel.findByTopicId(testTopic.id);
+  expect(results[0].prompt).toBe('Second batch'); // 可能失败
+});
+```
+
+### 常见问题和解决方案 💡
+
+#### 问题 1：权限检查缺失导致安全漏洞
+
+**现象**: 测试失败，用户能修改其他用户的数据 **解决**: 在 Model 的 `update` 和 `delete` 方法中添加 `and(eq(table.id, id), eq(table.userId, this.userId))`
+
+#### 问题 2：Mock 未生效或验证失败
+
+**现象**: `undefined is not a spy` 错误 **解决**: 检查 Mock 设置位置和方式，确保在测试文件顶部设置，在 `beforeEach` 中重置
+
+#### 问题 3：测试数据污染
+
+**现象**: 测试间相互影响，结果不稳定 **解决**: 在 `beforeEach` 和 `afterEach` 中正确清理数据库状态
+
+#### 问题 4：外部依赖导致测试失败
+
+**现象**: 因为真实的外部服务调用导致测试不稳定 **解决**: Mock 所有外部依赖，使测试更可控和快速
+
+#### 问题 5：外键约束违反导致测试失败
+
+**现象**: `insert or update on table "xxx" violates foreign key constraint` **解决**:
+
+- 将可选外键字段设为 `null` 而不是无效的字符串值
+- 或者先创建被引用的记录，再创建当前记录
+
+```typescript
+// ❌ 错误：无效的外键值
+const testData = {
+    asyncTaskId: 'invalid-uuid',  // 表中不存在此记录
+    fileId: 'non-existent-file',  // 表中不存在此记录
+};
+
+// ✅ 正确：使用 null 值
+const testData = {
+    asyncTaskId: null,  // 避免外键约束
+    fileId: null,       // 避免外键约束
+};
+
+// ✅ 或者：先创建被引用的记录
+beforeEach(async () => {
+    const [asyncTask] = await serverDB.insert(asyncTasks).values({
+        id: 'valid-task-id',
+        status: 'pending',
+        type: 'generation',
+    }).returning();
+
+    const testData = {
+        asyncTaskId: asyncTask.id,  // 使用有效的外键值
+    };
+});
+```
+
+#### 问题 6：排序测试结果不一致
+
+**现象**: 相同的测试有时通过，有时失败，特别是涉及排序的测试 **解决**: 使用明确的时间戳，不要依赖数据库的默认时间戳
+
+```typescript
+// ❌ 错误：依赖插入顺序和默认时间戳
+await serverDB.insert(table).values([data1, data2]); // 时间戳不可预测
+
+// ✅ 正确：明确指定时间戳
+const oldDate = new Date('2024-01-01T10:00:00Z');
+const newDate = new Date('2024-01-02T10:00:00Z');
+await serverDB.insert(table).values([
+  { ...data1, createdAt: oldDate },
+  { ...data2, createdAt: newDate },
+]);
+```
+
+#### 问题 7：Mock 验证失败或调用次数不匹配
+
+**现象**: `expect(mockFunction).toHaveBeenCalledWith(...)` 失败 **解决**:
+
+- 检查 Mock 函数的实际调用参数和期望参数是否完全匹配
+- 确认 Mock 在正确的时机被重置和配置
+- 使用 `toHaveBeenCalledTimes()` 验证调用次数
+
+```typescript
+// 在 beforeEach 中正确配置 Mock
+beforeEach(() => {
+  vi.clearAllMocks(); // 重置所有 Mock
+
+  mockGetFullFileUrl.mockImplementation((url: string) => `https://example.com/${url}`);
+  mockTransformGeneration.mockResolvedValue({
+    id: 'test-id',
+    // ... 其他字段
+  });
+});
+
+// 测试中验证 Mock 调用
+it('should call FileService with correct parameters', async () => {
+  await model.someMethod();
+
+  // 验证调用参数
+  expect(mockGetFullFileUrl).toHaveBeenCalledWith('expected-url');
+  // 验证调用次数
+  expect(mockGetFullFileUrl).toHaveBeenCalledTimes(1);
+});
+```
+
+### Model 测试检查清单 ✅
+
+创建 Model 测试时，请确保以下各项都已完成：
+
+#### 🔧 基础配置
+
+- [ ] **双环境验证** - 在客户端环境 (vitest.config.ts) 和服务端环境 (vitest.config.server.ts) 下都测试通过
+- [ ] 参考了 `_template.ts` 和现有 Model 的实现模式
+- [ ] **使用正确的 Schema 类型** - 测试数据使用 `NewXxx` 类型声明，如 `NewGenerationBatch`、`NewGeneration`
+
+#### 🔒 安全测试
+
+- [ ] **所有涉及用户数据的操作都包含用户权限检查**
+- [ ] 包含了用户权限隔离的安全测试
+- [ ] 测试了用户无法访问其他用户数据的场景
+
+#### 🗃️ 数据处理
+
+- [ ] **正确处理外键约束** - 使用 `null` 值或先创建被引用记录
+- [ ] **排序测试使用明确时间戳** - 不依赖数据库默认时间，确保结果可预测
+- [ ] 在 `beforeEach` 和 `afterEach` 中正确管理数据库状态
+- [ ] 所有测试都能独立运行且互不干扰
+
+#### 🎭 Mock 和外部依赖
+
+- [ ] 正确 Mock 了外部依赖服务 (如 FileService、GenerationModel)
+- [ ] 在 `beforeEach` 中重置和配置 Mock
+- [ ] 验证了 Mock 服务的调用参数和次数
+- [ ] 测试了外部服务错误场景的处理
+
+#### 📋 测试覆盖
+
+- [ ] 测试覆盖了所有主要方法 (create, query, update, delete)
+- [ ] 测试了边界条件和错误场景
+- [ ] 包含了空结果处理的测试
+- [ ] **确认两个环境下的测试结果一致**
+
+#### 🚨 常见问题检查
+
+- [ ] 没有外键约束违反错误
+- [ ] 排序测试结果稳定可预测
+- [ ] Mock 验证无失败
+- [ ] 无测试数据污染问题
+
+### 安全警告 ⚠️
+
+**数据库 Model 层是安全的第一道防线**。如果 Model 层缺少用户权限检查：
+
+1. **任何用户都能访问和修改其他用户的数据**
+2. **即使上层有权限检查，也可能被绕过**
+3. **可能导致严重的数据泄露和安全事故**
+
+因此，**每个涉及用户数据的 Model 方法都必须包含用户权限检查，且必须有对应的安全测试来验证这些检查的有效性**。
@@ -0,0 +1,80 @@
+---
+description: Electron IPC 接口测试策略
+alwaysApply: false
+---
+
+### Electron IPC 接口测试策略 🖥️
+
+对于涉及 Electron IPC 接口的测试，由于提供真实的 Electron 环境比较复杂，采用 **Mock 返回值** 的方式进行测试。
+
+#### 基本 Mock 设置
+
+```typescript
+import { vi } from 'vitest';
+
+import { electronIpcClient } from '@/server/modules/ElectronIPCClient';
+
+// Mock Electron IPC 客户端
+vi.mock('@/server/modules/ElectronIPCClient', () => ({
+  electronIpcClient: {
+    getFilePathById: vi.fn(),
+    deleteFiles: vi.fn(),
+    // 根据需要添加其他 IPC 方法
+  },
+}));
+```
+
+#### 在测试中设置 Mock 行为
+
+```typescript
+beforeEach(() => {
+  // 重置所有 Mock
+  vi.resetAllMocks();
+
+  // 设置默认的 Mock 返回值
+  vi.mocked(electronIpcClient.getFilePathById).mockResolvedValue('/path/to/file.txt');
+  vi.mocked(electronIpcClient.deleteFiles).mockResolvedValue({
+    success: true,
+  });
+});
+```
+
+#### 测试不同场景的示例
+
+```typescript
+it('应该处理文件删除成功的情况', async () => {
+  // 设置成功场景的 Mock
+  vi.mocked(electronIpcClient.deleteFiles).mockResolvedValue({
+    success: true,
+  });
+
+  const result = await service.deleteFiles(['desktop://file1.txt']);
+
+  expect(electronIpcClient.deleteFiles).toHaveBeenCalledWith(['desktop://file1.txt']);
+  expect(result.success).toBe(true);
+});
+
+it('应该处理文件删除失败的情况', async () => {
+  // 设置失败场景的 Mock
+  vi.mocked(electronIpcClient.deleteFiles).mockRejectedValue(new Error('删除失败'));
+
+  const result = await service.deleteFiles(['desktop://file1.txt']);
+
+  expect(result.success).toBe(false);
+  expect(result.errors).toBeDefined();
+});
+```
+
+#### Mock 策略的优势
+
+1. **环境简化**: 避免了复杂的 Electron 环境搭建
+2. **测试可控**: 可以精确控制 IPC 调用的返回值和行为
+3. **场景覆盖**: 容易测试各种成功/失败场景
+4. **执行速度**: Mock 调用比真实 IPC 调用更快
+
+#### 注意事项
+
+- **Mock 准确性**: 确保 Mock 的行为与真实 IPC 接口行为一致
+- **类型安全**: 使用 `vi.mocked()` 确保类型安全
+- **Mock 重置**: 在 `beforeEach` 中重置 Mock 状态，避免测试间干扰
+- **调用验证**: 不仅要验证返回值，还要验证 IPC 方法是否被正确调用
@@ -0,0 +1,510 @@
+---
+globs: *.test.ts,*.test.tsx
+alwaysApply: false
+---
+
+# 测试指南 - LobeChat Testing Guide
+
+## 测试环境概览
+
+LobeChat 项目使用 Vitest 测试库，配置了两种不同的测试环境：
+
+### 客户端数据库测试环境 (DOM Environment)
+
+- **配置文件**: [vitest.config.ts](mdc:vitest.config.ts)
+- **环境**: Happy DOM (浏览器环境模拟)
+- **数据库**: PGLite (浏览器环境的 PostgreSQL)
+- **用途**: 测试前端组件、客户端逻辑、React 组件等
+- **设置文件**: [tests/setup.ts](mdc:tests/setup.ts)
+
+### 服务端数据库测试环境 (Node Environment)
+
+目前只有 `packages/database` 下的测试可以通过配置 `TEST_SERVER_DB=1` 环境变量来使用服务端数据库测试
+
+- **配置文件**: [packages/database/vitest.config.mts](mdc:packages/database/vitest.config.mts) 并且设置环境变量 `TEST_SERVER_DB=1`
+- **环境**: Node.js
+- **数据库**: 真实的 PostgreSQL 数据库
+- **并发限制**: 单线程运行 (`singleFork: true`)
+- **用途**: 测试数据库模型、服务端逻辑、API 端点等
+- **设置文件**: [packages/database/tests/setup-db.ts](mdc:packages/database/tests/setup-db.ts)
+
+## 测试运行命令
+
+** 性能警告**: 项目包含 3000+ 测试用例，完整运行需要约 10 分钟。务必使用文件过滤或测试名称过滤。
+
+### 正确的命令格式
+
+```bash
+# 运行所有客户端/服务端测试
+bunx vitest run --silent='passed-only'                                          # 客户端测试
+cd packages/database && TEST_SERVER_DB=1 bunx vitest run --silent='passed-only' # 服务端测试
+
+# 运行特定测试文件 (支持模糊匹配)
+bunx vitest run --silent='passed-only' user.test.ts
+
+# 运行特定测试用例名称 (使用 -t 参数)
+bunx vitest run --silent='passed-only' -t "test case name"
+
+# 组合使用文件和测试名称过滤
+bunx vitest run --silent='passed-only' filename.test.ts -t "specific test"
+
+# 生成覆盖率报告 (使用 --coverage 参数)
+bunx vitest run --silent='passed-only' --coverage
+```
+
+### 避免的命令格式
+
+```bash
+#  这些命令会运行所有 3000+ 测试用例，耗时约 10 分钟！
+npm test
+npm test some-file.test.ts
+
+#  不要使用裸 vitest (会进入 watch 模式)
+vitest test-file.test.ts
+```
+
+## 测试修复原则
+
+### 核心原则
+
+1. **收集足够的上下文**  
+   在修复测试之前，务必做到：
+   - 完整理解测试的意图和实现
+   - 强烈建议阅读当前的 git diff 和 PR diff
+
+2. **测试优先修复**  
+   如果是测试本身写错了，应优先修改测试，而不是实现代码。
+
+3. **专注单一问题**  
+   只修复指定的测试，不要顺带添加额外测试。
+
+4. **不自作主张**  
+   发现其他问题时，不要直接修改，需先提出并讨论。
+
+### 测试协作最佳实践
+
+基于实际开发经验总结的重要协作原则：
+
+#### 1. 失败处理策略
+
+**核心原则**: 避免盲目重试，快速识别问题并寻求帮助。
+
+- **失败阈值**: 当连续尝试修复测试 1-2 次都失败后，应立即停止继续尝试
+- **问题总结**: 分析失败原因，整理已尝试的解决方案及其失败原因
+- **寻求帮助**: 带着清晰的问题摘要和尝试记录向团队寻求帮助
+- **避免陷阱**: 不要陷入"不断尝试相同或类似方法"的循环
+
+```typescript
+//  错误做法：连续失败后继续盲目尝试
+// 第3次、第4次仍在用相似的方法修复同一个问题
+
+//  正确做法：失败1-2次后总结问题
+/*
+问题总结：
+1. 尝试过的方法：修改 mock 数据结构
+2. 失败原因：仍然提示类型不匹配
+3. 具体错误：Expected 'UserData' but received 'UserProfile'
+4. 需要帮助：不确定最新的 UserData 接口定义
+*/
+```
+
+#### 2. 测试用例命名规范
+
+**核心原则**: 测试应该关注"行为"，而不是"实现细节"。
+
+- **描述业务场景**: `describe` 和 `it` 的标题应该描述具体的业务场景和预期行为
+- **避免实现绑定**: 不要在测试名称中提及具体的代码行号、覆盖率目标或实现细节
+- **保持稳定性**: 测试名称应该在代码重构后仍然有意义
+
+```typescript
+//  错误的测试命名
+describe('User component coverage', () => {
+  it('covers line 45-50 in getUserData', () => {
+    // 为了覆盖第45-50行而写的测试
+  });
+
+  it('tests the else branch', () => {
+    // 仅为了测试某个分支而存在
+  });
+});
+
+//  正确的测试命名
+describe('<UserAvatar />', () => {
+  it('should render fallback icon when image url is not provided', () => {
+    // 测试具体的业务场景，自然会覆盖相关代码分支
+  });
+
+  it('should display user initials when avatar image fails to load', () => {
+    // 描述用户行为和预期结果
+  });
+});
+```
+
+**覆盖率提升的正确思路**:
+
+- 通过设计各种业务场景（正常流程、边缘情况、错误处理）来自然提升覆盖率
+- 不要为了达到覆盖率数字而写测试，更不要在测试中注释"为了覆盖 xxx 行"
+
+#### 3. 测试组织结构
+
+**核心原则**: 维护清晰的测试层次结构，避免冗余的顶级测试块。
+
+- **复用现有结构**: 添加新测试时，优先在现有的 `describe` 块中寻找合适的位置
+- **逻辑分组**: 相关的测试用例应该组织在同一个 `describe` 块内
+- **避免碎片化**: 不要为了单个测试用例就创建新的顶级 `describe` 块
+
+```typescript
+//  错误的组织方式：创建过多顶级块
+describe('<UserProfile />', () => {
+  it('should render user name', () => {});
+});
+
+describe('UserProfile new prop test', () => {
+  // 不必要的新块
+  it('should handle email display', () => {});
+});
+
+describe('UserProfile edge cases', () => {
+  // 不必要的新块
+  it('should handle missing avatar', () => {});
+});
+
+//  正确的组织方式：合并相关测试
+describe('<UserProfile />', () => {
+  it('should render user name', () => {});
+
+  it('should handle email display', () => {});
+
+  it('should handle missing avatar', () => {});
+
+  describe('when user data is incomplete', () => {
+    // 只有在有多个相关子场景时才创建子组
+    it('should show placeholder for missing name', () => {});
+    it('should hide email section when email is undefined', () => {});
+  });
+});
+```
+
+**组织决策流程**:
+
+1. 是否存在逻辑相关的现有 `describe` 块？ → 如果有，添加到其中
+2. 是否有多个（3个以上）相关的测试用例？ → 如果有，可以考虑创建新的子 `describe`
+3. 是否是独立的、无关联的功能模块？ → 如果是，才考虑创建新的顶级 `describe`
+
+### 测试修复流程
+
+1. **复现问题**: 定位并运行失败的测试，确认能在本地复现
+2. **分析原因**: 阅读测试代码、错误日志和相关文件的 Git 修改历史
+3. **建立假设**: 判断问题出在测试逻辑、实现代码还是环境配置
+4. **修复验证**: 根据假设进行修复，重新运行测试确认通过
+5. **扩大验证**: 运行当前文件内所有测试，确保没有引入新问题
+6. **撰写总结**: 说明错误原因和修复方法
+
+### 修复完成后的总结
+
+测试修复完成后，应该提供简要说明，包括：
+
+1. **错误原因分析**: 说明测试失败的根本原因
+   - 测试逻辑错误
+   - 实现代码bug
+   - 环境配置问题
+   - 依赖变更导致的问题
+
+2. **修复方法说明**: 简述采用的修复方式
+   - 修改了哪些文件
+   - 采用了什么解决方案
+   - 为什么选择这种修复方式
+
+**示例格式**:
+
+```markdown
+## 测试修复总结
+
+**错误原因**: 测试中的 mock 数据格式与实际 API 返回格式不匹配，导致断言失败。
+
+**修复方法**: 更新了测试文件中的 mock 数据结构，使其与最新的 API 响应格式保持一致。具体修改了 `user.test.ts` 中的 `mockUserData` 对象结构。
+```
+
+## 测试编写最佳实践
+
+### Mock 数据策略：追求"低成本的真实性"
+
+**核心原则**: 测试数据应默认追求真实性，只有在引入"高昂的测试成本"时才进行简化。
+
+#### 什么是"高昂的测试成本"？
+
+"高成本"指的是测试中引入了外部依赖，使测试变慢、不稳定或复杂：
+
+- **文件 I/O 操作**：读写硬盘文件
+- **网络请求**：HTTP 调用、数据库连接
+- **系统调用**：获取系统时间、环境变量等
+
+#### 推荐做法：Mock 依赖，保留真实数据
+
+```typescript
+//  好的做法：Mock I/O 操作，但使用真实的文件内容格式
+describe('parseContentType', () => {
+  beforeEach(() => {
+    // Mock 文件读取操作（避免真实 I/O）
+    vi.spyOn(fs, 'readFileSync').mockImplementation((path) => {
+      // 但返回真实的文件内容格式
+      if (path.includes('.pdf')) return '%PDF-1.4\n%âãÏÓ'; // 真实 PDF 文件头
+      if (path.includes('.png')) return '\x89PNG\r\n\x1a\n'; // 真实 PNG 文件头
+      return '';
+    });
+  });
+
+  it('should detect PDF content type correctly', () => {
+    const result = parseContentType('/path/to/file.pdf');
+    expect(result).toBe('application/pdf');
+  });
+});
+
+//  过度简化：使用不真实的数据
+describe('parseContentType', () => {
+  it('should detect PDF content type correctly', () => {
+    // 这种简化数据没有测试价值
+    const result = parseContentType('fake-pdf-content');
+    expect(result).toBe('application/pdf');
+  });
+});
+```
+
+#### 真实标识符的价值
+
+```typescript
+// ✅ 使用真实标识符
+const result = parseModelString('openai', '+gpt-4,+gpt-3.5-turbo');
+
+// ❌ 使用占位符（价值较低）
+const result = parseModelString('test-provider', '+model1,+model2');
+```
+
+### 现代化Mock技巧：环境设置与Mock方法
+
+**环境设置 + Mock方法结合使用**
+
+客户端代码测试时，推荐使用环境注释配合现代化Mock方法：
+
+```typescript
+/**
+ * @vitest-environment happy-dom  // 提供浏览器API
+ */
+import { beforeEach, vi } from 'vitest';
+
+beforeEach(() => {
+  // 现代方法1：使用vi.stubGlobal替代global.xxx = ...
+  const mockImage = vi.fn().mockImplementation(() => ({
+    addEventListener: vi.fn(),
+    naturalHeight: 600,
+    naturalWidth: 800,
+  }));
+  vi.stubGlobal('Image', mockImage);
+
+  // 现代方法2：使用vi.spyOn保留原功能，只mock特定方法
+  vi.spyOn(URL, 'createObjectURL').mockReturnValue('blob:mock-url');
+  vi.spyOn(URL, 'revokeObjectURL').mockImplementation(() => {});
+});
+```
+
+**环境选择优先级**
+
+1. **@vitest-environment happy-dom** (推荐) - 轻量、快速，项目已安装
+2. **@vitest-environment jsdom** - 功能完整，但需要额外安装jsdom包
+3. **不设置环境** - Node.js环境，需要手动mock所有浏览器API
+
+**Mock方法对比**
+
+```typescript
+// ❌ 旧方法：直接操作global对象（类型问题）
+global.Image = mockImage;
+global.URL = { ...global.URL, createObjectURL: mockFn };
+
+// ✅ 现代方法：类型安全的vi API
+vi.stubGlobal('Image', mockImage); // 完全替换全局对象
+vi.spyOn(URL, 'createObjectURL'); // 部分mock，保留其他功能
+```
+
+### 测试覆盖率原则：代码分支优于用例数量
+
+**核心原则**: 优先覆盖所有代码分支，而非编写大量重复用例
+
+```typescript
+// ❌ 过度测试：29个测试用例都验证相同分支
+describe('getImageDimensions', () => {
+  it('should reject .txt files');
+  it('should reject .pdf files');
+  // ... 25个类似测试，都走相同的验证分支
+});
+
+// ✅ 精简测试：4个核心用例覆盖所有分支
+describe('getImageDimensions', () => {
+  it('should return dimensions for valid File object'); // 成功路径 - File
+  it('should return dimensions for valid data URI'); // 成功路径 - String
+  it('should return undefined for invalid inputs'); // 输入验证分支
+  it('should return undefined when image fails to load'); // 错误处理分支
+});
+```
+
+**分支覆盖策略**
+
+1. **成功路径** - 每种输入类型1个测试即可
+2. **边界条件** - 合并类似场景到单个测试
+3. **错误处理** - 测试代表性错误即可
+4. **业务逻辑** - 覆盖所有if/else分支
+
+**合理测试数量**
+
+- 简单工具函数：2-5个测试
+- 复杂业务逻辑：5-10个测试
+- 核心安全功能：适当增加，但避免重复路径
+
+### 错误处理测试：测试"行为"而非"文本"
+
+**核心原则**: 测试应该验证程序在错误发生时的行为是可预测的，而不是验证易变的错误信息文本。
+
+#### 推荐的错误测试方式
+
+```typescript
+// ✅ 测试错误类型和属性
+expect(() => validateUser({})).toThrow(ValidationError);
+expect(() => processPayment({})).toThrow(
+  expect.objectContaining({
+    code: 'INVALID_PAYMENT_DATA',
+    statusCode: 400,
+  }),
+);
+
+// ❌ 避免测试具体错误文本
+expect(() => processUser({})).toThrow('用户数据不能为空，请检查输入参数');
+```
+
+### 疑难解答：警惕模块污染
+
+**识别信号**: 当你的测试出现以下"灵异"现象时，优先怀疑模块污染：
+
+- 单独运行某个测试通过，但和其他测试一起运行就失败
+- 测试的执行顺序影响结果
+- Mock 设置看起来正确，但实际使用的是旧的 Mock 版本
+
+#### 典型场景：动态 Mock 同一模块
+
+```typescript
+// ❌ 问题：动态Mock同一模块
+it('dev mode', async () => {
+  vi.doMock('./config', () => ({ isDev: true }));
+  const { getSettings } = await import('./service'); // 可能使用缓存
+});
+
+// ✅ 解决：清除模块缓存
+beforeEach(() => {
+  vi.resetModules(); // 确保每个测试都是干净环境
+});
+```
+
+**记住**: `vi.resetModules()` 是解决测试"灵异"失败的终极武器。
+
+## 测试文件组织
+
+### 文件命名约定
+
+`*.test.ts`, `*.test.tsx` (任意位置)
+
+### 测试文件组织风格
+
+项目采用 **测试文件与源文件同目录** 的组织风格：
+
+- 测试文件放在对应源文件的同一目录下
+- 命名格式：`原文件名.test.ts` 或 `原文件名.test.tsx`
+
+例如：
+
+```plaintext
+src/components/Button/
+├── index.tsx           # 源文件
+└── index.test.tsx      # 测试文件
+```
+
+- 也有少数情况会统一放到 `__tests__` 文件夹， 例如 `packages/database/src/models/__tests__`
+- 测试使用的辅助文件放到 fixtures 文件夹
+
+## 测试调试技巧
+
+### 测试调试步骤
+
+1. **确定测试环境**: 根据文件路径选择正确的配置文件
+2. **隔离问题**: 使用 `-t` 参数只运行失败的测试用例
+3. **分析错误**: 仔细阅读错误信息、堆栈跟踪和最近的文件修改记录
+4. **添加调试**: 在测试中添加 `console.log` 了解执行流程
+
+### TypeScript 类型处理
+
+在测试中，为了提高编写效率和可读性，可以适当放宽 TypeScript 类型检测：
+
+#### 推荐的类型放宽策略
+
+```typescript
+//  使用非空断言访问测试中确定存在的属性
+const result = await someFunction();
+expect(result!.data).toBeDefined();
+expect(result!.status).toBe('success');
+
+//  使用 any 类型简化复杂的 Mock 设置
+const mockStream = new ReadableStream() as any;
+mockStream.toReadableStream = () => mockStream;
+
+//  访问私有成员
+await instance['getFromCache']('key'); // 推荐中括号
+await (instance as any).getFromCache('key'); // 避免as any
+```
+
+#### 适用场景
+
+- **Mock 对象**: 对于测试用的 Mock 数据，使用 `as any` 避免复杂的类型定义
+- **第三方库**: 处理复杂的第三方库类型时，适当使用 `any` 提高效率
+- **测试断言**: 在确定对象存在的测试场景中，使用 `!` 非空断言
+- **私有成员访问**: 优先使用中括号 `instance['privateMethod']()` 而不是 `(instance as any).privateMethod()`
+- **临时调试**: 快速编写测试时，先用 `any` 保证功能，后续可选择性地优化类型
+
+#### 注意事项
+
+- **适度使用**: 不要过度依赖 `any`，核心业务逻辑的类型仍应保持严格
+- **私有成员访问优先级**: 中括号访问 > `as any` 转换，保持更好的类型安全性
+- **文档说明**: 对于使用 `any` 的复杂场景，添加注释说明原因
+- **测试覆盖**: 确保即使使用了 `any`，测试仍能有效验证功能正确性
+
+### 检查最近修改记录
+
+**核心原则**：测试突然失败时，优先检查最近的代码修改。
+
+#### 快速检查方法
+
+```bash
+git status                  # 查看当前修改状态
+git diff HEAD -- '*.test.*' # 检查测试文件改动
+git diff main...HEAD        # 对比主分支差异
+gh pr diff                  # 查看PR中的所有改动
+```
+
+#### 常见原因与解决
+
+- **最新提交引入bug** → 检查并修复实现代码
+- **分支代码滞后** → `git rebase main` 同步主分支
+
+## 特殊场景的测试
+
+针对一些特殊场景的测试，需要阅读相关 rules：
+
+- [Electron IPC 接口测试策略](mdc:./electron-ipc-test.mdc)
+- [数据库 Model 测试指南](mdc:./db-model-test.mdc)
+
+## 核心要点
+
+- **命令格式**: 使用 `bunx vitest run --silent='passed-only'` 并指定文件过滤
+- **修复原则**: 失败1-2次后寻求帮助，测试命名关注行为而非实现细节
+- **调试流程**: 复现 → 分析 → 假设 → 修复 → 验证 → 总结
+- **文件组织**: 优先在现有 `describe` 块中添加测试，避免创建冗余顶级块
+- **数据策略**: 默认追求真实性，只有高成本（I/O、网络等）时才简化
+- **错误测试**: 测试错误类型和行为，避免依赖具体的错误信息文本
+- **模块污染**: 测试"灵异"失败时，优先怀疑模块污染，使用 `vi.resetModules()` 解决
+- **安全要求**: Model 测试必须包含权限检查，并在双环境下验证通过
@@ -0,0 +1,579 @@
+---
+description: Best practices for testing Zustand store actions
+globs: "src/store/**/*.test.ts"
+alwaysApply: false
+---
+
+# Zustand Store Action Testing Guide
+
+This guide provides best practices for testing Zustand store actions, based on our proven testing patterns.
+
+## Basic Test Structure
+
+```typescript
+import { act, renderHook } from '@testing-library/react';
+import { afterEach, beforeEach, describe, expect, it, vi } from 'vitest';
+
+import { messageService } from '@/services/message';
+import { useChatStore } from '../../store';
+
+// Keep zustand mock as it's needed globally
+vi.mock('zustand/traditional');
+
+beforeEach(() => {
+  // Reset store state
+  vi.clearAllMocks();
+  useChatStore.setState(
+    {
+      activeId: 'test-session-id',
+      messagesMap: {},
+      loadingIds: [],
+    },
+    false,
+  );
+
+  // ✅ Setup only spies that MOST tests need
+  vi.spyOn(messageService, 'createMessage').mockResolvedValue('new-message-id');
+  // ❌ Don't setup spies that only few tests need - spy only when needed
+
+  // Setup common mock methods
+  act(() => {
+    useChatStore.setState({
+      refreshMessages: vi.fn(),
+      internal_coreProcessMessage: vi.fn(),
+    });
+  });
+});
+
+afterEach(() => {
+  vi.restoreAllMocks();
+});
+
+describe('action name', () => {
+  describe('validation', () => {
+    // Validation tests
+  });
+
+  describe('normal flow', () => {
+    // Happy path tests
+  });
+
+  describe('error handling', () => {
+    // Error case tests
+  });
+});
+```
+
+## Testing Best Practices
+
+### 1. Test Layering - Spy Direct Dependencies Only
+
+✅ **Good**: Spy on the direct dependency
+
+```typescript
+// When testing internal_coreProcessMessage, spy its direct dependency
+const fetchAIChatSpy = vi
+  .spyOn(result.current, 'internal_fetchAIChatMessage')
+  .mockResolvedValue({ isFunctionCall: false, content: 'AI response' });
+```
+
+❌ **Bad**: Spy on lower-level implementation details
+
+```typescript
+// Don't spy on services that internal_fetchAIChatMessage uses
+const streamSpy = vi
+  .spyOn(chatService, 'createAssistantMessageStream')
+  .mockImplementation(...);
+```
+
+**Why**: Each test should only mock its direct dependencies, not the entire call chain. This makes tests more maintainable and less brittle.
+
+### 2. Mock Management - Minimize Global Spies
+
+✅ **Good**: Spy only when needed
+
+```typescript
+beforeEach(() => {
+  // ✅ Only spy services that most tests need
+  vi.spyOn(messageService, 'createMessage').mockResolvedValue('new-message-id');
+  // ✅ Don't spy chatService globally
+});
+
+it('should process message', async () => {
+  // ✅ Spy chatService only in tests that need it
+  const streamSpy = vi.spyOn(chatService, 'createAssistantMessageStream')
+    .mockImplementation(...);
+
+  // test logic
+
+  streamSpy.mockRestore();
+});
+```
+
+❌ **Bad**: Setup all spies globally
+
+```typescript
+beforeEach(() => {
+  vi.spyOn(messageService, 'createMessage').mockResolvedValue('id');
+  vi.spyOn(chatService, 'createAssistantMessageStream').mockResolvedValue({}); // ❌ Not all tests need this
+  vi.spyOn(fileService, 'uploadFile').mockResolvedValue({}); // ❌ Creates implicit coupling
+});
+```
+
+### 3. Service Mocking - Mock the Correct Layer
+
+✅ **Good**: Mock the service method
+
+```typescript
+it('should fetch AI chat response', async () => {
+  const streamSpy = vi
+    .spyOn(chatService, 'createAssistantMessageStream')
+    .mockImplementation(async ({ onMessageHandle, onFinish }) => {
+      await onMessageHandle?.({ type: 'text', text: 'Hello' } as any);
+      await onFinish?.('Hello', {});
+    });
+
+  // test logic
+});
+```
+
+❌ **Bad**: Mock global fetch
+
+```typescript
+it('should fetch AI chat response', async () => {
+  global.fetch = vi.fn().mockResolvedValue(...); // ❌ Too low level
+});
+```
+
+### 4. Test Organization - Use Descriptive Nesting
+
+✅ **Good**: Clear nested structure
+
+```typescript
+describe('sendMessage', () => {
+  describe('validation', () => {
+    it('should not send when session is inactive', async () => {});
+    it('should not send when message is empty', async () => {});
+  });
+
+  describe('message creation', () => {
+    it('should create user message and trigger AI processing', async () => {});
+    it('should send message with files attached', async () => {});
+  });
+
+  describe('error handling', () => {
+    it('should handle message creation errors gracefully', async () => {});
+  });
+});
+```
+
+❌ **Bad**: Flat structure
+
+```typescript
+describe('sendMessage', () => {
+  it('test 1', async () => {});
+  it('test 2', async () => {});
+  it('test 3', async () => {});
+});
+```
+
+### 5. Testing Async Actions
+
+Always wrap async operations in `act()`:
+
+```typescript
+it('should send message', async () => {
+  const { result } = renderHook(() => useChatStore());
+
+  await act(async () => {
+    await result.current.sendMessage({ message: 'Hello' });
+  });
+
+  expect(messageService.createMessage).toHaveBeenCalled();
+});
+```
+
+### 6. State Setup - Use act() for setState
+
+```typescript
+it('should handle disabled state', async () => {
+  act(() => {
+    useChatStore.setState({ activeId: undefined });
+  });
+
+  const { result } = renderHook(() => useChatStore());
+  // test logic
+});
+```
+
+### 7. Testing Complex Flows
+
+For complex flows with multiple steps, use clear spy setup:
+
+```typescript
+it('should handle topic creation flow', async () => {
+  // Setup store state
+  act(() => {
+    useChatStore.setState({
+      activeTopicId: undefined,
+      messagesMap: {
+        'test-session-id': [
+          { id: 'msg-1', role: 'user', content: 'Message 1' },
+          { id: 'msg-2', role: 'assistant', content: 'Response 1' },
+          { id: 'msg-3', role: 'user', content: 'Message 2' },
+        ],
+      },
+    });
+  });
+
+  const { result } = renderHook(() => useChatStore());
+
+  // Spy on action dependencies
+  const createTopicSpy = vi.spyOn(result.current, 'createTopic')
+    .mockResolvedValue('new-topic-id');
+  const toggleLoadingSpy = vi.spyOn(result.current, 'internal_toggleMessageLoading');
+
+  // Execute
+  await act(async () => {
+    await result.current.sendMessage({ message: 'Test message' });
+  });
+
+  // Assert
+  expect(createTopicSpy).toHaveBeenCalled();
+  expect(toggleLoadingSpy).toHaveBeenCalledWith(true, expect.any(String));
+});
+```
+
+### 8. Streaming Response Mocking
+
+When testing streaming responses, simulate the flow properly:
+
+```typescript
+it('should handle streaming chunks', async () => {
+  const { result } = renderHook(() => useChatStore());
+  const messages = [
+    { id: 'msg-1', role: 'user', content: 'Hello', sessionId: 'test-session' },
+  ];
+
+  const streamSpy = vi
+    .spyOn(chatService, 'createAssistantMessageStream')
+    .mockImplementation(async ({ onMessageHandle, onFinish }) => {
+      // Simulate streaming chunks
+      await onMessageHandle?.({ type: 'text', text: 'Hello' } as any);
+      await onMessageHandle?.({ type: 'text', text: ' World' } as any);
+      await onFinish?.('Hello World', {});
+    });
+
+  await act(async () => {
+    await result.current.internal_fetchAIChatMessage({
+      messages,
+      messageId: 'test-message-id',
+      model: 'gpt-4o-mini',
+      provider: 'openai',
+    });
+  });
+
+  expect(result.current.internal_dispatchMessage).toHaveBeenCalled();
+
+  streamSpy.mockRestore();
+});
+```
+
+### 9. Error Handling Tests
+
+Always test error scenarios:
+
+```typescript
+it('should handle errors gracefully', async () => {
+  const { result } = renderHook(() => useChatStore());
+
+  vi.spyOn(messageService, 'createMessage').mockRejectedValue(
+    new Error('create message error'),
+  );
+
+  await act(async () => {
+    try {
+      await result.current.sendMessage({ message: 'Test message' });
+    } catch {
+      // Expected to throw
+    }
+  });
+
+  expect(result.current.internal_coreProcessMessage).not.toHaveBeenCalled();
+});
+```
+
+### 10. Cleanup After Tests
+
+Always restore mocks after each test:
+
+```typescript
+afterEach(() => {
+  vi.restoreAllMocks();
+});
+
+// For individual test cleanup:
+it('should test something', async () => {
+  const spy = vi.spyOn(service, 'method').mockImplementation(...);
+
+  // test logic
+
+  spy.mockRestore(); // Optional: cleanup immediately after test
+});
+```
+
+## Common Patterns
+
+### Testing Store Methods That Call Other Store Methods
+
+```typescript
+it('should call internal methods', async () => {
+  const { result } = renderHook(() => useChatStore());
+
+  const internalMethodSpy = vi.spyOn(result.current, 'internal_method')
+    .mockResolvedValue();
+
+  await act(async () => {
+    await result.current.publicMethod();
+  });
+
+  expect(internalMethodSpy).toHaveBeenCalledWith(
+    expect.any(String),
+    expect.objectContaining({ key: 'value' }),
+  );
+});
+```
+
+### Testing Conditional Logic
+
+```typescript
+describe('conditional behavior', () => {
+  it('should execute when condition is true', async () => {
+    const { result } = renderHook(() => useChatStore());
+    vi.spyOn(result.current, 'internal_shouldUseRAG').mockReturnValue(true);
+
+    await act(async () => {
+      await result.current.sendMessage({ message: 'test' });
+    });
+
+    expect(result.current.internal_retrieveChunks).toHaveBeenCalled();
+  });
+
+  it('should not execute when condition is false', async () => {
+    const { result } = renderHook(() => useChatStore());
+    vi.spyOn(result.current, 'internal_shouldUseRAG').mockReturnValue(false);
+
+    await act(async () => {
+      await result.current.sendMessage({ message: 'test' });
+    });
+
+    expect(result.current.internal_retrieveChunks).not.toHaveBeenCalled();
+  });
+});
+```
+
+### Testing AbortController
+
+```typescript
+it('should abort generation and clear loading state', () => {
+  const abortController = new AbortController();
+
+  act(() => {
+    useChatStore.setState({ chatLoadingIdsAbortController: abortController });
+  });
+
+  const { result } = renderHook(() => useChatStore());
+  const toggleLoadingSpy = vi.spyOn(result.current, 'internal_toggleChatLoading');
+
+  act(() => {
+    result.current.stopGenerateMessage();
+  });
+
+  expect(abortController.signal.aborted).toBe(true);
+  expect(toggleLoadingSpy).toHaveBeenCalledWith(false, undefined, expect.any(String));
+});
+```
+
+## Anti-Patterns to Avoid
+
+❌ **Don't**: Mock the entire store
+
+```typescript
+vi.mock('../../store', () => ({
+  useChatStore: vi.fn(() => ({
+    sendMessage: vi.fn(),
+  })),
+}));
+```
+
+❌ **Don't**: Test implementation details
+
+```typescript
+// Bad: testing internal state structure
+expect(result.current.messagesMap).toHaveProperty('test-session');
+
+// Good: testing behavior
+expect(result.current.refreshMessages).toHaveBeenCalled();
+```
+
+❌ **Don't**: Create tight coupling between tests
+
+```typescript
+// Bad: Tests depend on order
+let messageId: string;
+
+it('test 1', () => {
+  messageId = 'some-id'; // Side effect
+});
+
+it('test 2', () => {
+  expect(messageId).toBeDefined(); // Depends on test 1
+});
+```
+
+❌ **Don't**: Over-mock services
+
+```typescript
+// Bad: Mocking everything
+beforeEach(() => {
+  vi.mock('@/services/chat');
+  vi.mock('@/services/message');
+  vi.mock('@/services/file');
+  vi.mock('@/services/agent');
+  // ... too many global mocks
+});
+```
+
+## Testing SWR Hooks in Zustand Stores
+
+Some Zustand store slices use SWR hooks for data fetching. These require a different testing approach.
+
+### Basic SWR Hook Test Structure
+
+```typescript
+import { renderHook, waitFor } from '@testing-library/react';
+import { beforeEach, describe, expect, it, vi } from 'vitest';
+
+import { discoverService } from '@/services/discover';
+import { globalHelpers } from '@/store/global/helpers';
+import { useDiscoverStore as useStore } from '../../store';
+
+vi.mock('zustand/traditional');
+
+beforeEach(() => {
+  vi.clearAllMocks();
+});
+
+describe('SWR Hook Actions', () => {
+  it('should fetch data and return correct response', async () => {
+    const mockData = [{ id: '1', name: 'Item 1' }];
+
+    // Mock the service call (the fetcher)
+    vi.spyOn(discoverService, 'getPluginCategories').mockResolvedValue(mockData as any);
+    vi.spyOn(globalHelpers, 'getCurrentLanguage').mockReturnValue('en-US');
+
+    const params = {} as any;
+    const { result } = renderHook(() => useStore.getState().usePluginCategories(params));
+
+    // Use waitFor to wait for async data loading
+    await waitFor(() => {
+      expect(result.current.data).toEqual(mockData);
+    });
+
+    expect(discoverService.getPluginCategories).toHaveBeenCalledWith(params);
+  });
+});
+```
+
+**Key points**:
+- **DO NOT mock useSWR** - let it use the real implementation
+- Only mock the **service methods** (fetchers)
+- Use `waitFor` from `@testing-library/react` to wait for async operations
+- Check `result.current.data` directly after waitFor completes
+
+### Testing SWR Key Generation
+
+```typescript
+it('should generate correct SWR key with locale and params', () => {
+  vi.spyOn(globalHelpers, 'getCurrentLanguage').mockReturnValue('zh-CN');
+
+  const useSWRMock = vi.mocked(useSWR);
+  let capturedKey: string | null = null;
+  useSWRMock.mockImplementation(((key: string) => {
+    capturedKey = key;
+    return { data: undefined, error: undefined, isValidating: false, mutate: vi.fn() };
+  }) as any);
+
+  const params = { page: 2, category: 'tools' } as any;
+  renderHook(() => useStore.getState().usePluginList(params));
+
+  expect(capturedKey).toBe('plugin-list-zh-CN-2-tools');
+});
+```
+
+### Testing SWR Configuration
+
+```typescript
+it('should have correct SWR configuration', () => {
+  const useSWRMock = vi.mocked(useSWR);
+  let capturedOptions: any = null;
+  useSWRMock.mockImplementation(((key: string, fetcher: any, options: any) => {
+    capturedOptions = options;
+    return { data: undefined, error: undefined, isValidating: false, mutate: vi.fn() };
+  }) as any);
+
+  renderHook(() => useStore.getState().usePluginIdentifiers());
+
+  expect(capturedOptions).toMatchObject({ revalidateOnFocus: false });
+});
+```
+
+### Testing Conditional Fetching
+
+```typescript
+it('should not fetch when required parameter is missing', () => {
+  const useSWRMock = vi.mocked(useSWR);
+  let capturedKey: string | null = null;
+  useSWRMock.mockImplementation(((key: string | null) => {
+    capturedKey = key;
+    return { data: undefined, error: undefined, isValidating: false, mutate: vi.fn() };
+  }) as any);
+
+  // When identifier is undefined, SWR key should be null
+  renderHook(() => useStore.getState().usePluginDetail({ identifier: undefined }));
+
+  expect(capturedKey).toBeNull();
+});
+```
+
+### Key Differences from Regular Action Tests
+
+1. **Mock useSWR globally**: Use `vi.mock('swr')` at the top level
+2. **Mock the fetcher, not the result**:
+   - ✅ **Correct**: `const data = fetcher?.()` - call fetcher and return its Promise
+   - ❌ **Wrong**: `return { data: mockData }` - hardcode the result
+3. **Await Promise results**: The `data` field is a Promise, use `await result.current.data`
+4. **No act() wrapper needed**: SWR hooks don't trigger React state updates in these tests
+5. **Test SWR key generation**: Verify keys include locale and parameters
+6. **Test configuration**: Verify revalidation and other SWR options
+7. **Type assertions**: Use `as any` for test mock data where type definitions are strict
+
+**Why this matters**:
+- The fetcher (service method) is what we're testing - it must be called
+- Hardcoding the return value bypasses the actual fetcher logic
+- SWR returns Promises in real usage, tests should mirror this behavior
+
+## Benefits of This Approach
+
+✅ **Clear test layers** - Each test only spies on direct dependencies
+✅ **Correct mocks** - Mocks match actual implementation
+✅ **Better maintainability** - Changes to implementation require fewer test updates
+✅ **Improved coverage** - Structured approach ensures all branches are tested
+✅ **Reduced coupling** - Tests are independent and can run in any order
+
+## Reference
+
+See example implementation in:
+- `src/store/chat/slices/aiChat/actions/__tests__/generateAIChat.test.ts` (Regular actions)
+- `src/store/discover/slices/plugin/action.test.ts` (SWR hooks)
+- `src/store/discover/slices/mcp/action.test.ts` (SWR hooks)
@@ -0,0 +1,58 @@
+---
+description: TypeScript code style and optimization guidelines
+globs: *.ts,*.tsx,*.mts
+alwaysApply: false
+---
+
+# TypeScript Code Style Guide
+
+## Types and Type Safety
+
+- avoid explicit type annotations when TypeScript can infer types.
+- 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` and `any`).
+- 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.
+- prefer `@ts-expect-error` over `@ts-ignore` over `as any`
+- Avoid meaningless null/undefined parameters; design strict function contracts.
+
+## 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
+
+- 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.
+- Defer formatting to tooling; ignore purely formatting-only issues and autofixable lint problems.
+
+## 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.
+- Reuse existing utils inside `packages/utils` or installed npm packages rather than reinventing the wheel.
+- 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.
+
+## Logging
+
+- 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.
@@ -0,0 +1,360 @@
+---
+description: 
+globs: src/store/**
+alwaysApply: false
+---
+# LobeChat Zustand Action 组织模式
+
+本文档详细说明了 LobeChat 项目中 Zustand Action 的组织方式、命名规范和实现模式，特别关注乐观更新与后端服务的集成。
+
+## Action 类型分层
+
+LobeChat 的 Action 采用分层架构，明确区分不同职责：
+
+### 1. Public Actions
+对外暴露的主要接口，供 UI 组件调用：
+- 命名：动词形式（`createTopic`, `sendMessage`, `updateTopicTitle`）
+- 职责：参数验证、流程编排、调用 internal actions
+- 示例：[src/store/chat/slices/topic/action.ts](mdc:src/store/chat/slices/topic/action.ts)
+
+```typescript
+// Public Action 示例
+createTopic: async () => {
+  const { activeId, internal_createTopic } = get();
+  const messages = chatSelectors.activeBaseChats(get());
+  
+  if (messages.length === 0) return;
+  
+  const topicId = await internal_createTopic({
+    sessionId: activeId,
+    title: t('defaultTitle', { ns: 'topic' }),
+    messages: messages.map((m) => m.id),
+  });
+  
+  return topicId;
+},
+```
+
+### 2. Internal Actions (`internal_*`)
+内部实现细节，处理核心业务逻辑：
+- 命名：`internal_` 前缀 + 动词（`internal_createTopic`, `internal_updateMessageContent`）
+- 职责：乐观更新、服务调用、错误处理、状态同步
+- 不应该被 UI 组件直接调用
+
+```typescript
+// Internal Action 示例 - 乐观更新模式
+internal_createTopic: async (params) => {
+  const tmpId = Date.now().toString();
+  
+  // 1. 立即更新前端状态（乐观更新）
+  get().internal_dispatchTopic(
+    { type: 'addTopic', value: { ...params, id: tmpId } },
+    'internal_createTopic',
+  );
+  get().internal_updateTopicLoading(tmpId, true);
+  
+  // 2. 调用后端服务
+  const topicId = await topicService.createTopic(params);
+  get().internal_updateTopicLoading(tmpId, false);
+  
+  // 3. 刷新数据确保一致性
+  get().internal_updateTopicLoading(topicId, true);
+  await get().refreshTopic();
+  get().internal_updateTopicLoading(topicId, false);
+  
+  return topicId;
+},
+```
+
+### 3. Dispatch Methods (`internal_dispatch*`)
+专门处理状态更新的方法：
+- 命名：`internal_dispatch` + 实体名（`internal_dispatchTopic`, `internal_dispatchMessage`）
+- 职责：调用 reducer、更新 Zustand store、处理状态对比
+
+```typescript
+// Dispatch Method 示例
+internal_dispatchTopic: (payload, action) => {
+  const nextTopics = topicReducer(topicSelectors.currentTopics(get()), payload);
+  const nextMap = { ...get().topicMaps, [get().activeId]: nextTopics };
+
+  if (isEqual(nextMap, get().topicMaps)) return;
+  
+  set({ topicMaps: nextMap }, false, action ?? n(`dispatchTopic/${payload.type}`));
+},
+```
+
+## 何时使用 Reducer 模式 vs. 简单 `set`
+
+### 使用 Reducer 模式的场景
+
+适用于复杂的数据结构管理，特别是：
+- 管理对象列表或映射（如 `messagesMap`, `topicMaps`）
+- 需要乐观更新的场景
+- 状态转换逻辑复杂
+- 需要类型安全的 action payload
+
+```typescript
+// Reducer 模式示例 - 复杂消息状态管理
+export const messagesReducer = (state: ChatMessage[], payload: MessageDispatch): ChatMessage[] => {
+  switch (payload.type) {
+    case 'updateMessage': {
+      return produce(state, (draftState) => {
+        const index = draftState.findIndex((i) => i.id === payload.id);
+        if (index < 0) return;
+        draftState[index] = merge(draftState[index], { 
+          ...payload.value, 
+          updatedAt: Date.now() 
+        });
+      });
+    }
+    case 'createMessage': {
+      return produce(state, (draftState) => {
+        draftState.push({ 
+          ...payload.value, 
+          id: payload.id,
+          createdAt: Date.now(),
+          updatedAt: Date.now(),
+          meta: {}
+        });
+      });
+    }
+    // ...其他复杂状态转换
+  }
+};
+```
+
+### 使用简单 `set` 的场景
+
+适用于简单状态更新：
+- 切换布尔值
+- 更新简单字符串/数字
+- 设置单一状态字段
+
+```typescript
+// 简单 set 示例
+updateInputMessage: (message) => {
+  if (isEqual(message, get().inputMessage)) return;
+  set({ inputMessage: message }, false, n('updateInputMessage'));
+},
+
+togglePortal: (open?: boolean) => {
+  set({ showPortal: open ?? !get().showPortal }, false, 'togglePortal');
+},
+```
+
+## 乐观更新实现模式
+
+乐观更新是 LobeChat 中的核心模式，用于提供流畅的用户体验：
+
+### 标准乐观更新流程
+
+```typescript
+// 完整的乐观更新示例
+internal_updateMessageContent: async (id, content, extra) => {
+  const { internal_dispatchMessage, refreshMessages } = get();
+
+  // 1. 立即更新前端状态（乐观更新）
+  internal_dispatchMessage({
+    id,
+    type: 'updateMessage',
+    value: { content },
+  });
+
+  // 2. 调用后端服务
+  await messageService.updateMessage(id, {
+    content,
+    tools: extra?.toolCalls ? internal_transformToolCalls(extra.toolCalls) : undefined,
+    // ...其他字段
+  });
+
+  // 3. 刷新确保数据一致性
+  await refreshMessages();
+},
+```
+
+### 创建操作的乐观更新
+
+```typescript
+internal_createMessage: async (message, context) => {
+  const { internal_createTmpMessage, refreshMessages, internal_toggleMessageLoading } = get();
+  
+  let tempId = context?.tempMessageId;
+  if (!tempId) {
+    // 创建临时消息用于乐观更新
+    tempId = internal_createTmpMessage(message);
+    internal_toggleMessageLoading(true, tempId);
+  }
+
+  try {
+    const id = await messageService.createMessage(message);
+    if (!context?.skipRefresh) {
+      await refreshMessages();
+    }
+    internal_toggleMessageLoading(false, tempId);
+    return id;
+  } catch (e) {
+    internal_toggleMessageLoading(false, tempId);
+    // 错误处理：更新消息错误状态
+    internal_dispatchMessage({
+      id: tempId,
+      type: 'updateMessage',
+      value: { error: { type: ChatErrorType.CreateMessageError, message: e.message } },
+    });
+  }
+},
+```
+
+### 删除操作模式（不使用乐观更新）
+
+删除操作通常不适合乐观更新，因为：
+- 删除是破坏性操作，错误恢复复杂
+- 用户对删除操作的即时反馈期望较低
+- 删除失败时恢复原状态会造成困惑
+
+```typescript
+// 删除操作的标准模式 - 无乐观更新
+removeGenerationTopic: async (id: string) => {
+  const { internal_removeGenerationTopic } = get();
+  await internal_removeGenerationTopic(id);
+},
+
+internal_removeGenerationTopic: async (id: string) => {
+  // 1. 显示加载状态
+  get().internal_updateGenerationTopicLoading(id, true);
+  
+  try {
+    // 2. 直接调用后端服务
+    await generationTopicService.deleteTopic(id);
+    
+    // 3. 刷新数据获取最新状态
+    await get().refreshGenerationTopics();
+  } finally {
+    // 4. 确保清除加载状态（无论成功或失败）
+    get().internal_updateGenerationTopicLoading(id, false);
+  }
+},
+```
+
+删除操作的特点：
+- 直接调用服务，不预先更新状态
+- 依赖 loading 状态提供用户反馈
+- 操作完成后刷新整个列表确保一致性
+- 使用 `try/finally` 确保 loading 状态总是被清理
+
+## 加载状态管理模式
+
+LobeChat 使用统一的加载状态管理模式：
+
+### 数组式加载状态
+
+```typescript
+// 在 initialState.ts 中定义
+export interface ChatMessageState {
+  messageLoadingIds: string[];      // 消息加载状态
+  messageEditingIds: string[];      // 消息编辑状态
+  chatLoadingIds: string[];         // 对话生成状态
+}
+
+// 在 action 中管理
+internal_toggleMessageLoading: (loading, id) => {
+  set({
+    messageLoadingIds: toggleBooleanList(get().messageLoadingIds, id, loading),
+  }, false, `internal_toggleMessageLoading/${loading ? 'start' : 'end'}`);
+},
+```
+
+### 统一的加载状态工具
+
+```typescript
+// 通用的加载状态切换工具
+internal_toggleLoadingArrays: (key, loading, id, action) => {
+  const abortControllerKey = `${key}AbortController`;
+  
+  if (loading) {
+    const abortController = new AbortController();
+    set({
+      [abortControllerKey]: abortController,
+      [key]: toggleBooleanList(get()[key] as string[], id!, loading),
+    }, false, action);
+    return abortController;
+  } else {
+    set({
+      [abortControllerKey]: undefined,
+      [key]: id ? toggleBooleanList(get()[key] as string[], id, loading) : [],
+    }, false, action);
+  }
+},
+```
+
+## SWR 集成模式
+
+LobeChat 使用 SWR 进行数据获取和缓存管理：
+
+### Hook 式数据获取
+
+```typescript
+// 在 action.ts 中定义 SWR hook
+useFetchMessages: (enable, sessionId, activeTopicId) =>
+  useClientDataSWR<ChatMessage[]>(
+    enable ? [SWR_USE_FETCH_MESSAGES, sessionId, activeTopicId] : null,
+    async ([, sessionId, topicId]) => messageService.getMessages(sessionId, topicId),
+    {
+      onSuccess: (messages, key) => {
+        const nextMap = {
+          ...get().messagesMap,
+          [messageMapKey(sessionId, activeTopicId)]: messages,
+        };
+        
+        if (get().messagesInit && isEqual(nextMap, get().messagesMap)) return;
+        
+        set({ messagesInit: true, messagesMap: nextMap }, false, n('useFetchMessages'));
+      },
+    },
+  ),
+```
+
+### 缓存失效和刷新
+
+```typescript
+// 刷新数据的标准模式
+refreshMessages: async () => {
+  await mutate([SWR_USE_FETCH_MESSAGES, get().activeId, get().activeTopicId]);
+},
+
+refreshTopic: async () => {
+  return mutate([SWR_USE_FETCH_TOPIC, get().activeId]);
+},
+```
+
+## 命名规范总结
+
+### Action 命名模式
+- Public Actions: 动词形式，描述用户意图
+  - `createTopic`, `sendMessage`, `regenerateMessage`
+- Internal Actions: `internal_` + 动词，描述内部操作
+  - `internal_createTopic`, `internal_updateMessageContent`
+- Dispatch Methods: `internal_dispatch` + 实体名
+  - `internal_dispatchTopic`, `internal_dispatchMessage`
+- Toggle Methods: `internal_toggle` + 状态名
+  - `internal_toggleMessageLoading`, `internal_toggleChatLoading`
+
+### 状态命名模式
+- ID 数组: `[entity]LoadingIds`, `[entity]EditingIds`
+- 映射结构: `[entity]Maps`, `[entity]Map`
+- 当前激活: `active[Entity]Id`
+- 初始化标记: `[entity]sInit`
+
+## 最佳实践
+
+1. 合理使用乐观更新：
+   - ✅ 适用：创建、更新操作（用户交互频繁）
+   - ❌ 避免：删除操作（破坏性操作，错误恢复复杂）
+2. 加载状态管理：使用统一的加载状态数组管理并发操作
+3. 类型安全：为所有 action payload 定义 TypeScript 接口
+4. SWR 集成：使用 SWR 管理数据获取和缓存失效
+5. AbortController：为长时间运行的操作提供取消能力
+6. 操作模式选择：
+   - 创建/更新：乐观更新 + 最终一致性
+   - 删除：加载状态 + 服务调用 + 数据刷新
+
+这套 Action 组织模式确保了代码的一致性、可维护性，并提供了优秀的用户体验。
@@ -0,0 +1,300 @@
+---
+description: 
+globs: src/store/**
+alwaysApply: false
+---
+# LobeChat Zustand Store Slice 组织架构
+
+本文档描述了 LobeChat 项目中 Zustand Store 的模块化 Slice 组织方式，展示如何通过分片架构管理复杂的应用状态。
+
+## 顶层 Store 结构
+
+LobeChat 的 `chat` store (`src/store/chat/`) 采用模块化的 slice 结构来组织状态和逻辑。
+
+### 关键聚合文件
+
+- `src/store/chat/initialState.ts`: 聚合所有 slice 的初始状态
+- `src/store/chat/store.ts`: 定义顶层的 `ChatStore`，组合所有 slice 的 actions
+- `src/store/chat/selectors.ts`: 统一导出所有 slice 的 selectors
+- `src/store/chat/helpers.ts`: 提供聊天相关的辅助函数
+
+### Store 聚合模式
+
+```typescript
+// src/store/chat/initialState.ts
+import { ChatTopicState, initialTopicState } from './slices/topic/initialState';
+import { ChatMessageState, initialMessageState } from './slices/message/initialState';
+import { ChatAIChatState, initialAiChatState } from './slices/aiChat/initialState';
+
+export type ChatStoreState = ChatTopicState &
+  ChatMessageState &
+  ChatAIChatState &
+  // ...其他 slice states
+
+export const initialState: ChatStoreState = {
+  ...initialMessageState,
+  ...initialTopicState,
+  ...initialAiChatState,
+  // ...其他 initial slice states
+};
+```
+
+```typescript
+// src/store/chat/store.ts
+import { ChatMessageAction, chatMessage } from './slices/message/action';
+import { ChatTopicAction, chatTopic } from './slices/topic/action';
+import { ChatAIChatAction, chatAiChat } from './slices/aiChat/actions';
+
+export interface ChatStoreAction
+  extends ChatMessageAction,
+    ChatTopicAction,
+    ChatAIChatAction,
+    // ...其他 slice actions
+
+const createStore: StateCreator<ChatStore, [['zustand/devtools', never]]> = (...params) => ({
+  ...initialState,
+  ...chatMessage(...params),
+  ...chatTopic(...params),
+  ...chatAiChat(...params),
+  // ...其他 slice action creators
+});
+
+export const useChatStore = createWithEqualityFn<ChatStore>()(
+  subscribeWithSelector(devtools(createStore)),
+  shallow,
+);
+```
+
+## 单个 Slice 的标准结构
+
+每个 slice 位于 `src/store/chat/slices/[sliceName]/` 目录下：
+
+```
+src/store/chat/slices/
+└── [sliceName]/                 # 例如 message, topic, aiChat, builtinTool
+    ├── action.ts                # 定义 actions (或者是一个 actions/ 目录)
+    ├── initialState.ts          # 定义 state 结构和初始值
+    ├── reducer.ts               # (可选) 如果使用 reducer 模式
+    ├── selectors.ts             # 定义 selectors
+    └── index.ts                 # (可选) 重新导出模块内容
+```
+
+### 文件职责说明
+
+1. `initialState.ts`:
+   - 定义 slice 的 TypeScript 状态接口
+   - 提供初始状态默认值
+
+```typescript
+// 典型的 initialState.ts 结构
+export interface ChatTopicState {
+  activeTopicId?: string;
+  topicMaps: Record<string, ChatTopic[]>; // 核心数据结构
+  topicsInit: boolean;
+  topicLoadingIds: string[];
+  // ...其他状态字段
+}
+
+export const initialTopicState: ChatTopicState = {
+  activeTopicId: undefined,
+  topicMaps: {},
+  topicsInit: false,
+  topicLoadingIds: [],
+  // ...其他初始值
+};
+```
+
+2. `reducer.ts` (复杂状态使用):
+   - 定义纯函数 reducer，处理同步状态转换
+   - 使用 `immer` 确保不可变更新
+
+```typescript
+// 典型的 reducer.ts 结构
+import { produce } from 'immer';
+
+interface AddChatTopicAction {
+  type: 'addTopic';
+  value: CreateTopicParams & { id?: string };
+}
+
+interface UpdateChatTopicAction {
+  id: string;
+  type: 'updateTopic';
+  value: Partial<ChatTopic>;
+}
+
+export type ChatTopicDispatch = AddChatTopicAction | UpdateChatTopicAction;
+
+export const topicReducer = (state: ChatTopic[] = [], payload: ChatTopicDispatch): ChatTopic[] => {
+  switch (payload.type) {
+    case 'addTopic': {
+      return produce(state, (draftState) => {
+        draftState.unshift({
+          ...payload.value,
+          id: payload.value.id ?? Date.now().toString(),
+          createdAt: Date.now(),
+        });
+      });
+    }
+    case 'updateTopic': {
+      return produce(state, (draftState) => {
+        const index = draftState.findIndex((topic) => topic.id === payload.id);
+        if (index !== -1) {
+          draftState[index] = { ...draftState[index], ...payload.value };
+        }
+      });
+    }
+    default:
+      return state;
+  }
+};
+```
+
+3. `selectors.ts`:
+   - 提供状态查询和计算函数
+   - 供 UI 组件使用的状态订阅接口
+   - 重要: 使用 `export const xxxSelectors` 模式聚合所有 selectors
+
+```typescript
+// 典型的 selectors.ts 结构
+import { ChatStoreState } from '../../initialState';
+
+const currentTopics = (s: ChatStoreState): ChatTopic[] | undefined => 
+  s.topicMaps[s.activeId];
+
+const currentActiveTopic = (s: ChatStoreState): ChatTopic | undefined => {
+  return currentTopics(s)?.find((topic) => topic.id === s.activeTopicId);
+};
+
+const getTopicById = (id: string) => (s: ChatStoreState): ChatTopic | undefined =>
+  currentTopics(s)?.find((topic) => topic.id === id);
+
+// 核心模式：使用 xxxSelectors 聚合导出
+export const topicSelectors = {
+  currentActiveTopic,
+  currentTopics,
+  getTopicById,
+  // ...其他 selectors
+};
+```
+
+## 特殊 Slice 组织模式
+
+### 复杂 Actions 的子目录结构 (aiChat Slice)
+
+当 slice 的 actions 过于复杂时，可以拆分到子目录：
+
+```
+src/store/chat/slices/aiChat/
+├── actions/
+│   ├── generateAIChat.ts       # AI 对话生成
+│   ├── rag.ts                  # RAG 检索增强生成
+│   ├── memory.ts               # 对话记忆管理
+│   └── index.ts                # 聚合所有 actions
+├── initialState.ts
+├── selectors.ts
+└── index.ts
+```
+
+参考：`src/store/chat/slices/aiChat/actions/`
+
+### 工具类 Slice (builtinTool)
+
+管理多种内置工具的状态：
+
+```
+src/store/chat/slices/builtinTool/
+├── actions/
+│   ├── dalle.ts                # DALL-E 图像生成
+│   ├── search.ts               # 搜索功能
+│   ├── localFile.ts            # 本地文件操作
+│   └── index.ts
+├── initialState.ts
+├── selectors.ts
+└── index.ts
+```
+
+参考：`src/store/chat/slices/builtinTool/`
+
+## 状态设计模式
+
+### 1. Map 结构用于关联数据
+```typescript
+// 以 sessionId 为 key，管理多个会话的数据
+topicMaps: Record<string, ChatTopic[]>
+messagesMap: Record<string, ChatMessage[]>
+```
+
+### 2. 数组用于加载状态管理
+```typescript
+// 管理多个并发操作的加载状态
+messageLoadingIds: string[]
+topicLoadingIds: string[]
+chatLoadingIds: string[]
+```
+
+### 3. 可选字段用于当前活动项
+```typescript
+// 当前激活的实体 ID
+activeId: string
+activeTopicId?: string
+activeThreadId?: string
+```
+
+## Slice 集成到顶层 Store
+
+### 1. 状态聚合
+```typescript
+// 在 initialState.ts 中
+export type ChatStoreState = ChatTopicState &
+  ChatMessageState &
+  ChatAIChatState &
+  // ...其他 slice states
+```
+
+### 2. Action 接口聚合
+```typescript
+// 在 store.ts 中
+export interface ChatStoreAction
+  extends ChatMessageAction,
+    ChatTopicAction,
+    ChatAIChatAction,
+    // ...其他 slice actions
+```
+
+### 3. Selector 统一导出
+```typescript
+// 在 selectors.ts 中 - 统一聚合 selectors
+export { chatSelectors } from './slices/message/selectors';
+export { topicSelectors } from './slices/topic/selectors';
+export { aiChatSelectors } from './slices/aiChat/selectors';
+
+// 每个 slice 的 selectors.ts 都使用 xxxSelectors 模式：
+// export const chatSelectors = { ... }
+// export const topicSelectors = { ... }
+// export const aiChatSelectors = { ... }
+```
+
+## 最佳实践
+
+1. Slice 划分原则:
+   - 按功能领域划分（message, topic, aiChat 等）
+   - 每个 slice 管理相关的状态和操作
+   - 避免 slice 之间的强耦合
+
+2. 文件命名规范:
+   - 使用小驼峰命名 slice 目录
+   - 文件名使用一致的模式（action.ts, selectors.ts 等）
+   - 复杂 actions 时使用 actions/ 子目录
+
+3. 状态结构设计:
+   - 扁平化的状态结构，避免深层嵌套
+   - 使用 Map 结构管理列表数据
+   - 分离加载状态和业务数据
+
+4. 类型安全:
+   - 为每个 slice 定义清晰的 TypeScript 接口
+   - 使用 Zustand 的 StateCreator 确保类型一致性
+   - 在顶层聚合时保持类型安全
+
+这种模块化的 slice 组织方式使得大型应用的状态管理变得清晰、可维护，并且易于扩展。
@@ -0,0 +1,6 @@
+# Add directories or file patterns to ignore during indexing (e.g. foo/ or *.csv)
+locales/
+apps/desktop/resources/locales/
+**/__snapshots__/
+**/fixtures/
+src/database/migrations/
@@ -1,6 +1,7 @@
 {
-  "image": "mcr.microsoft.com/devcontainers/universal:2",
  "features": {
-    "ghcr.io/devcontainers/features/node:1": {}
-  }
+    "ghcr.io/devcontainer-community/devcontainer-features/bun.sh:1": {},
+    "ghcr.io/devcontainers/features/docker-outside-of-docker:1": {}
+  },
+  "image": "mcr.microsoft.com/devcontainers/typescript-node"
 }
@@ -0,0 +1,8 @@
+# copy this file to .env when you want to develop the desktop app or you will fail
+APP_URL=http://localhost:3015
+FEATURE_FLAGS=-check_updates,+pin_list
+KEY_VAULTS_SECRET=oLXWIiR/AKF+rWaqy9lHkrYgzpATbW3CtJp3UfkVgpE=
+DATABASE_URL=postgresql://postgres@localhost:5432/postgres
+SEARCH_PROVIDERS=search1api
+NEXT_PUBLIC_IS_DESKTOP_APP=1
+NEXT_PUBLIC_ENABLE_NEXT_AUTH=0
@@ -4,9 +4,28 @@
 # Specify your API Key selection method, currently supporting `random` and `turn`.
 # API_KEY_SELECT_MODE=random

+########################################
+########### Security Settings ###########
+########################################
+
+# Control Content Security Policy headers
+# Set to '1' to enable X-Frame-Options and Content-Security-Policy headers
+# Default is '0' (enabled)
+# ENABLED_CSP=1
+
+# SSRF Protection Settings
+# Set to '1' to allow connections to private IP addresses (disable SSRF protection)
+# WARNING: Only enable this in trusted environments
+# Default is '0' (SSRF protection enabled)
+# SSRF_ALLOW_PRIVATE_IP_ADDRESS=0
+
+# Whitelist of allowed private IP addresses (comma-separated)
+# Only takes effect when SSRF_ALLOW_PRIVATE_IP_ADDRESS is '0'
+# Example: Allow specific internal servers while keeping SSRF protection
+# SSRF_ALLOW_IP_ADDRESS_LIST=192.168.1.100,10.0.0.50

 ########################################
-######## Model Provider Service ########
+########## AI Provider Service #########
 ########################################

 ### OpenAI ###
@@ -33,7 +52,7 @@ OPENAI_API_KEY=sk-xxxxxxxxx
 # AZURE_ENDPOINT=https://docs-test-001.openai.azure.com

 # Azure's API version, follows the YYYY-MM-DD format
-# AZURE_API_VERSION=2024-06-01
+# AZURE_API_VERSION=2024-10-21


 ### Anthropic Service ####
@@ -106,8 +125,14 @@ OPENAI_API_KEY=sk-xxxxxxxxx

 ### DeepSeek AI  ####

+# DEEPSEEK_PROXY_URL=https://api.deepseek.com/v1
 # DEEPSEEK_API_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

+### Qiniu AI  ####
+
+# QINIU_PROXY_URL=https://api.qnaigc.com/v1
+# QINIU_API_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
+
 ### Qwen AI  ####

 # QWEN_API_KEY=sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
@@ -121,6 +146,61 @@ OPENAI_API_KEY=sk-xxxxxxxxx

 # SILICONCLOUD_API_KEY=sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

+
+### TencentCloud AI  ####
+
+# TENCENT_CLOUD_API_KEY=sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
+
+### PPIO ####
+
+# PPIO_API_KEY=sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
+
+### INFINI-AI ###
+
+# INFINIAI_API_KEY=sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
+
+
+### 302.AI ###
+
+# AI302_API_KEY=sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
+
+### ModelScope ###
+
+# MODELSCOPE_API_KEY=sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
+
+### AiHubMix ###
+
+# AIHUBMIX_API_KEY=sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
+
+### BFL ###
+
+# BFL_API_KEY=bfl-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
+
+### FAL ###
+
+# FAL_API_KEY=fal-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
+
+########################################
+######### AI Image Settings ############
+########################################
+
+# Default image generation count (range: 1-20, default: 4)
+# AI_IMAGE_DEFAULT_IMAGE_NUM=4
+
+### Nebius ###
+
+# NEBIUS_API_KEY=sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
+
+### NewAPI Service ###
+
+# NEWAPI_API_KEY=sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
+# NEWAPI_PROXY_URL=https://your-newapi-server.com
+
+### Vercel AI Gateway ###
+
+# VERCELAIGATEWAY_API_KEY=your_vercel_ai_gateway_api_key
+
+
 ########################################
 ############ Market Service ############
 ########################################
@@ -187,8 +267,12 @@ OPENAI_API_KEY=sk-xxxxxxxxx
 # you need to config the clerk webhook secret key if you want to use the clerk with database
 #CLERK_WEBHOOK_SECRET=whsec_xxxxxxxxxxxxxxxxxxxxxx

+# Clear allow origin https://clerk.com/docs/guides/dashboard/dns-domains/satellite-domains
+# Authentication across different domains , use,to splite different origin
+# NEXT_PUBLIC_CLERK_AUTH_ALLOW_ORIGINS='https://market.lobehub.com,https://lobehub.com'

 # NextAuth related configurations
+# NEXT_PUBLIC_ENABLE_NEXT_AUTH=1
 # NEXT_AUTH_SECRET=

 # Auth0 configurations
@@ -200,15 +284,19 @@ OPENAI_API_KEY=sk-xxxxxxxxx
 ########## Server Database #############
 ########################################

-# Specify the service mode as server if you want to use the server database
-# NEXT_PUBLIC_SERVICE_MODE=server
-
 # Postgres database URL
 # DATABASE_URL=postgres://username:password@host:port/database

 # use `openssl rand -base64 32` to generate a key for the encryption of the database
-# we use this key to encrypt the user api key
+# we use this key to encrypt the user api key and proxy url
 #KEY_VAULTS_SECRET=xxxxx/xxxxxxxxxxxxxx=

 # Specify the Embedding model and Reranker model(unImplemented)
 # DEFAULT_FILES_CONFIG="embedding_model=openai/embedding-text-3-small,reranker_model=cohere/rerank-english-v3.0,query_mode=full_text"
+
+########################################
+########## MCP Service Config ##########
+########################################
+
+# MCP tool call timeout (milliseconds)
+# MCP_TOOL_TIMEOUT=60000
@@ -0,0 +1,120 @@
+# LobeChat Development Server Configuration
+# This file contains environment variables for both LobeChat server mode and Docker compose setup
+
+COMPOSE_FILE="docker-compose.development.yml"
+
+# ⚠️⚠️⚠️ DO NOT USE THE SECRETS BELOW IN PRODUCTION!
+UNSAFE_SECRET="ww+0igxjGRAAR/eTNFQ55VmhQB5KE5trFZseuntThJs="
+UNSAFE_PASSWORD="CHANGE_THIS_PASSWORD_IN_PRODUCTION"
+
+# Core Server Configuration
+
+# Service Ports Configuration
+LOBE_PORT=3010
+
+# Application URL - the base URL where LobeChat will be accessible
+APP_URL=http://localhost:${LOBE_PORT}
+
+# Secret key for encrypting vault data (generate with: openssl rand -base64 32)
+KEY_VAULTS_SECRET=${UNSAFE_SECRET}
+
+# Database Configuration
+# Database name for LobeChat
+LOBE_DB_NAME=lobechat
+
+# PostgreSQL password
+POSTGRES_PASSWORD=${UNSAFE_PASSWORD}
+
+# PostgreSQL database connection URL
+DATABASE_URL=postgresql://postgres:${POSTGRES_PASSWORD}@localhost:5432/${LOBE_DB_NAME}
+
+# Database driver type
+DATABASE_DRIVER=node
+
+# Authentication Configuration
+# Enable NextAuth authentication
+NEXT_PUBLIC_ENABLE_NEXT_AUTH=1
+
+# NextAuth secret for JWT signing (generate with: openssl rand -base64 32)
+NEXT_AUTH_SECRET=${UNSAFE_SECRET}
+
+NEXTAUTH_URL=${APP_URL}
+
+# Authentication URL
+AUTH_URL=${APP_URL}/api/auth
+
+# SSO providers configuration - using Casdoor for development
+NEXT_AUTH_SSO_PROVIDERS=casdoor
+
+# Casdoor Configuration
+# Casdoor service port
+CASDOOR_PORT=8000
+
+# Casdoor OIDC issuer URL
+AUTH_CASDOOR_ISSUER=http://localhost:${CASDOOR_PORT}
+
+# Casdoor application client ID
+AUTH_CASDOOR_ID=a387a4892ee19b1a2249 # DO NOT USE IN PROD
+
+# Casdoor application client secret
+AUTH_CASDOOR_SECRET=dbf205949d704de81b0b5b3603174e23fbecc354 # DO NOT USE IN PROD
+
+# Origin URL for Casdoor internal configuration
+origin=http://localhost:${CASDOOR_PORT}
+
+# MinIO Storage Configuration
+# MinIO service port
+MINIO_PORT=9000
+
+# MinIO root user (admin username)
+MINIO_ROOT_USER=admin
+
+# MinIO root password
+MINIO_ROOT_PASSWORD=${UNSAFE_PASSWORD}
+
+# MinIO bucket for LobeChat files
+MINIO_LOBE_BUCKET=lobe
+
+# S3/MinIO Configuration for LobeChat
+# S3/MinIO access key ID
+S3_ACCESS_KEY_ID=${MINIO_ROOT_USER}
+
+# S3/MinIO secret access key
+S3_SECRET_ACCESS_KEY=${MINIO_ROOT_PASSWORD}
+
+# S3/MinIO endpoint URL
+S3_ENDPOINT=http://localhost:${MINIO_PORT}
+
+# S3 bucket name for storing files
+S3_BUCKET=${MINIO_LOBE_BUCKET}
+
+# Public domain for S3 file access
+S3_PUBLIC_DOMAIN=http://localhost:${MINIO_PORT}
+
+# Enable path-style S3 requests (required for MinIO)
+S3_ENABLE_PATH_STYLE=1
+
+# Disable S3 ACL setting (for MinIO compatibility)
+S3_SET_ACL=0
+
+# Use base64 encoding for LLM vision images
+LLM_VISION_IMAGE_USE_BASE64=1
+
+# Search Service Configuration
+# SearXNG search engine URL
+SEARXNG_URL=http://searxng:8080
+
+# Development Options
+# Uncomment to skip authentication during development
+
+# Proxy Configuration (Optional)
+# Uncomment if you need proxy support (e.g., for GitHub auth or API access)
+# HTTP_PROXY=http://localhost:7890
+# HTTPS_PROXY=http://localhost:7890
+
+# AI Model Configuration (Optional)
+# Add your AI model API keys and configurations here
+# ⚠️  WARNING: Never commit real API keys to version control!
+# OPENAI_API_KEY=sk-NEVER_USE_REAL_API_KEYS_IN_CONFIG_FILES
+# OPENAI_PROXY_URL=https://api.openai.com/v1
+# OPENAI_MODEL_LIST=...
@@ -29,3 +29,20 @@ logs
 # misc
 # add other ignore file below
 .next
+
+# temporary directories
+tmp
+temp
+.temp
+.local
+docs/.local
+
+# cache directories
+.cache
+
+# AI coding tools directories
+.claude
+.serena
+
+# MCP tools
+/.serena/**
@@ -17,6 +17,10 @@ config.rules['unicorn/prefer-spread'] = 0;
 config.rules['unicorn/catch-error-name'] = 0;
 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;
+// 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.overrides = [
  {
@@ -32,6 +36,16 @@ config.overrides = [
      'mdx/code-blocks': false,
    },
  },
+
+  {
+    files: ['src/store/image/**/*', 'src/types/generation/**/*'],
+    rules: {
+      '@typescript-eslint/no-empty-interface': 0,
+      'sort-keys-fix/sort-keys-fix': 0,
+      'typescript-sort-keys/interface': 0,
+      'typescript-sort-keys/string-enum': 0,
+    },
+  },
 ];

 module.exports = config;
@@ -1,28 +1,22 @@
 name: '🐛 Bug Report'
 description: 'Report an bug'
-title: '[Bug] '
-labels: ['🐛 Bug']
+labels: ['unconfirm']
+type: Bug
 body:
  - type: dropdown
    attributes:
-      label: '📦 Environment'
+      label: '📱 Client Type'
+      description: 'Select how you are accessing LobeChat'
      multiple: true
      options:
-        - 'Official Preview'
-        - 'Vercel'
-        - 'Zeabur'
-        - 'Sealos'
-        - 'Netlify'
-        - 'Docker'
+        - 'Web (Desktop Browser)'
+        - 'Web (Mobile Browser)'
+        - 'Desktop App (Electron)'
+        - 'Mobile App (React Native)'
        - 'Other'
    validations:
      required: true
-  - type: input
-    attributes:
-      label: '📌 Version'
-    validations:
-      required: true
-  
+
  - type: dropdown
    attributes:
      label: '💻 Operating System'
@@ -37,6 +31,39 @@ body:
        - 'Other'
    validations:
      required: true
+
+  - type: dropdown
+    attributes:
+      label: '📦 Deployment Platform'
+      multiple: true
+      options:
+        - 'Official Cloud'
+        - 'Vercel'
+        - 'Zeabur'
+        - 'Sealos'
+        - 'Netlify'
+        - 'Self hosting Docker'
+        - 'Other'
+    validations:
+      required: false
+
+  - type: dropdown
+    attributes:
+      label: '🔧 Deployment Mode'
+      multiple: true
+      options:
+        - 'client db (lobe-chat image)'
+        - 'client pgelite db (lobe-chat-pglite image)'
+        - 'server db (lobe-chat-database image)'
+    validations:
+      required: true
+
+  - type: input
+    attributes:
+      label: '📌 Version'
+    validations:
+      required: true
+
  - type: dropdown
    attributes:
      label: '🌐 Browser'
@@ -49,21 +76,49 @@ body:
        - 'Other'
    validations:
      required: true
+
  - type: textarea
    attributes:
      label: '🐛 Bug Description'
      description: A clear and concise description of the bug, if the above option is `Other`, please also explain in detail.
    validations:
      required: true
+
  - type: textarea
    attributes:
      label: '📷 Recurrence Steps'
      description: A clear and concise description of how to recurrence.
+
  - type: textarea
    attributes:
      label: '🚦 Expected Behavior'
      description: A clear and concise description of what you expected to happen.
+
  - type: textarea
    attributes:
      label: '📝 Additional Information'
      description: If your problem needs further explanation, or if the issue you're seeing cannot be reproduced in a gist, please add more information here.
+
+  - type: dropdown
+    attributes:
+      label: '🛠️ Willing to Submit a PR?'
+      description: Would you be willing to submit a pull request to fix this bug?
+      options:
+        - 'Yes, I am willing to submit a PR'
+        - 'No, but I am happy to help test the fix'
+    validations:
+      required: false
+
+  - type: checkboxes
+    attributes:
+      label: '✅ Validations'
+      description: Before submitting the issue, please make sure you do the following
+      options:
+        - label: Read the [docs](https://lobehub.com/zh/docs).
+          required: true
+        - label: Check that there isn't [already an issue](https://github.com/lobehub/lobe-chat/issues) that reports the same bug to avoid creating a duplicate.
+          required: true
+        - label: Make sure this is a LobeChat issue and not a third-party library or provider issue.
+          required: true
+        - label: Check that this is a concrete bug. For Q&A, please use [GitHub Discussions](https://github.com/lobehub/lobe-chat/discussions) or join our [Discord Server](https://discord.gg/rGHwKq4R).
+          required: true
@@ -1,69 +0,0 @@
-name: '🐛 反馈缺陷'
-description: '反馈一个问题缺陷'
-title: '[Bug] '
-labels: ['🐛 Bug']
-body:
-  - type: dropdown
-    attributes:
-      label: '📦 部署环境'
-      multiple: true
-      options:
-        - 'Official Preview'
-        - 'Vercel'
-        - 'Zeabur'
-        - 'Sealos'
-        - 'Netlify'
-        - 'Docker'
-        - 'Other'
-    validations:
-      required: true
-  - type: input
-    attributes:
-      label: '📌 软件版本'
-    validations:
-      required: true
-
-  - type: dropdown
-    attributes:
-      label: '💻 系统环境'
-      multiple: true
-      options:
-        - 'Windows'
-        - 'macOS'
-        - 'Ubuntu'
-        - 'Other Linux'
-        - 'iOS'
-        - 'Android'
-        - 'Other'
-    validations:
-      required: true
-  - type: dropdown
-    attributes:
-      label: '🌐 浏览器'
-      multiple: true
-      options:
-        - 'Chrome'
-        - 'Edge'
-        - 'Safari'
-        - 'Firefox'
-        - 'Other'
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: '🐛 问题描述'
-      description: 请提供一个清晰且简洁的问题描述，若上述选项为`Other`，也请详细说明。
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: '📷 复现步骤'
-      description: 请提供一个清晰且简洁的描述，说明如何复现问题。
-  - type: textarea
-    attributes:
-      label: '🚦 期望结果'
-      description: 请提供一个清晰且简洁的描述，说明您期望发生什么。
-  - type: textarea
-    attributes:
-      label: '📝 补充信息'
-      description: 如果您的问题需要进一步说明，或者您遇到的问题无法在一个简单的示例中复现，请在这里添加更多信息。
@@ -1,7 +1,7 @@
 name: '🌠 Feature Request'
 description: 'Suggest an idea'
 title: '[Request] '
-labels: ['🌠 Feature Request']
+type: Feature
 body:
  - type: textarea
    attributes:
@@ -1,21 +0,0 @@
-name: '🌠 功能需求'
-description: '提出需求或建议'
-title: '[Request] '
-labels: ['🌠 Feature Request']
-body:
-  - type: textarea
-    attributes:
-      label: '🥰 需求描述'
-      description: 请添加一个清晰且简洁的问题描述，阐述您希望通过这个功能需求解决的问题。
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: '🧐 解决方案'
-      description: 请清晰且简洁地描述您想要的解决方案。
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: '📝 补充信息'
-      description: 在这里添加关于问题的任何其他背景信息。
@@ -1,4 +1,7 @@
 contact_links:
-  - name: Questions and ideas | 问题和想法
+  - name: Ask a question for self-hosting
+    url: https://github.com/lobehub/lobe-chat/discussions/new?category=self-hosting-%E7%A7%81%E6%9C%89%E5%8C%96%E9%83%A8%E7%BD%B2
+    about: Please post questions, and ideas in discussions.
+  - name: Questions and ideas
    url: https://github.com/lobehub/lobe-chat/discussions/new/choose
-    about: Please post questions, and ideas in discussions. | 请在讨论区发布问题和想法。
+    about: Please post questions, and ideas in discussions.
@@ -1,4 +1,4 @@
-#### 💻 变更类型 | Change Type
+#### 💻 Change Type

 <!-- For change type, change [ ] to [x]. -->

@@ -8,13 +8,40 @@
 - [ ] 💄 style
 - [ ] 👷 build
 - [ ] ⚡️ perf
+- [ ] ✅ test
 - [ ] 📝 docs
 - [ ] 🔨 chore

-#### 🔀 变更说明 | Description of Change
+#### 🔗 Related Issue
+
+<!-- Link to the issue that is fixed by this PR -->
+
+<!-- Example: Fixes #123, Closes #456, Related to #789 -->
+
+#### 🔀 Description of Change

 <!-- Thank you for your Pull Request. Please provide a description above. -->

-#### 📝 补充信息 | Additional Information
+#### 🧪 How to Test
+
+<!-- Please describe how you tested your changes -->
+
+<!-- For AI features, please include test prompts or scenarios -->
+
+- [ ] Tested locally
+- [ ] Added/updated tests
+- [ ] No tests needed
+
+#### 📸 Screenshots / Videos
+
+<!-- If this PR includes UI changes, please provide screenshots or videos -->
+
+| Before | After |
+| ------ | ----- |
+| ...    | ...   |
+
+#### 📝 Additional Information

 <!-- Add any other context about the Pull Request here. -->
+
+<!-- Breaking changes? Migration guide? Performance impact? -->
@@ -0,0 +1,260 @@
+#!/usr/bin/env bun
+
+declare global {
+  // @ts-ignore
+  // eslint-disable-next-line no-var
+  var process: {
+    env: Record<string, string | undefined>;
+  };
+}
+
+interface GitHubIssue {
+  created_at: string;
+  number: number;
+  title: string;
+  user: { id: number };
+}
+
+interface GitHubComment {
+  body: string;
+  created_at: string;
+  id: number;
+  user: { id: number; type: string };
+}
+
+interface GitHubReaction {
+  content: string;
+  user: { id: number };
+}
+
+async function githubRequest<T>(
+  endpoint: string,
+  token: string,
+  method: string = 'GET',
+  body?: any,
+): Promise<T> {
+  const response = await fetch(`https://api.github.com${endpoint}`, {
+    headers: {
+      'Accept': 'application/vnd.github.v3+json',
+      'Authorization': `Bearer ${token}`,
+      'User-Agent': 'auto-close-duplicates-script',
+      ...(body && { 'Content-Type': 'application/json' }),
+    },
+    method,
+    ...(body && { body: JSON.stringify(body) }),
+  });
+
+  if (!response.ok) {
+    throw new Error(`GitHub API request failed: ${response.status} ${response.statusText}`);
+  }
+
+  return response.json();
+}
+
+function extractDuplicateIssueNumber(commentBody: string): number | null {
+  // Try to match #123 format first
+  let match = commentBody.match(/#(\d+)/);
+  if (match) {
+    return parseInt(match[1], 10);
+  }
+
+  // Try to match GitHub issue URL format: https://github.com/owner/repo/issues/123
+  match = commentBody.match(/github\.com\/[^/]+\/[^/]+\/issues\/(\d+)/);
+  if (match) {
+    return parseInt(match[1], 10);
+  }
+
+  return null;
+}
+
+async function closeIssueAsDuplicate(
+  owner: string,
+  repo: string,
+  issueNumber: number,
+  duplicateOfNumber: number,
+  token: string,
+): Promise<void> {
+  await githubRequest(`/repos/${owner}/${repo}/issues/${issueNumber}`, token, 'PATCH', {
+    labels: ['duplicate'],
+    state: 'closed',
+    state_reason: 'duplicate',
+  });
+
+  await githubRequest(`/repos/${owner}/${repo}/issues/${issueNumber}/comments`, token, 'POST', {
+    body: `This issue has been automatically closed as a duplicate of #${duplicateOfNumber}.
+
+If this is incorrect, please re-open this issue or create a new one.
+
+🤖 Generated with [Claude Code](https://claude.ai/code)`,
+  });
+}
+
+async function autoCloseDuplicates(): Promise<void> {
+  console.log('[DEBUG] Starting auto-close duplicates script');
+
+  const token = process.env.GITHUB_TOKEN;
+  if (!token) {
+    throw new Error('GITHUB_TOKEN environment variable is required');
+  }
+  console.log('[DEBUG] GitHub token found');
+
+  const owner = process.env.GITHUB_REPOSITORY_OWNER || 'lobehub';
+  const repo = process.env.GITHUB_REPOSITORY_NAME || 'lobe-chat';
+  console.log(`[DEBUG] Repository: ${owner}/${repo}`);
+
+  const threeDaysAgo = new Date();
+  threeDaysAgo.setDate(threeDaysAgo.getDate() - 3);
+  console.log(`[DEBUG] Checking for duplicate comments older than: ${threeDaysAgo.toISOString()}`);
+
+  console.log('[DEBUG] Fetching open issues created more than 3 days ago...');
+  const allIssues: GitHubIssue[] = [];
+  let page = 1;
+  const perPage = 100;
+
+  // eslint-disable-next-line no-constant-condition
+  while (true) {
+    const pageIssues: GitHubIssue[] = await githubRequest(
+      `/repos/${owner}/${repo}/issues?state=open&per_page=${perPage}&page=${page}`,
+      token,
+    );
+
+    if (pageIssues.length === 0) break;
+
+    // Filter for issues created more than 3 days ago
+    const oldEnoughIssues = pageIssues.filter(
+      (issue) => new Date(issue.created_at) <= threeDaysAgo,
+    );
+
+    allIssues.push(...oldEnoughIssues);
+    page++;
+
+    // Safety limit to avoid infinite loops
+    if (page > 20) break;
+  }
+
+  const issues = allIssues;
+  console.log(`[DEBUG] Found ${issues.length} open issues`);
+
+  let processedCount = 0;
+  let candidateCount = 0;
+
+  for (const issue of issues) {
+    processedCount++;
+    console.log(
+      `[DEBUG] Processing issue #${issue.number} (${processedCount}/${issues.length}): ${issue.title}`,
+    );
+
+    console.log(`[DEBUG] Fetching comments for issue #${issue.number}...`);
+    const comments: GitHubComment[] = await githubRequest(
+      `/repos/${owner}/${repo}/issues/${issue.number}/comments`,
+      token,
+    );
+    console.log(`[DEBUG] Issue #${issue.number} has ${comments.length} comments`);
+
+    const dupeComments = comments.filter(
+      (comment) =>
+        comment.body.includes('Found') &&
+        comment.body.includes('possible duplicate') &&
+        comment.user.type === 'Bot',
+    );
+    console.log(
+      `[DEBUG] Issue #${issue.number} has ${dupeComments.length} duplicate detection comments`,
+    );
+
+    if (dupeComments.length === 0) {
+      console.log(`[DEBUG] Issue #${issue.number} - no duplicate comments found, skipping`);
+      continue;
+    }
+
+    const lastDupeComment = dupeComments.at(-1);
+    // @ts-ignore
+    const dupeCommentDate = new Date(lastDupeComment.created_at);
+    console.log(
+      `[DEBUG] Issue #${
+        issue.number
+      } - most recent duplicate comment from: ${dupeCommentDate.toISOString()}`,
+    );
+
+    if (dupeCommentDate > threeDaysAgo) {
+      console.log(`[DEBUG] Issue #${issue.number} - duplicate comment is too recent, skipping`);
+      continue;
+    }
+    console.log(
+      `[DEBUG] Issue #${issue.number} - duplicate comment is old enough (${Math.floor(
+        (Date.now() - dupeCommentDate.getTime()) / (1000 * 60 * 60 * 24),
+      )} days)`,
+    );
+
+    const commentsAfterDupe = comments.filter(
+      (comment) => new Date(comment.created_at) > dupeCommentDate,
+    );
+    console.log(
+      `[DEBUG] Issue #${issue.number} - ${commentsAfterDupe.length} comments after duplicate detection`,
+    );
+
+    if (commentsAfterDupe.length > 0) {
+      console.log(
+        `[DEBUG] Issue #${issue.number} - has activity after duplicate comment, skipping`,
+      );
+      continue;
+    }
+
+    console.log(`[DEBUG] Issue #${issue.number} - checking reactions on duplicate comment...`);
+    const reactions: GitHubReaction[] = await githubRequest(
+      // @ts-ignore
+      `/repos/${owner}/${repo}/issues/comments/${lastDupeComment.id}/reactions`,
+      token,
+    );
+    console.log(
+      `[DEBUG] Issue #${issue.number} - duplicate comment has ${reactions.length} reactions`,
+    );
+
+    const authorThumbsDown = reactions.some(
+      (reaction) => reaction.user.id === issue.user.id && reaction.content === '-1',
+    );
+    console.log(
+      `[DEBUG] Issue #${issue.number} - author thumbs down reaction: ${authorThumbsDown}`,
+    );
+
+    if (authorThumbsDown) {
+      console.log(
+        `[DEBUG] Issue #${issue.number} - author disagreed with duplicate detection, skipping`,
+      );
+      continue;
+    }
+
+    // @ts-ignore
+    const duplicateIssueNumber = extractDuplicateIssueNumber(lastDupeComment.body);
+    if (!duplicateIssueNumber) {
+      console.log(
+        `[DEBUG] Issue #${issue.number} - could not extract duplicate issue number from comment, skipping`,
+      );
+      continue;
+    }
+
+    candidateCount++;
+    const issueUrl = `https://github.com/${owner}/${repo}/issues/${issue.number}`;
+
+    try {
+      console.log(
+        `[INFO] Auto-closing issue #${issue.number} as duplicate of #${duplicateIssueNumber}: ${issueUrl}`,
+      );
+      await closeIssueAsDuplicate(owner, repo, issue.number, duplicateIssueNumber, token);
+      console.log(
+        `[SUCCESS] Successfully closed issue #${issue.number} as duplicate of #${duplicateIssueNumber}`,
+      );
+    } catch (error) {
+      console.error(`[ERROR] Failed to close issue #${issue.number} as duplicate: ${error}`);
+    }
+  }
+
+  console.log(
+    `[DEBUG] Script completed. Processed ${processedCount} issues, found ${candidateCount} candidates for auto-close`,
+  );
+}
+
+// eslint-disable-next-line unicorn/prefer-top-level-await
+autoCloseDuplicates().catch(console.error);
+
+// Make it a module
+export {};
@@ -0,0 +1,256 @@
+/**
+ * Create or update GitHub issue when i18n workflow fails
+ * Usage: node create-failure-issue.js
+ */
+
+module.exports = async ({ github, context, core }) => {
+  const runUrl = `https://github.com/${context.repo.owner}/${context.repo.repo}/actions/runs/${context.runId}`;
+  const timestamp = new Date().toISOString();
+  const date = timestamp.split('T')[0];
+
+  // Get error details from environment variables
+  const errorDetails = {
+    validateEnv: process.env.ERROR_VALIDATE_ENV || '',
+    rebaseAttempt: process.env.ERROR_REBASE_ATTEMPT || '',
+    createBranch: process.env.ERROR_CREATE_BRANCH || '',
+    installDeps: process.env.ERROR_INSTALL_DEPS || '',
+    runI18n: process.env.ERROR_RUN_I18N || '',
+    commitPush: process.env.ERROR_COMMIT_PUSH || '',
+  };
+
+  // Get step conclusions from environment variables
+  const stepStatus = {
+    validateEnv: process.env.STEP_VALIDATE_ENV || 'Not run',
+    checkBranch: process.env.STEP_CHECK_BRANCH || 'Not run',
+    rebaseAttempt: process.env.STEP_REBASE_ATTEMPT || 'Not run',
+    createBranch: process.env.STEP_CREATE_BRANCH || 'Not run',
+    installDeps: process.env.STEP_INSTALL_DEPS || 'Not run',
+    runI18n: process.env.STEP_RUN_I18N || 'Not run',
+    commitPush: process.env.STEP_COMMIT_PUSH || 'Not run',
+    createPr: process.env.STEP_CREATE_PR || 'Not run',
+  };
+
+  // Find the first non-empty error
+  const mainError =
+    Object.values(errorDetails).find((error) => error && error.trim()) || 'Unknown error occurred';
+
+  // Determine error category for better troubleshooting
+  const getErrorCategory = (error) => {
+    if (error.includes('API') || error.includes('authentication')) return 'API/Authentication';
+    if (error.includes('network') || error.includes('timeout')) return 'Network/Connectivity';
+    if (error.includes('dependencies') || error.includes('bun')) return 'Dependencies';
+    if (error.includes('git') || error.includes('branch') || error.includes('rebase'))
+      return 'Git Operations';
+    if (error.includes('permission') || error.includes('token')) return 'Permissions';
+    return 'General';
+  };
+
+  const errorCategory = getErrorCategory(mainError);
+
+  const issueTitle = `🚨 Daily i18n Update Failed - ${date}`;
+
+  const issueBody = `## 🚨 Automated i18n Update Failure
+
+**Timestamp:** ${timestamp}  
+**Workflow Run:** [#${context.runNumber}](${runUrl})  
+**Repository:** ${context.repo.owner}/${context.repo.repo}  
+**Branch:** ${context.ref}  
+**Commit:** ${context.sha}
+
+## ❌ Error Details
+**Primary Error:** ${mainError}  
+**Category:** ${errorCategory}
+
+## 🔍 Step Status
+| Step | Status |
+|------|--------|
+| Environment Validation | ${stepStatus.validateEnv} |
+| Branch Check | ${stepStatus.checkBranch} |
+| Rebase Attempt | ${stepStatus.rebaseAttempt} |
+| Branch Creation | ${stepStatus.createBranch} |
+| Dependencies | ${stepStatus.installDeps} |
+| i18n Update | ${stepStatus.runI18n} |
+| Git Operations | ${stepStatus.commitPush} |
+| PR Creation | ${stepStatus.createPr} |
+
+## 🔧 Environment Info
+- **Runner OS:** ${process.env.RUNNER_OS || 'Unknown'}
+- **Bun Version:** ${process.env.BUN_VERSION || 'Default'}
+- **Workflow:** \`${context.workflow}\`
+
+## 📋 Debug Information
+Debug logs have been uploaded as artifacts and will be available for 7 days.
+
+${getErrorCategoryHelp(errorCategory)}
+
+## 🛠️ General Troubleshooting Steps
+1. Check if all required secrets are properly configured
+2. Verify OpenAI API quota and billing status  
+3. Review the workflow run logs for detailed error messages
+4. Check if there are any ongoing GitHub API issues
+5. Manually trigger the workflow to retry
+
+## 📊 Workflow Statistics
+- **Run Number:** ${context.runNumber}
+- **Run ID:** ${context.runId}
+- **Event:** ${context.eventName}
+
+---
+**Auto-generated by:** [\`${context.workflow}\`](${runUrl})  
+**Labels:** automated, bug, i18n, workflow-failure, ${errorCategory.toLowerCase().replace(/[^a-z0-9]/g, '-')}`;
+
+  try {
+    // Search for existing open issues with similar title
+    const existingIssues = await github.rest.issues.listForRepo({
+      owner: context.repo.owner,
+      repo: context.repo.repo,
+      labels: 'automated,workflow-failure',
+      state: 'open',
+      per_page: 50,
+    });
+
+    const todayPrefix = `🚨 Daily i18n Update Failed - ${date}`;
+    const existingIssue = existingIssues.data.find((issue) => issue.title.startsWith(todayPrefix));
+
+    if (existingIssue) {
+      // Update existing issue with comment
+      const commentBody = `## 🔄 Additional Failure
+
+**Timestamp:** ${timestamp}  
+**Workflow Run:** [#${context.runNumber}](${runUrl})  
+**Error Category:** ${errorCategory}  
+**Error:** ${mainError}
+
+Same issue occurred again. Please investigate the recurring problem.
+
+### Quick Actions
+- [ ] Check API quotas and billing
+- [ ] Verify network connectivity
+- [ ] Review recent changes that might cause conflicts
+- [ ] Consider manual intervention
+
+---
+*This is failure #${(await getFailureCount(github, context, existingIssue.number)) + 1} for today.*`;
+
+      await github.rest.issues.createComment({
+        owner: context.repo.owner,
+        repo: context.repo.repo,
+        issue_number: existingIssue.number,
+        body: commentBody,
+      });
+
+      // Add priority label if this is a recurring issue
+      const failureCount = await getFailureCount(github, context, existingIssue.number);
+      if (failureCount >= 2) {
+        await github.rest.issues.addLabels({
+          owner: context.repo.owner,
+          repo: context.repo.repo,
+          issue_number: existingIssue.number,
+          labels: ['priority-high', 'recurring'],
+        });
+      }
+
+      core.info(`✅ Updated existing issue #${existingIssue.number}`);
+      core.setOutput('issue-number', existingIssue.number);
+      core.setOutput('issue-url', existingIssue.html_url);
+      core.setOutput('action', 'updated');
+    } else {
+      // Create new issue
+      const labels = [
+        'automated',
+        'bug',
+        'i18n',
+        'workflow-failure',
+        errorCategory.toLowerCase().replace(/[^a-z0-9]/g, '-'),
+      ];
+
+      const issue = await github.rest.issues.create({
+        owner: context.repo.owner,
+        repo: context.repo.repo,
+        title: issueTitle,
+        body: issueBody,
+        labels: labels,
+      });
+
+      core.info(`✅ Created new issue #${issue.data.number}`);
+      core.setOutput('issue-number', issue.data.number);
+      core.setOutput('issue-url', issue.data.html_url);
+      core.setOutput('action', 'created');
+    }
+  } catch (error) {
+    core.setFailed(`Failed to create or update issue: ${error.message}`);
+    throw error;
+  }
+};
+
+/**
+ * Get category-specific help text
+ */
+function getErrorCategoryHelp(category) {
+  const helpTexts = {
+    'API/Authentication': `
+### 🔑 API/Authentication Issues
+- Verify \`OPENAI_API_KEY\` is correctly set and valid
+- Check if API key has sufficient quota/credits
+- Ensure \`GH_TOKEN\` has necessary permissions
+- Test API connectivity manually`,
+
+    'Network/Connectivity': `
+### 🌐 Network/Connectivity Issues  
+- Check if OpenAI API is experiencing outages
+- Verify proxy settings if using \`OPENAI_PROXY_URL\`
+- Retry the workflow as this might be temporary
+- Check GitHub Actions service status`,
+
+    'Dependencies': `
+### 📦 Dependencies Issues
+- Verify \`bun\` version compatibility
+- Check for package.json changes that might affect dependencies
+- Clear cache and retry installation
+- Review recent dependency updates`,
+
+    'Git Operations': `
+### 🔧 Git Operations Issues
+- Check for conflicting changes in target branch
+- Verify repository permissions
+- Review recent commits that might cause conflicts
+- Manual branch cleanup might be required`,
+
+    'Permissions': `
+### 🔐 Permissions Issues
+- Verify \`GH_TOKEN\` has \`repo\` and \`issues\` permissions
+- Check if token can create/update PRs and branches
+- Ensure token hasn't expired
+- Review repository settings and branch protection rules`,
+
+    'General': `
+### 🔍 General Issues
+- Review detailed error logs in workflow run
+- Check for recent changes in codebase
+- Verify all environment variables are set
+- Consider running workflow manually with debug enabled`,
+  };
+
+  return helpTexts[category] || helpTexts['General'];
+}
+
+/**
+ * Count how many times this issue has failed today
+ */
+async function getFailureCount(github, context, issueNumber) {
+  try {
+    const comments = await github.rest.issues.listComments({
+      owner: context.repo.owner,
+      repo: context.repo.repo,
+      issue_number: issueNumber,
+    });
+
+    const today = new Date().toISOString().split('T')[0];
+    return comments.data.filter(
+      (comment) =>
+        comment.body.includes('Additional Failure') && comment.created_at.startsWith(today),
+    ).length;
+  } catch (error) {
+    return 0;
+  }
+}
@@ -0,0 +1,89 @@
+/**
+ * Generate or update PR comment with Docker build info
+ */
+module.exports = async ({
+  github,
+  context,
+  dockerMetaJson,
+  image,
+  version,
+  dockerhubUrl,
+  platforms,
+}) => {
+  const COMMENT_IDENTIFIER = '<!-- DOCKER-BUILD-COMMENT -->';
+
+  const parseTags = () => {
+    try {
+      if (dockerMetaJson) {
+        const parsed = JSON.parse(dockerMetaJson);
+        if (Array.isArray(parsed.tags) && parsed.tags.length > 0) {
+          return parsed.tags;
+        }
+      }
+    } catch (e) {
+      // ignore parsing error, fallback below
+    }
+    if (image && version) {
+      return [`${image}:${version}`];
+    }
+    return [];
+  };
+
+  const generateCommentBody = () => {
+    const tags = parseTags();
+    const buildTime = new Date().toISOString();
+
+    // Use the first tag as the main version
+    const mainTag = tags.length > 0 ? tags[0] : `${image}:${version}`;
+    const tagVersion = mainTag.includes(':') ? mainTag.split(':')[1] : version;
+
+    return [
+      COMMENT_IDENTIFIER,
+      '',
+      '### 🐳 Database Docker Build Completed!',
+      `**Version**: \`${tagVersion || 'N/A'}\``,
+      `**Build Time**: \`${buildTime}\``,
+      '',
+      dockerhubUrl ? `🔗 View all tags on Docker Hub: ${dockerhubUrl}` : '',
+      '',
+      '### Pull Image',
+      'Download the Docker image to your local machine:',
+      '',
+      '```bash',
+      `docker pull ${mainTag}`,
+      '```',
+      '> [!IMPORTANT]',
+      '> This build is for testing and validation purposes.',
+    ]
+      .filter(Boolean)
+      .join('\n');
+  };
+
+  const body = generateCommentBody();
+
+  // List comments on the PR
+  const { data: comments } = await github.rest.issues.listComments({
+    issue_number: context.issue.number,
+    owner: context.repo.owner,
+    repo: context.repo.repo,
+  });
+
+  const existing = comments.find((c) => c.body && c.body.includes(COMMENT_IDENTIFIER));
+  if (existing) {
+    await github.rest.issues.updateComment({
+      comment_id: existing.id,
+      owner: context.repo.owner,
+      repo: context.repo.repo,
+      body,
+    });
+    return { updated: true, id: existing.id };
+  }
+
+  const result = await github.rest.issues.createComment({
+    issue_number: context.issue.number,
+    owner: context.repo.owner,
+    repo: context.repo.repo,
+    body,
+  });
+  return { updated: false, id: result.data.id };
+};
@@ -0,0 +1,78 @@
+// @ts-check
+/**
+ * Lock closed issues after 7 days of inactivity
+ * @param {object} github - GitHub API client
+ * @param {object} context - GitHub Actions context
+ */
+module.exports = async ({ github, context }) => {
+  const sevenDaysAgo = new Date();
+  sevenDaysAgo.setDate(sevenDaysAgo.getDate() - 7);
+
+  const lockComment = `This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.`;
+
+  let page = 1;
+  let hasMore = true;
+  let totalLocked = 0;
+
+  while (hasMore) {
+    // Get closed issues (pagination)
+    const { data: issues } = await github.rest.issues.listForRepo({
+      owner: context.repo.owner,
+      repo: context.repo.repo,
+      state: 'closed',
+      sort: 'updated',
+      direction: 'asc',
+      per_page: 100,
+      page: page,
+    });
+
+    if (issues.length === 0) {
+      hasMore = false;
+      break;
+    }
+
+    for (const issue of issues) {
+      // Skip if already locked
+      if (issue.locked) continue;
+
+      // Skip pull requests
+      if (issue.pull_request) continue;
+
+      // Check if updated more than 7 days ago
+      const updatedAt = new Date(issue.updated_at);
+      if (updatedAt > sevenDaysAgo) {
+        // Since issues are sorted by updated_at ascending,
+        // once we hit a recent issue, all remaining will be recent too
+        hasMore = false;
+        break;
+      }
+
+      try {
+        // Add comment before locking
+        await github.rest.issues.createComment({
+          owner: context.repo.owner,
+          repo: context.repo.repo,
+          issue_number: issue.number,
+          body: lockComment,
+        });
+
+        // Lock the issue
+        await github.rest.issues.lock({
+          owner: context.repo.owner,
+          repo: context.repo.repo,
+          issue_number: issue.number,
+          lock_reason: 'resolved',
+        });
+
+        totalLocked++;
+        console.log(`Locked issue #${issue.number}: ${issue.title}`);
+      } catch (error) {
+        console.error(`Failed to lock issue #${issue.number}: ${error.message}`);
+      }
+    }
+
+    page++;
+  }
+
+  console.log(`Total issues locked: ${totalLocked}`);
+};
@@ -0,0 +1,140 @@
+/**
+ * Generate PR comment with download links for desktop builds
+ * and handle comment creation/update logic
+ */
+module.exports = async ({ github, context, releaseUrl, version, tag }) => {
+  // 用于识别构建评论的标识符
+  const COMMENT_IDENTIFIER = '<!-- DESKTOP-BUILD-COMMENT -->';
+
+  /**
+   * 生成评论内容
+   */
+  const generateCommentBody = async () => {
+    try {
+      // Get release assets to create download links
+      const release = await github.rest.repos.getReleaseByTag({
+        owner: context.repo.owner,
+        repo: context.repo.repo,
+        tag,
+      });
+
+      // Organize assets by platform
+      const macAssets = release.data.assets.filter(
+        (asset) =>
+          (asset.name.includes('.dmg') || asset.name.includes('.zip')) &&
+          !asset.name.includes('.blockmap'),
+      );
+
+      const winAssets = release.data.assets.filter(
+        (asset) => asset.name.includes('.exe') && !asset.name.includes('.blockmap'),
+      );
+
+      const linuxAssets = release.data.assets.filter(
+        (asset) => asset.name.includes('.AppImage') && !asset.name.includes('.blockmap'),
+      );
+
+      // Generate combined download table
+      let assetTable = '| Platform | File | Size |\n| --- | --- | --- |\n';
+
+      // Add macOS assets with architecture detection
+      macAssets.forEach((asset) => {
+        const sizeInMB = (asset.size / (1024 * 1024)).toFixed(2);
+
+        // Detect architecture from filename
+        let architecture = '';
+        if (asset.name.includes('arm64')) {
+          architecture = ' (Apple Silicon)';
+        } else if (asset.name.includes('x64') || asset.name.includes('-mac.')) {
+          architecture = ' (Intel)';
+        }
+
+        assetTable += `| macOS${architecture} | [${asset.name}](${asset.browser_download_url}) | ${sizeInMB} MB |\n`;
+      });
+
+      // Add Windows assets
+      winAssets.forEach((asset) => {
+        const sizeInMB = (asset.size / (1024 * 1024)).toFixed(2);
+        assetTable += `| Windows | [${asset.name}](${asset.browser_download_url}) | ${sizeInMB} MB |\n`;
+      });
+
+      // Add Linux assets
+      linuxAssets.forEach((asset) => {
+        const sizeInMB = (asset.size / (1024 * 1024)).toFixed(2);
+        assetTable += `| Linux | [${asset.name}](${asset.browser_download_url}) | ${sizeInMB} MB |\n`;
+      });
+
+      return `${COMMENT_IDENTIFIER}
+### 🚀 Desktop App Build Completed!
+
+**Version**: \`${version}\`
+**Build Time**: \`${new Date().toISOString()}\`
+
+📦 [View All Build Artifacts](${releaseUrl})
+
+
+## Build Artifacts
+
+${assetTable}
+
+> [!Warning]
+>
+> Note: This is a temporary build for testing purposes only.`;
+    } catch (error) {
+      console.error('Error generating PR comment:', error);
+      // Fallback to a simple comment if error occurs
+      return `${COMMENT_IDENTIFIER}
+### 🚀 Desktop App Build Completed!
+
+**Version**: \`${version}\`
+**Build Time**: \`${new Date().toISOString()}\`
+
+## 📦 [View All Build Artifacts](${releaseUrl})
+
+> Note: This is a temporary build for testing purposes only.
+      `;
+    }
+  };
+
+  /**
+   * 查找并更新或创建PR评论
+   */
+  const updateOrCreateComment = async () => {
+    // 生成评论内容
+    const body = await generateCommentBody();
+
+    // 查找我们之前可能创建的评论
+    const { data: comments } = await github.rest.issues.listComments({
+      issue_number: context.issue.number,
+      owner: context.repo.owner,
+      repo: context.repo.repo,
+    });
+
+    // 查找包含我们标识符的评论
+    const buildComment = comments.find((comment) => comment.body.includes(COMMENT_IDENTIFIER));
+
+    if (buildComment) {
+      // 如果找到现有评论，则更新它
+      await github.rest.issues.updateComment({
+        comment_id: buildComment.id,
+        owner: context.repo.owner,
+        repo: context.repo.repo,
+        body: body,
+      });
+      console.log(`已更新现有评论 ID: ${buildComment.id}`);
+      return { updated: true, id: buildComment.id };
+    } else {
+      // 如果没有找到现有评论，则创建新评论
+      const result = await github.rest.issues.createComment({
+        issue_number: context.issue.number,
+        owner: context.repo.owner,
+        repo: context.repo.repo,
+        body: body,
+      });
+      console.log(`已创建新评论 ID: ${result.data.id}`);
+      return { updated: false, id: result.data.id };
+    }
+  };
+
+  // 执行评论更新或创建
+  return await updateOrCreateComment();
+};
@@ -0,0 +1,62 @@
+/**
+ * Generate PR pre-release body content
+ * This script generates the description text for PR pre-releases
+ */
+module.exports = ({ version, prNumber, branch }) => {
+  const prLink = `https://github.com/lobehub/lobe-chat/pull/${prNumber}`;
+
+  return `
+## PR Build Information
+
+**Version**: \`${version}\`
+**Release Time**: \`${new Date().toISOString()}\`
+**PR**: [#${prNumber}](${prLink})
+
+
+## ⚠️ Important Notice
+
+This is a **development build** specifically created for testing purposes. Please note:
+
+- This build is **NOT** intended for production use
+- Features may be incomplete or unstable
+- Use only for validating PR changes in a desktop environment
+- May contain experimental code that hasn't been fully reviewed
+- No guarantees are provided regarding stability or reliability
+
+### Intended Use
+
+- Focused testing of specific PR changes
+- Verification of desktop-specific behaviors
+- UI/UX validation on desktop platforms
+- Performance testing on target devices
+
+Please report any issues found in this build directly in the PR discussion.
+
+---
+
+## PR 构建信息
+
+**版本**: \`${version}\`
+**发布时间**: \`${new Date().toISOString()}\`
+**PR**: [#${prNumber}](${prLink})
+
+## ⚠️ 重要提示
+
+这是专为测试目的创建的**开发构建版本**。请注意:
+
+- 本构建**不适用于**生产环境
+- 功能可能不完整或不稳定
+- 仅用于在桌面环境中验证 PR 更改
+- 可能包含尚未完全审核的实验性代码
+- 不对稳定性或可靠性提供任何保证
+
+### 适用场景
+
+- 针对性测试特定 PR 变更
+- 验证桌面特定的行为表现
+- 在桌面平台上进行 UI/UX 验证
+- 在目标设备上进行性能测试
+
+如发现任何问题，请直接在 PR 讨论中报告。
+`;
+};
@@ -0,0 +1,71 @@
+name: Daily i18n Update
+
+on:
+  schedule:
+    - cron: '0 0 * * *'
+  workflow_dispatch:
+
+# Add permissions configuration
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  update-i18n:
+    runs-on: ubuntu-latest
+    timeout-minutes: 30
+
+    steps:
+      - name: Configure Git
+        run: |
+          git config --global user.name "lobehubbot"
+          git config --global user.email "i@lobehub.com"
+
+      - uses: actions/checkout@v5
+        with:
+          ref: ${{ github.event.pull_request.head.ref }}
+
+      - name: Install bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: ${{ secrets.BUN_VERSION }}
+
+      - name: Install deps
+        run: bun i
+
+      - name: Update i18n
+        run: bun run i18n
+        env:
+          OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
+          OPENAI_PROXY_URL: ${{ secrets.OPENAI_PROXY_URL }}
+
+      - name: create pull request
+        id: cpr
+        uses: peter-evans/create-pull-request@v7
+        with:
+          token: ${{ secrets.GH_TOKEN }}
+          add-paths: |
+            locales/**/*.json
+          labels: |
+            i18n
+            automated
+            style
+          branch: style/auto-i18n
+          delete-branch: true
+          title: '🤖 style: update i18n'
+          commit-message: '💄 style: update i18n'
+          body: |
+            This PR was automatically generated by the i18n update workflow.
+            Please review the changes and merge if everything looks good.
+
+            ## 🤖 Automation Info
+              - Workflow: `${{ github.workflow }}`
+              - Run ID: `${{ github.run_id }}`
+              - Commit: `${{ github.sha }}`
+
+            <details>
+            <summary>i18n Update Log</summary>
+            ```bash
+            $(cat i18n_update.log)
+            ```
+            </details>
@@ -0,0 +1,73 @@
+name: Claude Auto Testing Coverage
+description: Automatically add unit tests to improve code coverage
+
+on:
+  schedule:
+    # Run daily at 05:30 UTC (13:30 Beijing Time)
+    - cron: '30 5 * * *'
+  workflow_dispatch:
+    inputs:
+      target_module:
+        description: 'Specific module to add tests (e.g., packages/database, src/services/user)'
+        required: false
+        type: string
+
+concurrency:
+  group: auto-testing
+  cancel-in-progress: false
+
+jobs:
+  add-tests:
+    runs-on: ubuntu-latest
+    timeout-minutes: 45
+    permissions:
+      contents: write
+      pull-requests: write
+      id-token: write
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 1
+
+      - name: Setup Bun
+        uses: oven-sh/setup-bun@v2
+
+      - name: Install dependencies
+        run: bun install --frozen-lockfile
+
+      - name: Configure Git
+        run: |
+          git config --global user.name "claude-bot[bot]"
+          git config --global user.email "claude-bot[bot]@users.noreply.github.com"
+
+      - name: Copy testing prompt
+        run: |
+          mkdir -p /tmp/claude-prompts
+          cp .claude/prompts/auto-testing.md /tmp/claude-prompts/
+
+      - name: Run Claude Code for Auto Testing
+        uses: anthropics/claude-code-action@main
+        with:
+          github_token: ${{ secrets.GH_TOKEN }}
+          allowed_non_write_users: "*"
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          claude_args: "--allowed-tools Bash,Read,Edit,Write,Glob,Grep"
+          prompt: |
+            Follow the auto testing guide located at:
+            ```bash
+            cat /tmp/claude-prompts/auto-testing.md
+            ```
+
+            ## Task Assignment
+
+            ${{ inputs.target_module && format('Process the specified module: {0}', inputs.target_module) || 'Automatically select one module from the target directories that needs test coverage' }}
+
+            ## Environment Information
+            - Repository: ${{ github.repository }}
+            - Branch: ${{ github.ref_name }}
+            - Target Module: ${{ inputs.target_module || 'Auto-select' }}
+            - Run ID: ${{ github.run_id }}
+
+            **Start the auto testing process now.**
@@ -0,0 +1,33 @@
+name: Claude Issue Dedupe
+description: Automatically dedupe GitHub issues using Claude Code
+on:
+  issues:
+    types: [opened]
+  workflow_dispatch:
+    inputs:
+      issue_number:
+        description: 'Issue number to process for duplicate detection'
+        required: true
+        type: string
+
+jobs:
+  claude-dedupe-issues:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    permissions:
+      contents: read
+      issues: write
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 1
+
+      - name: Run Claude Code slash command
+        uses: anthropics/claude-code-action@main
+        with:
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          allowed_non_write_users: "*"
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          prompt: '/dedupe ${{ github.repository }}/issues/${{ github.event.issue.number || inputs.issue_number }}'
@@ -0,0 +1,65 @@
+name: Claude Issue Triage
+description: Automatically triage GitHub issues using Claude Code
+on:
+  issues:
+    types: [opened, labeled]
+
+jobs:
+  triage-issue:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    # Only run on issue opened, or when "trigger:triage" label is added
+    if: github.event.action == 'opened' || (github.event.action == 'labeled' && github.event.label.name == 'trigger:triage')
+    permissions:
+      contents: read
+      issues: write
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v5
+
+      - name: Copy triage prompts
+        run: |
+          mkdir -p /tmp/claude-prompts
+          cp .claude/prompts/team-assignment.md /tmp/claude-prompts/
+          cp .claude/prompts/issue-triage.md /tmp/claude-prompts/
+
+      - name: Run Claude Code for Issue Triage
+        uses: anthropics/claude-code-action@main
+        with:
+          github_token: ${{ secrets.GH_TOKEN }}
+          allowed_non_write_users: "*"
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          claude_args: "--allowed-tools Bash(gh *),Read"
+          prompt: |
+            You're an issue triage assistant for GitHub issues. Your task is to analyze issues, apply appropriate labels, and mention the responsible team member.
+
+            REPOSITORY: ${{ github.repository }}
+            ISSUE_NUMBER: ${{ github.event.issue.number }}
+
+            ## Instructions
+
+            Follow the complete triage guide located at:
+            ```bash
+            cat /tmp/claude-prompts/issue-triage.md
+            ```
+
+            Read the team assignment guide for determining team members:
+            ```bash
+            cat /tmp/claude-prompts/team-assignment.md
+            ```
+
+            **IMPORTANT**:
+            - Follow ALL steps in the issue-triage.md guide
+            - Apply labels according to the guide's rules
+            - Post a mention comment to the appropriate team member(s) based on team-assignment.md
+            - Replace [ISSUE_NUMBER] with: ${{ github.event.issue.number }}
+
+            **Start the triage process now.**
+
+      - name: Remove trigger label
+        if: github.event.action == 'labeled' && github.event.label.name == 'trigger:triage'
+        run: |
+          gh issue edit ${{ github.event.issue.number }} --remove-label "trigger:triage"
+        env:
+          GH_TOKEN: ${{ secrets.GH_TOKEN }}
@@ -0,0 +1,67 @@
+name: Claude Translate Non-English Comments
+description: Automatically detect and translate non-English comments to English in codebase
+
+on:
+  schedule:
+    # Run daily at 02:00 UTC (10:00 Beijing Time)
+    - cron: '0 2 * * *'
+  workflow_dispatch:
+    inputs:
+      target_module:
+        description: 'Specific module to translate (e.g., packages/database, apps/desktop/src/modules/auth)'
+        required: false
+        type: string
+
+concurrency:
+  group: translate-comments
+  cancel-in-progress: false
+
+jobs:
+  translate-comments:
+    runs-on: ubuntu-latest
+    timeout-minutes: 30
+    permissions:
+      contents: write
+      pull-requests: write
+      id-token: write
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 1
+
+      - name: Configure Git
+        run: |
+          git config --global user.name "claude-bot[bot]"
+          git config --global user.email "claude-bot[bot]@users.noreply.github.com"
+
+      - name: Copy translation prompt
+        run: |
+          mkdir -p /tmp/claude-prompts
+          cp .claude/prompts/translate-comments.md /tmp/claude-prompts/
+
+      - name: Run Claude Code for Comment Translation
+        uses: anthropics/claude-code-action@main
+        with:
+          github_token: ${{ secrets.GH_TOKEN }}
+          allowed_non_write_users: "*"
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          claude_args: "--allowed-tools Bash,Read,Edit,Glob,Grep"
+          prompt: |
+            Follow the translation guide located at:
+            ```bash
+            cat /tmp/claude-prompts/translate-comments.md
+            ```
+
+            ## Task Assignment
+
+            ${{ inputs.target_module && format('Process the specified module: {0}', inputs.target_module) || 'Automatically select one module from the target directories that has not been processed recently' }}
+
+            ## Environment Information
+            - Repository: ${{ github.repository }}
+            - Branch: ${{ github.ref_name }}
+            - Target Module: ${{ inputs.target_module || 'Auto-select' }}
+            - Run ID: ${{ github.run_id }}
+
+            **Start the translation process now.**
@@ -0,0 +1,121 @@
+name: Claude Translator
+concurrency:
+  group: translator-${{ github.event.comment.id || github.event.issue.number || github.event.review.id }}
+  cancel-in-progress: false
+
+on:
+  issues:
+    types: [opened]
+  issue_comment:
+    types: [created, edited]
+  pull_request_review:
+    types: [submitted, edited]
+  pull_request_review_comment:
+    types: [created, edited]
+
+jobs:
+  translate:
+    if: |
+      (github.event_name == 'issues') ||
+      (github.event_name == 'issue_comment' && github.event.sender.type != 'Bot') ||
+      (github.event_name == 'pull_request_review' && github.event.sender.type != 'Bot') ||
+      (github.event_name == 'pull_request_review_comment' && github.event.sender.type != 'Bot')
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+    permissions:
+      contents: read
+      # update issues/comments
+      issues: write
+      pull-requests: write
+      id-token: write
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 1
+
+      - name: Run Claude for translation
+        uses: anthropics/claude-code-action@main
+        id: claude
+        with:
+          # Warning: Permissions should have been controlled by workflow permission.
+          # Now `contents: read` is safe for files, but we could make a fine-grained token to control it.
+          # See: https://github.com/anthropics/claude-code-action/blob/main/docs/security.md
+          github_token: ${{ secrets.GH_TOKEN }}
+          allowed_non_write_users: "*"
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          claude_args: "--allowed-tools Bash(gh issue:*),Bash(gh api:repos/*/issues:*),Bash(gh api:repos/*/pulls/*/reviews/*),Bash(gh api:repos/*/pulls/comments/*)"
+          prompt: |
+            You are a multilingual translation assistant. You need to respond to the following four types of GitHub Webhook events:
+
+            - issues
+            - issue_comment
+            - pull_request_review
+            - pull_request_review_comment
+
+            Please complete the following tasks:
+
+            1. Retrieve complete information for the current event.
+
+               - If the current event is 'issues', get the issue information.
+               - If the current event is 'issue_comment', get the comment information.
+               - If the current event is 'pull_request_review', get the review information.
+               - If the current event is 'pull_request_review_comment', get the comment information.
+
+            2. Intelligently detect content.
+
+                - If the retrieved information is already translated content following the format requirements, check if the translation matches the original content. If not, retranslate to match and follow the format requirements.
+                - If the retrieved information is untranslated content, check its language. If not in English, translate to English.
+                - If the retrieved information is partially translated to English, translate it completely to English.
+                - If the retrieved information contains references to already translated content, clean the referenced content to contain only English. Referenced content should not include "This xxx was translated by Claude" and "Original Content" etc.
+                - If the retrieved information contains other types of references (i.e., references to non-Claude translated content), keep them as-is without translation.
+                - If the retrieved information is email reply content, place email content references at the end during translation. Include only the reply content itself in both original and translated content, without email content references.
+                - If the retrieved information doesn't need any processing, skip the task.
+
+            3. Format requirements:
+
+               - Title: English translation (if non-English)
+               - Content format:
+                 [Translated content]
+
+                 ---
+                 > This issue/comment/review was translated by Claude.
+
+                 <details>
+                 <summary>Original Content</summary>
+                 [Original content]
+                 </details>
+
+            4. CRITICAL RULES to prevent hallucination and ensure accuracy:
+
+               - The "Original Content" section MUST contain the EXACT, UNMODIFIED original text byte-for-byte. NEVER add, remove, modify, or hallucinate ANY content in this section.
+               - Code blocks, error logs, JSON structures, and other technical content MUST appear in BOTH the translated section AND the original content section WITHOUT ANY MODIFICATION.
+               - When translating content with code/logs/JSON:
+                 * Copy the code/logs/JSON blocks identically to both sections
+                 * Only translate the natural language text (e.g., Chinese, Japanese) surrounding the code blocks
+                 * Keep all technical content (URLs, variable names, error messages in English) unchanged
+               - ALWAYS verify the "Original Content" section matches the source text exactly before updating
+               - If you detect any discrepancy, retrieve the original content again to ensure accuracy
+               - Pay special attention to the end of comments - do not drop or hallucinate the last sentences
+
+            5. Update using gh tool:
+
+               - Choose the correct command based on the Event type in environment information:
+                 - If Event is 'issues': gh issue edit [ISSUE_NUMBER] --title "[English title]" --body "[Translated content + Original content]"
+                 - If Event is 'issue_comment': gh api -X PATCH /repos/${{ github.repository }}/issues/comments/${{ github.event.comment.id }} -f body="[Translated content + Original content]"
+                 - If Event is 'pull_request_review': gh api -X PUT /repos/${{ github.repository }}/pulls/${{ github.event.pull_request.number }}/reviews/${{ github.event.review.id }} -f body="[Translated content]"
+                 - If Event is 'pull_request_review_comment': gh api -X PATCH /repos/${{ github.repository }}/pulls/comments/${{ github.event.comment.id }} -f body="[Translated content + Original content]"
+
+            <environment_context>
+            - Event: ${{ github.event_name }}
+            - Issue Number: ${{ github.event.issue.number }}
+            - Repository: ${{ github.repository }}
+            - (Review) Comment ID: ${{ github.event.comment.id || 'N/A' }}
+            - Pull Request Number: ${{ github.event.pull_request.number || 'N/A' }}
+            - Review ID: ${{ github.event.review.id || 'N/A' }}
+            </environment_context>
+
+
+            Use the following command to get complete information:
+            gh issue view ${{ github.event.issue.number }} --json title,body,comments
@@ -0,0 +1,64 @@
+name: Claude Code
+
+on:
+  issue_comment:
+    types: [created]
+  pull_request_review_comment:
+    types: [created]
+  issues:
+    types: [opened, assigned]
+  pull_request_review:
+    types: [submitted]
+
+jobs:
+  claude:
+    if: |
+      (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude')) ||
+      (github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@claude')) ||
+      (github.event_name == 'pull_request_review' && contains(github.event.review.body, '@claude')) ||
+      (github.event_name == 'issues' && (contains(github.event.issue.body, '@claude') || contains(github.event.issue.title, '@claude')))
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: read
+      issues: read
+      id-token: write
+      actions: read # Required for Claude to read CI results on PRs
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 1
+
+      - name: Run Claude Code
+        id: claude
+        uses: anthropics/claude-code-action@beta
+        with:
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+
+          # This is an optional setting that allows Claude to read CI results on PRs
+          additional_permissions: |
+            actions: read
+
+          # Optional: Specify model (defaults to Claude Sonnet 4, uncomment for Claude Opus 4)
+          # model: 'claude-opus-4-1-20250805'
+          allowed_bots: 'bot'
+
+          # Optional: Customize the trigger phrase (default: @claude)
+          # trigger_phrase: "/claude"
+
+          # Optional: Trigger when specific user is assigned to an issue
+          # assignee_trigger: "claude-bot"
+
+          # Optional: Allow Claude to run specific commands
+          allowed_tools: 'Bash(bun run:*),Bash(pnpm run:*),Bash(npm run:*),Bash(npx:*),Bash(bunx:*),Bash(vitest:*),Bash(rg:*),Bash(find:*),Bash(sed:*),Bash(grep:*),Bash(awk:*),Bash(wc:*),Bash(xargs:*)'
+
+          # Optional: Add custom instructions for Claude to customize its behavior for your project
+          # custom_instructions: |
+          #   Follow our coding standards
+          #   Ensure all new code has tests
+          #   Use TypeScript for new files
+
+          # Optional: Custom environment variables for Claude
+          # claude_env: |
+          #   NODE_ENV: test
@@ -0,0 +1,358 @@
+name: Desktop PR Build
+
+on:
+  pull_request_target:
+    types: [synchronize, labeled, unlabeled] # PR 更新或标签变化时触发
+
+# 确保同一 PR 同一时间只运行一个相同的 workflow，取消正在进行的旧的运行
+concurrency:
+  group: pr-${{ github.event.pull_request.number }}-${{ github.workflow }}
+  cancel-in-progress: true
+
+# Add default permissions
+permissions:
+  contents: write
+  pull-requests: write
+
+env:
+  PR_TAG_PREFIX: pr- # PR 构建版本的前缀标识
+
+jobs:
+  test:
+    name: Code quality check
+    # 添加 PR label 触发条件，只有添加了 trigger:build-desktop 标签的 PR 才会触发构建
+    if: contains(github.event.pull_request.labels.*.name, 'trigger:build-desktop')
+    runs-on: ubuntu-latest # 只在 ubuntu 上运行一次检查
+    steps:
+      - name: Checkout base
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: 24
+          package-manager-cache: false
+
+      - name: Install bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: 1.2.23
+
+      - name: Install deps
+        run: bun i
+        env:
+          NODE_OPTIONS: --max-old-space-size=6144
+
+      - name: Lint
+        run: bun run lint
+        env:
+          NODE_OPTIONS: --max-old-space-size=6144
+
+  version:
+    name: Determine version
+    # 与 test job 相同的触发条件
+    if: contains(github.event.pull_request.labels.*.name, 'trigger:build-desktop')
+    runs-on: ubuntu-latest
+    outputs:
+      # 输出版本信息，供后续 job 使用
+      version: ${{ steps.set_version.outputs.version }}
+    steps:
+      - uses: actions/checkout@v5
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: 24
+          package-manager-cache: false
+
+      # 主要逻辑：确定构建版本号
+      - name: Set version
+        id: set_version
+        run: |
+          # 从 apps/desktop/package.json 读取基础版本号
+          base_version=$(node -p "require('./apps/desktop/package.json').version")
+
+          # PR 构建：在基础版本号上添加 PR 信息
+          pr_number="${{ github.event.pull_request.number }}"
+          ci_build_number="${{ github.run_number }}" # CI 构建编号
+          version="0.0.0-nightly.pr${pr_number}.${ci_build_number}"
+          echo "version=${version}" >> $GITHUB_OUTPUT
+          echo "📦 Release Version: ${version} (based on base version ${base_version})"
+
+        env:
+          NODE_OPTIONS: --max-old-space-size=6144
+
+      # 输出版本信息总结，方便在 GitHub Actions 界面查看
+      - name: Version Summary
+        run: |
+          echo "🚦 Release Version: ${{ steps.set_version.outputs.version }}"
+
+  build:
+    needs: [version, test]
+    name: Build Desktop App
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [macos-latest, macos-15-intel, windows-2025, ubuntu-latest]
+    steps:
+      - uses: actions/checkout@v5
+        with:
+          fetch-depth: 0
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          run_install: false
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: 24
+          package-manager-cache: false
+
+      # node-linker=hoisted 模式将可以确保 asar 压缩可用
+      - name: Install dependencies
+        run: pnpm install --node-linker=hoisted
+
+      - name: Install deps on Desktop
+        run: npm run install-isolated --prefix=./apps/desktop
+
+      # 设置 package.json 的版本号
+      - name: Set package version
+        run: npm run workflow:set-desktop-version ${{ needs.version.outputs.version }} nightly
+
+      # macOS 构建处理
+      - name: Build artifact on macOS
+        if: runner.os == 'macOS'
+        run: npm run desktop:build
+        env:
+          # 设置更新通道，PR构建为nightly，否则为stable
+          UPDATE_CHANNEL: "nightly"
+          APP_URL: http://localhost:3015
+          DATABASE_URL: "postgresql://postgres@localhost:5432/postgres"
+          # 默认添加一个加密 SECRET
+          KEY_VAULTS_SECRET: "oLXWIiR/AKF+rWaqy9lHkrYgzpATbW3CtJp3UfkVgpE="
+          # macOS 签名和公证配置
+          CSC_LINK: ${{ secrets.APPLE_CERTIFICATE_BASE64 }}
+          CSC_KEY_PASSWORD: ${{ secrets.APPLE_CERTIFICATE_PASSWORD }}
+          NEXT_PUBLIC_DESKTOP_PROJECT_ID: ${{ secrets.UMAMI_NIGHTLY_DESKTOP_PROJECT_ID }}
+          NEXT_PUBLIC_DESKTOP_UMAMI_BASE_URL: ${{ secrets.UMAMI_NIGHTLY_DESKTOP_BASE_URL }}
+
+          # allow provisionally
+          CSC_FOR_PULL_REQUEST: true
+          APPLE_ID: ${{ secrets.APPLE_ID }}
+          APPLE_APP_SPECIFIC_PASSWORD: ${{ secrets.APPLE_APP_SPECIFIC_PASSWORD }}
+          APPLE_TEAM_ID: ${{ secrets.APPLE_TEAM_ID }}
+
+      #  Windows 平台构建处理
+      - name: Build artifact on Windows
+        if: runner.os == 'Windows'
+        run: npm run desktop:build
+        env:
+          # 设置更新通道，PR构建为nightly，否则为stable
+          UPDATE_CHANNEL: "nightly"
+          APP_URL: http://localhost:3015
+          DATABASE_URL: "postgresql://postgres@localhost:5432/postgres"
+          KEY_VAULTS_SECRET: "oLXWIiR/AKF+rWaqy9lHkrYgzpATbW3CtJp3UfkVgpE="
+          NEXT_PUBLIC_DESKTOP_PROJECT_ID: ${{ secrets.UMAMI_NIGHTLY_DESKTOP_PROJECT_ID }}
+          NEXT_PUBLIC_DESKTOP_UMAMI_BASE_URL: ${{ secrets.UMAMI_NIGHTLY_DESKTOP_BASE_URL }}
+          # 将 TEMP 和 TMP 目录设置到 C 盘
+          TEMP: C:\temp
+          TMP: C:\temp
+
+      # Linux 平台构建处理
+      - name: Build artifact on Linux
+        if: runner.os == 'Linux'
+        run: npm run desktop:build
+        env:
+          # 设置更新通道，PR构建为nightly，否则为stable
+          UPDATE_CHANNEL: "nightly"
+          APP_URL: http://localhost:3015
+          DATABASE_URL: "postgresql://postgres@localhost:5432/postgres"
+          KEY_VAULTS_SECRET: "oLXWIiR/AKF+rWaqy9lHkrYgzpATbW3CtJp3UfkVgpE="
+          NEXT_PUBLIC_DESKTOP_PROJECT_ID: ${{ secrets.UMAMI_NIGHTLY_DESKTOP_PROJECT_ID }}
+          NEXT_PUBLIC_DESKTOP_UMAMI_BASE_URL: ${{ secrets.UMAMI_NIGHTLY_DESKTOP_BASE_URL }}
+
+      # 处理 macOS latest-mac.yml 重命名 (避免多架构覆盖)
+      - name: Rename macOS latest-mac.yml for multi-architecture support
+        if: runner.os == 'macOS'
+        run: |
+          cd apps/desktop/release
+          if [ -f "latest-mac.yml" ]; then
+            # 使用系统架构检测，与 electron-builder 输出保持一致
+            SYSTEM_ARCH=$(uname -m)
+            if [[ "$SYSTEM_ARCH" == "arm64" ]]; then
+              ARCH_SUFFIX="arm64"
+            else
+              ARCH_SUFFIX="x64"
+            fi
+
+            mv latest-mac.yml "latest-mac-${ARCH_SUFFIX}.yml"
+            echo "✅ Renamed latest-mac.yml to latest-mac-${ARCH_SUFFIX}.yml (detected: $SYSTEM_ARCH)"
+            ls -la latest-mac-*.yml
+          else
+            echo "⚠️ latest-mac.yml not found, skipping rename"
+            ls -la latest*.yml || echo "No latest*.yml files found"
+          fi
+
+      # 上传构建产物
+      - name: Upload artifact
+        uses: actions/upload-artifact@v5
+        with:
+          name: release-${{ matrix.os }}
+          path: |
+            apps/desktop/release/latest*
+            apps/desktop/release/*.dmg*
+            apps/desktop/release/*.zip*
+            apps/desktop/release/*.exe*
+            apps/desktop/release/*.AppImage
+            apps/desktop/release/*.deb*
+            apps/desktop/release/*.snap*
+            apps/desktop/release/*.rpm*
+            apps/desktop/release/*.tar.gz*
+          retention-days: 5
+
+  # 合并 macOS 多架构 latest-mac.yml 文件
+  merge-mac-files:
+    needs: [build, version]
+    name: Merge macOS Release Files for PR
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v5
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: 24
+          package-manager-cache: false
+
+      - name: Install bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: 1.2.23
+
+      # 下载所有平台的构建产物
+      - name: Download artifacts
+        uses: actions/download-artifact@v6
+        with:
+          path: release
+          pattern: release-*
+          merge-multiple: true
+
+      # 列出下载的构建产物
+      - name: List downloaded artifacts
+        run: ls -R release
+
+      # 仅为该步骤在脚本目录安装 yaml 单包，避免安装整个 monorepo 依赖
+      - name: Install yaml only for merge step
+        run: |
+          cd scripts/electronWorkflow
+          # 在脚本目录创建最小 package.json，防止 bun 向上寻找根 package.json
+          if [ ! -f package.json ]; then
+            echo '{"name":"merge-mac-release","private":true}' > package.json
+          fi
+          bun add --no-save yaml@2.8.1
+
+      # 合并 macOS YAML 文件 (使用 bun 运行 JavaScript)
+      - name: Merge latest-mac.yml files
+        run: bun run scripts/electronWorkflow/mergeMacReleaseFiles.js
+
+      # 上传合并后的构建产物
+      - name: Upload artifacts with merged macOS files
+        uses: actions/upload-artifact@v5
+        with:
+          name: merged-release-pr
+          path: release/
+          retention-days: 1
+
+  publish-pr:
+    needs: [merge-mac-files, version]
+    name: Publish PR Build
+    runs-on: ubuntu-latest
+    # Grant write permissions for creating release and commenting on PR
+    permissions:
+      contents: write
+      pull-requests: write
+    outputs:
+      artifact_path: ${{ steps.set_path.outputs.path }}
+    steps:
+      - uses: actions/checkout@v5
+        with:
+          fetch-depth: 0
+
+      # 下载合并后的构建产物
+      - name: Download merged artifacts
+        uses: actions/download-artifact@v6
+        with:
+          name: merged-release-pr
+          path: release
+
+      # 列出所有构建产物
+      - name: List final artifacts
+        run: ls -R release
+
+      # 生成PR发布描述
+      - name: Generate PR Release Body
+        id: pr_release_body
+        uses: actions/github-script@v8
+        with:
+          result-encoding: string
+          script: |
+            const generateReleaseBody = require('${{ github.workspace }}/.github/scripts/pr-release-body.js');
+
+            const body = generateReleaseBody({
+              version: "${{ needs.version.outputs.version }}",
+              prNumber: "${{ github.event.pull_request.number }}",
+              branch: "${{ github.head_ref }}"
+            });
+
+            return body;
+
+      - name: Create Temporary Release for PR
+        id: create_release
+        uses: softprops/action-gh-release@v1
+        with:
+          name: PR Build v${{ needs.version.outputs.version }}
+          tag_name: v${{ needs.version.outputs.version }}
+          #          tag_name: pr-build-${{ github.event.pull_request.number }}-${{ github.sha }}
+          body: ${{ steps.pr_release_body.outputs.result }}
+          draft: false
+          prerelease: true
+          files: |
+            release/latest*
+            release/*.dmg*
+            release/*.zip*
+            release/*.exe*
+            release/*.AppImage
+            release/*.deb*
+            release/*.snap*
+            release/*.rpm*
+            release/*.tar.gz*
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      # 在 PR 上添加评论，包含构建信息和下载链接
+      - name: Comment on PR
+        uses: actions/github-script@v8
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+          script: |
+            const releaseUrl = "${{ steps.create_release.outputs.url }}";
+            const prCommentGenerator = require('${{ github.workspace }}/.github/scripts/pr-comment.js');
+
+            const result = await prCommentGenerator({
+              github,
+              context,
+              releaseUrl,
+              version: "${{ needs.version.outputs.version }}",
+              tag: "v${{ needs.version.outputs.version }}"
+            });
+
+            console.log(`评论状态: ${result.updated ? '已更新' : '已创建'}, ID: ${result.id}`);
@@ -1,46 +0,0 @@
-name: Publish Database Docker Image
-
-on:
-  workflow_dispatch:
-  release:
-    types: [published]
-
-jobs:
-  push_to_registry:
-    name: Push Docker image to Docker Hub
-    runs-on: ubuntu-latest
-    steps:
-      - name: Check out the repo
-        uses: actions/checkout@v4
-      - name: Log in to Docker Hub
-        uses: docker/login-action@v3
-        with:
-          username: ${{ secrets.DOCKER_REGISTRY_USER }}
-          password: ${{ secrets.DOCKER_REGISTRY_PASSWORD }}
-
-      - name: Extract metadata (tags, labels) for Docker
-        id: meta
-        uses: docker/metadata-action@v5
-        with:
-          images: lobehub/lobe-chat-database
-          tags: |
-            type=raw,value=latest
-            type=ref,event=tag
-
-      - name: Set up QEMU
-        uses: docker/setup-qemu-action@v3
-
-      - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@v3
-
-      - name: Build and push Docker image
-        uses: docker/build-push-action@v5
-        with:
-          context: .
-          file: ./Dockerfile.database  # 指定使用 Dockerfile.database 文件
-          platforms: linux/amd64,linux/arm64
-          push: true
-          tags: ${{ steps.meta.outputs.tags }}
-          labels: ${{ steps.meta.outputs.labels }}
-          cache-from: type=gha
-          cache-to: type=gha,mode=max
@@ -1,45 +1,186 @@
 name: Publish Docker Image
+permissions:
+  contents: read
+  pull-requests: write

 on:
  workflow_dispatch:
  release:
    types: [published]
+  pull_request_target:
+    types: [synchronize, labeled, unlabeled]
+
+concurrency:
+  group: ${{ github.ref }}-${{ github.workflow }}
+  # PR 构建时取消旧的运行,但 release 构建不取消
+  cancel-in-progress: ${{ github.event_name != 'release' }}
+
+env:
+  REGISTRY_IMAGE: lobehub/lobehub
+  PR_TAG_PREFIX: pr-

 jobs:
-  push_to_registry:
-    name: Push Docker image to Docker Hub
-    runs-on: ubuntu-latest
+  build:
+    # 添加 PR label 触发条件
+    if: |
+      github.event_name == 'release' ||
+      github.event_name == 'workflow_dispatch' ||
+      (github.event_name == 'pull_request_target' &&
+       contains(github.event.pull_request.labels.*.name, 'trigger:build-docker'))
+
+    strategy:
+      matrix:
+        include:
+          - platform: linux/amd64
+            os: ubuntu-latest
+          - platform: linux/arm64
+            os: ubuntu-24.04-arm
+    runs-on: ${{ matrix.os }}
+    name: Build ${{ matrix.platform }} Image
    steps:
-      - name: Check out the repo
-        uses: actions/checkout@v4
-      - name: Log in to Docker Hub
+      - name: Prepare
+        run: |
+          platform=${{ matrix.platform }}
+          echo "PLATFORM_PAIR=${platform//\//-}" >> $GITHUB_ENV
+
+      - name: Checkout base
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 0
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v3
+
+      # 为 PR 生成特殊的 tag
+      - name: Generate PR metadata
+        if: github.event_name == 'pull_request_target'
+        id: pr_meta
+        env:
+          BRANCH_NAME: ${{ github.head_ref }}
+        run: |
+          sanitized_branch=$(echo "${BRANCH_NAME}" | sed -E 's/[^a-zA-Z0-9_.-]+/-/g')
+          echo "pr_tag=${sanitized_branch}-$(git rev-parse --short HEAD)" >> $GITHUB_OUTPUT
+
+      - name: Docker meta
+        id: meta
+        uses: docker/metadata-action@v5
+        with:
+          images: ${{ env.REGISTRY_IMAGE }}
+          tags: |
+            # PR 构建使用特殊的 tag
+            type=raw,value=${{ env.PR_TAG_PREFIX }}${{ steps.pr_meta.outputs.pr_tag }},enable=${{ github.event_name == 'pull_request_target' }}
+            # release 构建使用版本号
+            type=semver,pattern={{version}},enable=${{ github.event_name != 'pull_request_target' }}
+            type=raw,value=latest,enable=${{ github.event_name != 'pull_request_target' }}
+
+      - name: Docker login
        uses: docker/login-action@v3
        with:
          username: ${{ secrets.DOCKER_REGISTRY_USER }}
          password: ${{ secrets.DOCKER_REGISTRY_PASSWORD }}

-      - name: Extract metadata (tags, labels) for Docker
-        id: meta
-        uses: docker/metadata-action@v5
-        with:
-          images: lobehub/lobe-chat
-          tags: |
-            type=raw,value=latest
-            type=ref,event=tag
+      - name: Get commit SHA
+        if: github.ref == 'refs/heads/main'
+        id: vars
+        run: echo "sha_short=$(git rev-parse --short HEAD)" >> $GITHUB_OUTPUT

-      - name: Set up QEMU
-        uses: docker/setup-qemu-action@v3
+      - name: Build and export
+        id: build
+        uses: docker/build-push-action@v6
+        with:
+          platforms: ${{ matrix.platform }}
+          context: .
+          file: ./Dockerfile
+          labels: ${{ steps.meta.outputs.labels }}
+          build-args: |
+            SHA=${{ steps.vars.outputs.sha_short }}
+          outputs: type=image,name=${{ env.REGISTRY_IMAGE }},push-by-digest=true,name-canonical=true,push=true
+
+      - name: Export digest
+        run: |
+          rm -rf /tmp/digests
+          mkdir -p /tmp/digests
+          digest="${{ steps.build.outputs.digest }}"
+          touch "/tmp/digests/${digest#sha256:}"
+
+      - name: Upload artifact
+        uses: actions/upload-artifact@v5
+        with:
+          name: digest-${{ env.PLATFORM_PAIR }}
+          path: /tmp/digests/*
+          if-no-files-found: error
+          retention-days: 1
+
+  merge:
+    name: Merge
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout base
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 0
+
+      - name: Download digests
+        uses: actions/download-artifact@v6
+        with:
+          path: /tmp/digests
+          pattern: digest-*
+          merge-multiple: true

      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v3

-      - name: Build and push Docker image
-        uses: docker/build-push-action@v5
+      # 为 merge job 添加 PR metadata 生成
+      - name: Generate PR metadata
+        if: github.event_name == 'pull_request_target'
+        id: pr_meta
+        env:
+          BRANCH_NAME: ${{ github.head_ref }}
+        run: |
+          sanitized_branch=$(echo "${BRANCH_NAME}" | sed -E 's/[^a-zA-Z0-9_.-]+/-/g')
+          echo "pr_tag=${sanitized_branch}-$(git rev-parse --short HEAD)" >> $GITHUB_OUTPUT
+
+      - name: Docker meta
+        id: meta
+        uses: docker/metadata-action@v5
        with:
-          context: .
-          platforms: linux/amd64,linux/arm64
-          push: true
-          tags: ${{ steps.meta.outputs.tags }}
-          labels: ${{ steps.meta.outputs.labels }}
-          cache-from: type=gha
-          cache-to: type=gha,mode=max
+          images: ${{ env.REGISTRY_IMAGE }}
+          tags: |
+            type=raw,value=${{ env.PR_TAG_PREFIX }}${{ steps.pr_meta.outputs.pr_tag }},enable=${{ github.event_name == 'pull_request_target' }}
+            type=semver,pattern={{version}},enable=${{ github.event_name != 'pull_request_target' }}
+            type=raw,value=latest,enable=${{ github.event_name != 'pull_request_target' }}
+
+      - name: Docker login
+        uses: docker/login-action@v3
+        with:
+          username: ${{ secrets.DOCKER_REGISTRY_USER }}
+          password: ${{ secrets.DOCKER_REGISTRY_PASSWORD }}
+
+      - name: Create manifest list and push
+        working-directory: /tmp/digests
+        run: |
+          docker buildx imagetools create $(jq -cr '.tags | map("-t " + .) | join(" ")' <<< "$DOCKER_METADATA_OUTPUT_JSON") \
+            $(printf '${{ env.REGISTRY_IMAGE }}@sha256:%s ' *)
+
+      - name: Inspect image
+        run: |
+          docker buildx imagetools inspect ${{ env.REGISTRY_IMAGE }}:${{ steps.meta.outputs.version }}
+
+      - name: Comment on PR with Docker build info
+        if: github.event_name == 'pull_request_target'
+        uses: actions/github-script@v8
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+          script: |
+            const prComment = require('${{ github.workspace }}/.github/scripts/docker-pr-comment.js');
+            const result = await prComment({
+              github,
+              context,
+              dockerMetaJson: ${{ toJSON(steps.meta.outputs.json) }},
+              image: "${{ env.REGISTRY_IMAGE }}",
+              version: "${{ steps.meta.outputs.version }}",
+              dockerhubUrl: "https://hub.docker.com/r/${{ env.REGISTRY_IMAGE }}/tags",
+              platforms: "linux/amd64, linux/arm64",
+            });
+            core.info(`Status: ${result.updated ? 'Updated' : 'Created'}, ID: ${result.id}`);
@@ -0,0 +1,66 @@
+name: E2E CI
+permissions:
+  contents: read
+
+on:
+    pull_request:
+    push:
+
+concurrency:
+    group: e2e-${{ github.ref }}
+    cancel-in-progress: true
+
+jobs:
+    e2e:
+        name: Test Web App
+        runs-on: ubuntu-latest
+        services:
+          postgres:
+            image: paradedb/paradedb:latest
+            env:
+              POSTGRES_PASSWORD: postgres
+            options: >-
+              --health-cmd pg_isready --health-interval 10s --health-timeout 5s  --health-retries 5
+
+            ports:
+              - 5432:5432
+
+        timeout-minutes: 25
+        steps:
+            - name: Checkout
+              uses: actions/checkout@v5
+
+            - name: Setup Bun
+              uses: oven-sh/setup-bun@v2
+              with:
+                  bun-version: 1.2.23
+
+            - name: Install dependencies (bun)
+              run: bun install
+
+            - name: Install Playwright browsers (with system deps)
+              run: bunx playwright install --with-deps chromium
+
+            - name: Run E2E tests
+              env:
+                  PORT: 3010
+                  DATABASE_URL: postgresql://postgres:postgres@localhost:5432/postgres
+                  DATABASE_DRIVER: node
+                  KEY_VAULTS_SECRET: LA7n9k3JdEcbSgml2sxfw+4TV1AzaaFU5+R176aQz4s=
+              run: bun run e2e
+
+            - name: Upload Cucumber HTML report (on failure)
+              if: failure()
+              uses: actions/upload-artifact@v5
+              with:
+                  name: cucumber-report
+                  path: e2e/reports
+                  if-no-files-found: ignore
+
+            - name: Upload screenshots (on failure)
+              if: failure()
+              uses: actions/upload-artifact@v5
+              with:
+                  name: test-screenshots
+                  path: e2e/screenshots
+                  if-no-files-found: ignore
@@ -0,0 +1,30 @@
+name: Auto-close duplicate issues
+description: Auto-closes issues that are duplicates of existing issues
+on:
+  schedule:
+    - cron: "0 2 * * *"
+  workflow_dispatch:
+
+jobs:
+  auto-close-duplicates:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    permissions:
+      contents: read
+      issues: write
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v5
+
+      - name: Setup Bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: latest
+
+      - name: Auto-close duplicate issues
+        run: bun run .github/scripts/auto-close-duplicates.ts
+        env:
+          GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
+          GITHUB_REPOSITORY_OWNER: ${{ github.repository_owner }}
+          GITHUB_REPOSITORY_NAME: ${{ github.event.repository.name }}
@@ -28,8 +28,7 @@ jobs:
            👀 @{{ author }}

            Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
-            Please make sure you have given us as much context as possible.\
-            非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。
+            Please make sure you have given us as much context as possible.
      - name: Auto Comment on Issues Closed
        uses: wow-actions/auto-comment@v1
        with:
@@ -37,8 +36,7 @@ jobs:
          issuesClosed: |
            ✅ @{{ author }}

-            This issue is closed, If you have any questions, you can comment and reply.\
-            此问题已经关闭。如果您有任何问题，可以留言并回复。
+            This issue is closed, If you have any questions, you can comment and reply.
      - name: Auto Comment on Pull Request Opened
        uses: wow-actions/auto-comment@v1
        with:
@@ -48,9 +46,7 @@ jobs:

            Thank you for raising your pull request and contributing to our Community
            Please make sure you have followed our contributing guidelines. We will review it as soon as possible.
-            If you encounter any problems, please feel free to connect with us.\
-            非常感谢您提出拉取请求并为我们的社区做出贡献，请确保您已经遵循了我们的贡献指南，我们会尽快审查它。
-            如果您遇到任何问题，请随时与我们联系。
+            If you encounter any problems, please feel free to connect with us.
      - name: Auto Comment on Pull Request Merged
        uses: actions-cool/pr-welcome@main
        if: github.event.pull_request.merged == true
@@ -59,8 +55,7 @@ jobs:
          comment: |
            ❤️ Great PR @${{ github.event.pull_request.user.login }} ❤️

-            The growth of project is inseparable from user feedback and contribution, thanks for your contribution! If you are interesting with the lobehub developer community, please join our [discord](https://discord.com/invite/AYFPHvv2jT) and then dm @arvinxx or @canisminor1990. They will invite you to our private developer channel. We are talking about the lobe-chat development or sharing ai newsletter around the world.\
-            项目的成长离不开用户反馈和贡献，感谢您的贡献! 如果您对 LobeHub 开发者社区感兴趣，请加入我们的 [discord](https://discord.com/invite/AYFPHvv2jT)，然后私信 @arvinxx 或 @canisminor1990。他们会邀请您加入我们的私密开发者频道。我们将会讨论关于 Lobe Chat 的开发，分享和讨论全球范围内的 AI 消息。
+            The growth of project is inseparable from user feedback and contribution, thanks for your contribution! If you are interesting with the lobehub developer community, please join our [discord](https://discord.com/invite/AYFPHvv2jT) and then dm @arvinxx or @canisminor1990. They will invite you to our private developer channel. We are talking about the lobe-chat development or sharing ai newsletter around the world.
          emoji: 'hooray'
          pr-emoji: '+1, heart'
      - name: Remove inactive
@@ -38,8 +38,7 @@ jobs:
          body: |
            👋 @{{ author }}
            <br/>
-            Since the issue was labeled with `✅ Fixed`, but no response in 3 days. This issue will be closed. If you have any questions, you can comment and reply.\
-            由于该 issue 被标记为已修复，同时 3 天未收到回应。现关闭 issue，若有任何问题，可评论回复。
+            Since the issue was labeled with `✅ Fixed`, but no response in 3 days. This issue will be closed. If you have any questions, you can comment and reply.
      - name: need reproduce
        uses: actions-cool/issues-helper@v3
        with:
@@ -50,8 +49,7 @@ jobs:
          body: |
            👋 @{{ author }}
            <br/>
-            Since the issue was labeled with `🤔 Need Reproduce`, but no response in 3 days. This issue will be closed. If you have any questions, you can comment and reply.\
-            由于该 issue 被标记为需要更多信息，却 3 天未收到回应。现关闭 issue，若有任何问题，可评论回复。
+            Since the issue was labeled with `🤔 Need Reproduce`, but no response in 3 days. This issue will be closed. If you have any questions, you can comment and reply.
      - name: need reproduce
        uses: actions-cool/issues-helper@v3
        with:
@@ -62,5 +60,4 @@ jobs:
          body: |
            👋 @{{ github.event.issue.user.login }}
            <br/>
-            Since the issue was labeled with `🙅🏻‍♀️ WON'T DO`, and no response in 3 days. This issue will be closed. If you have any questions, you can comment and reply.\
-            由于该 issue 被标记为暂不处理，同时 3 天未收到回应。现关闭 issue，若有任何问题，可评论回复。
+            Since the issue was labeled with `🙅🏻‍♀️ WON'T DO`, and no response in 3 days. This issue will be closed. If you have any questions, you can comment and reply.
@@ -1,14 +0,0 @@
-name: Issue Translate
-on:
-  issue_comment:
-    types: [created]
-  issues:
-    types: [opened]
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: usthe/issues-translate-action@v2.7
-        with:
-          BOT_GITHUB_TOKEN: ${{ secrets.GH_TOKEN }}
@@ -18,28 +18,20 @@ on:
 jobs:
  lighthouse-badger-advanced:
    name: ${{ matrix.NAME }}
-    runs-on: ubuntu-22.04
+    runs-on: ubuntu-24.04
    timeout-minutes: 8
    strategy:
      fail-fast: false
      matrix:
        include:
-          - NAME: 'LobeChat | Welcome'
-            URLS: 'https://chat-preview.lobehub.com/welcome'
-            BADGES_ARGS: '-b pagespeed -o lighthouse/welcome -r'
-            COMMIT_MESSAGE: '🤖 chore: Lighthouse Results | Welcome'
          - NAME: 'LobeChat | Chat'
-            URLS: 'https://chat-preview.lobehub.com/chat'
+            URLS: 'https://lobechat.com/chat'
            BADGES_ARGS: '-b pagespeed -o lighthouse/chat -r'
            COMMIT_MESSAGE: '🤖 chore: Lighthouse Results | Chat'
          - NAME: 'LobeChat | Market'
-            URLS: 'https://chat-preview.lobehub.com/market'
-            BADGES_ARGS: '-b pagespeed -o lighthouse/market -r'
-            COMMIT_MESSAGE: '🤖 chore: Lighthouse Results | Market'
-          - NAME: 'LobeChat | Settings'
-            URLS: 'https://chat-preview.lobehub.com/settings'
-            BADGES_ARGS: '-b pagespeed -o lighthouse/settings -r'
-            COMMIT_MESSAGE: '🤖 chore: Lighthouse Results | Settings'
+            URLS: 'https://lobechat.com/discover'
+            BADGES_ARGS: '-b pagespeed -o lighthouse/discover -r'
+            COMMIT_MESSAGE: '🤖 chore: Lighthouse Results | Discover'

    steps:
      - name: Preparatory Tasks
@@ -50,12 +42,12 @@ jobs:
          echo "BRANCH=$BRANCH" >> $GITHUB_ENV
        env:
          REPO_BRANCH: ${{ matrix.REPO_BRANCH || env.REPO_BRANCH }}
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
        with:
          repository: ${{ env.REPOSITORY }}
          token: ${{ secrets[matrix.TOKEN_NAME] || secrets[env.TOKEN_NAME] }}
          ref: ${{ env.BRANCH }}
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
        with:
          repository: 'myactionway/lighthouse-badges'
          path: temp_lighthouse_badges_nested
@@ -0,0 +1,26 @@
+name: "Lock Stale Issues"
+
+on:
+  schedule:
+    - cron: "0 1 * * *"
+  workflow_dispatch:
+
+permissions:
+  issues: write
+
+concurrency:
+  group: lock-threads
+
+jobs:
+  lock-closed-issues:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v5
+
+      - name: Lock closed issues after 7 days of inactivity
+        uses: actions/github-script@v8
+        with:
+          script: |
+            const lockScript = require('./.github/scripts/lock-closed-issues.js');
+            await lockScript({ github, context });
@@ -0,0 +1,290 @@
+name: Release Desktop Beta
+
+on:
+  release:
+    types: [published] # 发布 release 时触发构建
+
+# 确保同一时间只运行一个相同的 workflow，取消正在进行的旧的运行
+concurrency:
+  group: ${{ github.ref }}-${{ github.workflow }}
+  cancel-in-progress: true
+
+# Add default permissions
+permissions: read-all
+
+jobs:
+  test:
+    name: Code quality check
+    # 添加 PR label 触发条件，只有添加了 trigger:build-desktop 标签的 PR 才会触发构建
+    runs-on: ubuntu-latest # 只在 ubuntu 上运行一次检查
+    steps:
+      - name: Checkout base
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: 24
+          package-manager-cache: false
+
+      - name: Install bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: 1.2.23
+
+      - name: Install deps
+        run: bun i
+
+      - name: Lint
+        run: bun run lint
+
+  version:
+    name: Determine version
+    runs-on: ubuntu-latest
+    outputs:
+      # 输出版本信息，供后续 job 使用
+      version: ${{ steps.set_version.outputs.version }}
+      is_pr_build: ${{ steps.set_version.outputs.is_pr_build }}
+    steps:
+      - uses: actions/checkout@v5
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: 24
+          package-manager-cache: false
+
+      # 主要逻辑：确定构建版本号
+      - name: Set version
+        id: set_version
+        run: |
+          # 从 apps/desktop/package.json 读取基础版本号
+          base_version=$(node -p "require('./apps/desktop/package.json').version")
+
+          # Release 事件直接使用 release tag 作为版本号，去掉可能的 v 前缀
+          version="${{ github.event.release.tag_name }}"
+          version="${version#v}"
+          echo "version=${version}" >> $GITHUB_OUTPUT
+          echo "📦 Release Version: ${version}"
+
+      # 输出版本信息总结，方便在 GitHub Actions 界面查看
+      - name: Version Summary
+        run: |
+          echo "🚦 Release Version: ${{ steps.set_version.outputs.version }}"
+
+  build:
+    needs: [version, test]
+    name: Build Desktop App
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [macos-latest, macos-15-intel, windows-2025, ubuntu-latest]
+    steps:
+      - uses: actions/checkout@v5
+        with:
+          fetch-depth: 0
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          run_install: false
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: 24
+          package-manager-cache: false
+
+      # node-linker=hoisted 模式将可以确保 asar 压缩可用
+      - name: Install dependencies
+        run: pnpm install --node-linker=hoisted
+
+      - name: Install deps on Desktop
+        run: npm run install-isolated --prefix=./apps/desktop
+
+      # 设置 package.json 的版本号
+      - name: Set package version
+        run: npm run workflow:set-desktop-version ${{ needs.version.outputs.version }} beta
+
+      # macOS 构建处理
+      - name: Build artifact on macOS
+        if: runner.os == 'macOS'
+        run: npm run desktop:build
+        env:
+          APP_URL: http://localhost:3015
+          DATABASE_URL: "postgresql://postgres@localhost:5432/postgres"
+          # 默认添加一个加密 SECRET
+          KEY_VAULTS_SECRET: "oLXWIiR/AKF+rWaqy9lHkrYgzpATbW3CtJp3UfkVgpE="
+          # macOS 签名和公证配置
+          CSC_LINK: ${{ secrets.APPLE_CERTIFICATE_BASE64 }}
+          CSC_KEY_PASSWORD: ${{ secrets.APPLE_CERTIFICATE_PASSWORD }}
+          # allow provisionally
+          CSC_FOR_PULL_REQUEST: true
+          APPLE_ID: ${{ secrets.APPLE_ID }}
+          APPLE_APP_SPECIFIC_PASSWORD: ${{ secrets.APPLE_APP_SPECIFIC_PASSWORD }}
+          APPLE_TEAM_ID: ${{ secrets.APPLE_TEAM_ID }}
+
+          NEXT_PUBLIC_DESKTOP_PROJECT_ID: ${{ secrets.UMAMI_BETA_DESKTOP_PROJECT_ID }}
+          NEXT_PUBLIC_DESKTOP_UMAMI_BASE_URL: ${{ secrets.UMAMI_BETA_DESKTOP_BASE_URL }}
+
+      #  Windows 平台构建处理
+      - name: Build artifact on Windows
+        if: runner.os == 'Windows'
+        run: npm run desktop:build
+        env:
+          APP_URL: http://localhost:3015
+          DATABASE_URL: "postgresql://postgres@localhost:5432/postgres"
+          KEY_VAULTS_SECRET: "oLXWIiR/AKF+rWaqy9lHkrYgzpATbW3CtJp3UfkVgpE="
+          NEXT_PUBLIC_DESKTOP_PROJECT_ID: ${{ secrets.UMAMI_BETA_DESKTOP_PROJECT_ID }}
+          NEXT_PUBLIC_DESKTOP_UMAMI_BASE_URL: ${{ secrets.UMAMI_BETA_DESKTOP_BASE_URL }}
+
+          # 将 TEMP 和 TMP 目录设置到 C 盘
+          TEMP: C:\temp
+          TMP: C:\temp
+
+      # Linux 平台构建处理
+      - name: Build artifact on Linux
+        if: runner.os == 'Linux'
+        run: npm run desktop:build
+        env:
+          APP_URL: http://localhost:3015
+          DATABASE_URL: "postgresql://postgres@localhost:5432/postgres"
+          KEY_VAULTS_SECRET: "oLXWIiR/AKF+rWaqy9lHkrYgzpATbW3CtJp3UfkVgpE="
+          NEXT_PUBLIC_DESKTOP_PROJECT_ID: ${{ secrets.UMAMI_BETA_DESKTOP_PROJECT_ID }}
+          NEXT_PUBLIC_DESKTOP_UMAMI_BASE_URL: ${{ secrets.UMAMI_BETA_DESKTOP_BASE_URL }}
+
+      # 处理 macOS latest-mac.yml 重命名 (避免多架构覆盖)
+      - name: Rename macOS latest-mac.yml for multi-architecture support
+        if: runner.os == 'macOS'
+        run: |
+          cd apps/desktop/release
+          if [ -f "latest-mac.yml" ]; then
+            # 使用系统架构检测，与 electron-builder 输出保持一致
+            SYSTEM_ARCH=$(uname -m)
+            if [[ "$SYSTEM_ARCH" == "arm64" ]]; then
+              ARCH_SUFFIX="arm64"
+            else
+              ARCH_SUFFIX="x64"
+            fi
+
+            mv latest-mac.yml "latest-mac-${ARCH_SUFFIX}.yml"
+            echo "✅ Renamed latest-mac.yml to latest-mac-${ARCH_SUFFIX}.yml (detected: $SYSTEM_ARCH)"
+            ls -la latest-mac-*.yml
+          else
+            echo "⚠️ latest-mac.yml not found, skipping rename"
+            ls -la latest*.yml || echo "No latest*.yml files found"
+          fi
+
+      # 上传构建产物 (工作流处理重命名，不依赖 electron-builder 钩子)
+      - name: Upload artifact
+        uses: actions/upload-artifact@v5
+        with:
+          name: release-${{ matrix.os }}
+          path: |
+            apps/desktop/release/latest*
+            apps/desktop/release/*.dmg*
+            apps/desktop/release/*.zip*
+            apps/desktop/release/*.exe*
+            apps/desktop/release/*.AppImage
+            apps/desktop/release/*.deb*
+            apps/desktop/release/*.snap*
+            apps/desktop/release/*.rpm*
+            apps/desktop/release/*.tar.gz*
+          retention-days: 5
+
+  # 合并 macOS 多架构 latest-mac.yml 文件
+  merge-mac-files:
+    needs: [build, version]
+    name: Merge macOS Release Files
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v5
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: 24
+          package-manager-cache: false
+
+      - name: Install bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: 1.2.23
+
+      # 下载所有平台的构建产物
+      - name: Download artifacts
+        uses: actions/download-artifact@v6
+        with:
+          path: release
+          pattern: release-*
+          merge-multiple: true
+
+      # 列出下载的构建产物
+      - name: List downloaded artifacts
+        run: ls -R release
+
+      # 仅为该步骤在脚本目录安装 yaml 单包，避免安装整个 monorepo 依赖
+      - name: Install yaml only for merge step
+        run: |
+          cd scripts/electronWorkflow
+          # 在脚本目录创建最小 package.json，防止 bun 向上寻找根 package.json
+          if [ ! -f package.json ]; then
+            echo '{"name":"merge-mac-release","private":true}' > package.json
+          fi
+          bun add --no-save yaml@2.8.1
+
+      # 合并 macOS YAML 文件 (使用 bun 运行 JavaScript)
+      - name: Merge latest-mac.yml files
+        run: bun run scripts/electronWorkflow/mergeMacReleaseFiles.js
+
+      # 上传合并后的构建产物
+      - name: Upload artifacts with merged macOS files
+        uses: actions/upload-artifact@v5
+        with:
+          name: merged-release
+          path: release/
+          retention-days: 1
+
+  # 发布所有平台构建产物
+  publish-release:
+    needs: [merge-mac-files]
+    name: Publish Beta Release
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      # 下载合并后的构建产物
+      - name: Download merged artifacts
+        uses: actions/download-artifact@v6
+        with:
+          name: merged-release
+          path: release
+
+      # 列出所有构建产物
+      - name: List final artifacts
+        run: ls -R release
+
+      # 将构建产物上传到现有 release (现在包含合并后的 latest-mac.yml)
+      - name: Upload to Release
+        uses: softprops/action-gh-release@v1
+        with:
+          tag_name: ${{ github.event.release.tag_name }}
+          files: |
+            release/latest*
+            release/*.dmg*
+            release/*.zip*
+            release/*.exe*
+            release/*.AppImage
+            release/*.deb*
+            release/*.snap*
+            release/*.rpm*
+            release/*.tar.gz*
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
@@ -1,8 +1,15 @@
 name: Release CI
+
+permissions:
+  contents: write
+  issues: write
+  pull-requests: write
+
 on:
  push:
    branches:
      - main
+      - next

 jobs:
  release:
@@ -11,21 +18,30 @@ jobs:

    services:
      postgres:
-        image: pgvector/pgvector:pg16
+        image: paradedb/paradedb:latest
        env:
          POSTGRES_PASSWORD: postgres
        options: >-
          --health-cmd pg_isready --health-interval 10s --health-timeout 5s  --health-retries 5
+
        ports:
          - 5432:5432

    steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
+        with:
+          token: ${{ secrets.GH_TOKEN }}
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: 24
+          package-manager-cache: false

      - name: Install bun
-        uses: oven-sh/setup-bun@v1
+        uses: oven-sh/setup-bun@v2
        with:
-          bun-version: ${{ secrets.BUN_VERSION }}
+          bun-version: 1.2.23

      - name: Install deps
        run: bun i
@@ -33,18 +49,17 @@ jobs:
      - name: Lint
        run: bun run lint

-      - name: Test Server Coverage
-        run: bun run test-server:coverage
+      - name: Test Database Coverage
+        run: bun run --filter @lobechat/database test
        env:
          DATABASE_TEST_URL: postgresql://postgres:postgres@localhost:5432/postgres
          DATABASE_DRIVER: node
-          NEXT_PUBLIC_SERVICE_MODE: server
-          KEY_VAULTS_SECRET: LA7n9k3JdEcbSgml2sxfw+4TV1AzaaFU5+R176aQz4s=
+          KEY_VAULTS_SECRET: Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ=
          S3_PUBLIC_DOMAIN: https://example.com
          APP_URL: https://home.com

-      - name: Test App Coverage
-        run: bun run test-app:coverage
+      - name: Test App
+        run: bun run test-app

      - name: Release
        run: bun run release
@@ -0,0 +1,29 @@
+name: Database Schema Visualization CI
+permissions:
+  contents: read
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - 'docs/development/database-schema.dbml'
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v5
+
+      - name: Install bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: ${{ secrets.BUN_VERSION }}
+
+      - name: Install deps
+        run: bun i
+
+      - name: sync database schema to dbdocs
+        env:
+          DBDOCS_TOKEN: ${{ secrets.DBDOCS_TOKEN }}
+        run: npm run db:visualize
@@ -17,7 +17,7 @@ jobs:
    if: ${{ github.event.repository.fork }}

    steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5

      - name: Clean issue notice
        uses: actions-cool/issues-helper@v3
@@ -50,5 +50,5 @@ jobs:
            ![](https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/273954625-df80c890-0822-4ac2-95e6-c990785cbed5.png)

            [lobechat]: https://github.com/lobehub/lobe-chat
-            [tutorial-zh-CN]: https://github.com/lobehub/lobe-chat/wiki/Upstream-Sync.zh-CN
-            [tutorial-en-US]: https://github.com/lobehub/lobe-chat/wiki/Upstream-Sync
+            [tutorial-zh-CN]: https://lobehub.com/zh/docs/self-hosting/advanced/upstream-sync
+            [tutorial-en-US]: https://lobehub.com/docs/self-hosting/advanced/upstream-sync
@@ -2,59 +2,214 @@ name: Test CI

 on: [push, pull_request]

+permissions:
+  contents: read
+
 jobs:
-  test:
+  # Package tests - using each package's own test script
+  test-intenral-packages:
    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        package:
+          - file-loaders
+          - prompts
+          - model-runtime
+          - web-crawler
+          - electron-server-ipc
+          - utils
+          - python-interpreter
+          - context-engine
+          - agent-runtime
+          - conversation-flow

-    services:
-      postgres:
-        image: pgvector/pgvector:pg16
-        env:
-          POSTGRES_PASSWORD: postgres
-        options: >-
-          --health-cmd pg_isready --health-interval 10s --health-timeout 5s  --health-retries 5
-
-
-        ports:
-          - 5432:5432
+    name: Test package ${{ matrix.package }}

    steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: 24
+          package-manager-cache: false

      - name: Install bun
-        uses: oven-sh/setup-bun@v1
+        uses: oven-sh/setup-bun@v2
        with:
          bun-version: ${{ secrets.BUN_VERSION }}

      - name: Install deps
        run: bun i

-      - name: Lint
-        run: bun run lint
+      - name: Test ${{ matrix.package }} package with coverage
+        run: bun run --filter @lobechat/${{ matrix.package }} test:coverage

-      - name: Test Server Coverage
-        run: bun run test-server:coverage
-        env:
-          DATABASE_TEST_URL: postgresql://postgres:postgres@localhost:5432/postgres
-          DATABASE_DRIVER: node
-          NEXT_PUBLIC_SERVICE_MODE: server
-          KEY_VAULTS_SECRET: LA7n9k3JdEcbSgml2sxfw+4TV1AzaaFU5+R176aQz4s=
-          S3_PUBLIC_DOMAIN: https://example.com
-          APP_URL: https://home.com
-
-      - name: Upload Server coverage to Codecov
-        uses: codecov/codecov-action@v4
+      - name: Upload ${{ matrix.package }} coverage to Codecov
+        uses: codecov/codecov-action@v5
        with:
          token: ${{ secrets.CODECOV_TOKEN }}
-          files: ./coverage/server/lcov.info
-          flags: server
+          files: ./packages/${{ matrix.package }}/coverage/lcov.info
+          flags: packages/${{ matrix.package }}
+
+  test-packages:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        package: [model-bank]
+
+    name: Test package ${{ matrix.package }}
+
+    steps:
+      - uses: actions/checkout@v5
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: 24
+          package-manager-cache: false
+
+      - name: Install bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: 1.2.23
+
+      - name: Install deps
+        run: bun i
+
+      - name: Test ${{ matrix.package }} package with coverage
+        run: bun run --filter ${{ matrix.package }} test:coverage
+
+      - name: Upload ${{ matrix.package }} coverage to Codecov
+        uses: codecov/codecov-action@v5
+        with:
+          token: ${{ secrets.CODECOV_TOKEN }}
+          files: ./packages/${{ matrix.package }}/coverage/lcov.info
+          flags: packages/${{ matrix.package }}
+
+  # App tests
+  test-website:
+    name: Test Website
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v5
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: 24
+          package-manager-cache: false
+
+      - name: Install bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: 1.2.23
+
+      - name: Install deps
+        run: bun i

      - name: Test App Coverage
        run: bun run test-app:coverage

      - name: Upload App Coverage to Codecov
-        uses: codecov/codecov-action@v4
+        uses: codecov/codecov-action@v5
        with:
          token: ${{ secrets.CODECOV_TOKEN }}
          files: ./coverage/app/lcov.info
          flags: app
+
+  test-desktop:
+    name: Test Desktop App
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v5
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: 24
+          package-manager-cache: false
+
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v2
+        with:
+          version: 10
+
+      - name: Install deps
+        run: pnpm install
+        working-directory: apps/desktop
+        env:
+          NODE_OPTIONS: --max-old-space-size=6144
+
+
+      - name: Test Desktop Client
+        run: pnpm test
+        working-directory: apps/desktop
+
+      - name: Upload Desktop App Coverage to Codecov
+        uses: codecov/codecov-action@v5
+        with:
+          token: ${{ secrets.CODECOV_TOKEN }}
+          files: ./apps/desktop/coverage/lcov.info
+          flags: desktop
+
+  test-databsae:
+    name: Test Database
+
+    runs-on: ubuntu-latest
+
+    services:
+      postgres:
+        image: paradedb/paradedb:latest
+        env:
+          POSTGRES_PASSWORD: postgres
+        options: >-
+          --health-cmd pg_isready --health-interval 10s --health-timeout 5s  --health-retries 5
+
+        ports:
+          - 5432:5432
+
+    steps:
+      - uses: actions/checkout@v5
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: 24
+          package-manager-cache: false
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
+
+      - name: Install deps
+        run: pnpm i
+
+      - name: Lint
+        run: npm run lint
+
+      - name: Test Client DB
+        run: pnpm --filter @lobechat/database test:client-db
+        env:
+          KEY_VAULTS_SECRET: Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ=
+          S3_PUBLIC_DOMAIN: https://example.com
+          APP_URL: https://home.com
+
+      - name: Test Coverage
+        run: pnpm --filter @lobechat/database test:coverage
+        env:
+          DATABASE_TEST_URL: postgresql://postgres:postgres@localhost:5432/postgres
+          DATABASE_DRIVER: node
+          KEY_VAULTS_SECRET: Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ=
+          S3_PUBLIC_DOMAIN: https://example.com
+          APP_URL: https://home.com
+
+      - name: Upload Database coverage to Codecov
+        uses: codecov/codecov-action@v5
+        with:
+          token: ${{ secrets.CODECOV_TOKEN }}
+          files: ./packages/database/coverage/lcov.info
+          flags: database
@@ -1,19 +0,0 @@
-name: Wiki Sync
-
-on:
-  workflow_dispatch:
-  push:
-    paths:
-      - 'contributing/**'
-    branches:
-      - main
-
-jobs:
-  update-wiki:
-    runs-on: ubuntu-latest
-    name: Wiki sync
-    steps:
-      - uses: OrlovM/Wiki-Action@v1
-        with:
-          path: 'contributing'
-          token: ${{ secrets.GH_TOKEN }}
@@ -1,70 +1,120 @@
 # Gitignore for LobeHub
 ################################################################

-# general
+# System files
 .DS_Store
-.idea
-.vscode
-.history
-.temp
-.env.local
-venv
-temp
-tmp
+Thumbs.db
+ehthumbs.db
+Desktop.ini

-# dependencies
-node_modules
+# Linux/Ubuntu system files
+*~
+*.swp
+*.swo
+.fuse_hidden*
+.directory
+.Trash-*
+.nfs*
+.gvfs-fuse-daemon-*
+
+# IDE and editors
+.idea/
+*.sublime-*
+.history/
+.windsurfrules
+*.code-workspace
+.vscode/sessions.json
+
+# Temporary files
+.temp/
+temp/
+tmp/
+*.tmp
+*.temp
 *.log
+*.cache
+.cache/
+
+# Environment files
+.env
+.env.local
+.env*.local
+.env.development
+venv/
+.venv/
+
+# Dependencies
+node_modules/
 *.lock
 package-lock.json
+bun.lockb
+.pnpm-store/

-# ci
-coverage
-.coverage
+# Build outputs
+dist/
+es/
+lib/
+.next/
+logs/
+test-output/
+*.tsbuildinfo
+next-env.d.ts
+
+# Framework specific
+# Umi
+.umi/
+.umi-production/
+.umi-test/
+.dumi/tmp*/
+
+# Vercel
+.vercel/
+
+# Testing and CI
+coverage/
+.coverage/
+.nyc_output/
 .eslintcache
 .stylelintcache

-# production
-dist
-es
-lib
-logs
-test-output
-
-# umi
-.umi
-.umi-production
-.umi-test
-.dumi/tmp*
-
-# husky
-.husky/prepare-commit-msg
-
-# misc
-# add other ignore file below
-
-# local env files
-.env*.local
-
-# vercel
-.vercel
-
-# typescript
-*.tsbuildinfo
-next-env.d.ts
-.next
-.env
-public/*.js
-public/sitemap.xml
-public/sitemap-index.xml
-bun.lockb
-sitemap*.xml
-robots.txt
-
+# Service Worker
 # Serwist
 public/sw*
 public/swe-worker*

+# Generated files
+public/*.js
+public/sitemap.xml
+public/sitemap-index.xml
+sitemap*.xml
+robots.txt
+
+# Git hooks
+.husky/prepare-commit-msg
+
+# Documents and media
 *.patch
 *.pdf
+
+# Cloud service keys
 vertex-ai-key.json
+
+# AI coding tools
+.local/
+.claude/
+.mcp.json
+
+CLAUDE.local.md
+
+# MCP tools
+.serena/**
+
+# Misc
+./packages/lobe-ui
+*.ppt*
+*.doc*
+*.xls*
+
+prd
+GEMINI.md
+e2e/reports
@@ -24,7 +24,8 @@ module.exports = defineConfig({
    'fa-IR',
  ],
  temperature: 0,
-  modelName: 'gpt-4o-mini',
+  saveImmediately: true,
+  modelName: 'chatgpt-4o-latest',
  experimental: {
    jsonMode: true,
  },
@@ -1,8 +1,10 @@
 lockfile=false
 resolution-mode=highest

+ignore-workspace-root-check=true
 enable-pre-post-scripts=true

+
 public-hoist-pattern[]=*@umijs/lint*
 public-hoist-pattern[]=*changelog*
 public-hoist-pattern[]=*commitlint*
@@ -1 +1 @@
-lts/iron
+lts/Krypton
@@ -5,7 +5,6 @@
 .DS_Store
 .editorconfig
 .idea
-.vscode
 .history
 .temp
 .env.local
@@ -0,0 +1,18 @@
+const config = require('@lobehub/lint').semanticRelease;
+
+config.branches = [
+  'main',
+  {
+    name: 'next',
+    prerelease: true,
+  },
+];
+
+config.plugins.push([
+  '@semantic-release/exec',
+  {
+    prepareCmd: 'npm run workflow:changelog',
+  },
+]);
+
+module.exports = config;
@@ -1,10 +0,0 @@
-const config = require('@lobehub/lint').semanticRelease;
-
-config.plugins.push([
-  '@semantic-release/exec',
-  {
-    prepareCmd: 'npm run workflow:changelog',
-  },
-]);
-
-module.exports = config;
@@ -0,0 +1,39 @@
+# Stylelintignore for LobeHub
+################################################################
+
+# dependencies
+node_modules
+
+# ci
+coverage
+.coverage
+
+# production
+dist
+es
+lib
+logs
+
+# framework specific
+.next
+.umi
+.umi-production
+.umi-test
+.dumi/tmp*
+
+# temporary directories
+tmp
+temp
+.temp
+.local
+docs/.local
+
+# cache directories
+.cache
+
+# AI coding tools directories
+.claude
+.serena
+
+# MCP tools
+/.serena/**
@@ -0,0 +1,13 @@
+{
+    "recommendations": [
+        "Anthropic.claude-code",
+        "dbaeumer.vscode-eslint",
+        "jrr997.antd-docs",
+        "seatonjiang.gitmoji-vscode",
+        "styled-components.vscode-styled-components",
+        "stylelint.vscode-stylelint",
+        "unifiedjs.vscode-mdx",
+        "unifiedjs.vscode-remark",
+        "vitest.explorer",
+    ]
+}
@@ -0,0 +1,96 @@
+{
+  "editor.codeActionsOnSave": {
+    "source.addMissingImports": "explicit",
+    "source.fixAll.eslint": "explicit",
+    "source.fixAll.stylelint": "explicit"
+  },
+  "editor.formatOnSave": true,
+  // don't show errors, but fix when save and git pre commit
+  "eslint.rules.customizations": [
+    { "rule": "import/order", "severity": "off" },
+    { "rule": "prettier/prettier", "severity": "off" },
+    { "rule": "react/jsx-sort-props", "severity": "off" },
+    { "rule": "sort-keys-fix/sort-keys-fix", "severity": "off" },
+    { "rule": "simple-import-sort/exports", "severity": "off" },
+    { "rule": "typescript-sort-keys/interface", "severity": "off" }
+  ],
+  "eslint.validate": [
+    "javascript",
+    "javascriptreact",
+    "typescript",
+    "typescriptreact",
+    // support mdx
+    "mdx"
+  ],
+  "npm.packageManager": "pnpm",
+  "search.exclude": {
+    "**/node_modules": true,
+    // useless to search this big folder
+    "locales": true
+  },
+  "stylelint.validate": [
+    "css",
+    "postcss",
+    // make stylelint work with tsx antd-style css template string
+    "typescriptreact"
+  ],
+  "vitest.maximumConfigs": 20,
+  "workbench.editor.customLabels.patterns": {
+    "**/app/**/[[]*[]]/[[]*[]]/page.tsx": "${dirname(2)}/${dirname(1)}/${dirname} • page component",
+    "**/app/**/[[]*[]]/page.tsx": "${dirname(1)}/${dirname} • page component",
+    "**/app/**/page.tsx": "${dirname} • page component",
+
+    "**/app/**/[[]*[]]/[[]*[]]/layout.tsx": "${dirname(2)}/${dirname(1)}/${dirname} • page layout",
+    "**/app/**/[[]*[]]/layout.tsx": "${dirname(1)}/${dirname} • page layout",
+    "**/app/**/layout.tsx": "${dirname} • page layout",
+
+    "**/app/**/[[]*[]]/[[]*[]]/default.tsx": "${dirname(2)}/${dirname(1)}/${dirname} • slot default",
+    "**/app/**/[[]*[]]/default.tsx": "${dirname(1)}/${dirname} • slot default",
+    "**/app/**/default.tsx": "${dirname} • slot default",
+
+    "**/app/**/[[]*[]]/[[]*[]]/error.tsx": "${dirname(2)}/${dirname(1)}/${dirname} • error component",
+    "**/app/**/[[]*[]]/error.tsx": "${dirname(1)}/${dirname} • error component",
+    "**/app/**/error.tsx": "${dirname} • error component",
+
+    "**/app/**/[[]*[]]/[[]*[]]/loading.tsx": "${dirname(2)}/${dirname(1)}/${dirname} • loading component",
+    "**/app/**/[[]*[]]/loading.tsx": "${dirname(1)}/${dirname} • loading component",
+    "**/app/**/loading.tsx": "${dirname} • loading component",
+
+    "**/src/**/route.ts": "${dirname(1)}/${dirname} • route",
+    "**/src/**/index.tsx": "${dirname} • component",
+
+    "**/packages/database/src/repositories/*/index.ts": "${dirname} • db repository",
+    "**/packages/database/src/models/*.ts": "${filename} • db model",
+    "**/packages/database/src/schemas/*.ts": "${filename} • db schema",
+
+    "**/src/services/*.ts": "${filename} • service",
+    "**/src/services/*/client.ts": "${dirname} • client service",
+    "**/src/services/*/server.ts": "${dirname} • server service",
+
+    "**/src/store/*/action.ts": "${dirname} • action",
+    "**/src/store/*/slices/*/action.ts": "${dirname(2)}/${dirname} • action",
+    "**/src/store/*/slices/*/actions/*.ts": "${dirname(1)}/${dirname}/${filename} • action",
+
+    "**/src/store/*/initialState.ts": "${dirname} • state",
+    "**/src/store/*/slices/*/initialState.ts": "${dirname(2)}/${dirname} • state",
+
+    "**/src/store/*/selectors.ts": "${dirname} • selectors",
+    "**/src/store/*/slices/*/selectors.ts": "${dirname(2)}/${dirname} • selectors",
+
+    "**/src/store/*/reducer.ts": "${dirname} • reducer",
+    "**/src/store/*/slices/*/reducer.ts": "${dirname(2)}/${dirname} • reducer",
+
+    "**/src/config/modelProviders/*.ts": "${filename} • provider",
+    "**/packages/model-bank/src/aiModels/*.ts": "${filename} • model",
+    "**/packages/model-runtime/src/providers/*/index.ts": "${dirname} • runtime",
+
+    "**/src/server/services/*/index.ts": "${dirname} • server/service",
+    "**/src/server/routers/lambda/*.ts": "${filename} • lambda",
+    "**/src/server/routers/async/*.ts": "${filename} • async",
+    "**/src/server/routers/edge/*.ts": "${filename} • edge",
+
+    "**/src/locales/default/*.ts": "${filename} • locale",
+
+    "**/index.*": "${dirname}/${filename}.${extname}"
+  }
+}
@@ -0,0 +1,109 @@
+# LobeChat Development Guidelines
+
+This document serves as a comprehensive guide for all team members when developing LobeChat.
+
+## Tech Stack
+
+Built with modern technologies:
+
+- **Frontend**: Next.js 15, React 19, TypeScript
+- **UI Components**: Ant Design, @lobehub/ui, antd-style
+- **State Management**: Zustand, SWR
+- **Database**: PostgreSQL, PGLite, Drizzle ORM
+- **Testing**: Vitest, Testing Library
+- **Package Manager**: pnpm (monorepo structure)
+- **Build Tools**: Next.js (Turbopack in dev, Webpack in prod)
+
+## Directory Structure
+
+The project follows a well-organized monorepo structure:
+
+- `apps/` - Main applications
+- `packages/` - Shared packages and libraries
+- `src/` - Main source code
+- `docs/` - Documentation
+- `.cursor/rules/` - Development rules and guidelines
+
+## Development Workflow
+
+### Git Workflow
+
+- Use rebase for git pull
+- Git commit messages should prefix with gitmoji
+- Git branch name format: `username/feat/feature-name`
+- Use `.github/PULL_REQUEST_TEMPLATE.md` for PR descriptions
+
+### Package Management
+
+- Use `pnpm` as the primary package manager
+- Use `bun` to run npm scripts
+- Use `bunx` to run executable npm packages
+- Navigate to specific packages using `cd packages/<package-name>`
+
+### Code Style Guidelines
+
+#### TypeScript
+
+- Prefer interfaces over types for object shapes
+
+### Testing Strategy
+
+**Required Rule**: `testing-guide/testing-guide.mdc`
+
+**Commands**:
+
+- Web: `bunx vitest run --silent='passed-only' '[file-path-pattern]'`
+- Packages: `cd packages/[package-name] && bunx vitest run --silent='passed-only' '[file-path-pattern]'` (each subpackage contains its own vitest.config.mts)
+
+**Important Notes**:
+
+- Wrap file paths in single quotes to avoid shell expansion
+- Never run `bun run test` - this runs all tests and takes \~10 minutes
+
+### Type Checking
+
+- Use `bun run type-check` to check for type errors
+
+### i18n
+
+- **Keys**: Add to `src/locales/default/namespace.ts`
+- **Dev**: Translate `locales/zh-CN/namespace.json` locale file only for preview
+- DON'T run `pnpm i18n`, let CI auto handle it
+
+## Project Rules Index
+
+All following rules are saved under `.cursor/rules/` directory:
+
+### Backend
+
+- `drizzle-schema-style-guide.mdc` – Style guide for defining Drizzle ORM schemas
+
+### Frontend
+
+- `react-component.mdc` – React component style guide and conventions
+- `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
+
+### Desktop (Electron)
+
+- `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
+
+### Debugging
+
+- `debug-usage.mdc` – Using the debug package and namespace conventions
+
+### Testing
+
+- `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
@@ -0,0 +1,59 @@
+# CLAUDE.md
+
+This document serves as a shared guideline for all team members when using Claude Code in this repository.
+
+## Tech Stack
+
+read @.cursor/rules/project-introduce.mdc
+
+## Directory Structure
+
+read @.cursor/rules/project-structure.mdc
+
+## Development
+
+### Git Workflow
+
+- use rebase for git pull
+- git commit message should prefix with gitmoji
+- git branch name format example: tj/feat/feature-name
+- use .github/PULL_REQUEST_TEMPLATE.md to generate pull request description
+
+### Package Management
+
+This repository adopts a monorepo structure.
+
+- Use `pnpm` as the primary package manager for dependency management
+- Use `bun` to run npm scripts
+- Use `bunx` to run executable npm packages
+
+### TypeScript Code Style Guide
+
+see @.cursor/rules/typescript.mdc
+
+### Testing
+
+- **Required Rule**: read `@.cursor/rules/testing-guide/testing-guide.mdc` before writing tests
+- **Command**:
+  - web: `bunx vitest run --silent='passed-only' '[file-path-pattern]'`
+  - packages(eg: database): `cd packages/database && bunx vitest run --silent='passed-only' '[file-path-pattern]'`
+
+**Important**:
+
+- wrap the file path in single quotes to avoid shell expansion
+- Never run `bun run test` etc to run tests, this will run all tests and cost about 10mins
+- If trying to fix the same test twice, but still failed, stop and ask for help.
+
+### Typecheck
+
+- use `bun run type-check` to check type errors.
+
+### i18n
+
+- **Keys**: Add to `src/locales/default/namespace.ts`
+- **Dev**: Translate `locales/zh-CN/namespace.json` and `locales/en-US/namespace.json` locales file only for dev preview
+- DON'T run `pnpm i18n`, let CI auto handle it
+
+## Rules Index
+
+Some useful project rules are listed in @.cursor/rules/rules-index.mdc
@@ -1,5 +1,5 @@
 ## Set global build ENV
-ARG NODEJS_VERSION="22"
+ARG NODEJS_VERSION="24"

 ## Base image for all building stages
 FROM node:${NODEJS_VERSION}-slim AS base
@@ -37,6 +37,9 @@ FROM base AS builder

 ARG USE_CN_MIRROR
 ARG NEXT_PUBLIC_BASE_PATH
+ARG NEXT_PUBLIC_ENABLE_NEXT_AUTH
+ARG NEXT_PUBLIC_ENABLE_CLERK_AUTH
+ARG NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY
 ARG NEXT_PUBLIC_SENTRY_DSN
 ARG NEXT_PUBLIC_ANALYTICS_POSTHOG
 ARG NEXT_PUBLIC_POSTHOG_HOST
@@ -44,8 +47,19 @@ ARG NEXT_PUBLIC_POSTHOG_KEY
 ARG NEXT_PUBLIC_ANALYTICS_UMAMI
 ARG NEXT_PUBLIC_UMAMI_SCRIPT_URL
 ARG NEXT_PUBLIC_UMAMI_WEBSITE_ID
+ARG FEATURE_FLAGS

-ENV NEXT_PUBLIC_BASE_PATH="${NEXT_PUBLIC_BASE_PATH}"
+ENV NEXT_PUBLIC_BASE_PATH="${NEXT_PUBLIC_BASE_PATH}" \
+    FEATURE_FLAGS="${FEATURE_FLAGS}"
+
+ENV NEXT_PUBLIC_ENABLE_NEXT_AUTH="${NEXT_PUBLIC_ENABLE_NEXT_AUTH:-1}" \
+    NEXT_PUBLIC_ENABLE_CLERK_AUTH="${NEXT_PUBLIC_ENABLE_CLERK_AUTH:-0}" \
+    NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY="${NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY}" \
+    CLERK_WEBHOOK_SECRET="whsec_xxx" \
+    APP_URL="http://app.com" \
+    DATABASE_DRIVER="node" \
+    DATABASE_URL="postgres://postgres:password@localhost:5432/postgres" \
+    KEY_VAULTS_SECRET="use-for-build"

 # Sentry
 ENV NEXT_PUBLIC_SENTRY_DSN="${NEXT_PUBLIC_SENTRY_DSN}" \
@@ -63,12 +77,13 @@ ENV NEXT_PUBLIC_ANALYTICS_UMAMI="${NEXT_PUBLIC_ANALYTICS_UMAMI}" \
    NEXT_PUBLIC_UMAMI_WEBSITE_ID="${NEXT_PUBLIC_UMAMI_WEBSITE_ID}"

 # Node
-ENV NODE_OPTIONS="--max-old-space-size=8192"
+ENV NODE_OPTIONS="--max-old-space-size=6144"

 WORKDIR /app

-COPY package.json ./
+COPY package.json pnpm-workspace.yaml ./
 COPY .npmrc ./
+COPY packages ./packages

 RUN \
    # If you want to build docker in China, build with --build-arg USE_CN_MIRROR=true
@@ -79,15 +94,19 @@ RUN \
    fi \
    # Set the registry for corepack
    && export COREPACK_NPM_REGISTRY=$(npm config get registry | sed 's/\/$//') \
+    # Update corepack to latest (nodejs/corepack#612)
+    && npm i -g corepack@latest \
    # Enable corepack
    && corepack enable \
    # Use pnpm for corepack
-    && corepack use pnpm@9 \
+    && corepack use $(sed -n 's/.*"packageManager": "\(.*\)".*/\1/p' package.json) \
    # Install the dependencies
    && pnpm i \
-    # Add sharp dependencies
+    # Add db migration dependencies
    && mkdir -p /deps \
-    && pnpm add sharp --prefix /deps
+    && cd /deps \
+    && pnpm init \
+    && pnpm add pg drizzle-orm

 COPY . .

@@ -99,13 +118,19 @@ FROM busybox:latest AS app

 COPY --from=base /distroless/ /

-COPY --from=builder /app/public /app/public
-
 # Automatically leverage output traces to reduce image size
 # https://nextjs.org/docs/advanced-features/output-file-tracing
 COPY --from=builder /app/.next/standalone /app/
-COPY --from=builder /app/.next/static /app/.next/static
+
+# Copy database migrations
+COPY --from=builder /app/packages/database/migrations /app/migrations
+COPY --from=builder /app/scripts/migrateServerDB/docker.cjs /app/docker.cjs
+COPY --from=builder /app/scripts/migrateServerDB/errorHint.js /app/errorHint.js
+
+# copy dependencies
 COPY --from=builder /deps/node_modules/.pnpm /app/node_modules/.pnpm
+COPY --from=builder /deps/node_modules/pg /app/node_modules/pg
+COPY --from=builder /deps/node_modules/drizzle-orm /app/node_modules/drizzle-orm

 # Copy server launcher
 COPY --from=builder /app/scripts/serverLauncher/startServer.js /app/startServer.js
@@ -127,7 +152,11 @@ ENV NODE_ENV="production" \
    NODE_OPTIONS="--dns-result-order=ipv4first --use-openssl-ca" \
    NODE_EXTRA_CA_CERTS="" \
    NODE_TLS_REJECT_UNAUTHORIZED="" \
-    SSL_CERT_DIR="/etc/ssl/certs/ca-certificates.crt"
+    SSL_CERT_FILE="/etc/ssl/certs/ca-certificates.crt"
+
+# Make the middleware rewrite through local as default
+# refs: https://github.com/lobehub/lobe-chat/issues/5876
+ENV MIDDLEWARE_REWRITE_THROUGH_LOCAL="1"

 # set hostname to localhost
 ENV HOSTNAME="0.0.0.0" \
@@ -135,11 +164,37 @@ ENV HOSTNAME="0.0.0.0" \

 # General Variables
 ENV ACCESS_CODE="" \
+    APP_URL="" \
    API_KEY_SELECT_MODE="" \
    DEFAULT_AGENT_CONFIG="" \
    SYSTEM_AGENT="" \
    FEATURE_FLAGS="" \
-    PROXY_URL=""
+    PROXY_URL="" \
+    ENABLE_AUTH_PROTECTION=""
+
+# Database
+ENV KEY_VAULTS_SECRET="" \
+    DATABASE_DRIVER="node" \
+    DATABASE_URL=""
+
+# Next Auth
+ENV NEXT_AUTH_SECRET="" \
+    NEXT_AUTH_SSO_PROVIDERS="" \
+    NEXTAUTH_URL=""
+
+# Clerk
+ENV CLERK_SECRET_KEY="" \
+    CLERK_WEBHOOK_SECRET=""
+
+# S3
+ENV NEXT_PUBLIC_S3_DOMAIN="" \
+    S3_PUBLIC_DOMAIN="" \
+    S3_ACCESS_KEY_ID="" \
+    S3_BUCKET="" \
+    S3_ENDPOINT="" \
+    S3_SECRET_ACCESS_KEY="" \
+    S3_ENABLE_PATH_STYLE="" \
+    S3_SET_ACL=""

 # Model Variables
 ENV \
@@ -147,16 +202,23 @@ ENV \
    AI21_API_KEY="" AI21_MODEL_LIST="" \
    # Ai360
    AI360_API_KEY="" AI360_MODEL_LIST="" \
+    # AiHubMix
+    AIHUBMIX_API_KEY="" AIHUBMIX_MODEL_LIST="" \
    # Anthropic
    ANTHROPIC_API_KEY="" ANTHROPIC_MODEL_LIST="" ANTHROPIC_PROXY_URL="" \
    # Amazon Bedrock
-    AWS_ACCESS_KEY_ID="" AWS_SECRET_ACCESS_KEY="" AWS_REGION="" AWS_BEDROCK_MODEL_LIST="" \
+    ENABLED_AWS_BEDROCK="" AWS_ACCESS_KEY_ID="" AWS_SECRET_ACCESS_KEY="" AWS_REGION="" AWS_BEDROCK_MODEL_LIST="" \
    # Azure OpenAI
    AZURE_API_KEY="" AZURE_API_VERSION="" AZURE_ENDPOINT="" AZURE_MODEL_LIST="" \
    # Baichuan
    BAICHUAN_API_KEY="" BAICHUAN_MODEL_LIST="" \
    # Cloudflare
    CLOUDFLARE_API_KEY="" CLOUDFLARE_BASE_URL_OR_ACCOUNT_ID="" CLOUDFLARE_MODEL_LIST="" \
+    # Cohere
+    COHERE_API_KEY="" COHERE_MODEL_LIST="" COHERE_PROXY_URL="" \
+    # ComfyUI
+    ENABLED_COMFYUI="" COMFYUI_BASE_URL="" COMFYUI_AUTH_TYPE="" \
+    COMFYUI_API_KEY="" COMFYUI_USERNAME="" COMFYUI_PASSWORD="" COMFYUI_CUSTOM_HEADERS="" \
    # DeepSeek
    DEEPSEEK_API_KEY="" DEEPSEEK_MODEL_LIST="" \
    # Fireworks AI
@@ -177,30 +239,48 @@ ENV \
    HUNYUAN_API_KEY="" HUNYUAN_MODEL_LIST="" \
    # InternLM
    INTERNLM_API_KEY="" INTERNLM_MODEL_LIST="" \
+    # Jina
+    JINA_API_KEY="" JINA_MODEL_LIST="" JINA_PROXY_URL="" \
    # Minimax
    MINIMAX_API_KEY="" MINIMAX_MODEL_LIST="" \
    # Mistral
    MISTRAL_API_KEY="" MISTRAL_MODEL_LIST="" \
+    # ModelScope
+    MODELSCOPE_API_KEY="" MODELSCOPE_MODEL_LIST="" MODELSCOPE_PROXY_URL="" \
    # Moonshot
    MOONSHOT_API_KEY="" MOONSHOT_MODEL_LIST="" MOONSHOT_PROXY_URL="" \
+    # Nebius
+    NEBIUS_API_KEY="" NEBIUS_MODEL_LIST="" NEBIUS_PROXY_URL="" \
+    # NewAPI
+    NEWAPI_API_KEY="" NEWAPI_PROXY_URL="" \
    # Novita
    NOVITA_API_KEY="" NOVITA_MODEL_LIST="" \
+    # Nvidia NIM
+    NVIDIA_API_KEY="" NVIDIA_MODEL_LIST="" NVIDIA_PROXY_URL="" \
    # Ollama
    ENABLED_OLLAMA="" OLLAMA_MODEL_LIST="" OLLAMA_PROXY_URL="" \
    # OpenAI
-    OPENAI_API_KEY="" OPENAI_MODEL_LIST="" OPENAI_PROXY_URL="" \
+    ENABLED_OPENAI="" OPENAI_API_KEY="" OPENAI_MODEL_LIST="" OPENAI_PROXY_URL="" \
    # OpenRouter
    OPENROUTER_API_KEY="" OPENROUTER_MODEL_LIST="" \
    # Perplexity
    PERPLEXITY_API_KEY="" PERPLEXITY_MODEL_LIST="" PERPLEXITY_PROXY_URL="" \
+    # PPIO
+    PPIO_API_KEY="" PPIO_MODEL_LIST="" \
+    # Qiniu
+    QINIU_API_KEY="" QINIU_MODEL_LIST="" QINIU_PROXY_URL="" \
    # Qwen
    QWEN_API_KEY="" QWEN_MODEL_LIST="" QWEN_PROXY_URL="" \
+    # SambaNova
+    SAMBANOVA_API_KEY="" SAMBANOVA_MODEL_LIST="" \
+    # Search1API
+    SEARCH1API_API_KEY="" SEARCH1API_MODEL_LIST="" \
    # SenseNova
    SENSENOVA_API_KEY="" SENSENOVA_MODEL_LIST="" \
    # SiliconCloud
    SILICONCLOUD_API_KEY="" SILICONCLOUD_MODEL_LIST="" SILICONCLOUD_PROXY_URL="" \
    # Spark
-    SPARK_API_KEY="" SPARK_MODEL_LIST="" \
+    SPARK_API_KEY="" SPARK_MODEL_LIST="" SPARK_PROXY_URL="" SPARK_SEARCH_MODE="" \
    # Stepfun
    STEPFUN_API_KEY="" STEPFUN_MODEL_LIST="" \
    # Taichu
@@ -209,14 +289,34 @@ ENV \
    TOGETHERAI_API_KEY="" TOGETHERAI_MODEL_LIST="" \
    # Upstage
    UPSTAGE_API_KEY="" UPSTAGE_MODEL_LIST="" \
+    # v0 (Vercel)
+    V0_API_KEY="" V0_MODEL_LIST="" \
+    # vLLM
+    VLLM_API_KEY="" VLLM_MODEL_LIST="" VLLM_PROXY_URL="" \
    # Wenxin
-    WENXIN_ACCESS_KEY="" WENXIN_SECRET_KEY="" WENXIN_MODEL_LIST="" \
+    WENXIN_API_KEY="" WENXIN_MODEL_LIST="" \
    # xAI
    XAI_API_KEY="" XAI_MODEL_LIST="" XAI_PROXY_URL="" \
+    # Xinference
+    XINFERENCE_API_KEY="" XINFERENCE_MODEL_LIST="" XINFERENCE_PROXY_URL="" \
    # 01.AI
    ZEROONE_API_KEY="" ZEROONE_MODEL_LIST="" \
    # Zhipu
-    ZHIPU_API_KEY="" ZHIPU_MODEL_LIST=""
+    ZHIPU_API_KEY="" ZHIPU_MODEL_LIST="" \
+    # Tencent Cloud
+    TENCENT_CLOUD_API_KEY="" TENCENT_CLOUD_MODEL_LIST="" \
+    # Infini-AI
+    INFINIAI_API_KEY="" INFINIAI_MODEL_LIST="" \
+    # 302.AI
+    AI302_API_KEY="" AI302_MODEL_LIST="" \
+    # FAL
+    ENABLED_FAL="" FAL_API_KEY="" FAL_MODEL_LIST="" \
+    # BFL
+    BFL_API_KEY="" BFL_MODEL_LIST="" \
+    # Vercel AI Gateway
+    VERCELAIGATEWAY_API_KEY="" VERCELAIGATEWAY_MODEL_LIST="" \
+    # Cerebras
+    CEREBRAS_API_KEY="" CEREBRAS_MODEL_LIST=""

 USER nextjs

@@ -1,262 +0,0 @@
-## Set global build ENV
-ARG NODEJS_VERSION="22"
-
-## Base image for all building stages
-FROM node:${NODEJS_VERSION}-slim AS base
-
-ARG USE_CN_MIRROR
-
-ENV DEBIAN_FRONTEND="noninteractive"
-
-RUN \
-    # If you want to build docker in China, build with --build-arg USE_CN_MIRROR=true
-    if [ "${USE_CN_MIRROR:-false}" = "true" ]; then \
-        sed -i "s/deb.debian.org/mirrors.ustc.edu.cn/g" "/etc/apt/sources.list.d/debian.sources"; \
-    fi \
-    # Add required package
-    && apt update \
-    && apt install ca-certificates proxychains-ng -qy \
-    # Prepare required package to distroless
-    && mkdir -p /distroless/bin /distroless/etc /distroless/etc/ssl/certs /distroless/lib \
-    # Copy proxychains to distroless
-    && cp /usr/lib/$(arch)-linux-gnu/libproxychains.so.4 /distroless/lib/libproxychains.so.4 \
-    && cp /usr/lib/$(arch)-linux-gnu/libdl.so.2 /distroless/lib/libdl.so.2 \
-    && cp /usr/bin/proxychains4 /distroless/bin/proxychains \
-    && cp /etc/proxychains4.conf /distroless/etc/proxychains4.conf \
-    # Copy node to distroless
-    && cp /usr/lib/$(arch)-linux-gnu/libstdc++.so.6 /distroless/lib/libstdc++.so.6 \
-    && cp /usr/lib/$(arch)-linux-gnu/libgcc_s.so.1 /distroless/lib/libgcc_s.so.1 \
-    && cp /usr/local/bin/node /distroless/bin/node \
-    # Copy CA certificates to distroless
-    && cp /etc/ssl/certs/ca-certificates.crt /distroless/etc/ssl/certs/ca-certificates.crt \
-    # Cleanup temp files
-    && rm -rf /tmp/* /var/lib/apt/lists/* /var/tmp/*
-
-## Builder image, install all the dependencies and build the app
-FROM base AS builder
-
-ARG USE_CN_MIRROR
-ARG NEXT_PUBLIC_BASE_PATH
-ARG NEXT_PUBLIC_SERVICE_MODE
-ARG NEXT_PUBLIC_SENTRY_DSN
-ARG NEXT_PUBLIC_ANALYTICS_POSTHOG
-ARG NEXT_PUBLIC_POSTHOG_HOST
-ARG NEXT_PUBLIC_POSTHOG_KEY
-ARG NEXT_PUBLIC_ANALYTICS_UMAMI
-ARG NEXT_PUBLIC_UMAMI_SCRIPT_URL
-ARG NEXT_PUBLIC_UMAMI_WEBSITE_ID
-
-ENV NEXT_PUBLIC_BASE_PATH="${NEXT_PUBLIC_BASE_PATH}"
-
-ENV NEXT_PUBLIC_SERVICE_MODE="${NEXT_PUBLIC_SERVICE_MODE:-server}" \
-    APP_URL="http://app.com" \
-    DATABASE_DRIVER="node" \
-    DATABASE_URL="postgres://postgres:password@localhost:5432/postgres" \
-    KEY_VAULTS_SECRET="use-for-build"
-
-# Sentry
-ENV NEXT_PUBLIC_SENTRY_DSN="${NEXT_PUBLIC_SENTRY_DSN}" \
-    SENTRY_ORG="" \
-    SENTRY_PROJECT=""
-
-# Posthog
-ENV NEXT_PUBLIC_ANALYTICS_POSTHOG="${NEXT_PUBLIC_ANALYTICS_POSTHOG}" \
-    NEXT_PUBLIC_POSTHOG_HOST="${NEXT_PUBLIC_POSTHOG_HOST}" \
-    NEXT_PUBLIC_POSTHOG_KEY="${NEXT_PUBLIC_POSTHOG_KEY}"
-
-# Umami
-ENV NEXT_PUBLIC_ANALYTICS_UMAMI="${NEXT_PUBLIC_ANALYTICS_UMAMI}" \
-    NEXT_PUBLIC_UMAMI_SCRIPT_URL="${NEXT_PUBLIC_UMAMI_SCRIPT_URL}" \
-    NEXT_PUBLIC_UMAMI_WEBSITE_ID="${NEXT_PUBLIC_UMAMI_WEBSITE_ID}"
-
-# Node
-ENV NODE_OPTIONS="--max-old-space-size=8192"
-
-WORKDIR /app
-
-COPY package.json ./
-COPY .npmrc ./
-
-RUN \
-    # If you want to build docker in China, build with --build-arg USE_CN_MIRROR=true
-    if [ "${USE_CN_MIRROR:-false}" = "true" ]; then \
-        export SENTRYCLI_CDNURL="https://npmmirror.com/mirrors/sentry-cli"; \
-        npm config set registry "https://registry.npmmirror.com/"; \
-        echo 'canvas_binary_host_mirror=https://npmmirror.com/mirrors/canvas' >> .npmrc; \
-    fi \
-    # Set the registry for corepack
-    && export COREPACK_NPM_REGISTRY=$(npm config get registry | sed 's/\/$//') \
-    # Enable corepack
-    && corepack enable \
-    # Use pnpm for corepack
-    && corepack use pnpm@9 \
-    # Install the dependencies
-    && pnpm i \
-    # Add sharp and db migration dependencies
-    && mkdir -p /deps \
-    && pnpm add sharp pg drizzle-orm --prefix /deps
-
-COPY . .
-
-# run build standalone for docker version
-RUN npm run build:docker
-
-## Application image, copy all the files for production
-FROM busybox:latest AS app
-
-COPY --from=base /distroless/ /
-
-COPY --from=builder /app/public /app/public
-
-# Automatically leverage output traces to reduce image size
-# https://nextjs.org/docs/advanced-features/output-file-tracing
-COPY --from=builder /app/.next/standalone /app/
-COPY --from=builder /app/.next/static /app/.next/static
-
-# copy dependencies
-COPY --from=builder /deps/node_modules/.pnpm /app/node_modules/.pnpm
-COPY --from=builder /deps/node_modules/pg /app/node_modules/pg
-COPY --from=builder /deps/node_modules/drizzle-orm /app/node_modules/drizzle-orm
-
-# Copy database migrations
-COPY --from=builder /app/src/database/migrations /app/migrations
-COPY --from=builder /app/scripts/migrateServerDB/docker.cjs /app/docker.cjs
-COPY --from=builder /app/scripts/migrateServerDB/errorHint.js /app/errorHint.js
-
-# Copy server launcher
-COPY --from=builder /app/scripts/serverLauncher/startServer.js /app/startServer.js
-
-RUN \
-    # Add nextjs:nodejs to run the app
-    addgroup -S -g 1001 nodejs \
-    && adduser -D -G nodejs -H -S -h /app -u 1001 nextjs \
-    # Set permission for nextjs:nodejs
-    && chown -R nextjs:nodejs /app /etc/proxychains4.conf
-
-## Production image, copy all the files and run next
-FROM scratch
-
-# Copy all the files from app, set the correct permission for prerender cache
-COPY --from=app / /
-
-ENV NODE_ENV="production" \
-    NODE_OPTIONS="--dns-result-order=ipv4first --use-openssl-ca" \
-    NODE_EXTRA_CA_CERTS="" \
-    NODE_TLS_REJECT_UNAUTHORIZED="" \
-    SSL_CERT_DIR="/etc/ssl/certs/ca-certificates.crt"
-
-# set hostname to localhost
-ENV HOSTNAME="0.0.0.0" \
-    PORT="3210"
-
-# General Variables
-ENV ACCESS_CODE="" \
-    APP_URL="" \
-    API_KEY_SELECT_MODE="" \
-    DEFAULT_AGENT_CONFIG="" \
-    SYSTEM_AGENT="" \
-    FEATURE_FLAGS="" \
-    PROXY_URL=""
-
-# Database
-ENV KEY_VAULTS_SECRET="" \
-    DATABASE_DRIVER="node" \
-    DATABASE_URL=""
-
-# Next Auth
-ENV NEXT_AUTH_SECRET="" \
-    NEXT_AUTH_SSO_PROVIDERS="" \
-    NEXTAUTH_URL=""
-
-# S3
-ENV NEXT_PUBLIC_S3_DOMAIN="" \
-    S3_PUBLIC_DOMAIN="" \
-    S3_ACCESS_KEY_ID="" \
-    S3_BUCKET="" \
-    S3_ENDPOINT="" \
-    S3_SECRET_ACCESS_KEY=""
-
-# Model Variables
-ENV \
-    # AI21
-    AI21_API_KEY="" AI21_MODEL_LIST="" \
-    # Ai360
-    AI360_API_KEY="" AI360_MODEL_LIST="" \
-    # Anthropic
-    ANTHROPIC_API_KEY="" ANTHROPIC_MODEL_LIST="" ANTHROPIC_PROXY_URL="" \
-    # Amazon Bedrock
-    AWS_ACCESS_KEY_ID="" AWS_SECRET_ACCESS_KEY="" AWS_REGION="" AWS_BEDROCK_MODEL_LIST="" \
-    # Azure OpenAI
-    AZURE_API_KEY="" AZURE_API_VERSION="" AZURE_ENDPOINT="" AZURE_MODEL_LIST="" \
-    # Baichuan
-    BAICHUAN_API_KEY="" BAICHUAN_MODEL_LIST="" \
-    # Cloudflare
-    CLOUDFLARE_API_KEY="" CLOUDFLARE_BASE_URL_OR_ACCOUNT_ID="" CLOUDFLARE_MODEL_LIST="" \
-    # DeepSeek
-    DEEPSEEK_API_KEY="" DEEPSEEK_MODEL_LIST="" \
-    # Fireworks AI
-    FIREWORKSAI_API_KEY="" FIREWORKSAI_MODEL_LIST="" \
-    # Gitee AI
-    GITEE_AI_API_KEY="" GITEE_AI_MODEL_LIST="" \
-    # GitHub
-    GITHUB_TOKEN="" GITHUB_MODEL_LIST="" \
-    # Google
-    GOOGLE_API_KEY="" GOOGLE_MODEL_LIST="" GOOGLE_PROXY_URL="" \
-    # Groq
-    GROQ_API_KEY="" GROQ_MODEL_LIST="" GROQ_PROXY_URL="" \
-    # Higress
-    HIGRESS_API_KEY="" HIGRESS_MODEL_LIST="" HIGRESS_PROXY_URL="" \
-    # HuggingFace
-    HUGGINGFACE_API_KEY="" HUGGINGFACE_MODEL_LIST="" HUGGINGFACE_PROXY_URL="" \
-    # Hunyuan
-    HUNYUAN_API_KEY="" HUNYUAN_MODEL_LIST="" \
-    # InternLM
-    INTERNLM_API_KEY="" INTERNLM_MODEL_LIST="" \
-    # Minimax
-    MINIMAX_API_KEY="" MINIMAX_MODEL_LIST="" \
-    # Mistral
-    MISTRAL_API_KEY="" MISTRAL_MODEL_LIST="" \
-    # Moonshot
-    MOONSHOT_API_KEY="" MOONSHOT_MODEL_LIST="" MOONSHOT_PROXY_URL="" \
-    # Novita
-    NOVITA_API_KEY="" NOVITA_MODEL_LIST="" \
-    # Ollama
-    ENABLED_OLLAMA="" OLLAMA_MODEL_LIST="" OLLAMA_PROXY_URL="" \
-    # OpenAI
-    OPENAI_API_KEY="" OPENAI_MODEL_LIST="" OPENAI_PROXY_URL="" \
-    # OpenRouter
-    OPENROUTER_API_KEY="" OPENROUTER_MODEL_LIST="" \
-    # Perplexity
-    PERPLEXITY_API_KEY="" PERPLEXITY_MODEL_LIST="" PERPLEXITY_PROXY_URL="" \
-    # Qwen
-    QWEN_API_KEY="" QWEN_MODEL_LIST="" QWEN_PROXY_URL="" \
-    # SenseNova
-    SENSENOVA_API_KEY="" SENSENOVA_MODEL_LIST="" \
-    # SiliconCloud
-    SILICONCLOUD_API_KEY="" SILICONCLOUD_MODEL_LIST="" SILICONCLOUD_PROXY_URL="" \
-    # Spark
-    SPARK_API_KEY="" SPARK_MODEL_LIST="" \
-    # Stepfun
-    STEPFUN_API_KEY="" STEPFUN_MODEL_LIST="" \
-    # Taichu
-    TAICHU_API_KEY="" TAICHU_MODEL_LIST="" \
-    # TogetherAI
-    TOGETHERAI_API_KEY="" TOGETHERAI_MODEL_LIST="" \
-    # Upstage
-    UPSTAGE_API_KEY="" UPSTAGE_MODEL_LIST="" \
-    # Wenxin
-    WENXIN_ACCESS_KEY="" WENXIN_SECRET_KEY="" WENXIN_MODEL_LIST="" \
-    # xAI
-    XAI_API_KEY="" XAI_MODEL_LIST="" XAI_PROXY_URL="" \
-    # 01.AI
-    ZEROONE_API_KEY="" ZEROONE_MODEL_LIST="" \
-    # Zhipu
-    ZHIPU_API_KEY="" ZHIPU_MODEL_LIST=""
-
-USER nextjs
-
-EXPOSE 3210/tcp
-
-ENTRYPOINT ["/bin/node"]
-
-CMD ["/app/startServer.js"]
@@ -1,10 +1,10 @@
-Apache License Version 2.0
+LobeHub Community License

 Copyright (c) 2024/06/17 - current LobeHub LLC. All rights reserved.

 ----------

-From 1.0, LobeChat is licensed under the Apache License 2.0, with the following additional conditions:
+From 1.0, LobeChat is licensed under the LobeHub Community License, based on Apache License 2.0 with the following additional conditions:

 1. The commercial usage of LobeChat:

@@ -22,17 +22,3 @@ Please contact hello@lobehub.com by email to inquire about licensing matters.
  b. Your contributed code may be used for commercial purposes, including but not limited to its cloud edition.

 Apart from the specific conditions mentioned above, all other rights and restrictions follow the Apache License 2.0. Detailed information about the Apache License 2.0 can be found at http://www.apache.org/licenses/LICENSE-2.0.
-
----------
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
@@ -1,844 +0,0 @@
-<div align="center"><a name="readme-top"></a>
-
-[![][image-banner]][vercel-link]
-
-# Lobe Chat
-
-オープンソースのモダンデザイン ChatGPT/LLMs UI / フレームワーク。<br/>
-音声合成、マルチモーダル、拡張可能な（[function call][docs-functionc-call]）プラグインシステムをサポート。<br/>
-プライベートな OpenAI ChatGPT/Claude/Gemini/Groq/Ollama チャットアプリケーションをワンクリックで**無料**でデプロイ。
-
-[English](./README.md) · [繁體中文](./README.zh-TW.md) · [简体中文](./README.zh-CN.md) · **日本語** · [公式サイト][official-site] · [変更履歴][changelog] · [ドキュメント][docs] · [ブログ][blog] · [フィードバック][github-issues-link]
-
-<!-- SHIELD GROUP -->
-
-[![][github-release-shield]][github-release-link]
-[![][docker-release-shield]][docker-release-link]
-[![][vercel-shield]][vercel-link]
-[![][discord-shield]][discord-link]<br/>
-[![][codecov-shield]][codecov-link]
-[![][github-action-test-shield]][github-action-test-link]
-[![][github-action-release-shield]][github-action-release-link]
-[![][github-releasedate-shield]][github-releasedate-link]<br/>
-[![][github-contributors-shield]][github-contributors-link]
-[![][github-forks-shield]][github-forks-link]
-[![][github-stars-shield]][github-stars-link]
-[![][github-issues-shield]][github-issues-link]
-[![][github-license-shield]][github-license-link]<br>
-[![][sponsor-shield]][sponsor-link]
-
-**LobeChat リポジトリを共有**
-
-[![][share-x-shield]][share-x-link]
-[![][share-telegram-shield]][share-telegram-link]
-[![][share-whatsapp-shield]][share-whatsapp-link]
-[![][share-reddit-shield]][share-reddit-link]
-[![][share-weibo-shield]][share-weibo-link]
-[![][share-mastodon-shield]][share-mastodon-link]
-[![][share-linkedin-shield]][share-linkedin-link]
-
-<sup>新しい時代の思考と創造を先導します。あなたのために、スーパー個人のために作られました。</sup>
-
-[![][github-trending-shield]][github-trending-url]
-
-[![][image-overview]][vercel-link]
-
-</div>
-
-<details>
-<summary><kbd>目次</kbd></summary>
-
-#### TOC
-
- [👋🏻 はじめに & コミュニティに参加](#-はじめに--コミュニティに参加)
- [✨ 特徴](#-特徴)
-  - [`1` マルチモデルサービスプロバイダーのサポート](#1-マルチモデルサービスプロバイダーのサポート)
-  - [`2` ローカル大規模言語モデル (LLM) のサポート](#2-ローカル大規模言語モデル-llm-のサポート)
-  - [`3` モデルの視覚認識](#3-モデルの視覚認識)
-  - [`4` TTS & STT 音声会話](#4-tts--stt-音声会話)
-  - [`5` テキストから画像生成](#5-テキストから画像生成)
-  - [`6` プラグインシステム (Function Calling)](#6-プラグインシステム-function-calling)
-  - [`7` エージェントマーケット (GPTs)](#7-エージェントマーケット-gpts)
-  - [`8` ローカル / リモートデータベースのサポート](#8-ローカル--リモートデータベースのサポート)
-  - [`9` マルチユーザ管理のサポート](#9-マルチユーザ管理のサポート)
-  - [`10` プログレッシブウェブアプリ (PWA)](#10-プログレッシブウェブアプリ-pwa)
-  - [`11` モバイルデバイスの適応](#11-モバイルデバイスの適応)
-  - [`12` カスタムテーマ](#12-カスタムテーマ)
-  - [`*` その他の特徴](#-その他の特徴)
- [⚡️ パフォーマンス](#️-パフォーマンス)
- [🛳 自己ホスティング](#-自己ホスティング)
-  - [`A` Vercel、Zeabur、Sealos でのデプロイ](#a-vercelzeabursealos-でのデプロイ)
-  - [`B` Docker でのデプロイ](#b-docker-でのデプロイ)
-  - [環境変数](#環境変数)
- [📦 エコシステム](#-エコシステム)
- [🧩 プラグイン](#-プラグイン)
- [⌨️ ローカル開発](#️-ローカル開発)
- [🤝 コントリビュート](#-コントリビュート)
- [❤️ スポンサー](#️-スポンサー)
- [🔗 その他の製品](#-その他の製品)
-
-####
-
-<br/>
-
-</details>
-
-## 👋🏻 はじめに & コミュニティに参加
-
-私たちは、AIGC のためのモダンデザインコンポーネントとツールを提供することを目指すデザインエンジニアのグループです。
-ブートストラッピングアプローチを採用することで、開発者とユーザーに対してよりオープンで透明性のある、使いやすい製品エコシステムを提供することを目指しています。
-
-ユーザーやプロの開発者にとって、LobeHub はあなたの AI エージェントの遊び場となるでしょう。LobeChat は現在アクティブに開発中であり、遭遇した[問題][issues-link]についてのフィードバックを歓迎します。
-
-| [![][vercel-shield-badge]][vercel-link]   | インストールや登録は不要です！私たちのウェブサイトにアクセスして、直接体験してください。                                |
-| :---------------------------------------- | :---------------------------------------------------------------------------------------------------------------------- |
-| [![][discord-shield-badge]][discord-link] | 私たちの Discord コミュニティに参加しましょう！ここでは、LobeHub の開発者や他の熱心なユーザーとつながることができます。 |
-
-> \[!IMPORTANT]
->
-> **スターを付けてください**。GitHub からのすべてのリリース通知を遅延なく受け取ることができます～⭐️
-
-[![][image-star]][github-stars-link]
-
-<details>
-  <summary><kbd>スター履歴</kbd></summary>
-  <picture>
-    <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=lobehub%2Flobe-chat&theme=dark&type=Date">
-    <img width="100%" src="https://api.star-history.com/svg?repos=lobehub%2Flobe-chat&type=Date">
-  </picture>
-</details>
-
-## ✨ 特徴
-
-[![][image-feat-privoder]][docs-feat-provider]
-
-### `1` [マルチモデルサービスプロバイダーのサポート][docs-feat-provider]
-
-LobeChat の継続的な開発において、AI 会話サービスを提供する際のモデルサービスプロバイダーの多様性がコミュニティのニーズを満たすために重要であることを深く理解しています。そのため、単一のモデルサービスプロバイダーに限定せず、複数のモデルサービスプロバイダーをサポートすることで、ユーザーにより多様で豊富な会話の選択肢を提供しています。
-
-このようにして、LobeChat は異なるユーザーのニーズにより柔軟に対応し、開発者にも幅広い選択肢を提供します。
-
-#### サポートされているモデルサービスプロバイダー
-
-以下のモデルサービスプロバイダーをサポートしています：
-
-<!-- PROVIDER LIST -->
-
- **[OpenAI](https://lobechat.com/discover/provider/openai)**: OpenAI は、世界をリードする人工知能研究機関であり、GPT シリーズなどのモデルを開発し、自然言語処理の最前線を推進しています。OpenAI は、革新と効率的な AI ソリューションを通じて、さまざまな業界を変革することに取り組んでいます。彼らの製品は、顕著な性能と経済性を持ち、研究、ビジネス、革新アプリケーションで広く使用されています。
- **[Ollama](https://lobechat.com/discover/provider/ollama)**: Ollama が提供するモデルは、コード生成、数学演算、多言語処理、対話インタラクションなどの分野を広くカバーし、企業向けおよびローカライズされた展開の多様なニーズに対応しています。
- **[Anthropic](https://lobechat.com/discover/provider/anthropic)**: Anthropic は、人工知能の研究と開発に特化した企業であり、Claude 3.5 Sonnet、Claude 3 Sonnet、Claude 3 Opus、Claude 3 Haiku などの先進的な言語モデルを提供しています。これらのモデルは、知性、速度、コストの理想的なバランスを実現しており、企業向けのワークロードから迅速な応答が求められるさまざまなアプリケーションシーンに適しています。Claude 3.5 Sonnet は最新のモデルであり、複数の評価で優れたパフォーマンスを示し、高いコストパフォーマンスを維持しています。
- **[Bedrock](https://lobechat.com/discover/provider/bedrock)**: Bedrock は、Amazon AWS が提供するサービスで、企業に先進的な AI 言語モデルと視覚モデルを提供することに特化しています。そのモデルファミリーには、Anthropic の Claude シリーズや Meta の Llama 3.1 シリーズなどが含まれ、軽量から高性能までのさまざまな選択肢を提供し、テキスト生成、対話、画像処理などの多様なタスクをサポートし、異なる規模とニーズの企業アプリケーションに適しています。
- **[Google](https://lobechat.com/discover/provider/google)**: Google の Gemini シリーズは、Google DeepMind によって開発された最先端で汎用的な AI モデルであり、多モーダル設計に特化しており、テキスト、コード、画像、音声、動画のシームレスな理解と処理をサポートします。データセンターからモバイルデバイスまでのさまざまな環境に適しており、AI モデルの効率と適用範囲を大幅に向上させています。
- **[DeepSeek](https://lobechat.com/discover/provider/deepseek)**: DeepSeek は、人工知能技術の研究と応用に特化した企業であり、最新のモデル DeepSeek-V2.5 は、汎用対話とコード処理能力を融合させ、人間の好みの整合、ライティングタスク、指示の遵守などの面で顕著な向上を実現しています。
- **[HuggingFace](https://lobechat.com/discover/provider/huggingface)**: HuggingFace Inference API は、数千のモデルをさまざまなタスクに対して探索するための迅速かつ無料の方法を提供します。新しいアプリケーションのプロトタイプを作成している場合でも、機械学習の機能を試している場合でも、この API は複数の分野の高性能モデルに即座にアクセスできるようにします。
- **[OpenRouter](https://lobechat.com/discover/provider/openrouter)**: OpenRouter は、OpenAI、Anthropic、LLaMA などのさまざまな最先端の大規模モデルインターフェースを提供するサービスプラットフォームであり、多様な開発と応用のニーズに適しています。ユーザーは、自身のニーズに応じて最適なモデルと価格を柔軟に選択し、AI 体験の向上を支援します。
- **[Cloudflare Workers AI](https://lobechat.com/discover/provider/cloudflare)**: Cloudflare のグローバルネットワーク上で、サーバーレス GPU によって駆動される機械学習モデルを実行します。
- **[GitHub](https://lobechat.com/discover/provider/github)**: GitHub モデルを使用することで、開発者は AI エンジニアになり、業界をリードする AI モデルを使って構築できます。
-
-<details><summary><kbd>See more providers (+26)</kbd></summary>
-
- **[Novita](https://lobechat.com/discover/provider/novita)**: Novita AI は、さまざまな大規模言語モデルと AI 画像生成の API サービスを提供するプラットフォームであり、柔軟で信頼性が高く、コスト効率に優れています。Llama3、Mistral などの最新のオープンソースモデルをサポートし、生成的 AI アプリケーションの開発に向けた包括的でユーザーフレンドリーかつ自動スケーリングの API ソリューションを提供し、AI スタートアップの急成長を支援します。
- **[Together AI](https://lobechat.com/discover/provider/togetherai)**: Together AI は、革新的な AI モデルを通じて先進的な性能を実現することに取り組んでおり、迅速なスケーリングサポートや直感的な展開プロセスを含む広範なカスタマイズ能力を提供し、企業のさまざまなニーズに応えています。
- **[Fireworks AI](https://lobechat.com/discover/provider/fireworksai)**: Fireworks AI は、先進的な言語モデルサービスのリーダーであり、機能呼び出しと多モーダル処理に特化しています。最新のモデル Firefunction V2 は Llama-3 に基づいており、関数呼び出し、対話、指示の遵守に最適化されています。視覚言語モデル FireLLaVA-13B は、画像とテキストの混合入力をサポートしています。他の注目すべきモデルには、Llama シリーズや Mixtral シリーズがあり、高効率の多言語指示遵守と生成サポートを提供しています。
- **[Groq](https://lobechat.com/discover/provider/groq)**: Groq の LPU 推論エンジンは、最新の独立した大規模言語モデル（LLM）ベンチマークテストで卓越したパフォーマンスを示し、その驚異的な速度と効率で AI ソリューションの基準を再定義しています。Groq は、即時推論速度の代表であり、クラウドベースの展開で良好なパフォーマンスを発揮しています。
- **[Perplexity](https://lobechat.com/discover/provider/perplexity)**: Perplexity は、先進的な対話生成モデルの提供者であり、さまざまな Llama 3.1 モデルを提供し、オンラインおよびオフラインアプリケーションをサポートし、特に複雑な自然言語処理タスクに適しています。
- **[Mistral](https://lobechat.com/discover/provider/mistral)**: Mistral は、先進的な汎用、専門、研究型モデルを提供し、複雑な推論、多言語タスク、コード生成などの分野で広く使用されています。機能呼び出しインターフェースを通じて、ユーザーはカスタム機能を統合し、特定のアプリケーションを実現できます。
- **[Ai21Labs](https://lobechat.com/discover/provider/ai21)**: AI21 Labs は企業向けに基盤モデルと人工知能システムを構築し、生成的人工知能の生産への応用を加速します。
- **[Upstage](https://lobechat.com/discover/provider/upstage)**: Upstage は、さまざまなビジネスニーズに応じた AI モデルの開発に特化しており、Solar LLM や文書 AI を含み、人造一般知能（AGI）の実現を目指しています。Chat API を通じてシンプルな対話エージェントを作成し、機能呼び出し、翻訳、埋め込み、特定分野のアプリケーションをサポートします。
- **[xAI](https://lobechat.com/discover/provider/xai)**: xAI は、人類の科学的発見を加速するための人工知能を構築することに専念している企業です。私たちの使命は、宇宙に対する共通の理解を促進することです。
- **[Qwen](https://lobechat.com/discover/provider/qwen)**: 通義千問は、アリババクラウドが独自に開発した超大規模言語モデルであり、強力な自然言語理解と生成能力を持っています。さまざまな質問に答えたり、文章を創作したり、意見を表現したり、コードを執筆したりすることができ、さまざまな分野で活躍しています。
- **[Wenxin](https://lobechat.com/discover/provider/wenxin)**: 企業向けのワンストップ大規模モデルと AI ネイティブアプリケーションの開発およびサービスプラットフォームで、最も包括的で使いやすい生成的人工知能モデルの開発とアプリケーション開発の全プロセスツールチェーンを提供します。
- **[Hunyuan](https://lobechat.com/discover/provider/hunyuan)**: テンセントが開発した大規模言語モデルであり、強力な中国語の創作能力、複雑な文脈における論理的推論能力、そして信頼性の高いタスク実行能力を備えています。
- **[ZhiPu](https://lobechat.com/discover/provider/zhipu)**: 智谱 AI は、多モーダルおよび言語モデルのオープンプラットフォームを提供し、テキスト処理、画像理解、プログラミング支援など、幅広い AI アプリケーションシーンをサポートしています。
- **[SiliconCloud](https://lobechat.com/discover/provider/siliconcloud)**: SiliconFlow は、AGI を加速させ、人類に利益をもたらすことを目指し、使いやすくコスト効率の高い GenAI スタックを通じて大規模 AI の効率を向上させることに取り組んでいます。
- **[01.AI](https://lobechat.com/discover/provider/zeroone)**: 01.AI は、AI 2.0 時代の人工知能技術に特化し、「人 + 人工知能」の革新と応用を推進し、超強力なモデルと先進的な AI 技術を用いて人類の生産性を向上させ、技術の力を実現します。
- **[Spark](https://lobechat.com/discover/provider/spark)**: 科大訊飛星火大モデルは、多分野、多言語の強力な AI 能力を提供し、先進的な自然言語処理技術を利用して、スマートハードウェア、スマート医療、スマート金融などのさまざまな垂直シーンに適した革新的なアプリケーションを構築します。
- **[SenseNova](https://lobechat.com/discover/provider/sensenova)**: 商湯日日新は、商湯の強力な基盤支援に基づき、高効率で使いやすい全スタックの大規模モデルサービスを提供します。
- **[Stepfun](https://lobechat.com/discover/provider/stepfun)**: 階級星辰大モデルは、業界をリードする多モーダルおよび複雑な推論能力を備え、超長文の理解と強力な自律的検索エンジン機能をサポートしています。
- **[Moonshot](https://lobechat.com/discover/provider/moonshot)**: Moonshot は、北京月之暗面科技有限公司が提供するオープンプラットフォームであり、さまざまな自然言語処理モデルを提供し、コンテンツ創作、学術研究、スマート推薦、医療診断などの広範な応用分野を持ち、長文処理や複雑な生成タスクをサポートしています。
- **[Baichuan](https://lobechat.com/discover/provider/baichuan)**: 百川智能は、人工知能大モデルの研究開発に特化した企業であり、そのモデルは国内の知識百科、長文処理、生成創作などの中国語タスクで卓越したパフォーマンスを示し、海外の主流モデルを超えています。百川智能は、業界をリードする多モーダル能力を持ち、複数の権威ある評価で優れたパフォーマンスを示しています。そのモデルには、Baichuan 4、Baichuan 3 Turbo、Baichuan 3 Turbo 128k などが含まれ、異なるアプリケーションシーンに最適化され、高コストパフォーマンスのソリューションを提供しています。
- **[Minimax](https://lobechat.com/discover/provider/minimax)**: MiniMax は 2021 年に設立された汎用人工知能テクノロジー企業であり、ユーザーと共に知能を共創することに取り組んでいます。MiniMax は、さまざまなモードの汎用大モデルを独自に開発しており、トリリオンパラメータの MoE テキスト大モデル、音声大モデル、画像大モデルを含んでいます。また、海螺 AI などのアプリケーションも展開しています。
- **[InternLM](https://lobechat.com/discover/provider/internlm)**: 大規模モデルの研究と開発ツールチェーンに特化したオープンソース組織です。すべての AI 開発者に対して、高効率で使いやすいオープンプラットフォームを提供し、最先端の大規模モデルとアルゴリズム技術を身近に感じられるようにします。
- **[Higress](https://lobechat.com/discover/provider/higress)**: Higress は、阿里内部で Tengine のリロードが長期接続のビジネスに悪影響を及ぼすことや、gRPC/Dubbo の負荷分散能力が不足している問題を解決するために生まれた、クラウドネイティブな API ゲートウェイです。
- **[Gitee AI](https://lobechat.com/discover/provider/giteeai)**: Gitee AI の Serverless API は、AI 開発者に開梱即使用の大モデル推論 API サービスを提供する。
- **[Taichu](https://lobechat.com/discover/provider/taichu)**: 中科院自動化研究所と武漢人工知能研究院が新世代の多モーダル大モデルを発表し、多輪問答、テキスト創作、画像生成、3D 理解、信号分析などの包括的な問答タスクをサポートし、より強力な認知、理解、創作能力を持ち、新しいインタラクティブな体験を提供します。
- **[360 AI](https://lobechat.com/discover/provider/ai360)**: 360 AI は、360 社が提供する AI モデルとサービスプラットフォームであり、360GPT2 Pro、360GPT Pro、360GPT Turbo、360GPT Turbo Responsibility 8K など、さまざまな先進的な自然言語処理モデルを提供しています。これらのモデルは、大規模なパラメータと多モーダル能力を組み合わせており、テキスト生成、意味理解、対話システム、コード生成などの分野で広く使用されています。柔軟な価格戦略を通じて、360 AI は多様なユーザーのニーズに応え、開発者の統合をサポートし、スマートアプリケーションの革新と発展を促進します。
-
-</details>
-
-> 📊 Total providers: [<kbd>**36**</kbd>](https://lobechat.com/discover/providers)
-
- <!-- PROVIDER LIST -->
-
-同時に、私たちはさらに多くのモデルサービスプロバイダーをサポートする計画を立てており、サービスプロバイダーのライブラリをさらに充実させる予定です。 LobeChat があなたのお気に入りのサービスプロバイダーをサポートすることを希望する場合は、[💬 コミュニティディスカッション](https://github.com/lobehub/lobe-chat/discussions/1284)に参加してください。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-local]][docs-feat-local]
-
-### `2` [ローカル大規模言語モデル (LLM) のサポート][docs-feat-local]
-
-特定のユーザーのニーズに応えるために、LobeChat は[Ollama](https://ollama.ai)に基づいてローカルモデルの使用をサポートしており、ユーザーが自分自身またはサードパーティのモデルを柔軟に使用できるようにしています。
-
-> \[!TIP]
->
-> [📘 LobeChat での Ollama の使用][docs-usage-ollama]について詳しくはこちらをご覧ください。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-vision]][docs-feat-vision]
-
-### `3` [モデルの視覚認識][docs-feat-vision]
-
-LobeChat は、OpenAI の最新の視覚認識機能を備えた[`gpt-4-vision`](https://platform.openai.com/docs/guides/vision)モデルをサポートしています。
-これは視覚を認識できるマルチモーダルインテリジェンスです。ユーザーは簡単に画像をアップロードしたり、画像をドラッグアンドドロップして対話ボックスに入れることができ、
-エージェントは画像の内容を認識し、これに基づいてインテリジェントな会話を行い、よりスマートで多様なチャットシナリオを作成します。
-
-この機能は、新しいインタラクティブな方法を提供し、コミュニケーションがテキストを超えて視覚要素を含むことを可能にします。
-日常の使用での画像共有や特定の業界での画像解釈に関係なく、エージェントは優れた会話体験を提供します。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-tts]][docs-feat-tts]
-
-### `4` [TTS & STT 音声会話][docs-feat-tts]
-
-LobeChat は、テキストから音声への変換（Text-to-Speech、TTS）および音声からテキストへの変換（Speech-to-Text、STT）技術をサポートしており、
-テキストメッセージを明瞭な音声出力に変換し、ユーザーが実際の人と話しているかのように対話エージェントと対話できるようにします。
-ユーザーは、エージェントに適した音声を選択することができます。
-
-さらに、TTS は聴覚学習を好む人や忙しい中で情報を受け取りたい人にとって優れたソリューションを提供します。
-LobeChat では、異なる地域や文化的背景のユーザーのニーズに応えるために、さまざまな高品質の音声オプション（OpenAI Audio、Microsoft Edge Speech）を慎重に選択しました。
-ユーザーは、個人の好みや特定のシナリオに応じて適切な音声を選択し、パーソナライズされたコミュニケーション体験を得ることができます。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-t2i]][docs-feat-t2i]
-
-### `5` [テキストから画像生成][docs-feat-t2i]
-
-最新のテキストから画像生成技術をサポートし、LobeChat はユーザーがエージェントとの対話中に直接画像作成ツールを呼び出すことができるようになりました。
-[`DALL-E 3`](https://openai.com/dall-e-3)、[`MidJourney`](https://www.midjourney.com/)、[`Pollinations`](https://pollinations.ai/)などの AI ツールの能力を活用することで、
-エージェントはあなたのアイデアを画像に変えることができます。
-
-これにより、プライベートで没入感のある創造プロセスが可能になり、個人的な対話に視覚的なストーリーテリングをシームレスに統合することができます。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-plugin]][docs-feat-plugin]
-
-### `6` [プラグインシステム (Function Calling)][docs-feat-plugin]
-
-LobeChat のプラグインエコシステムは、そのコア機能の重要な拡張であり、LobeChat アシスタントの実用性と柔軟性を大幅に向上させます。
-
-<video controls src="https://github.com/lobehub/lobe-chat/assets/28616219/f29475a3-f346-4196-a435-41a6373ab9e2" muted="false"></video>
-
-プラグインを利用することで、LobeChat アシスタントはリアルタイムの情報を取得して処理することができ、ウェブ情報を検索し、ユーザーに即時かつ関連性の高いニュースを提供することができます。
-
-さらに、これらのプラグインはニュースの集約に限定されず、他の実用的な機能にも拡張できます。たとえば、ドキュメントの迅速な検索、画像の生成、Bilibili、Steam などのさまざまなプラットフォームからのデータの取得、さまざまなサードパーティサービスとの連携などです。
-
-> \[!TIP]
->
-> [📘 プラグインの使用][docs-usage-plugin]について詳しくはこちらをご覧ください。
-
-<!-- PLUGIN LIST -->
-
-| 最近追加                                                                                                               | 説明                                                                                                      |
-| ---------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
-| [MintbaseSearch](https://lobechat.com/discover/plugin/mintbasesearch)<br/><sup>By **mintbase** on **2024-12-31**</sup> | NEAR プロトコル上の任意の NFT データを見つける。<br/>`暗号通貨` `nft`                                     |
-| [PortfolioMeta](https://lobechat.com/discover/plugin/StockData)<br/><sup>By **portfoliometa** on **2024-12-22**</sup>  | 株を分析し、包括的なリアルタイムの投資データと分析を取得します。<br/>`stock`                              |
-| [Google CSE](https://lobechat.com/discover/plugin/google-cse)<br/><sup>By **vsnthdev** on **2024-12-02**</sup>         | 公式の CSE API を通じて Google を検索します。<br/>`ウェブ` `検索`                                         |
-| [話す](https://lobechat.com/discover/plugin/speak)<br/><sup>By **speak** on **2024-12-02**</sup>                       | Speak は、AI パワードの言語チューターで、他の言語で何でも言う方法を学ぶことができます。<br/>`教育` `言語` |
-
-> 📊 Total plugins: [<kbd>**48**</kbd>](https://lobechat.com/discover/plugins)
-
- <!-- PLUGIN LIST -->
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-agent]][docs-feat-agent]
-
-### `7` [エージェントマーケット (GPTs)][docs-feat-agent]
-
-LobeChat エージェントマーケットプレイスでは、クリエイターが多くの優れたエージェントを発見できる活気に満ちた革新的なコミュニティを提供しています。
-これらのエージェントは、仕事のシナリオで重要な役割を果たすだけでなく、学習プロセスでも大いに便利です。
-私たちのマーケットプレイスは、単なるショーケースプラットフォームではなく、協力の場でもあります。ここでは、誰もが自分の知恵を貢献し、開発したエージェントを共有できます。
-
-> \[!TIP]
->
-> [🤖/🏪 エージェントを提出][submit-agents-link]することで、簡単にエージェント作品をプラットフォームに提出できます。
-> 重要なのは、LobeChat が高度な自動化国際化（i18n）ワークフローを確立しており、
-> あなたのエージェントを複数の言語バージョンにシームレスに翻訳できることです。
-> これにより、ユーザーがどの言語を話していても、エージェントを障害なく体験できます。
-
-> \[!IMPORTANT]
->
-> すべてのユーザーがこの成長するエコシステムに参加し、エージェントの反復と最適化に参加することを歓迎します。
-> 一緒に、より面白く、実用的で革新的なエージェントを作成し、エージェントの多様性と実用性をさらに豊かにしましょう。
-
-<!-- AGENT LIST -->
-
-| 最近追加                                                                                                                                                                  | 説明                                                                                                                                |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
-| [システム指示の専門家](https://lobechat.com/discover/assistant/instructer)<br/><sup>By **[yuyun2000](https://github.com/yuyun2000)** on **2024-12-04**</sup>              | 効率的なシステム指示を精練し生成することに長けています<br/>`システム指示` `執筆` `詳細最適化` `ユーザーのニーズ`                    |
-| [日本語記憶支援者](https://lobechat.com/discover/assistant/japan-language-helper)<br/><sup>By **[sharkbear212](https://github.com/sharkbear212)** on **2024-12-04**</sup> | 日本語の五十音、ひらがな、カタカナ、単語やフレーズの説明と記憶のテクニックに特化しています<br/>`説明` `記憶テクニック` `日本語教育` |
-| [詩詞カードデザイナー](https://lobechat.com/discover/assistant/poetry-card-designer)<br/><sup>By **[lianxin255](https://github.com/lianxin255)** on **2024-12-03**</sup>  | 詩詞カードのデザインに優れ、芸術感と魅力を高めます<br/>`詩詞カードデザイン` `カード` `クリエイティブ` `アート表現`                  |
-| [日常医師](https://lobechat.com/discover/assistant/yunchat-docter)<br/><sup>By **[yuyun2000](https://github.com/yuyun2000)** on **2024-11-30**</sup>                      | 外科診療と個別化健康管理に優れています<br/>`総合診療` `外科` `健康相談` `個別化治療` `医学教育`                                     |
-
-> 📊 Total agents: [<kbd>**453**</kbd> ](https://lobechat.com/discover/assistants)
-
- <!-- AGENT LIST -->
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-database]][docs-feat-database]
-
-### `8` [ローカル / リモートデータベースのサポート][docs-feat-database]
-
-LobeChat は、サーバーサイドデータベースとローカルデータベースの両方の使用をサポートしています。ニーズに応じて、適切なデプロイメントソリューションを選択できます：
-
- **ローカルデータベース**：データとプライバシー保護に対するより多くの制御を希望するユーザーに適しています。LobeChat は CRDT（Conflict-Free Replicated Data Type）技術を使用してマルチデバイス同期を実現しています。これはシームレスなデータ同期体験を提供することを目的とした実験的な機能です。
- **サーバーサイドデータベース**：より便利なユーザー体験を希望するユーザーに適しています。LobeChat は PostgreSQL をサーバーサイドデータベースとしてサポートしています。サーバーサイドデータベースの設定方法についての詳細なドキュメントは、[サーバーサイドデータベースの設定](https://lobehub.com/docs/self-hosting/advanced/server-database)をご覧ください。
-
-どのデータベースを選択しても、LobeChat は優れたユーザー体験を提供します。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-auth]][docs-feat-auth]
-
-### `9` [マルチユーザ管理のサポート][docs-feat-auth]
-
-LobeChat はマルチユーザ管理をサポートし、異なるニーズに応じて 2 つの主要なユーザ認証および管理ソリューションを提供します：
-
- **next-auth**：LobeChat は、複数の認証方法（OAuth、メールログイン、資格情報ログインなど）をサポートする柔軟で強力な認証ライブラリである`next-auth`を統合しています。`next-auth`を使用すると、ユーザの登録、ログイン、セッション管理、ソーシャルログインなどの機能を簡単に実装し、ユーザデータのセキュリティとプライバシーを確保できます。
-
- **Clerk**：より高度なユーザ管理機能が必要なユーザ向けに、LobeChat は`Clerk`もサポートしています。`Clerk`は、現代的なユーザ管理プラットフォームであり、多要素認証（MFA）、ユーザプロファイル管理、ログイン活動の監視など、より豊富な機能を提供します。`Clerk`を使用すると、より高いセキュリティと柔軟性を得ることができ、複雑なユーザ管理ニーズに簡単に対応できます。
-
-どのユーザ管理ソリューションを選択しても、LobeChat は優れたユーザー体験と強力な機能サポートを提供します。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-pwa]][docs-feat-pwa]
-
-### `10` [プログレッシブウェブアプリ (PWA)][docs-feat-pwa]
-
-私たちは、今日のマルチデバイス環境でユーザーにシームレスな体験を提供することの重要性を深く理解しています。
-そのため、プログレッシブウェブアプリケーション（[PWA](https://support.google.com/chrome/answer/9658361)）技術を採用しました。
-これは、ウェブアプリケーションをネイティブアプリに近い体験に引き上げるモダンなウェブ技術です。
-
-PWA を通じて、LobeChat はデスクトップとモバイルデバイスの両方で高度に最適化されたユーザー体験を提供しながら、その軽量で高性能な特性を維持します。
-視覚的および感覚的には、インターフェースを慎重に設計し、ネイティブアプリと区別がつかないようにし、
-スムーズなアニメーション、レスポンシブレイアウト、および異なるデバイスの画面解像度に適応するようにしています。
-
-> \[!NOTE]
->
-> PWA のインストールプロセスに慣れていない場合は、以下の手順に従って LobeChat をデスクトップアプリケーション（モバイルデバイスにも適用）として追加できます：
->
-> - コンピュータで Chrome または Edge ブラウザを起動します。
-> - LobeChat のウェブページにアクセスします。
-> - アドレスバーの右上にある<kbd>インストール</kbd>アイコンをクリックします。
-> - 画面の指示に従って PWA のインストールを完了します。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-mobile]][docs-feat-mobile]
-
-### `11` [モバイルデバイスの適応][docs-feat-mobile]
-
-モバイルデバイスのユーザー体験を向上させるために、一連の最適化設計を行いました。現在、モバイルユーザー体験のバージョンを繰り返し改善しています。ご意見やアイデアがある場合は、GitHub Issues や Pull Requests を通じてフィードバックをお寄せください。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-theme]][docs-feat-theme]
-
-### `12` [カスタムテーマ][docs-feat-theme]
-
-デザインエンジニアリング指向のアプリケーションとして、LobeChat はユーザーの個別体験を重視しており、
-柔軟で多様なテーマモードを導入しています。日中のライトモードと夜間のダークモードを含みます。
-テーマモードの切り替えに加えて、さまざまな色のカスタマイズオプションを提供し、ユーザーが自分の好みに応じてアプリケーションのテーマカラーを調整できるようにしています。
-落ち着いたダークブルー、活気のあるピーチピンク、プロフェッショナルなグレーホワイトなど、LobeChat では自分のスタイルに合った色の選択肢を見つけることができます。
-
-> \[!TIP]
->
-> デフォルトの設定は、ユーザーのシステムのカラーモードをインテリジェントに認識し、テーマを自動的に切り替えて、オペレーティングシステムと一貫した視覚体験を提供します。
-> 詳細を手動で制御するのが好きなユーザーには、直感的な設定オプションと、会話シナリオに対してチャットバブルモードとドキュメントモードの選択肢を提供します。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-### `*` その他の特徴
-
-これらの特徴に加えて、LobeChat は基本的な技術基盤も優れています：
-
- [x] 💨 **迅速なデプロイ**：Vercel プラットフォームまたは Docker イメージを使用して、ワンクリックでデプロイを行い、1 分以内にプロセスを完了できます。複雑な設定は不要です。
- [x] 🌐 **カスタムドメイン**：ユーザーが独自のドメインを持っている場合、プラットフォームにバインドして、どこからでも対話エージェントに迅速にアクセスできます。
- [x] 🔒 **プライバシー保護**：すべてのデータはユーザーのブラウザにローカルに保存され、ユーザーのプライバシーを保護します。
- [x] 💎 **洗練された UI デザイン**：慎重に設計されたインターフェースで、エレガントな外観とスムーズなインタラクションを提供します。ライトモードとダークモードをサポートし、モバイルフレンドリーです。PWA サポートにより、よりネイティブに近い体験を提供します。
- [x] 🗣️ **スムーズな会話体験**：流れるような応答により、スムーズな会話体験を提供します。Markdown レンダリングを完全にサポートし、コードのハイライト、LaTex の数式、Mermaid のフローチャートなどを含みます。
-
-> ✨ LobeChat の進化に伴い、さらに多くの機能が追加されます。
-
---
-
-> \[!NOTE]
->
-> 今後の[ロードマップ][github-project-link]計画は、Projects セクションで確認できます。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-## ⚡️ パフォーマンス
-
-> \[!NOTE]
->
-> 完全なレポートのリストは[📘 Lighthouse レポート][docs-lighthouse]で確認できます。
-
-|                 デスクトップ                  |                   モバイル                   |
-| :-------------------------------------------: | :------------------------------------------: |
-|               ![][chat-desktop]               |               ![][chat-mobile]               |
-| [📑 Lighthouse レポート][chat-desktop-report] | [📑 Lighthouse レポート][chat-mobile-report] |
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-## 🛳 自己ホスティング
-
-LobeChat は、Vercel と[Docker イメージ][docker-release-link]を使用した自己ホスティングバージョンを提供しています。これにより、事前の知識がなくても数分で独自のチャットボットをデプロイできます。
-
-> \[!TIP]
->
-> [📘 独自の LobeChat を構築する][docs-self-hosting]について詳しくはこちらをご覧ください。
-
-### `A` Vercel、Zeabur、Sealos でのデプロイ
-
-このサービスを Vercel または Zeabur でデプロイしたい場合は、以下の手順に従ってください：
-
- [OpenAI API Key](https://platform.openai.com/account/api-keys)を準備します。
- 下のボタンをクリックしてデプロイを開始します：GitHub アカウントで直接ログインし、環境変数セクションに`OPENAI_API_KEY`（必須）と`ACCESS_CODE`（推奨）を入力します。
- デプロイが完了したら、使用を開始できます。
- カスタムドメインをバインド（オプション）：Vercel が割り当てたドメインの DNS は一部の地域で汚染されているため、カスタムドメインをバインドすることで直接接続できます。
-
-<div align="center">
-
-|            Vercel でデプロイ            |                      Zeabur でデプロイ                      |                      Sealos でデプロイ                      |
-| :-------------------------------------: | :---------------------------------------------------------: | :---------------------------------------------------------: |
-| [![][deploy-button-image]][deploy-link] | [![][deploy-on-zeabur-button-image]][deploy-on-zeabur-link] | [![][deploy-on-sealos-button-image]][deploy-on-sealos-link] |
-
-</div>
-
-#### フォーク後
-
-フォーク後、リポジトリのアクションページで他のアクションを無効にし、アップストリーム同期アクションのみを保持します。
-
-#### 更新を維持
-
-README のワンクリックデプロイ手順に従って独自のプロジェクトをデプロイした場合、「更新が利用可能です」というプロンプトが常に表示されることがあります。これは、Vercel がデフォルトで新しいプロジェクトを作成し、フォークしないため、更新を正確に検出できないためです。
-
-> \[!TIP]
->
-> [📘 最新バージョンと自動同期][docs-upstream-sync]の手順に従って再デプロイすることをお勧めします。
-
-<br/>
-
-### `B` Docker でのデプロイ
-
-[![][docker-release-shield]][docker-release-link]
-[![][docker-size-shield]][docker-size-link]
-[![][docker-pulls-shield]][docker-pulls-link]
-
-LobeChat サービスを独自のプライベートデバイスにデプロイするための Docker イメージを提供しています。以下のコマンドを使用して LobeChat サービスを開始します：
-
-```fish
-$ docker run -d -p 3210:3210 \
-  -e OPENAI_API_KEY=sk-xxxx \
-  -e ACCESS_CODE=lobe66 \
-  --name lobe-chat \
-  lobehub/lobe-chat
-```
-
-> \[!TIP]
->
-> OpenAI サービスをプロキシ経由で使用する必要がある場合は、`OPENAI_PROXY_URL`環境変数を使用してプロキシアドレスを設定できます：
-
-```fish
-$ docker run -d -p 3210:3210 \
-  -e OPENAI_API_KEY=sk-xxxx \
-  -e OPENAI_PROXY_URL=https://api-proxy.com/v1 \
-  -e ACCESS_CODE=lobe66 \
-  --name lobe-chat \
-  lobehub/lobe-chat
-```
-
-> \[!NOTE]
->
-> Docker を使用したデプロイの詳細な手順については、[📘 Docker デプロイガイド][docs-docker]を参照してください。
-
-<br/>
-
-### 環境変数
-
-このプロジェクトは、環境変数で設定される追加の構成項目を提供します：
-
-| 環境変数            | 必須   | 説明                                                                                                                                                                                                      | 例                                                                                                                   |
-| ------------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
-| `OPENAI_API_KEY`    | はい   | これは OpenAI アカウントページで申請した API キーです                                                                                                                                                     | `sk-xxxxxx...xxxxxx`                                                                                                 |
-| `OPENAI_PROXY_URL`  | いいえ | OpenAI インターフェイスプロキシを手動で設定する場合、この設定項目を使って、デフォルトの OpenAI API リクエストベース URL を上書きすることができます。                                                      | `https://api.chatanywhere.cn` または `https://aihubmix.com/v1` <br/>デフォルトの値は<br/>`https://api.openai.com/v1` |
-| `ACCESS_CODE`       | いいえ | このサービスにアクセスするためのパスワードを追加します。漏洩を避けるために長いパスワードを設定することができます。この値にカンマが含まれる場合は、パスワードの配列となります。                            | `awCTe)re_r74` または `rtrt_ewee3@09!` または `code1,code2,code3`                                                    |
-| `OPENAI_MODEL_LIST` | いいえ | モデルリストをコントロールするために使用します。モデルを追加するには `+` を、モデルを非表示にするには `-` を、モデルの表示名をカンマ区切りでカスタマイズするには `model_name=display_name` を使用します。 | `qwen-7b-chat,+glm-6b,-gpt-3.5-turbo`                                                                                |
-
-> \[!NOTE]
->
-> 環境変数の完全なリストは [📘環境変数][docs-env-var] にあります
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-## 📦 エコシステム
-
-| NPM                               | リポジトリ                              | 説明                                                                                  | バージョン                                |
-| --------------------------------- | --------------------------------------- | ------------------------------------------------------------------------------------- | ----------------------------------------- |
-| [@lobehub/ui][lobe-ui-link]       | [lobehub/lobe-ui][lobe-ui-github]       | AIGC ウェブアプリケーション構築専用のオープンソース UI コンポーネントライブラリ。     | [![][lobe-ui-shield]][lobe-ui-link]       |
-| [@lobehub/icons][lobe-icons-link] | [lobehub/lobe-icons][lobe-icons-github] | 人気の AI/LLM モデルブランドの SVG ロゴとアイコン集。                                 | [![][lobe-icons-shield]][lobe-icons-link] |
-| [@lobehub/tts][lobe-tts-link]     | [lobehub/lobe-tts][lobe-tts-github]     | 高品質で信頼性の高い TTS/STT React Hooks ライブラリ                                   | [![][lobe-tts-shield]][lobe-tts-link]     |
-| [@lobehub/lint][lobe-lint-link]   | [lobehub/lobe-lint][lobe-lint-github]   | LobeHub の ESlint、Stylelint、Commitlint、Prettier、Remark、Semantic Release の設定。 | [![][lobe-lint-shield]][lobe-lint-link]   |
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-## 🧩 プラグイン
-
-プラグインは、LobeChat の[関数呼び出し][docs-functionc-call]機能を拡張する手段を提供します。プラグインを使用して、新しい関数呼び出しやメッセージ結果の新しいレンダリング方法を導入することができます。プラグイン開発に興味がある方は、Wiki の[📘プラグイン開発ガイド][docs-plugin-dev]を参照してください。
-
- [lobe-chat-plugins][lobe-chat-plugins]: これは LobeChat のプラグインインデックスです。このリポジトリから index.json にアクセスし、LobeChat で利用可能なプラグインのリストをユーザに表示します。
- [chat-plugin-template][chat-plugin-template]: これは LobeChat プラグイン開発用のプラグインテンプレートです。
- [@lobehub/chat-plugin-sdk][chat-plugin-sdk]: LobeChat プラグイン SDK は、Lobe Chat 用の優れたチャットプラグインの作成を支援します。
- [@lobehub/chat-plugins-gateway][chat-plugins-gateway]: LobeChat Plugins Gateway は、LobeChat プラグインのためのゲートウェイを提供するバックエンドサービスです。このサービスは Vercel を使用してデプロイされます。プライマリ API の POST /api/v1/runner は Edge Function としてデプロイされます。
-
-> \[!NOTE]
->
-> プラグインシステムは現在大規模な開発中です。詳しくは以下の issue をご覧ください:
->
-> - [x] [**プラグインフェイズ 1**](https://github.com/lobehub/lobe-chat/issues/73): プラグインを本体から分離し、メンテナンスのためにプラグインを独立したリポジトリに分割し、プラグインの動的ロードを実現する。
-> - [x] [**プラグインフェイズ 2**](https://github.com/lobehub/lobe-chat/issues/97): プラグイン使用の安全性と安定性、より正確な異常状態の提示、プラグインアーキテクチャの保守性、開発者フレンドリー。
-> - [x] [**プラグインフェイズ 3**](https://github.com/lobehub/lobe-chat/issues/149): より高度で包括的なカスタマイズ機能、プラグイン認証のサポート、サンプル。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-## ⌨️ ローカル開発
-
-GitHub Codespaces を使ってオンライン開発ができます:
-
-[![][codespaces-shield]][codespaces-link]
-
-Or clone it for local development:
-
-```fish
-$ git clone https://github.com/lobehub/lobe-chat.git
-$ cd lobe-chat
-$ pnpm install
-$ pnpm dev
-```
-
-より詳しい情報をお知りになりたい方は、[📘開発ガイド][docs-dev-guide]をご覧ください。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-## 🤝 コントリビュート
-
-どのようなタイプのコントリビュートも大歓迎です；コードを提供することに興味がある方は、GitHub の [Issues][github-issues-link] や [Projects][github-project-link] をチェックして、あなたの力をお貸しください。
-
-> \[!TIP]
->
-> 私たちは技術主導のフォーラムを創設し、知識の交流とアイデアの交換を促進することで、相互のインスピレーションと協力的なイノベーションを生み出すことを目指しています。
->
-> LobeChat の改善にご協力ください。製品設計のフィードバックやユーザー体験に関するディスカッションを直接お寄せください。
->
-> **プリンシパルメンテナー:** [@arvinxx](https://github.com/arvinxx) [@canisminor1990](https://github.com/canisminor1990)
-
-[![][pr-welcome-shield]][pr-welcome-link]
-[![][submit-agents-shield]][submit-agents-link]
-[![][submit-plugin-shield]][submit-plugin-link]
-
-<a href="https://github.com/lobehub/lobe-chat/graphs/contributors" target="_blank">
-  <table>
-    <tr>
-      <th colspan="2">
-        <br><img src="https://contrib.rocks/image?repo=lobehub/lobe-chat"><br><br>
-      </th>
-    </tr>
-    <tr>
-      <td>
-        <picture>
-          <source media="(prefers-color-scheme: dark)" srcset="https://next.ossinsight.io/widgets/official/compose-org-active-contributors/thumbnail.png?activity=active&period=past_28_days&owner_id=131470832&repo_ids=643445235&image_size=2x3&color_scheme=dark">
-          <img src="https://next.ossinsight.io/widgets/official/compose-org-active-contributors/thumbnail.png?activity=active&period=past_28_days&owner_id=131470832&repo_ids=643445235&image_size=2x3&color_scheme=light">
-        </picture>
-      </td>
-      <td rowspan="2">
-        <picture>
-          <source media="(prefers-color-scheme: dark)" srcset="https://next.ossinsight.io/widgets/official/compose-org-participants-growth/thumbnail.png?activity=active&period=past_28_days&owner_id=131470832&repo_ids=643445235&image_size=4x7&color_scheme=dark">
-          <img src="https://next.ossinsight.io/widgets/official/compose-org-participants-growth/thumbnail.png?activity=active&period=past_28_days&owner_id=131470832&repo_ids=643445235&image_size=4x7&color_scheme=light">
-        </picture>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <picture>
-          <source media="(prefers-color-scheme: dark)" srcset="https://next.ossinsight.io/widgets/official/compose-org-active-contributors/thumbnail.png?activity=new&period=past_28_days&owner_id=131470832&repo_ids=643445235&image_size=2x3&color_scheme=dark">
-          <img src="https://next.ossinsight.io/widgets/official/compose-org-active-contributors/thumbnail.png?activity=new&period=past_28_days&owner_id=131470832&repo_ids=643445235&image_size=2x3&color_scheme=light">
-        </picture>
-      </td>
-    </tr>
-  </table>
-</a>
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-## ❤️ スポンサー
-
-あなたの一度きりの寄付が、私たちの銀河系で輝きを放ちます！皆様は流れ星であり、私たちの旅路に迅速かつ明るい影響を与えます。私たちを信じてくださり、ありがとうございます。皆様の寛大なお気持ちが、私たちの使命に向かって、一度に輝かしい閃光を放つよう導いてくださるのです。
-
-<a href="https://opencollective.com/lobehub" target="_blank">
-  <picture>
-    <source media="(prefers-color-scheme: dark)" srcset="https://github.com/lobehub/.github/blob/main/static/sponsor-dark.png?raw=true">
-    <img  src="https://github.com/lobehub/.github/blob/main/static/sponsor-light.png?raw=true">
-  </picture>
-</a>
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-## 🔗 その他の製品
-
- **[🅰️ Lobe SD Theme][lobe-theme]:** Stable Diffusion WebUI のためのモダンなテーマ、絶妙なインターフェースデザイン、高度にカスタマイズ可能な UI、効率を高める機能。
- **[⛵️ Lobe Midjourney WebUI][lobe-midjourney-webui]:** Midjourney の WebUI は、AI を活用しテキストプロンプトから豊富で多様な画像を素早く生成し、創造性を刺激して会話を盛り上げます。
- **[🌏 Lobe i18n][lobe-i18n] :** Lobe i18n は ChatGPT を利用した国際化翻訳プロセスの自動化ツールです。大きなファイルの自動分割、増分更新、OpenAI モデル、API プロキシ、温度のカスタマイズオプションなどの機能をサポートしています。
- **[💌 Lobe Commit][lobe-commit]:** Lobe Commit は、Langchain/ChatGPT を活用して Gitmoji ベースのコミットメッセージを生成する CLI ツールです。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
---
-
-<details><summary><h4>📝 License</h4></summary>
-
-[![][fossa-license-shield]][fossa-license-link]
-
-</details>
-
-Copyright © 2024 [LobeHub][profile-link]. <br />
-This project is [Apache 2.0](./LICENSE) licensed.
-
-<!-- LINK GROUP -->
-
-[back-to-top]: https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square
-[blog]: https://lobehub.com/blog
-[changelog]: https://lobehub.com/changelog
-[chat-desktop]: https://raw.githubusercontent.com/lobehub/lobe-chat/lighthouse/lighthouse/chat/desktop/pagespeed.svg
-[chat-desktop-report]: https://lobehub.github.io/lobe-chat/lighthouse/chat/desktop/chat_preview_lobehub_com_chat.html
-[chat-mobile]: https://raw.githubusercontent.com/lobehub/lobe-chat/lighthouse/lighthouse/chat/mobile/pagespeed.svg
-[chat-mobile-report]: https://lobehub.github.io/lobe-chat/lighthouse/chat/mobile/chat_preview_lobehub_com_chat.html
-[chat-plugin-sdk]: https://github.com/lobehub/chat-plugin-sdk
-[chat-plugin-template]: https://github.com/lobehub/chat-plugin-template
-[chat-plugins-gateway]: https://github.com/lobehub/chat-plugins-gateway
-[codecov-link]: https://codecov.io/gh/lobehub/lobe-chat
-[codecov-shield]: https://img.shields.io/codecov/c/github/lobehub/lobe-chat?labelColor=black&style=flat-square&logo=codecov&logoColor=white
-[codespaces-link]: https://codespaces.new/lobehub/lobe-chat
-[codespaces-shield]: https://github.com/codespaces/badge.svg
-[deploy-button-image]: https://vercel.com/button
-[deploy-link]: https://vercel.com/new/clone?repository-url=https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat&env=OPENAI_API_KEY,ACCESS_CODE&envDescription=Find%20your%20OpenAI%20API%20Key%20by%20click%20the%20right%20Learn%20More%20button.%20%7C%20Access%20Code%20can%20protect%20your%20website&envLink=https%3A%2F%2Fplatform.openai.com%2Faccount%2Fapi-keys&project-name=lobe-chat&repository-name=lobe-chat
-[deploy-on-sealos-button-image]: https://raw.githubusercontent.com/labring-actions/templates/main/Deploy-on-Sealos.svg
-[deploy-on-sealos-link]: https://cloud.sealos.io/?openapp=system-template%3FtemplateName%3Dlobe-chat
-[deploy-on-zeabur-button-image]: https://zeabur.com/button.svg
-[deploy-on-zeabur-link]: https://zeabur.com/templates/VZGGTI
-[discord-link]: https://discord.gg/AYFPHvv2jT
-[discord-shield]: https://img.shields.io/discord/1127171173982154893?color=5865F2&label=discord&labelColor=black&logo=discord&logoColor=white&style=flat-square
-[discord-shield-badge]: https://img.shields.io/discord/1127171173982154893?color=5865F2&label=discord&labelColor=black&logo=discord&logoColor=white&style=for-the-badge
-[docker-pulls-link]: https://hub.docker.com/r/lobehub/lobe-chat
-[docker-pulls-shield]: https://img.shields.io/docker/pulls/lobehub/lobe-chat?color=45cc11&labelColor=black&style=flat-square
-[docker-release-link]: https://hub.docker.com/r/lobehub/lobe-chat
-[docker-release-shield]: https://img.shields.io/docker/v/lobehub/lobe-chat?color=369eff&label=docker&labelColor=black&logo=docker&logoColor=white&style=flat-square
-[docker-size-link]: https://hub.docker.com/r/lobehub/lobe-chat
-[docker-size-shield]: https://img.shields.io/docker/image-size/lobehub/lobe-chat?color=369eff&labelColor=black&style=flat-square
-[docs]: https://lobehub.com/docs/usage/start
-[docs-dev-guide]: https://github.com/lobehub/lobe-chat/wiki/index
-[docs-docker]: https://lobehub.com/docs/self-hosting/platform/docker
-[docs-env-var]: https://lobehub.com/docs/self-hosting/environment-variables
-[docs-feat-agent]: https://lobehub.com/docs/usage/features/agent-market
-[docs-feat-auth]: https://lobehub.com/docs/usage/features/auth
-[docs-feat-database]: https://lobehub.com/docs/usage/features/database
-[docs-feat-local]: https://lobehub.com/docs/usage/features/local-llm
-[docs-feat-mobile]: https://lobehub.com/docs/usage/features/mobile
-[docs-feat-plugin]: https://lobehub.com/docs/usage/features/plugin-system
-[docs-feat-provider]: https://lobehub.com/docs/usage/features/multi-ai-providers
-[docs-feat-pwa]: https://lobehub.com/docs/usage/features/pwa
-[docs-feat-t2i]: https://lobehub.com/docs/usage/features/text-to-image
-[docs-feat-theme]: https://lobehub.com/docs/usage/features/theme
-[docs-feat-tts]: https://lobehub.com/docs/usage/features/tts
-[docs-feat-vision]: https://lobehub.com/docs/usage/features/vision
-[docs-functionc-call]: https://lobehub.com/blog/openai-function-call
-[docs-lighthouse]: https://github.com/lobehub/lobe-chat/wiki/Lighthouse
-[docs-plugin-dev]: https://lobehub.com/docs/usage/plugins/development
-[docs-self-hosting]: https://lobehub.com/docs/self-hosting/start
-[docs-upstream-sync]: https://lobehub.com/docs/self-hosting/advanced/upstream-sync
-[docs-usage-ollama]: https://lobehub.com/docs/usage/providers/ollama
-[docs-usage-plugin]: https://lobehub.com/docs/usage/plugins/basic
-[fossa-license-link]: https://app.fossa.com/projects/git%2Bgithub.com%2Flobehub%2Flobe-chat
-[fossa-license-shield]: https://app.fossa.com/api/projects/git%2Bgithub.com%2Flobehub%2Flobe-chat.svg?type=large
-[github-action-release-link]: https://github.com/actions/workflows/lobehub/lobe-chat/release.yml
-[github-action-release-shield]: https://img.shields.io/github/actions/workflow/status/lobehub/lobe-chat/release.yml?label=release&labelColor=black&logo=githubactions&logoColor=white&style=flat-square
-[github-action-test-link]: https://github.com/actions/workflows/lobehub/lobe-chat/test.yml
-[github-action-test-shield]: https://img.shields.io/github/actions/workflow/status/lobehub/lobe-chat/test.yml?label=test&labelColor=black&logo=githubactions&logoColor=white&style=flat-square
-[github-contributors-link]: https://github.com/lobehub/lobe-chat/graphs/contributors
-[github-contributors-shield]: https://img.shields.io/github/contributors/lobehub/lobe-chat?color=c4f042&labelColor=black&style=flat-square
-[github-forks-link]: https://github.com/lobehub/lobe-chat/network/members
-[github-forks-shield]: https://img.shields.io/github/forks/lobehub/lobe-chat?color=8ae8ff&labelColor=black&style=flat-square
-[github-issues-link]: https://github.com/lobehub/lobe-chat/issues
-[github-issues-shield]: https://img.shields.io/github/issues/lobehub/lobe-chat?color=ff80eb&labelColor=black&style=flat-square
-[github-license-link]: https://github.com/lobehub/lobe-chat/blob/main/LICENSE
-[github-license-shield]: https://img.shields.io/badge/license-apache%202.0-white?labelColor=black&style=flat-square
-[github-project-link]: https://github.com/lobehub/lobe-chat/projects
-[github-release-link]: https://github.com/lobehub/lobe-chat/releases
-[github-release-shield]: https://img.shields.io/github/v/release/lobehub/lobe-chat?color=369eff&labelColor=black&logo=github&style=flat-square
-[github-releasedate-link]: https://github.com/lobehub/lobe-chat/releases
-[github-releasedate-shield]: https://img.shields.io/github/release-date/lobehub/lobe-chat?labelColor=black&style=flat-square
-[github-stars-link]: https://github.com/lobehub/lobe-chat/network/stargazers
-[github-stars-shield]: https://img.shields.io/github/stars/lobehub/lobe-chat?color=ffcb47&labelColor=black&style=flat-square
-[github-trending-shield]: https://trendshift.io/api/badge/repositories/2256
-[github-trending-url]: https://trendshift.io/repositories/2256
-[image-banner]: https://github.com/lobehub/lobe-chat/assets/28616219/9f155dff-4737-429f-9cad-a70a1a860c5f
-[image-feat-agent]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/268670869-f1ffbf66-42b6-42cf-a937-9ce1f8328514.png
-[image-feat-auth]: https://github.com/lobehub/lobe-chat/assets/17870709/8ce70e15-40df-451e-b700-66090fe5b8c2
-[image-feat-database]: https://github.com/lobehub/lobe-chat/assets/17870709/c27a0234-a4e9-40e5-8bcb-42d5ce7e40f9
-[image-feat-local]: https://github.com/lobehub/lobe-chat/assets/28616219/ca9a21bc-ea6c-4c90-bf4a-fa53b4fb2b5c
-[image-feat-mobile]: https://gw.alipayobjects.com/zos/kitchen/R441AuFS4W/mobile.webp
-[image-feat-plugin]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/268670883-33c43a5c-a512-467e-855c-fa299548cce5.png
-[image-feat-privoder]: https://github.com/lobehub/lobe-chat/assets/28616219/b164bc54-8ba2-4c1e-b2f2-f4d7f7e7a551
-[image-feat-pwa]: https://gw.alipayobjects.com/zos/kitchen/69x6bllkX3/pwa.webp
-[image-feat-t2i]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/297746445-0ff762b9-aa08-4337-afb7-12f932b6efbb.png
-[image-feat-theme]: https://gw.alipayobjects.com/zos/kitchen/pvus1lo%26Z7/darkmode.webp
-[image-feat-tts]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/284072124-c9853d8d-f1b5-44a8-a305-45ebc0f6d19a.png
-[image-feat-vision]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/284072129-382bdf30-e3d6-4411-b5a0-249710b8ba08.png
-[image-overview]: https://github.com/lobehub/lobe-chat/assets/17870709/56b95d48-f573-41cd-8b38-387bf88bc4bf
-[image-star]: https://github.com/lobehub/lobe-chat/assets/17870709/cb06b748-513f-47c2-8740-d876858d7855
-[issues-link]: https://img.shields.io/github/issues/lobehub/lobe-chat.svg?style=flat
-[lobe-chat-plugins]: https://github.com/lobehub/lobe-chat-plugins
-[lobe-commit]: https://github.com/lobehub/lobe-commit/tree/master/packages/lobe-commit
-[lobe-i18n]: https://github.com/lobehub/lobe-commit/tree/master/packages/lobe-i18n
-[lobe-icons-github]: https://github.com/lobehub/lobe-icons
-[lobe-icons-link]: https://www.npmjs.com/package/@lobehub/icons
-[lobe-icons-shield]: https://img.shields.io/npm/v/@lobehub/icons?color=369eff&labelColor=black&logo=npm&logoColor=white&style=flat-square
-[lobe-lint-github]: https://github.com/lobehub/lobe-lint
-[lobe-lint-link]: https://www.npmjs.com/package/@lobehub/lint
-[lobe-lint-shield]: https://img.shields.io/npm/v/@lobehub/lint?color=369eff&labelColor=black&logo=npm&logoColor=white&style=flat-square
-[lobe-midjourney-webui]: https://github.com/lobehub/lobe-midjourney-webui
-[lobe-theme]: https://github.com/lobehub/sd-webui-lobe-theme
-[lobe-tts-github]: https://github.com/lobehub/lobe-tts
-[lobe-tts-link]: https://www.npmjs.com/package/@lobehub/tts
-[lobe-tts-shield]: https://img.shields.io/npm/v/@lobehub/tts?color=369eff&labelColor=black&logo=npm&logoColor=white&style=flat-square
-[lobe-ui-github]: https://github.com/lobehub/lobe-ui
-[lobe-ui-link]: https://www.npmjs.com/package/@lobehub/ui
-[lobe-ui-shield]: https://img.shields.io/npm/v/@lobehub/ui?color=369eff&labelColor=black&logo=npm&logoColor=white&style=flat-square
-[official-site]: https://lobehub.com
-[pr-welcome-link]: https://github.com/lobehub/lobe-chat/pulls
-[pr-welcome-shield]: https://img.shields.io/badge/🤯_pr_welcome-%E2%86%92-ffcb47?labelColor=black&style=for-the-badge
-[profile-link]: https://github.com/lobehub
-[share-linkedin-link]: https://linkedin.com/feed
-[share-linkedin-shield]: https://img.shields.io/badge/-share%20on%20linkedin-black?labelColor=black&logo=linkedin&logoColor=white&style=flat-square
-[share-mastodon-link]: https://mastodon.social/share?text=Check%20this%20GitHub%20repository%20out%20%F0%9F%A4%AF%20LobeChat%20-%20An%20open-source,%20extensible%20(Function%20Calling),%20high-performance%20chatbot%20framework.%20It%20supports%20one-click%20free%20deployment%20of%20your%20private%20ChatGPT/LLM%20web%20application.%20https://github.com/lobehub/lobe-chat%20#chatbot%20#chatGPT%20#openAI
-[share-mastodon-shield]: https://img.shields.io/badge/-share%20on%20mastodon-black?labelColor=black&logo=mastodon&logoColor=white&style=flat-square
-[share-reddit-link]: https://www.reddit.com/submit?title=Check%20this%20GitHub%20repository%20out%20%F0%9F%A4%AF%20LobeChat%20-%20An%20open-source%2C%20extensible%20%28Function%20Calling%29%2C%20high-performance%20chatbot%20framework.%20It%20supports%20one-click%20free%20deployment%20of%20your%20private%20ChatGPT%2FLLM%20web%20application.%20%23chatbot%20%23chatGPT%20%23openAI&url=https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat
-[share-reddit-shield]: https://img.shields.io/badge/-share%20on%20reddit-black?labelColor=black&logo=reddit&logoColor=white&style=flat-square
-[share-telegram-link]: https://t.me/share/url"?text=Check%20this%20GitHub%20repository%20out%20%F0%9F%A4%AF%20LobeChat%20-%20An%20open-source%2C%20extensible%20%28Function%20Calling%29%2C%20high-performance%20chatbot%20framework.%20It%20supports%20one-click%20free%20deployment%20of%20your%20private%20ChatGPT%2FLLM%20web%20application.%20%23chatbot%20%23chatGPT%20%23openAI&url=https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat
-[share-telegram-shield]: https://img.shields.io/badge/-share%20on%20telegram-black?labelColor=black&logo=telegram&logoColor=white&style=flat-square
-[share-weibo-link]: http://service.weibo.com/share/share.php?sharesource=weibo&title=Check%20this%20GitHub%20repository%20out%20%F0%9F%A4%AF%20LobeChat%20-%20An%20open-source%2C%20extensible%20%28Function%20Calling%29%2C%20high-performance%20chatbot%20framework.%20It%20supports%20one-click%20free%20deployment%20of%20your%20private%20ChatGPT%2FLLM%20web%20application.%20%23chatbot%20%23chatGPT%20%23openAI&url=https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat
-[share-weibo-shield]: https://img.shields.io/badge/-share%20on%20weibo-black?labelColor=black&logo=sinaweibo&logoColor=white&style=flat-square
-[share-whatsapp-link]: https://api.whatsapp.com/send?text=Check%20this%20GitHub%20repository%20out%20%F0%9F%A4%AF%20LobeChat%20-%20An%20open-source%2C%20extensible%20%28Function%20Calling%29%2C%20high-performance%20chatbot%20framework.%20It%20supports%20one-click%20free%20deployment%20of%20your%20private%20ChatGPT%2FLLM%20web%20application.%20https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat%20%23chatbot%20%23chatGPT%20%23openAI
-[share-whatsapp-shield]: https://img.shields.io/badge/-share%20on%20whatsapp-black?labelColor=black&logo=whatsapp&logoColor=white&style=flat-square
-[share-x-link]: https://x.com/intent/tweet?hashtags=chatbot%2CchatGPT%2CopenAI&text=Check%20this%20GitHub%20repository%20out%20%F0%9F%A4%AF%20LobeChat%20-%20An%20open-source%2C%20extensible%20%28Function%20Calling%29%2C%20high-performance%20chatbot%20framework.%20It%20supports%20one-click%20free%20deployment%20of%20your%20private%20ChatGPT%2FLLM%20web%20application.&url=https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat
-[share-x-shield]: https://img.shields.io/badge/-share%20on%20x-black?labelColor=black&logo=x&logoColor=white&style=flat-square
-[sponsor-link]: https://opencollective.com/lobehub 'Become ❤️ LobeHub Sponsor'
-[sponsor-shield]: https://img.shields.io/badge/-Sponsor%20LobeHub-f04f88?logo=opencollective&logoColor=white&style=flat-square
-[submit-agents-link]: https://github.com/lobehub/lobe-chat-agents
-[submit-agents-shield]: https://img.shields.io/badge/🤖/🏪_submit_agent-%E2%86%92-c4f042?labelColor=black&style=for-the-badge
-[submit-plugin-link]: https://github.com/lobehub/lobe-chat-plugins
-[submit-plugin-shield]: https://img.shields.io/badge/🧩/🏪_submit_plugin-%E2%86%92-95f3d9?labelColor=black&style=for-the-badge
-[vercel-link]: https://chat-preview.lobehub.com
-[vercel-shield]: https://img.shields.io/badge/vercel-online-55b467?labelColor=black&logo=vercel&style=flat-square
-[vercel-shield-badge]: https://img.shields.io/badge/TRY%20LOBECHAT-ONLINE-55b467?labelColor=black&logo=vercel&style=for-the-badge
@@ -1,14 +1,21 @@
+> \[!NOTE]
+>
+> **Version Information**
+>
+> - **v1.x** (Stable): Available on the [`main`](https://github.com/lobehub/lobe-chat/tree/main) branch
+> - **v2.x** (In Development): Currently being actively developed on the [`next`](https://github.com/lobehub/lobe-chat/tree/next) branch 🔥
+
 <div align="center"><a name="readme-top"></a>

 [![][image-banner]][vercel-link]

 # Lobe Chat

-An open-source, modern-design ChatGPT/LLMs UI/Framework.<br/>
-Supports speech-synthesis, multi-modal, and extensible ([function call][docs-functionc-call]) plugin system.<br/>
+An open-source, modern design ChatGPT/LLMs UI/framework.<br/>
+Supports speech synthesis, multi-modal, and extensible ([function call][docs-function-call]) plugin system.<br/>
 One-click **FREE** deployment of your private OpenAI ChatGPT/Claude/Gemini/Groq/Ollama chat application.

-**English** · [繁體中文](./README.zh-TW.md) · [简体中文](./README.zh-CN.md) · [日本語](./README.ja-JP.md) · [Official Site][official-site] · [Changelog][changelog] · [Documents][docs] · [Blog][blog] · [Feedback][github-issues-link]
+**English** · [简体中文](./README.zh-CN.md) · [Official Site][official-site] · [Changelog][changelog] · [Documents][docs] · [Blog][blog] · [Feedback][github-issues-link]

 <!-- SHIELD GROUP -->

@@ -39,9 +46,9 @@ One-click **FREE** deployment of your private OpenAI ChatGPT/Claude/Gemini/Groq/

 <sup>Pioneering the new age of thinking and creating. Built for you, the Super Individual.</sup>

-[![][github-trending-shield]][github-trending-url]
+[![][github-trending-shield]][github-trending-url] <br /> <br /> <a href="https://vercel.com/oss"> <img alt="Vercel OSS Program" src="https://vercel.com/oss/program-badge.svg" /> </a>

-[![][image-overview]][vercel-link]
+![][image-overview]

 </div>

@@ -52,19 +59,26 @@ One-click **FREE** deployment of your private OpenAI ChatGPT/Claude/Gemini/Groq/

 - [👋🏻 Getting Started & Join Our Community](#-getting-started--join-our-community)
 - [✨ Features](#-features)
-  - [`1` File Upload/Knowledge Base](#1-file-uploadknowledge-base)
-  - [`2` Multi-Model Service Provider Support](#2-multi-model-service-provider-support)
-  - [`3` Local Large Language Model (LLM) Support](#3-local-large-language-model-llm-support)
-  - [`4` Model Visual Recognition](#4-model-visual-recognition)
-  - [`5` TTS & STT Voice Conversation](#5-tts--stt-voice-conversation)
-  - [`6` Text to Image Generation](#6-text-to-image-generation)
-  - [`7` Plugin System (Function Calling)](#7-plugin-system-function-calling)
-  - [`8` Agent Market (GPTs)](#8-agent-market-gpts)
-  - [`9` Support Local / Remote Database](#9-support-local--remote-database)
-  - [`10` Support Multi-User Management](#10-support-multi-user-management)
-  - [`11` Progressive Web App (PWA)](#11-progressive-web-app-pwa)
-  - [`12` Mobile Device Adaptation](#12-mobile-device-adaptation)
-  - [`13` Custom Themes](#13-custom-themes)
+  - [✨ MCP Plugin One-Click Installation](#-mcp-plugin-one-click-installation)
+  - [🏪 MCP Marketplace](#-mcp-marketplace)
+  - [🖥️ Desktop App](#️-desktop-app)
+  - [🌐 Smart Internet Search](#-smart-internet-search)
+  - [Chain of Thought](#chain-of-thought)
+  - [Branching Conversations](#branching-conversations)
+  - [Artifacts Support](#artifacts-support)
+  - [File Upload /Knowledge Base](#file-upload-knowledge-base)
+  - [Multi-Model Service Provider Support](#multi-model-service-provider-support)
+  - [Local Large Language Model (LLM) Support](#local-large-language-model-llm-support)
+  - [Model Visual Recognition](#model-visual-recognition)
+  - [TTS & STT Voice Conversation](#tts--stt-voice-conversation)
+  - [Text to Image Generation](#text-to-image-generation)
+  - [Plugin System (Function Calling)](#plugin-system-function-calling)
+  - [Agent Market (GPTs)](#agent-market-gpts)
+  - [Support Local / Remote Database](#support-local--remote-database)
+  - [Support Multi-User Management](#support-multi-user-management)
+  - [Progressive Web App (PWA)](#progressive-web-app-pwa)
+  - [Mobile Device Adaptation](#mobile-device-adaptation)
+  - [Custom Themes](#custom-themes)
  - [`*` What's more](#-whats-more)
 - [⚡️ Performance](#️-performance)
 - [🛳 Self Hosting](#-self-hosting)
@@ -111,9 +125,98 @@ Whether for users or professional developers, LobeHub will be your AI Agent play

 ## ✨ Features

+Transform your AI experience with LobeChat's powerful features designed for seamless connectivity, enhanced productivity, and unlimited creativity.
+
+![][image-feat-mcp]
+
+### ✨ MCP Plugin One-Click Installation
+
+**Seamlessly Connect Your AI to the World**
+
+Unlock the full potential of your AI by enabling smooth, secure, and dynamic interactions with external tools, data sources, and services. LobeChat's MCP (Model Context Protocol) plugin system breaks down the barriers between your AI and the digital ecosystem, allowing for unprecedented connectivity and functionality.
+
+Transform your conversations into powerful workflows by connecting to databases, APIs, file systems, and more. Experience the freedom of AI that truly understands and interacts with your world.
+
+[![][back-to-top]](#readme-top)
+
+![][image-feat-mcp-market]
+
+### 🏪 MCP Marketplace
+
+**Discover, Connect, Extend**
+
+Browse a growing library of MCP plugins to expand your AI's capabilities and streamline your workflows effortlessly. Visit [lobehub.com/mcp](https://lobehub.com/mcp) to explore the MCP Marketplace, which offers a curated collection of integrations that enhance your AI's ability to work with various tools and services.
+
+From productivity tools to development environments, discover new ways to extend your AI's reach and effectiveness. Connect with the community and find the perfect plugins for your specific needs.
+
+[![][back-to-top]](#readme-top)
+
+![][image-feat-desktop]
+
+### 🖥️ Desktop App
+
+**Peak Performance, Zero Distractions**
+
+Get the full LobeChat experience without browser limitations—comprehensive, focused, and always ready to go. Our desktop application provides a dedicated environment for your AI interactions, ensuring optimal performance and minimal distractions.
+
+Experience faster response times, better resource management, and a more stable connection to your AI assistant. The desktop app is designed for users who demand the best performance from their AI tools.
+
+[![][back-to-top]](#readme-top)
+
+![][image-feat-web-search]
+
+### 🌐 Smart Internet Search
+
+**Online Knowledge On Demand**
+
+With real-time internet access, your AI keeps up with the world—news, data, trends, and more. Stay informed and get the most current information available, enabling your AI to provide accurate and up-to-date responses.
+
+Access live information, verify facts, and explore current events without leaving your conversation. Your AI becomes a gateway to the world's knowledge, always current and comprehensive.
+
+[![][back-to-top]](#readme-top)
+
+[![][image-feat-cot]][docs-feat-cot]
+
+### [Chain of Thought][docs-feat-cot]
+
+Experience AI reasoning like never before. Watch as complex problems unfold step by step through our innovative Chain of Thought (CoT) visualization. This breakthrough feature provides unprecedented transparency into AI's decision-making process, allowing you to observe how conclusions are reached in real-time.
+
+By breaking down complex reasoning into clear, logical steps, you can better understand and validate the AI's problem-solving approach. Whether you're debugging, learning, or simply curious about AI reasoning, CoT visualization transforms abstract thinking into an engaging, interactive experience.
+
+[![][back-to-top]](#readme-top)
+
+[![][image-feat-branch]][docs-feat-branch]
+
+### [Branching Conversations][docs-feat-branch]
+
+Introducing a more natural and flexible way to chat with AI. With Branch Conversations, your discussions can flow in multiple directions, just like human conversations do. Create new conversation branches from any message, giving you the freedom to explore different paths while preserving the original context.
+
+Choose between two powerful modes:
+
+- **Continuation Mode:** Seamlessly extend your current discussion while maintaining valuable context
+- **Standalone Mode:** Start fresh with a new topic based on any previous message
+
+This groundbreaking feature transforms linear conversations into dynamic, tree-like structures, enabling deeper exploration of ideas and more productive interactions.
+
+[![][back-to-top]](#readme-top)
+
+[![][image-feat-artifacts]][docs-feat-artifacts]
+
+### [Artifacts Support][docs-feat-artifacts]
+
+Experience the power of Claude Artifacts, now integrated into LobeChat. This revolutionary feature expands the boundaries of AI-human interaction, enabling real-time creation and visualization of diverse content formats.
+
+Create and visualize with unprecedented flexibility:
+
+- Generate and display dynamic SVG graphics
+- Build and render interactive HTML pages in real-time
+- Produce professional documents in multiple formats
+
+[![][back-to-top]](#readme-top)
+
 [![][image-feat-knowledgebase]][docs-feat-knowledgebase]

-### `1` [File Upload/Knowledge Base][docs-feat-knowledgebase]
+### [File Upload /Knowledge Base][docs-feat-knowledgebase]

 LobeChat supports file upload and knowledge base functionality. You can upload various types of files including documents, images, audio, and video, as well as create knowledge bases, making it convenient for users to manage and search for files. Additionally, you can utilize files and knowledge base features during conversations, enabling a richer dialogue experience.

@@ -131,7 +234,7 @@ LobeChat supports file upload and knowledge base functionality. You can upload v

 [![][image-feat-privoder]][docs-feat-provider]

-### `2` [Multi-Model Service Provider Support][docs-feat-provider]
+### [Multi-Model Service Provider Support][docs-feat-provider]

 In the continuous development of LobeChat, we deeply understand the importance of diversity in model service providers for meeting the needs of the community when providing AI conversation services. Therefore, we have expanded our support to multiple model service providers, rather than being limited to a single one, in order to offer users a more diverse and rich selection of conversations.

@@ -143,49 +246,11 @@ We have implemented support for the following model service providers:

 <!-- PROVIDER LIST -->

- **[OpenAI](https://lobechat.com/discover/provider/openai)**: OpenAI is a global leader in artificial intelligence research, with models like the GPT series pushing the frontiers of natural language processing. OpenAI is committed to transforming multiple industries through innovative and efficient AI solutions. Their products demonstrate significant performance and cost-effectiveness, widely used in research, business, and innovative applications.
- **[Ollama](https://lobechat.com/discover/provider/ollama)**: Ollama provides models that cover a wide range of fields, including code generation, mathematical operations, multilingual processing, and conversational interaction, catering to diverse enterprise-level and localized deployment needs.
- **[Anthropic](https://lobechat.com/discover/provider/anthropic)**: Anthropic is a company focused on AI research and development, offering a range of advanced language models such as Claude 3.5 Sonnet, Claude 3 Sonnet, Claude 3 Opus, and Claude 3 Haiku. These models achieve an ideal balance between intelligence, speed, and cost, suitable for various applications from enterprise workloads to rapid-response scenarios. Claude 3.5 Sonnet, as their latest model, has excelled in multiple evaluations while maintaining a high cost-performance ratio.
- **[Bedrock](https://lobechat.com/discover/provider/bedrock)**: Bedrock is a service provided by Amazon AWS, focusing on delivering advanced AI language and visual models for enterprises. Its model family includes Anthropic's Claude series, Meta's Llama 3.1 series, and more, offering a range of options from lightweight to high-performance, supporting tasks such as text generation, conversation, and image processing for businesses of varying scales and needs.
- **[Google](https://lobechat.com/discover/provider/google)**: Google's Gemini series represents its most advanced, versatile AI models, developed by Google DeepMind, designed for multimodal capabilities, supporting seamless understanding and processing of text, code, images, audio, and video. Suitable for various environments from data centers to mobile devices, it significantly enhances the efficiency and applicability of AI models.
- **[DeepSeek](https://lobechat.com/discover/provider/deepseek)**: DeepSeek is a company focused on AI technology research and application, with its latest model DeepSeek-V2.5 integrating general dialogue and code processing capabilities, achieving significant improvements in human preference alignment, writing tasks, and instruction following.
- **[HuggingFace](https://lobechat.com/discover/provider/huggingface)**: The HuggingFace Inference API provides a fast and free way for you to explore thousands of models for various tasks. Whether you are prototyping for a new application or experimenting with the capabilities of machine learning, this API gives you instant access to high-performance models across multiple domains.
- **[OpenRouter](https://lobechat.com/discover/provider/openrouter)**: OpenRouter is a service platform providing access to various cutting-edge large model interfaces, supporting OpenAI, Anthropic, LLaMA, and more, suitable for diverse development and application needs. Users can flexibly choose the optimal model and pricing based on their requirements, enhancing the AI experience.
- **[Cloudflare Workers AI](https://lobechat.com/discover/provider/cloudflare)**: Run serverless GPU-powered machine learning models on Cloudflare's global network.
- **[GitHub](https://lobechat.com/discover/provider/github)**: With GitHub Models, developers can become AI engineers and leverage the industry's leading AI models.
-
-<details><summary><kbd>See more providers (+26)</kbd></summary>
-
- **[Novita](https://lobechat.com/discover/provider/novita)**: Novita AI is a platform providing a variety of large language models and AI image generation API services, flexible, reliable, and cost-effective. It supports the latest open-source models like Llama3 and Mistral, offering a comprehensive, user-friendly, and auto-scaling API solution for generative AI application development, suitable for the rapid growth of AI startups.
- **[Together AI](https://lobechat.com/discover/provider/togetherai)**: Together AI is dedicated to achieving leading performance through innovative AI models, offering extensive customization capabilities, including rapid scaling support and intuitive deployment processes to meet various enterprise needs.
- **[Fireworks AI](https://lobechat.com/discover/provider/fireworksai)**: Fireworks AI is a leading provider of advanced language model services, focusing on functional calling and multimodal processing. Its latest model, Firefunction V2, is based on Llama-3, optimized for function calling, conversation, and instruction following. The visual language model FireLLaVA-13B supports mixed input of images and text. Other notable models include the Llama series and Mixtral series, providing efficient multilingual instruction following and generation support.
- **[Groq](https://lobechat.com/discover/provider/groq)**: Groq's LPU inference engine has excelled in the latest independent large language model (LLM) benchmarks, redefining the standards for AI solutions with its remarkable speed and efficiency. Groq represents instant inference speed, demonstrating strong performance in cloud-based deployments.
- **[Perplexity](https://lobechat.com/discover/provider/perplexity)**: Perplexity is a leading provider of conversational generation models, offering various advanced Llama 3.1 models that support both online and offline applications, particularly suited for complex natural language processing tasks.
- **[Mistral](https://lobechat.com/discover/provider/mistral)**: Mistral provides advanced general, specialized, and research models widely used in complex reasoning, multilingual tasks, and code generation. Through functional calling interfaces, users can integrate custom functionalities for specific applications.
- **[Ai21Labs](https://lobechat.com/discover/provider/ai21)**: AI21 Labs builds foundational models and AI systems for enterprises, accelerating the application of generative AI in production.
- **[Upstage](https://lobechat.com/discover/provider/upstage)**: Upstage focuses on developing AI models for various business needs, including Solar LLM and document AI, aiming to achieve artificial general intelligence (AGI) for work. It allows for the creation of simple conversational agents through Chat API and supports functional calling, translation, embedding, and domain-specific applications.
- **[xAI](https://lobechat.com/discover/provider/xai)**: xAI is a company dedicated to building artificial intelligence to accelerate human scientific discovery. Our mission is to advance our collective understanding of the universe.
- **[Qwen](https://lobechat.com/discover/provider/qwen)**: Tongyi Qianwen is a large-scale language model independently developed by Alibaba Cloud, featuring strong natural language understanding and generation capabilities. It can answer various questions, create written content, express opinions, and write code, playing a role in multiple fields.
- **[Wenxin](https://lobechat.com/discover/provider/wenxin)**: An enterprise-level one-stop platform for large model and AI-native application development and services, providing the most comprehensive and user-friendly toolchain for the entire process of generative artificial intelligence model development and application development.
- **[Hunyuan](https://lobechat.com/discover/provider/hunyuan)**: A large language model developed by Tencent, equipped with powerful Chinese creative capabilities, logical reasoning abilities in complex contexts, and reliable task execution skills.
- **[ZhiPu](https://lobechat.com/discover/provider/zhipu)**: Zhipu AI offers an open platform for multimodal and language models, supporting a wide range of AI application scenarios, including text processing, image understanding, and programming assistance.
- **[SiliconCloud](https://lobechat.com/discover/provider/siliconcloud)**: SiliconFlow is dedicated to accelerating AGI for the benefit of humanity, enhancing large-scale AI efficiency through an easy-to-use and cost-effective GenAI stack.
- **[01.AI](https://lobechat.com/discover/provider/zeroone)**: 01.AI focuses on AI 2.0 era technologies, vigorously promoting the innovation and application of 'human + artificial intelligence', using powerful models and advanced AI technologies to enhance human productivity and achieve technological empowerment.
- **[Spark](https://lobechat.com/discover/provider/spark)**: iFlytek's Spark model provides powerful AI capabilities across multiple domains and languages, utilizing advanced natural language processing technology to build innovative applications suitable for smart hardware, smart healthcare, smart finance, and other vertical scenarios.
- **[SenseNova](https://lobechat.com/discover/provider/sensenova)**: SenseNova, backed by SenseTime's robust infrastructure, offers efficient and user-friendly full-stack large model services.
- **[Stepfun](https://lobechat.com/discover/provider/stepfun)**: StepFun's large model possesses industry-leading multimodal and complex reasoning capabilities, supporting ultra-long text understanding and powerful autonomous scheduling search engine functions.
- **[Moonshot](https://lobechat.com/discover/provider/moonshot)**: Moonshot is an open-source platform launched by Beijing Dark Side Technology Co., Ltd., providing various natural language processing models with a wide range of applications, including but not limited to content creation, academic research, intelligent recommendations, and medical diagnosis, supporting long text processing and complex generation tasks.
- **[Baichuan](https://lobechat.com/discover/provider/baichuan)**: Baichuan Intelligence is a company focused on the research and development of large AI models, with its models excelling in domestic knowledge encyclopedias, long text processing, and generative creation tasks in Chinese, surpassing mainstream foreign models. Baichuan Intelligence also possesses industry-leading multimodal capabilities, performing excellently in multiple authoritative evaluations. Its models include Baichuan 4, Baichuan 3 Turbo, and Baichuan 3 Turbo 128k, each optimized for different application scenarios, providing cost-effective solutions.
- **[Minimax](https://lobechat.com/discover/provider/minimax)**: MiniMax is a general artificial intelligence technology company established in 2021, dedicated to co-creating intelligence with users. MiniMax has independently developed general large models of different modalities, including trillion-parameter MoE text models, voice models, and image models, and has launched applications such as Conch AI.
- **[InternLM](https://lobechat.com/discover/provider/internlm)**: An open-source organization dedicated to the research and development of large model toolchains. It provides an efficient and user-friendly open-source platform for all AI developers, making cutting-edge large models and algorithm technologies easily accessible.
- **[Higress](https://lobechat.com/discover/provider/higress)**: Higress is a cloud-native API gateway that was developed internally at Alibaba to address the issues of Tengine reload affecting long-lived connections and the insufficient load balancing capabilities for gRPC/Dubbo.
- **[Gitee AI](https://lobechat.com/discover/provider/giteeai)**: Gitee AI's Serverless API provides AI developers with an out of the box large model inference API service.
- **[Taichu](https://lobechat.com/discover/provider/taichu)**: The Institute of Automation, Chinese Academy of Sciences, and Wuhan Artificial Intelligence Research Institute have launched a new generation of multimodal large models, supporting comprehensive question-answering tasks such as multi-turn Q\&A, text creation, image generation, 3D understanding, and signal analysis, with stronger cognitive, understanding, and creative abilities, providing a new interactive experience.
- **[360 AI](https://lobechat.com/discover/provider/ai360)**: 360 AI is an AI model and service platform launched by 360 Company, offering various advanced natural language processing models, including 360GPT2 Pro, 360GPT Pro, 360GPT Turbo, and 360GPT Turbo Responsibility 8K. These models combine large-scale parameters and multimodal capabilities, widely applied in text generation, semantic understanding, dialogue systems, and code generation. With flexible pricing strategies, 360 AI meets diverse user needs, supports developer integration, and promotes the innovation and development of intelligent applications.
+<details><summary><kbd>See more providers (+-10)</kbd></summary>

 </details>

-> 📊 Total providers: [<kbd>**36**</kbd>](https://lobechat.com/discover/providers)
+> 📊 Total providers: [<kbd>**0**</kbd>](https://lobechat.com/discover/providers)

 <!-- PROVIDER LIST -->

@@ -199,7 +264,7 @@ At the same time, we are also planning to support more model service providers.

 [![][image-feat-local]][docs-feat-local]

-### `3` [Local Large Language Model (LLM) Support][docs-feat-local]
+### [Local Large Language Model (LLM) Support][docs-feat-local]

 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.

@@ -215,7 +280,7 @@ To meet the specific needs of users, LobeChat also supports the use of local mod

 [![][image-feat-vision]][docs-feat-vision]

-### `4` [Model Visual Recognition][docs-feat-vision]
+### [Model Visual Recognition][docs-feat-vision]

 LobeChat now supports OpenAI's latest [`gpt-4-vision`](https://platform.openai.com/docs/guides/vision) model with visual recognition capabilities,
 a multimodal intelligence that can perceive visuals. Users can easily upload or drag and drop images into the dialogue box,
@@ -233,7 +298,7 @@ Whether it's sharing images in daily use or interpreting images within specific

 [![][image-feat-tts]][docs-feat-tts]

-### `5` [TTS & STT Voice Conversation][docs-feat-tts]
+### [TTS & STT Voice Conversation][docs-feat-tts]

 LobeChat supports Text-to-Speech (TTS) and Speech-to-Text (STT) technologies, enabling our application to convert text messages into clear voice outputs,
 allowing users to interact with our conversational agent as if they were talking to a real person. Users can choose from a variety of voices to pair with the agent.
@@ -250,7 +315,7 @@ Users can choose the voice that suits their personal preferences or specific sce

 [![][image-feat-t2i]][docs-feat-t2i]

-### `6` [Text to Image Generation][docs-feat-t2i]
+### [Text to Image Generation][docs-feat-t2i]

 With support for the latest text-to-image generation technology, LobeChat now allows users to invoke image creation tools directly within conversations with the agent. By leveraging the capabilities of AI tools such as [`DALL-E 3`](https://openai.com/dall-e-3), [`MidJourney`](https://www.midjourney.com/), and [`Pollinations`](https://pollinations.ai/), the agents are now equipped to transform your ideas into images.

@@ -264,7 +329,7 @@ This enables a more private and immersive creative process, allowing for the sea

 [![][image-feat-plugin]][docs-feat-plugin]

-### `7` [Plugin System (Function Calling)][docs-feat-plugin]
+### [Plugin System (Function Calling)][docs-feat-plugin]

 The plugin ecosystem of LobeChat is an important extension of its core functionality, greatly enhancing the practicality and flexibility of the LobeChat assistant.

@@ -280,14 +345,14 @@ In addition, these plugins are not limited to news aggregation, but can also ext

 <!-- PLUGIN LIST -->

-| Recent Submits                                                                                                         | Description                                                                                                          |
-| ---------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
-| [MintbaseSearch](https://lobechat.com/discover/plugin/mintbasesearch)<br/><sup>By **mintbase** on **2024-12-31**</sup> | Find any NFT data on the NEAR Protocol.<br/>`crypto` `nft`                                                           |
-| [PortfolioMeta](https://lobechat.com/discover/plugin/StockData)<br/><sup>By **portfoliometa** on **2024-12-22**</sup>  | Analyze stocks and get comprehensive real-time investment data and analytics.<br/>`stock`                            |
-| [Google CSE](https://lobechat.com/discover/plugin/google-cse)<br/><sup>By **vsnthdev** on **2024-12-02**</sup>         | Searches Google through their official CSE API.<br/>`web` `search`                                                   |
-| [Speak](https://lobechat.com/discover/plugin/speak)<br/><sup>By **speak** on **2024-12-02**</sup>                      | Learn how to say anything in another language with Speak, your AI-powered language tutor.<br/>`education` `language` |
+| Recent Submits                                                                                                             | Description                                                                                                                               |
+| -------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| [SEO](https://lobechat.com/discover/plugin/SEO)<br/><sup>By **orrenprunckun** on **2025-11-14**</sup>                      | Enter any URL and keyword and get an On-Page SEO analysis & insights!<br/>`seo`                                                           |
+| [Shopping tools](https://lobechat.com/discover/plugin/ShoppingTools)<br/><sup>By **shoppingtools** on **2025-10-27**</sup> | Search for products on eBay & AliExpress, find eBay events & coupons. Get prompt examples.<br/>`shopping` `e-bay` `ali-express` `coupons` |
+| [PortfolioMeta](https://lobechat.com/discover/plugin/StockData)<br/><sup>By **portfoliometa** on **2025-09-27**</sup>      | Analyze stocks and get comprehensive real-time investment data and analytics.<br/>`stock`                                                 |
+| [Web](https://lobechat.com/discover/plugin/web)<br/><sup>By **Proghit** on **2025-01-24**</sup>                            | Smart web search that reads and analyzes pages to deliver comprehensive answers from Google results.<br/>`web` `search`                   |

-> 📊 Total plugins: [<kbd>**48**</kbd>](https://lobechat.com/discover/plugins)
+> 📊 Total plugins: [<kbd>**42**</kbd>](https://lobechat.com/discover/plugins)

 <!-- PLUGIN LIST -->

@@ -299,7 +364,7 @@ In addition, these plugins are not limited to news aggregation, but can also ext

 [![][image-feat-agent]][docs-feat-agent]

-### `8` [Agent Market (GPTs)][docs-feat-agent]
+### [Agent Market (GPTs)][docs-feat-agent]

 In LobeChat Agent Marketplace, creators can discover a vibrant and innovative community that brings together a multitude of well-designed agents,
 which not only play an important role in work scenarios but also offer great convenience in learning processes.
@@ -319,14 +384,14 @@ Our marketplace is not just a showcase platform but also a collaborative space.

 <!-- AGENT LIST -->

-| Recent Submits                                                                                                                                                                  | Description                                                                                                                                                              |
-| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| [System Instruction Expert](https://lobechat.com/discover/assistant/instructer)<br/><sup>By **[yuyun2000](https://github.com/yuyun2000)** on **2024-12-04**</sup>               | Skilled in refining and generating efficient system instructions<br/>`system-instructions` `writing` `detail-optimization` `user-needs`                                  |
-| [Japanese Memory Helper](https://lobechat.com/discover/assistant/japan-language-helper)<br/><sup>By **[sharkbear212](https://github.com/sharkbear212)** on **2024-12-04**</sup> | Specializes in Japanese Hiragana, Katakana, vocabulary, and memory techniques for explanations and phrases<br/>`explanation` `memory-techniques` `japanese-teaching`     |
-| [Poetry Card Designer](https://lobechat.com/discover/assistant/poetry-card-designer)<br/><sup>By **[lianxin255](https://github.com/lianxin255)** on **2024-12-03**</sup>        | Skilled in designing poetry cards to enhance artistic sense and appeal<br/>`poetry-card-design` `card` `creativity` `artistic-expression`                                |
-| [Daily Doctor](https://lobechat.com/discover/assistant/yunchat-docter)<br/><sup>By **[yuyun2000](https://github.com/yuyun2000)** on **2024-11-30**</sup>                        | Specializes in surgical diagnosis and personalized health management<br/>`general-medicine` `surgery` `health-consultation` `personalized-treatment` `medical-education` |
+| Recent Submits                                                                                                                                                                 | Description                                                                                                                                                                                                              |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| [Turtle Soup Host](https://lobechat.com/discover/assistant/lateral-thinking-puzzle)<br/><sup>By **[CSY2022](https://github.com/CSY2022)** on **2025-06-19**</sup>              | A turtle soup host needs to provide the scenario, the complete story (truth of the event), and the key point (the condition for guessing correctly).<br/>`turtle-soup` `reasoning` `interaction` `puzzle` `role-playing` |
+| [Gourmet Reviewer🍟](https://lobechat.com/discover/assistant/food-reviewer)<br/><sup>By **[renhai-lab](https://github.com/renhai-lab)** on **2025-06-17**</sup>                | Food critique expert<br/>`gourmet` `review` `writing`                                                                                                                                                                    |
+| [Academic Writing Assistant](https://lobechat.com/discover/assistant/academic-writing-assistant)<br/><sup>By **[swarfte](https://github.com/swarfte)** on **2025-06-17**</sup> | Expert in academic research paper writing and formal documentation<br/>`academic-writing` `research` `formal-style`                                                                                                      |
+| [Minecraft Senior Developer](https://lobechat.com/discover/assistant/java-development)<br/><sup>By **[iamyuuk](https://github.com/iamyuuk)** on **2025-06-17**</sup>           | Expert in advanced Java development and Minecraft mod and server plugin development<br/>`development` `programming` `minecraft` `java`                                                                                   |

-> 📊 Total agents: [<kbd>**453**</kbd> ](https://lobechat.com/discover/assistants)
+> 📊 Total agents: [<kbd>**505**</kbd> ](https://lobechat.com/discover/assistants)

 <!-- AGENT LIST -->

@@ -338,7 +403,7 @@ Our marketplace is not just a showcase platform but also a collaborative space.

 [![][image-feat-database]][docs-feat-database]

-### `9` [Support Local / Remote Database][docs-feat-database]
+### [Support Local / Remote Database][docs-feat-database]

 LobeChat supports the use of both server-side and local databases. Depending on your needs, you can choose the appropriate deployment solution:

@@ -355,7 +420,7 @@ Regardless of which database you choose, LobeChat can provide you with an excell

 [![][image-feat-auth]][docs-feat-auth]

-### `10` [Support Multi-User Management][docs-feat-auth]
+### [Support Multi-User Management][docs-feat-auth]

 LobeChat supports multi-user management and provides two main user authentication and management solutions to meet different needs:

@@ -373,13 +438,13 @@ Regardless of which user management solution you choose, LobeChat can provide yo

 [![][image-feat-pwa]][docs-feat-pwa]

-### `11` [Progressive Web App (PWA)][docs-feat-pwa]
+### [Progressive Web App (PWA)][docs-feat-pwa]

 We deeply understand the importance of providing a seamless experience for users in today's multi-device environment.
 Therefore, we have adopted Progressive Web Application ([PWA](https://support.google.com/chrome/answer/9658361)) technology,
 a modern web technology that elevates web applications to an experience close to that of native apps.

-Through PWA, LobeChat can offer a highly optimized user experience on both desktop and mobile devices while maintaining its lightweight and high-performance characteristics.
+Through PWA, LobeChat can offer a highly optimized user experience on both desktop and mobile devices while maintaining high-performance characteristics.
 Visually and in terms of feel, we have also meticulously designed the interface to ensure it is indistinguishable from native apps,
 providing smooth animations, responsive layouts, and adapting to different device screen resolutions.

@@ -400,7 +465,7 @@ providing smooth animations, responsive layouts, and adapting to different devic

 [![][image-feat-mobile]][docs-feat-mobile]

-### `12` [Mobile Device Adaptation][docs-feat-mobile]
+### [Mobile Device Adaptation][docs-feat-mobile]

 We have carried out a series of optimization designs for mobile devices to enhance the user's mobile experience. Currently, we are iterating on the mobile user experience to achieve smoother and more intuitive interactions. If you have any suggestions or ideas, we welcome you to provide feedback through GitHub Issues or Pull Requests.

@@ -412,7 +477,7 @@ We have carried out a series of optimization designs for mobile devices to enhan

 [![][image-feat-theme]][docs-feat-theme]

-### `13` [Custom Themes][docs-feat-theme]
+### [Custom Themes][docs-feat-theme]

 As a design-engineering-oriented application, LobeChat places great emphasis on users' personalized experiences,
 hence introducing flexible and diverse theme modes, including a light mode for daytime and a dark mode for nighttime.
@@ -518,25 +583,22 @@ If you have deployed your own project following the one-click deployment steps i

 We provide a Docker image for deploying the LobeChat service on your own private device. Use the following command to start the LobeChat service:

+1. create a folder to for storage files
+
 ```fish
-$ docker run -d -p 3210:3210 \
-  -e OPENAI_API_KEY=sk-xxxx \
-  -e ACCESS_CODE=lobe66 \
-  --name lobe-chat \
-  lobehub/lobe-chat
+$ mkdir lobe-chat-db && cd lobe-chat-db
 ```

-> \[!TIP]
->
-> If you need to use the OpenAI service through a proxy, you can configure the proxy address using the `OPENAI_PROXY_URL` environment variable:
+2. init the LobeChat infrastructure

 ```fish
-$ docker run -d -p 3210:3210 \
-  -e OPENAI_API_KEY=sk-xxxx \
-  -e OPENAI_PROXY_URL=https://api-proxy.com/v1 \
-  -e ACCESS_CODE=lobe66 \
-  --name lobe-chat \
-  lobehub/lobe-chat
+bash <(curl -fsSL https://lobe.li/setup.sh)
+```
+
+3. Start the LobeChat service
+
+```fish
+docker compose up -d
 ```

 > \[!NOTE]
@@ -583,7 +645,7 @@ This project provides some additional configuration items set with environment v

 ## 🧩 Plugins

-Plugins provide a means to extend the [Function Calling][docs-functionc-call] capabilities of LobeChat. They can be used to introduce new function calls and even new ways to render message results. If you are interested in plugin development, please refer to our [📘 Plugin Development Guide][docs-plugin-dev] in the Wiki.
+Plugins provide a means to extend the [Function Calling][docs-function-call] capabilities of LobeChat. They can be used to introduce new function calls and even new ways to render message results. If you are interested in plugin development, please refer to our [📘 Plugin Development Guide][docs-plugin-dev] in the Wiki.

 - [lobe-chat-plugins][lobe-chat-plugins]: This is the plugin index for LobeChat. It accesses index.json from this repository to display a list of available plugins for LobeChat to the user.
 - [chat-plugin-template][chat-plugin-template]: This is the plugin template for LobeChat plugin development.
@@ -629,7 +691,7 @@ If you would like to learn more details, please feel free to look at our [📘 D

 ## 🤝 Contributing

-Contributions of all types are more than welcome; if you are interested in contributing code, feel free to check out our GitHub [Issues][github-issues-link] and [Projects][github-project-link] to get stuck in to show us what you’re made of.
+Contributions of all types are more than welcome; if you are interested in contributing code, feel free to check out our GitHub [Issues][github-issues-link] and [Projects][github-project-link] to get stuck in to show us what you're made of.

 > \[!TIP]
 >
@@ -719,8 +781,8 @@ Every bit counts and your one-time donation sparkles in our galaxy of support! Y

 </details>

-Copyright © 2024 [LobeHub][profile-link]. <br />
-This project is [Apache 2.0](./LICENSE) licensed.
+Copyright © 2025 [LobeHub][profile-link]. <br />
+This project is [LobeHub Community License](./LICENSE) licensed.

 <!-- LINK GROUP -->

@@ -745,24 +807,27 @@ This project is [Apache 2.0](./LICENSE) licensed.
 [deploy-on-repocloud-button-image]: https://d16t0pc4846x52.cloudfront.net/deploylobe.svg
 [deploy-on-repocloud-link]: https://repocloud.io/details/?app_id=248
 [deploy-on-sealos-button-image]: https://raw.githubusercontent.com/labring-actions/templates/main/Deploy-on-Sealos.svg
-[deploy-on-sealos-link]: https://cloud.sealos.io/?openapp=system-template%3FtemplateName%3Dlobe-chat
+[deploy-on-sealos-link]: https://template.usw.sealos.io/deploy?templateName=lobe-chat-db
 [deploy-on-zeabur-button-image]: https://zeabur.com/button.svg
 [deploy-on-zeabur-link]: https://zeabur.com/templates/VZGGTI
 [discord-link]: https://discord.gg/AYFPHvv2jT
 [discord-shield]: https://img.shields.io/discord/1127171173982154893?color=5865F2&label=discord&labelColor=black&logo=discord&logoColor=white&style=flat-square
 [discord-shield-badge]: https://img.shields.io/discord/1127171173982154893?color=5865F2&label=discord&labelColor=black&logo=discord&logoColor=white&style=for-the-badge
-[docker-pulls-link]: https://hub.docker.com/r/lobehub/lobe-chat
-[docker-pulls-shield]: https://img.shields.io/docker/pulls/lobehub/lobe-chat?color=45cc11&labelColor=black&style=flat-square
-[docker-release-link]: https://hub.docker.com/r/lobehub/lobe-chat
-[docker-release-shield]: https://img.shields.io/docker/v/lobehub/lobe-chat?color=369eff&label=docker&labelColor=black&logo=docker&logoColor=white&style=flat-square
-[docker-size-link]: https://hub.docker.com/r/lobehub/lobe-chat
-[docker-size-shield]: https://img.shields.io/docker/image-size/lobehub/lobe-chat?color=369eff&labelColor=black&style=flat-square
+[docker-pulls-link]: https://hub.docker.com/r/lobehub/lobe-chat-database
+[docker-pulls-shield]: https://img.shields.io/docker/pulls/lobehub/lobe-chat?color=45cc11&labelColor=black&style=flat-square&sort=semver
+[docker-release-link]: https://hub.docker.com/r/lobehub/lobe-chat-database
+[docker-release-shield]: https://img.shields.io/docker/v/lobehub/lobe-chat-database?color=369eff&label=docker&labelColor=black&logo=docker&logoColor=white&style=flat-square&sort=semver
+[docker-size-link]: https://hub.docker.com/r/lobehub/lobe-chat-database
+[docker-size-shield]: https://img.shields.io/docker/image-size/lobehub/lobe-chat-database?color=369eff&labelColor=black&style=flat-square&sort=semver
 [docs]: https://lobehub.com/docs/usage/start
 [docs-dev-guide]: https://github.com/lobehub/lobe-chat/wiki/index
-[docs-docker]: https://lobehub.com/docs/self-hosting/platform/docker
+[docs-docker]: https://lobehub.com/docs/self-hosting/server-database/docker-compose
 [docs-env-var]: https://lobehub.com/docs/self-hosting/environment-variables
 [docs-feat-agent]: https://lobehub.com/docs/usage/features/agent-market
+[docs-feat-artifacts]: https://lobehub.com/docs/usage/features/artifacts
 [docs-feat-auth]: https://lobehub.com/docs/usage/features/auth
+[docs-feat-branch]: https://lobehub.com/docs/usage/features/branching-conversations
+[docs-feat-cot]: https://lobehub.com/docs/usage/features/cot
 [docs-feat-database]: https://lobehub.com/docs/usage/features/database
 [docs-feat-knowledgebase]: https://lobehub.com/blog/knowledge-base
 [docs-feat-local]: https://lobehub.com/docs/usage/features/local-llm
@@ -774,7 +839,7 @@ This project is [Apache 2.0](./LICENSE) licensed.
 [docs-feat-theme]: https://lobehub.com/docs/usage/features/theme
 [docs-feat-tts]: https://lobehub.com/docs/usage/features/tts
 [docs-feat-vision]: https://lobehub.com/docs/usage/features/vision
-[docs-functionc-call]: https://lobehub.com/blog/openai-function-call
+[docs-function-call]: https://lobehub.com/blog/openai-function-call
 [docs-lighthouse]: https://github.com/lobehub/lobe-chat/wiki/Lighthouse
 [docs-plugin-dev]: https://lobehub.com/docs/usage/plugins/development
 [docs-self-hosting]: https://lobehub.com/docs/self-hosting/start
@@ -800,26 +865,33 @@ This project is [Apache 2.0](./LICENSE) licensed.
 [github-release-shield]: https://img.shields.io/github/v/release/lobehub/lobe-chat?color=369eff&labelColor=black&logo=github&style=flat-square
 [github-releasedate-link]: https://github.com/lobehub/lobe-chat/releases
 [github-releasedate-shield]: https://img.shields.io/github/release-date/lobehub/lobe-chat?labelColor=black&style=flat-square
-[github-stars-link]: https://github.com/lobehub/lobe-chat/network/stargazers
+[github-stars-link]: https://github.com/lobehub/lobe-chat/stargazers
 [github-stars-shield]: https://img.shields.io/github/stars/lobehub/lobe-chat?color=ffcb47&labelColor=black&style=flat-square
 [github-trending-shield]: https://trendshift.io/api/badge/repositories/2256
 [github-trending-url]: https://trendshift.io/repositories/2256
-[image-banner]: https://github.com/lobehub/lobe-chat/assets/28616219/9f155dff-4737-429f-9cad-a70a1a860c5f
-[image-feat-agent]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/268670869-f1ffbf66-42b6-42cf-a937-9ce1f8328514.png
-[image-feat-auth]: https://github.com/lobehub/lobe-chat/assets/17870709/8ce70e15-40df-451e-b700-66090fe5b8c2
-[image-feat-database]: https://github.com/lobehub/lobe-chat/assets/17870709/c27a0234-a4e9-40e5-8bcb-42d5ce7e40f9
-[image-feat-knowledgebase]: https://github.com/user-attachments/assets/77e58e1c-c82f-4341-b159-f4eeede9967f
-[image-feat-local]: https://github.com/lobehub/lobe-chat/assets/28616219/ca9a21bc-ea6c-4c90-bf4a-fa53b4fb2b5c
-[image-feat-mobile]: https://gw.alipayobjects.com/zos/kitchen/R441AuFS4W/mobile.webp
-[image-feat-plugin]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/268670883-33c43a5c-a512-467e-855c-fa299548cce5.png
-[image-feat-privoder]: https://github.com/lobehub/lobe-chat/assets/28616219/b164bc54-8ba2-4c1e-b2f2-f4d7f7e7a551
-[image-feat-pwa]: https://gw.alipayobjects.com/zos/kitchen/69x6bllkX3/pwa.webp
-[image-feat-t2i]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/297746445-0ff762b9-aa08-4337-afb7-12f932b6efbb.png
-[image-feat-theme]: https://gw.alipayobjects.com/zos/kitchen/pvus1lo%26Z7/darkmode.webp
-[image-feat-tts]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/284072124-c9853d8d-f1b5-44a8-a305-45ebc0f6d19a.png
-[image-feat-vision]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/284072129-382bdf30-e3d6-4411-b5a0-249710b8ba08.png
-[image-overview]: https://github.com/lobehub/lobe-chat/assets/17870709/56b95d48-f573-41cd-8b38-387bf88bc4bf
-[image-star]: https://github.com/lobehub/lobe-chat/assets/17870709/cb06b748-513f-47c2-8740-d876858d7855
+[image-banner]: https://github.com/user-attachments/assets/6f293c7f-47b4-47eb-9202-fe68a942d35b
+[image-feat-agent]: https://github.com/user-attachments/assets/b3ab6e35-4fbc-468d-af10-e3e0c687350f
+[image-feat-artifacts]: https://github.com/user-attachments/assets/7f95fad6-b210-4e6e-84a0-7f39e96f3a00
+[image-feat-auth]: https://github.com/user-attachments/assets/80bb232e-19d1-4f97-98d6-e291f3585e6d
+[image-feat-branch]: https://github.com/user-attachments/assets/92f72082-02bd-4835-9c54-b089aad7fd41
+[image-feat-cot]: https://github.com/user-attachments/assets/f74f1139-d115-4e9c-8c43-040a53797a5e
+[image-feat-database]: https://github.com/user-attachments/assets/f1697c8b-d1fb-4dac-ba05-153c6295d91d
+[image-feat-desktop]: https://github.com/user-attachments/assets/a7bac8d3-ea96-4000-bb39-fadc9b610f96
+[image-feat-knowledgebase]: https://github.com/user-attachments/assets/7da7a3b2-92fd-4630-9f4e-8560c74955ae
+[image-feat-local]: https://github.com/user-attachments/assets/1239da50-d832-4632-a7ef-bd754c0f3850
+[image-feat-mcp]: https://github.com/user-attachments/assets/1be85d36-3975-4413-931f-27e05e440995
+[image-feat-mcp-market]: https://github.com/user-attachments/assets/bb114f9f-24c5-4000-a984-c10d187da5a0
+[image-feat-mobile]: https://github.com/user-attachments/assets/32cf43c4-96bd-4a4c-bfb6-59acde6fe380
+[image-feat-plugin]: https://github.com/user-attachments/assets/66a891ac-01b6-4e3f-b978-2eb07b489b1b
+[image-feat-privoder]: https://github.com/user-attachments/assets/e553e407-42de-4919-977d-7dbfcf44a821
+[image-feat-pwa]: https://github.com/user-attachments/assets/9647f70f-b71b-43b6-9564-7cdd12d1c24d
+[image-feat-t2i]: https://github.com/user-attachments/assets/708274a7-2458-494b-a6ec-b73dfa1fa7c2
+[image-feat-theme]: https://github.com/user-attachments/assets/b47c39f1-806f-492b-8fcb-b0fa973937c1
+[image-feat-tts]: https://github.com/user-attachments/assets/50189597-2cc3-4002-b4c8-756a52ad5c0a
+[image-feat-vision]: https://github.com/user-attachments/assets/18574a1f-46c2-4cbc-af2c-35a86e128a07
+[image-feat-web-search]: https://github.com/user-attachments/assets/cfdc48ac-b5f8-4a00-acee-db8f2eba09ad
+[image-overview]: https://github.com/user-attachments/assets/dbfaa84a-2c82-4dd9-815c-5be616f264a4
+[image-star]: https://github.com/user-attachments/assets/c3b482e7-cef5-4e94-bef9-226900ecfaab
 [issues-link]: https://img.shields.io/github/issues/lobehub/lobe-chat.svg?style=flat
 [lobe-chat-plugins]: https://github.com/lobehub/lobe-chat-plugins
 [lobe-commit]: https://github.com/lobehub/lobe-commit/tree/master/packages/lobe-commit
@@ -844,7 +916,7 @@ This project is [Apache 2.0](./LICENSE) licensed.
 [profile-link]: https://github.com/lobehub
 [share-linkedin-link]: https://linkedin.com/feed
 [share-linkedin-shield]: https://img.shields.io/badge/-share%20on%20linkedin-black?labelColor=black&logo=linkedin&logoColor=white&style=flat-square
-[share-mastodon-link]: https://mastodon.social/share?text=Check%20this%20GitHub%20repository%20out%20%F0%9F%A4%AF%20LobeChat%20-%20An%20open-source,%20extensible%20(Function%20Calling),%20high-performance%20chatbot%20framework.%20It%20supports%20one-click%20free%20deployment%20of%20your%20private%20ChatGPT/LLM%20web%20application.%20https://github.com/lobehub/lobe-chat%20#chatbot%20#chatGPT%20#openAI
+[share-mastodon-link]: https://mastodon.social/share?text=Check%20this%20GitHub%20repository%20out%20%F0%9F%A4%AF%20LobeChat%20-%20An%20open-source,%20extensible%20%28Function%20Calling%29,%20high-performance%20chatbot%20framework.%20It%20supports%20one-click%20free%20deployment%20of%20your%20private%20ChatGPT%2FLLM%20web%20application.%20https://github.com/lobehub/lobe-chat%20#chatbot%20#chatGPT%20#openAI
 [share-mastodon-shield]: https://img.shields.io/badge/-share%20on%20mastodon-black?labelColor=black&logo=mastodon&logoColor=white&style=flat-square
 [share-reddit-link]: https://www.reddit.com/submit?title=Check%20this%20GitHub%20repository%20out%20%F0%9F%A4%AF%20LobeChat%20-%20An%20open-source%2C%20extensible%20%28Function%20Calling%29%2C%20high-performance%20chatbot%20framework.%20It%20supports%20one-click%20free%20deployment%20of%20your%20private%20ChatGPT%2FLLM%20web%20application.%20%23chatbot%20%23chatGPT%20%23openAI&url=https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat
 [share-reddit-shield]: https://img.shields.io/badge/-share%20on%20reddit-black?labelColor=black&logo=reddit&logoColor=white&style=flat-square
@@ -1,3 +1,10 @@
+> \[!NOTE]
+>
+> **版本信息**
+>
+> - **v1.x** (稳定版)：位于 [`main`](https://github.com/lobehub/lobe-chat/tree/main) 分支
+> - **v2.x** (开发中)：正在 [`next`](https://github.com/lobehub/lobe-chat/tree/next) 分支火热开发中 🔥
+
 <div align="center"><a name="readme-top"></a>

 [![][image-banner]][vercel-link]
@@ -8,7 +15,7 @@
 支持语音合成、多模态、可扩展的（[function call][docs-functionc-call]）插件系统<br/>
 一键**免费**拥有你自己的 ChatGPT/Gemini/Claude/Ollama 应用

-[English](./README.md) · [繁體中文](./README.zh-TW.md) · **简体中文** · [日本語](./README.ja-JP.md) · [官网][official-site] · [更新日志][changelog] · [文档][docs] · [博客][blog] · [反馈问题][github-issues-link]
+[English](./README.md) · **简体中文** · [官网][official-site] · [更新日志][changelog] · [文档][docs] · [博客][blog] · [反馈问题][github-issues-link]

 <!-- SHIELD GROUP -->

@@ -41,7 +48,7 @@
 [![][github-trending-shield]][github-trending-url]
 [![][github-hello-shield]][github-hello-url]

-[![][image-overview]][vercel-link]
+![][image-overview]

 </div>

@@ -52,20 +59,27 @@

 - [👋🏻 开始使用 & 交流](#-开始使用--交流)
 - [✨ 特性一览](#-特性一览)
-  - [`1` 文件上传 / 知识库](#1-文件上传--知识库)
-  - [`2` 多模型服务商支持](#2-多模型服务商支持)
-  - [`3` 支持本地大语言模型 (LLM)](#3-支持本地大语言模型-llm)
-  - [`4` 模型视觉识别 (Model Visual)](#4-模型视觉识别-model-visual)
-  - [`5` TTS & STT 语音会话](#5-tts--stt-语音会话)
-  - [`6` Text to Image 文生图](#6-text-to-image-文生图)
-  - [`7` 插件系统 (Tools Calling)](#7-插件系统-tools-calling)
-  - [`8` 助手市场 (GPTs)](#8-助手市场-gpts)
-  - [`9` 支持本地 / 远程数据库](#9-支持本地--远程数据库)
-  - [`10` 支持多用户管理](#10-支持多用户管理)
-  - [`11` 渐进式 Web 应用 (PWA)](#11-渐进式-web-应用-pwa)
-  - [`12` 移动设备适配](#12-移动设备适配)
-  - [`13` 自定义主题](#13-自定义主题)
-  - [更多特性](#更多特性)
+  - [✨ MCP 插件一键安装](#-mcp-插件一键安装)
+  - [🏪 MCP 市场](#-mcp-市场)
+  - [🖥️ 桌面应用](#️-桌面应用)
+  - [🌐 智能联网搜索](#-智能联网搜索)
+  - [思维链 (CoT)](#思维链-cot)
+  - [分支对话](#分支对话)
+  - [支持白板 (Artifacts)](#支持白板-artifacts)
+  - [文件上传 / 知识库](#文件上传--知识库)
+  - [多模型服务商支持](#多模型服务商支持)
+  - [支持本地大语言模型 (LLM)](#支持本地大语言模型-llm)
+  - [模型视觉识别 (Model Visual)](#模型视觉识别-model-visual)
+  - [TTS & STT 语音会话](#tts--stt-语音会话)
+  - [Text to Image 文生图](#text-to-image-文生图)
+  - [插件系统 (Tools Calling)](#插件系统-tools-calling)
+  - [助手市场 (GPTs)](#助手市场-gpts)
+  - [支持本地 / 远程数据库](#支持本地--远程数据库)
+  - [支持多用户管理](#支持多用户管理)
+  - [渐进式 Web 应用 (PWA)](#渐进式-web-应用-pwa)
+  - [移动设备适配](#移动设备适配)
+  - [自定义主题](#自定义主题)
+  - [`*` 更多特性](#-更多特性)
 - [⚡️ 性能测试](#️-性能测试)
 - [🛳 开箱即用](#-开箱即用)
  - [`A` 使用 Vercel、Zeabur 、Sealos 或 阿里云计算巢 部署](#a-使用-vercelzeabur-sealos-或-阿里云计算巢-部署)
@@ -111,9 +125,98 @@

 ## ✨ 特性一览

+通过 LobeChat 的强大功能，体验为无缝连接、提升效率和无限创意而设计的全新 AI 体验。
+
+### ✨ MCP 插件一键安装
+
+[![](https://github.com/user-attachments/assets/1be85d36-3975-4413-931f-27e05e440995)](https://lobehub.com/mcp)
+
+**无缝连接你的 AI 与世界**
+
+通过启用与外部工具、数据源和服务的平滑、安全和动态交互，释放你的 AI 的全部潜力。基于 MCP（模型上下文协议）的插件系统打破了 AI 与数字生态系统之间的壁垒，实现了前所未有的连接性和功能性。
+
+将对话转化为强大的工作流程，连接数据库、API、文件系统等。体验真正理解并与你的世界互动的 AI Agent。
+
+[![][back-to-top]](#readme-top)
+
+### 🏪 MCP 市场
+
+![][image-feat-mcp-market]
+
+**发现、连接、扩展**
+
+浏览不断增长的 MCP 插件库，轻松扩展你的 AI 能力并简化工作流程。访问 [lobehub.com/mcp](https://lobehub.com/mcp) 探索 MCP 市场，提供精选的集成集合，增强你的 AI 与各种工具和服务协作的能力。
+
+从生产力工具到开发环境，发现扩展 AI 覆盖范围和效率的新方式。与社区连接，找到满足特定需求的完美插件。
+
+[![][back-to-top]](#readme-top)
+
+### 🖥️ 桌面应用
+
+![][image-feat-desktop]
+
+**巅峰性能，零干扰**
+
+获得完整的 LobeChat 体验，摆脱浏览器限制 —— 轻量级、专注且随时就绪。我们的桌面应用程序为你的 AI 交互提供专用环境，确保最佳性能和最小干扰。
+
+体验更快的响应时间、更好的资源管理和与 AI 助手的更稳定连接。桌面应用专为要求 AI 工具最佳性能的用户设计。
+
+[![][back-to-top]](#readme-top)
+
+### 🌐 智能联网搜索
+
+![][image-feat-web-search]
+
+**在线知识，按需获取**
+
+通过实时联网访问，你的 AI 与世界保持同步 —— 新闻、数据、趋势等。保持信息更新，获取最新可用信息，使你的 AI 能够提供准确和最新的回复。
+
+访问实时信息，验证事实，探索当前事件，无需离开对话。你的 AI 成为通向世界知识的门户，始终保持最新和全面。
+
+[![][back-to-top]](#readme-top)
+
+[![][image-feat-cot]][docs-feat-cot]
+
+### [思维链 (CoT)][docs-feat-cot]
+
+体验前所未有的 AI 推理过程。通过创新的思维链（CoT）可视化功能，您可以实时观察复杂问题是如何一步步被解析的。这项突破性的功能为 AI 的决策过程提供了前所未有的透明度，让您能够清晰地了解结论是如何得出的。
+
+通过将复杂的推理过程分解为清晰的逻辑步骤，您可以更好地理解和验证 AI 的解题思路。无论您是在调试问题、学习知识，还是单纯对 AI 推理感兴趣，思维链可视化都能将抽象思维转化为一种引人入胜的互动体验。
+
+[![][back-to-top]](#readme-top)
+
+[![][image-feat-branch]][docs-feat-branch]
+
+### [分支对话][docs-feat-branch]
+
+为您带来更自然、更灵活的 AI 对话方式。通过分支对话功能，您的讨论可以像人类对话一样自然延伸。在任意消息处创建新的对话分支，让您在保留原有上下文的同时，自由探索不同的对话方向。
+
+两种强大模式任您选择：
+
+- **延续模式**：无缝延展当前讨论，保持宝贵的对话上下文
+- **独立模式**：基于任意历史消息，开启全新话题探讨
+
+这项突破性功能将线性对话转变为动态的树状结构，让您能够更深入地探索想法，实现更高效的互动体验。
+
+[![][back-to-top]](#readme-top)
+
+[![][image-feat-artifacts]][docs-feat-artifacts]
+
+### [支持白板 (Artifacts)][docs-feat-artifacts]
+
+体验集成于 LobeChat 的 Claude Artifacts 能力。这项革命性功能突破了 AI 人机交互的边界，让您能够实时创建和可视化各种格式的内容。
+
+以前所未有的灵活度进行创作与可视化：
+
+- 生成并展示动态 SVG 图形
+- 实时构建与渲染交互式 HTML 页面
+- 输出多种格式的专业文档
+
+[![][back-to-top]](#readme-top)
+
 [![][image-feat-knowledgebase]][docs-feat-knowledgebase]

-### `1` [文件上传 / 知识库][docs-feat-knowledgebase]
+### [文件上传 / 知识库][docs-feat-knowledgebase]

 LobeChat 支持文件上传与知识库功能，你可以上传文件、图片、音频、视频等多种类型的文件，以及创建知识库，方便用户管理和查找文件。同时在对话中使用文件和知识库功能，实现更加丰富的对话体验。

@@ -131,7 +234,7 @@ LobeChat 支持文件上传与知识库功能，你可以上传文件、图片

 [![][image-feat-privoder]][docs-feat-provider]

-### `2` [多模型服务商支持][docs-feat-provider]
+### [多模型服务商支持][docs-feat-provider]

 在 LobeChat 的不断发展过程中，我们深刻理解到在提供 AI 会话服务时模型服务商的多样性对于满足社区需求的重要性。因此，我们不再局限于单一的模型服务商，而是拓展了对多种模型服务商的支持，以便为用户提供更为丰富和多样化的会话选择。

@@ -143,53 +246,15 @@ LobeChat 支持文件上传与知识库功能，你可以上传文件、图片

 <!-- PROVIDER LIST -->

- **[OpenAI](https://lobechat.com/discover/provider/openai)**: OpenAI 是全球领先的人工智能研究机构，其开发的模型如 GPT 系列推动了自然语言处理的前沿。OpenAI 致力于通过创新和高效的 AI 解决方案改变多个行业。他们的产品具有显著的性能和经济性，广泛用于研究、商业和创新应用。
- **[Ollama](https://lobechat.com/discover/provider/ollama)**: Ollama 提供的模型广泛涵盖代码生成、数学运算、多语种处理和对话互动等领域，支持企业级和本地化部署的多样化需求。
- **[Anthropic](https://lobechat.com/discover/provider/anthropic)**: Anthropic 是一家专注于人工智能研究和开发的公司，提供了一系列先进的语言模型，如 Claude 3.5 Sonnet、Claude 3 Sonnet、Claude 3 Opus 和 Claude 3 Haiku。这些模型在智能、速度和成本之间取得了理想的平衡，适用于从企业级工作负载到快速响应的各种应用场景。Claude 3.5 Sonnet 作为其最新模型，在多项评估中表现优异，同时保持了较高的性价比。
- **[Bedrock](https://lobechat.com/discover/provider/bedrock)**: Bedrock 是亚马逊 AWS 提供的一项服务，专注于为企业提供先进的 AI 语言模型和视觉模型。其模型家族包括 Anthropic 的 Claude 系列、Meta 的 Llama 3.1 系列等，涵盖从轻量级到高性能的多种选择，支持文本生成、对话、图像处理等多种任务，适用于不同规模和需求的企业应用。
- **[Google](https://lobechat.com/discover/provider/google)**: Google 的 Gemini 系列是其最先进、通用的 AI 模型，由 Google DeepMind 打造，专为多模态设计，支持文本、代码、图像、音频和视频的无缝理解与处理。适用于从数据中心到移动设备的多种环境，极大提升了 AI 模型的效率与应用广泛性。
- **[DeepSeek](https://lobechat.com/discover/provider/deepseek)**: DeepSeek 是一家专注于人工智能技术研究和应用的公司，其最新模型 DeepSeek-V3 多项评测成绩超越 Qwen2.5-72B 和 Llama-3.1-405B 等开源模型，性能对齐领军闭源模型 GPT-4o 与 Claude-3.5-Sonnet。
- **[HuggingFace](https://lobechat.com/discover/provider/huggingface)**: HuggingFace Inference API 提供了一种快速且免费的方式，让您可以探索成千上万种模型，适用于各种任务。无论您是在为新应用程序进行原型设计，还是在尝试机器学习的功能，这个 API 都能让您即时访问多个领域的高性能模型。
- **[OpenRouter](https://lobechat.com/discover/provider/openrouter)**: OpenRouter 是一个提供多种前沿大模型接口的服务平台，支持 OpenAI、Anthropic、LLaMA 及更多，适合多样化的开发和应用需求。用户可根据自身需求灵活选择最优的模型和价格，助力 AI 体验的提升。
- **[Cloudflare Workers AI](https://lobechat.com/discover/provider/cloudflare)**: 在 Cloudflare 的全球网络上运行由无服务器 GPU 驱动的机器学习模型。
- **[GitHub](https://lobechat.com/discover/provider/github)**: 通过 GitHub 模型，开发人员可以成为 AI 工程师，并使用行业领先的 AI 模型进行构建。
-
-<details><summary><kbd>See more providers (+26)</kbd></summary>
-
- **[Novita](https://lobechat.com/discover/provider/novita)**: Novita AI 是一个提供多种大语言模型与 AI 图像生成的 API 服务的平台，灵活、可靠且具有成本效益。它支持 Llama3、Mistral 等最新的开源模型，并为生成式 AI 应用开发提供了全面、用户友好且自动扩展的 API 解决方案，适合 AI 初创公司的快速发展。
- **[Together AI](https://lobechat.com/discover/provider/togetherai)**: Together AI 致力于通过创新的 AI 模型实现领先的性能，提供广泛的自定义能力，包括快速扩展支持和直观的部署流程，满足企业的各种需求。
- **[Fireworks AI](https://lobechat.com/discover/provider/fireworksai)**: Fireworks AI 是一家领先的高级语言模型服务商，专注于功能调用和多模态处理。其最新模型 Firefunction V2 基于 Llama-3，优化用于函数调用、对话及指令跟随。视觉语言模型 FireLLaVA-13B 支持图像和文本混合输入。其他 notable 模型包括 Llama 系列和 Mixtral 系列，提供高效的多语言指令跟随与生成支持。
- **[Groq](https://lobechat.com/discover/provider/groq)**: Groq 的 LPU 推理引擎在最新的独立大语言模型（LLM）基准测试中表现卓越，以其惊人的速度和效率重新定义了 AI 解决方案的标准。Groq 是一种即时推理速度的代表，在基于云的部署中展现了良好的性能。
- **[Perplexity](https://lobechat.com/discover/provider/perplexity)**: Perplexity 是一家领先的对话生成模型提供商，提供多种先进的 Llama 3.1 模型，支持在线和离线应用，特别适用于复杂的自然语言处理任务。
- **[Mistral](https://lobechat.com/discover/provider/mistral)**: Mistral 提供先进的通用、专业和研究型模型，广泛应用于复杂推理、多语言任务、代码生成等领域，通过功能调用接口，用户可以集成自定义功能，实现特定应用。
- **[Ai21Labs](https://lobechat.com/discover/provider/ai21)**: AI21 Labs 为企业构建基础模型和人工智能系统，加速生成性人工智能在生产中的应用。
- **[Upstage](https://lobechat.com/discover/provider/upstage)**: Upstage 专注于为各种商业需求开发 AI 模型，包括 Solar LLM 和文档 AI，旨在实现工作的人造通用智能（AGI）。通过 Chat API 创建简单的对话代理，并支持功能调用、翻译、嵌入以及特定领域应用。
- **[xAI](https://lobechat.com/discover/provider/xai)**: xAI 是一家致力于构建人工智能以加速人类科学发现的公司。我们的使命是推动我们对宇宙的共同理解。
- **[Qwen](https://lobechat.com/discover/provider/qwen)**: 通义千问是阿里云自主研发的超大规模语言模型，具有强大的自然语言理解和生成能力。它可以回答各种问题、创作文字内容、表达观点看法、撰写代码等，在多个领域发挥作用。
- **[Wenxin](https://lobechat.com/discover/provider/wenxin)**: 企业级一站式大模型与 AI 原生应用开发及服务平台，提供最全面易用的生成式人工智能模型开发、应用开发全流程工具链
- **[Hunyuan](https://lobechat.com/discover/provider/hunyuan)**: 由腾讯研发的大语言模型，具备强大的中文创作能力，复杂语境下的逻辑推理能力，以及可靠的任务执行能力
- **[ZhiPu](https://lobechat.com/discover/provider/zhipu)**: 智谱 AI 提供多模态与语言模型的开放平台，支持广泛的 AI 应用场景，包括文本处理、图像理解与编程辅助等。
- **[SiliconCloud](https://lobechat.com/discover/provider/siliconcloud)**: SiliconCloud，基于优秀开源基础模型的高性价比 GenAI 云服务
- **[01.AI](https://lobechat.com/discover/provider/zeroone)**: 零一万物致力于推动以人为本的 AI 2.0 技术革命，旨在通过大语言模型创造巨大的经济和社会价值，并开创新的 AI 生态与商业模式。
- **[Spark](https://lobechat.com/discover/provider/spark)**: 科大讯飞星火大模型提供多领域、多语言的强大 AI 能力，利用先进的自然语言处理技术，构建适用于智能硬件、智慧医疗、智慧金融等多种垂直场景的创新应用。
- **[SenseNova](https://lobechat.com/discover/provider/sensenova)**: 商汤日日新，依托商汤大装置的强大的基础支撑，提供高效易用的全栈大模型服务。
- **[Stepfun](https://lobechat.com/discover/provider/stepfun)**: 阶级星辰大模型具备行业领先的多模态及复杂推理能力，支持超长文本理解和强大的自主调度搜索引擎功能。
- **[Moonshot](https://lobechat.com/discover/provider/moonshot)**: Moonshot 是由北京月之暗面科技有限公司推出的开源平台，提供多种自然语言处理模型，应用领域广泛，包括但不限于内容创作、学术研究、智能推荐、医疗诊断等，支持长文本处理和复杂生成任务。
- **[Baichuan](https://lobechat.com/discover/provider/baichuan)**: 百川智能是一家专注于人工智能大模型研发的公司，其模型在国内知识百科、长文本处理和生成创作等中文任务上表现卓越，超越了国外主流模型。百川智能还具备行业领先的多模态能力，在多项权威评测中表现优异。其模型包括 Baichuan 4、Baichuan 3 Turbo 和 Baichuan 3 Turbo 128k 等，分别针对不同应用场景进行优化，提供高性价比的解决方案。
- **[Minimax](https://lobechat.com/discover/provider/minimax)**: MiniMax 是 2021 年成立的通用人工智能科技公司，致力于与用户共创智能。MiniMax 自主研发了不同模态的通用大模型，其中包括万亿参数的 MoE 文本大模型、语音大模型以及图像大模型。并推出了海螺 AI 等应用。
- **[InternLM](https://lobechat.com/discover/provider/internlm)**: 致力于大模型研究与开发工具链的开源组织。为所有 AI 开发者提供高效、易用的开源平台，让最前沿的大模型与算法技术触手可及
- **[Higress](https://lobechat.com/discover/provider/higress)**: Higress 是一款云原生 API 网关，在阿里内部为解决 Tengine reload 对长连接业务有损，以及 gRPC/Dubbo 负载均衡能力不足而诞生。
- **[Gitee AI](https://lobechat.com/discover/provider/giteeai)**: Gitee AI 的 Serverless API 为 AI 开发者提供开箱即用的大模型推理 API 服务。
- **[Taichu](https://lobechat.com/discover/provider/taichu)**: 中科院自动化研究所和武汉人工智能研究院推出新一代多模态大模型，支持多轮问答、文本创作、图像生成、3D 理解、信号分析等全面问答任务，拥有更强的认知、理解、创作能力，带来全新互动体验。
- **[360 AI](https://lobechat.com/discover/provider/ai360)**: 360 AI 是 360 公司推出的 AI 模型和服务平台，提供多种先进的自然语言处理模型，包括 360GPT2 Pro、360GPT Pro、360GPT Turbo 和 360GPT Turbo Responsibility 8K。这些模型结合了大规模参数和多模态能力，广泛应用于文本生成、语义理解、对话系统与代码生成等领域。通过灵活的定价策略，360 AI 满足多样化用户需求，支持开发者集成，推动智能化应用的革新和发展。
+<details><summary><kbd>See more providers (+-10)</kbd></summary>

 </details>

-> 📊 Total providers: [<kbd>**36**</kbd>](https://lobechat.com/discover/providers)
+> 📊 Total providers: [<kbd>**0**</kbd>](https://lobechat.com/discover/providers)

 <!-- PROVIDER LIST -->

-同时，我们也在计划支持更多的模型服务商，以进一步丰富我们的服务商库。如果你希望让 LobeChat 支持你喜爱的服务商，欢迎加入我们的 [💬 社区讨论](https://github.com/lobehub/lobe-chat/discussions/1284)。
+同时，我们也在计划支持更多的模型服务商，以进一步丰富我们的服务商库。如果你希望让 LobeChat 支持你喜爱的服务商，欢迎加入我们的 [💬 社区讨论](https://github.com/lobehub/lobe-chat/discussions/6157)。

 <div align="right">

@@ -199,7 +264,7 @@ LobeChat 支持文件上传与知识库功能，你可以上传文件、图片

 [![][image-feat-local]][docs-feat-local]

-### `3` [支持本地大语言模型 (LLM)][docs-feat-local]
+### [支持本地大语言模型 (LLM)][docs-feat-local]

 为了满足特定用户的需求，LobeChat 还基于 [Ollama](https://ollama.ai) 支持了本地模型的使用，让用户能够更灵活地使用自己的或第三方的模型。

@@ -215,7 +280,7 @@ LobeChat 支持文件上传与知识库功能，你可以上传文件、图片

 [![][image-feat-vision]][docs-feat-vision]

-### `4` [模型视觉识别 (Model Visual)][docs-feat-vision]
+### [模型视觉识别 (Model Visual)][docs-feat-vision]

 LobeChat 已经支持 OpenAI 最新的 [`gpt-4-vision`](https://platform.openai.com/docs/guides/vision) 支持视觉识别的模型，这是一个具备视觉识别能力的多模态应用。
 用户可以轻松上传图片或者拖拽图片到对话框中，助手将能够识别图片内容，并在此基础上进行智能对话，构建更智能、更多元化的聊天场景。
@@ -230,7 +295,7 @@ LobeChat 已经支持 OpenAI 最新的 [`gpt-4-vision`](https://platform.openai.

 [![][image-feat-tts]][docs-feat-tts]

-### `5` [TTS & STT 语音会话][docs-feat-tts]
+### [TTS & STT 语音会话][docs-feat-tts]

 LobeChat 支持文字转语音（Text-to-Speech，TTS）和语音转文字（Speech-to-Text，STT）技术，这使得我们的应用能够将文本信息转化为清晰的语音输出，用户可以像与真人交谈一样与我们的对话助手进行交流。
 用户可以从多种声音中选择，给助手搭配合适的音源。 同时，对于那些倾向于听觉学习或者想要在忙碌中获取信息的用户来说，TTS 提供了一个极佳的解决方案。
@@ -245,7 +310,7 @@ LobeChat 支持文字转语音（Text-to-Speech，TTS）和语音转文字（Spe

 [![][image-feat-t2i]][docs-feat-t2i]

-### `6` [Text to Image 文生图][docs-feat-t2i]
+### [Text to Image 文生图][docs-feat-t2i]

 支持最新的文本到图片生成技术，LobeChat 现在能够让用户在与助手对话中直接调用文生图工具进行创作。
 通过利用 [`DALL-E 3`](https://openai.com/dall-e-3)、[`MidJourney`](https://www.midjourney.com/) 和 [`Pollinations`](https://pollinations.ai/) 等 AI 工具的能力， 助手们现在可以将你的想法转化为图像。
@@ -259,7 +324,7 @@ LobeChat 支持文字转语音（Text-to-Speech，TTS）和语音转文字（Spe

 [![][image-feat-plugin]][docs-feat-plugin]

-### `7` [插件系统 (Tools Calling)][docs-feat-plugin]
+### [插件系统 (Tools Calling)][docs-feat-plugin]

 LobeChat 的插件生态系统是其核心功能的重要扩展，它极大地增强了 ChatGPT 的实用性和灵活性。

@@ -273,14 +338,14 @@ LobeChat 的插件生态系统是其核心功能的重要扩展，它极大地

 <!-- PLUGIN LIST -->

-| 最近新增                                                                                                               | 描述                                                                             |
-| ---------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
-| [MintbaseSearch](https://lobechat.com/discover/plugin/mintbasesearch)<br/><sup>By **mintbase** on **2024-12-31**</sup> | 在 NEAR 协议上查找任何 NFT 数据。<br/>`加密货币` `nft`                           |
-| [PortfolioMeta](https://lobechat.com/discover/plugin/StockData)<br/><sup>By **portfoliometa** on **2024-12-22**</sup>  | 分析股票并获取全面的实时投资数据和分析。<br/>`股票`                              |
-| [谷歌自定义搜索引擎](https://lobechat.com/discover/plugin/google-cse)<br/><sup>By **vsnthdev** on **2024-12-02**</sup> | 通过他们的官方自定义搜索引擎 API 搜索谷歌。<br/>`网络` `搜索`                    |
-| [Speak](https://lobechat.com/discover/plugin/speak)<br/><sup>By **speak** on **2024-12-02**</sup>                      | 使用 Speak，您的 AI 语言导师，学习如何用另一种语言说任何事情。<br/>`教育` `语言` |
+| 最近新增                                                                                                              | 描述                                                                                                               |
+| --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
+| [SEO](https://lobechat.com/discover/plugin/SEO)<br/><sup>By **orrenprunckun** on **2025-11-14**</sup>                 | 输入任何 URL 和关键词，获取页面 SEO 分析和见解！<br/>`seo`                                                         |
+| [购物工具](https://lobechat.com/discover/plugin/ShoppingTools)<br/><sup>By **shoppingtools** on **2025-10-27**</sup>  | 在 eBay 和 AliExpress 上搜索产品，查找 eBay 活动和优惠券。获取快速示例。<br/>`购物` `e-bay` `ali-express` `优惠券` |
+| [PortfolioMeta](https://lobechat.com/discover/plugin/StockData)<br/><sup>By **portfoliometa** on **2025-09-27**</sup> | 分析股票并获取全面的实时投资数据和分析。<br/>`股票`                                                                |
+| [网页](https://lobechat.com/discover/plugin/web)<br/><sup>By **Proghit** on **2025-01-24**</sup>                      | 智能网页搜索，读取和分析页面，以提供来自 Google 结果的全面答案。<br/>`网页` `搜索`                                 |

-> 📊 Total plugins: [<kbd>**48**</kbd>](https://lobechat.com/discover/plugins)
+> 📊 Total plugins: [<kbd>**42**</kbd>](https://lobechat.com/discover/plugins)

 <!-- PLUGIN LIST -->

@@ -292,7 +357,7 @@ LobeChat 的插件生态系统是其核心功能的重要扩展，它极大地

 [![][image-feat-agent]][docs-feat-agent]

-### `8` [助手市场 (GPTs)][docs-feat-agent]
+### [助手市场 (GPTs)][docs-feat-agent]

 在 LobeChat 的助手市场中，创作者们可以发现一个充满活力和创新的社区，它汇聚了众多精心设计的助手，这些助手不仅在工作场景中发挥着重要作用，也在学习过程中提供了极大的便利。
 我们的市场不仅是一个展示平台，更是一个协作的空间。在这里，每个人都可以贡献自己的智慧，分享个人开发的助手。
@@ -308,14 +373,14 @@ LobeChat 的插件生态系统是其核心功能的重要扩展，它极大地

 <!-- AGENT LIST -->

-| 最近新增                                                                                                                                                                | 描述                                                                                      |
-| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
-| [系统指令专家](https://lobechat.com/discover/assistant/instructer)<br/><sup>By **[yuyun2000](https://github.com/yuyun2000)** on **2024-12-04**</sup>                    | 擅长精炼与生成高效系统指令<br/>`系统指令` `写作` `细节优化` `用户需求`                    |
-| [日语帮助记忆师](https://lobechat.com/discover/assistant/japan-language-helper)<br/><sup>By **[sharkbear212](https://github.com/sharkbear212)** on **2024-12-04**</sup> | 擅长日语五十音，平假名，片假名，单词和短语解释与记忆技巧<br/>`解释` `记忆技巧` `日语教学` |
-| [诗词卡片设计师](https://lobechat.com/discover/assistant/poetry-card-designer)<br/><sup>By **[lianxin255](https://github.com/lianxin255)** on **2024-12-03**</sup>      | 擅长设计诗词卡片，提升艺术感与吸引力<br/>`诗词卡片设计` `卡片` `创意` `艺术表现`          |
-| [日常医生](https://lobechat.com/discover/assistant/yunchat-docter)<br/><sup>By **[yuyun2000](https://github.com/yuyun2000)** on **2024-11-30**</sup>                    | 擅长外科诊疗与个性化健康管理<br/>`全科医学` `外科` `健康咨询` `个性化治疗` `医学教育`     |
+| 最近新增                                                                                                                                                         | 描述                                                                                                              |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
+| [海龟汤主持人](https://lobechat.com/discover/assistant/lateral-thinking-puzzle)<br/><sup>By **[CSY2022](https://github.com/CSY2022)** on **2025-06-19**</sup>    | 一个海龟汤主持人，需要自己提供汤面，汤底与关键点（猜中的判定条件）。<br/>`海龟汤` `推理` `互动` `谜题` `角色扮演` |
+| [美食评论员🍟](https://lobechat.com/discover/assistant/food-reviewer)<br/><sup>By **[renhai-lab](https://github.com/renhai-lab)** on **2025-06-17**</sup>        | 美食评价专家<br/>`美食` `评价` `写作`                                                                             |
+| [学术写作助手](https://lobechat.com/discover/assistant/academic-writing-assistant)<br/><sup>By **[swarfte](https://github.com/swarfte)** on **2025-06-17**</sup> | 专业的学术研究论文写作和正式文档编写专家<br/>`学术写作` `研究` `正式风格`                                         |
+| [Minecraft 资深开发者](https://lobechat.com/discover/assistant/java-development)<br/><sup>By **[iamyuuk](https://github.com/iamyuuk)** on **2025-06-17**</sup>   | 擅长高级 Java 开发及 Minecraft 开发<br/>`开发` `编程` `minecraft` `java`                                          |

-> 📊 Total agents: [<kbd>**453**</kbd> ](https://lobechat.com/discover/assistants)
+> 📊 Total agents: [<kbd>**505**</kbd> ](https://lobechat.com/discover/assistants)

 <!-- AGENT LIST -->

@@ -327,7 +392,7 @@ LobeChat 的插件生态系统是其核心功能的重要扩展，它极大地

 [![][image-feat-database]][docs-feat-database]

-### `9` [支持本地 / 远程数据库][docs-feat-database]
+### [支持本地 / 远程数据库][docs-feat-database]

 LobeChat 支持同时使用服务端数据库和本地数据库。根据您的需求，您可以选择合适的部署方案：

@@ -344,7 +409,7 @@ LobeChat 支持同时使用服务端数据库和本地数据库。根据您的

 [![][image-feat-auth]][docs-feat-auth]

-### `10` [支持多用户管理][docs-feat-auth]
+### [支持多用户管理][docs-feat-auth]

 LobeChat 支持多用户管理，提供了两种主要的用户认证和管理方案，以满足不同需求：

@@ -362,7 +427,7 @@ LobeChat 支持多用户管理，提供了两种主要的用户认证和管理

 [![][image-feat-pwa]][docs-feat-pwa]

-### `11` [渐进式 Web 应用 (PWA)][docs-feat-pwa]
+### [渐进式 Web 应用 (PWA)][docs-feat-pwa]

 我们深知在当今多设备环境下为用户提供无缝体验的重要性。为此，我们采用了渐进式 Web 应用 [PWA](https://support.google.com/chrome/answer/9658361) 技术，
 这是一种能够将网页应用提升至接近原生应用体验的现代 Web 技术。通过 PWA，LobeChat 能够在桌面和移动设备上提供高度优化的用户体验，同时保持轻量级和高性能的特点。
@@ -375,7 +440,6 @@ LobeChat 支持多用户管理，提供了两种主要的用户认证和管理
 > - 在电脑上运行 Chrome 或 Edge 浏览器 .
 > - 访问 LobeChat 网页 .
 > - 在地址栏的右上角，单击 <kbd>安装</kbd> 图标 .
-> - 根据屏幕上的指示完成 PWA 的安装 .

 <div align="right">

@@ -385,7 +449,7 @@ LobeChat 支持多用户管理，提供了两种主要的用户认证和管理

 [![][image-feat-mobile]][docs-feat-mobile]

-### `12` [移动设备适配][docs-feat-mobile]
+### [移动设备适配][docs-feat-mobile]

 针对移动设备进行了一系列的优化设计，以提升用户的移动体验。目前，我们正在对移动端的用户体验进行版本迭代，以实现更加流畅和直观的交互。如果您有任何建议或想法，我们非常欢迎您通过 GitHub Issues 或者 Pull Requests 提供反馈。

@@ -397,7 +461,7 @@ LobeChat 支持多用户管理，提供了两种主要的用户认证和管理

 [![][image-feat-theme]][docs-feat-theme]

-### `13` [自定义主题][docs-feat-theme]
+### [自定义主题][docs-feat-theme]

 作为设计工程师出身，LobeChat 在界面设计上充分考虑用户的个性化体验，因此引入了灵活多变的主题模式，其中包括日间的亮色模式和夜间的深色模式。
 除了主题模式的切换，还提供了一系列的颜色定制选项，允许用户根据自己的喜好来调整应用的主题色彩。无论是想要沉稳的深蓝，还是希望活泼的桃粉，或者是专业的灰白，用户都能够在 LobeChat 中找到匹配自己风格的颜色选择。
@@ -412,7 +476,7 @@ LobeChat 支持多用户管理，提供了两种主要的用户认证和管理

 </div>

-### 更多特性
+### `*` 更多特性

 除了上述功能特性以外，LobeChat 所具有的设计和技术能力将为你带来更多使用保障：

@@ -484,7 +548,7 @@ LobeChat 提供了 Vercel 的 自托管版本 和 [Docker 镜像][docker-release

 #### 保持更新

-如果你根据 README 中的一键部署步骤部署了自己的项目，你可能会发现总是被提示 “有可用更新”。这是因为 Vercel 默认为你创建新项目而非 fork 本项目，这将导致无法准确检测更新。
+如果你根据 README 中的一键部署步骤部署了自己的项目，你可能会发现总是被提示 "有可用更新"。这是因为 Vercel 默认为你创建新项目而非 fork 本项目，这将导致无法准确检测更新。

 > \[!TIP]
 >
@@ -498,27 +562,24 @@ LobeChat 提供了 Vercel 的 自托管版本 和 [Docker 镜像][docker-release
 [![][docker-size-shield]][docker-size-link]
 [![][docker-pulls-shield]][docker-pulls-link]

-我们提供了 Docker 镜像，供你在自己的私有设备上部署 LobeChat 服务。使用以下命令即可使用一键启动 LobeChat 服务：
+我们提供了一个用于在您自己的私有设备上部署 LobeChat 服务的 Docker 镜像。请使用以下命令启动 LobeChat 服务：
+
+1. 创建一个用于存储文件的文件夹

 ```fish
-$ docker run -d -p 3210:3210 \
-  -e OPENAI_API_KEY=sk-xxxx \
-  -e ACCESS_CODE=lobe66 \
-  --name lobe-chat \
-  lobehub/lobe-chat
+$ mkdir lobe-chat-db && cd lobe-chat-db
 ```

-> \[!TIP]
->
-> 如果你需要通过代理使用 OpenAI 服务，你可以使用 `OPENAI_PROXY_URL` 环境变量来配置代理地址：
+2. 启动一键脚本

 ```fish
-$ docker run -d -p 3210:3210 \
-  -e OPENAI_API_KEY=sk-xxxx \
-  -e OPENAI_PROXY_URL=https://api-proxy.com/v1 \
-  -e ACCESS_CODE=lobe66 \
-  --name lobe-chat \
-  lobehub/lobe-chat
+bash <(curl -fsSL https://lobe.li/setup.sh) -l zh_CN
+```
+
+3. 启动 LobeChat
+
+```fish
+docker compose up -d
 ```

 > \[!NOTE]
@@ -741,8 +802,8 @@ $ pnpm run dev

 </details>

-Copyright © 2023 [LobeHub][profile-link]. <br />
-This project is [Apache 2.0](./LICENSE) licensed.
+Copyright © 2025 [LobeHub][profile-link]. <br />
+This project is [LobeHub Community License](./LICENSE) licensed.

 <!-- LINK GROUP -->

@@ -750,9 +811,9 @@ This project is [Apache 2.0](./LICENSE) licensed.
 [blog]: https://lobehub.com/zh/blog
 [changelog]: https://lobehub.com/changelog
 [chat-desktop]: https://raw.githubusercontent.com/lobehub/lobe-chat/lighthouse/lighthouse/chat/desktop/pagespeed.svg
-[chat-desktop-report]: https://lobehub.github.io/lobe-chat/lighthouse/chat/desktop/chat_preview_lobehub_com_chat.html
+[chat-desktop-report]: https://lobehub.github.io/lobe-chat/lighthouse/chat/desktop/lobechat_com_chat.html
 [chat-mobile]: https://raw.githubusercontent.com/lobehub/lobe-chat/lighthouse/lighthouse/chat/mobile/pagespeed.svg
-[chat-mobile-report]: https://lobehub.github.io/lobe-chat/lighthouse/chat/mobile/chat_preview_lobehub_com_chat.html
+[chat-mobile-report]: https://lobehub.github.io/lobe-chat/lighthouse/chat/mobile/lobechat_com_chat.html
 [chat-plugin-sdk]: https://github.com/lobehub/chat-plugin-sdk
 [chat-plugin-template]: https://github.com/lobehub/chat-plugin-template
 [chat-plugins-gateway]: https://github.com/lobehub/chat-plugins-gateway
@@ -765,24 +826,27 @@ This project is [Apache 2.0](./LICENSE) licensed.
 [deploy-on-alibaba-cloud-button-image]: https://service-info-public.oss-cn-hangzhou.aliyuncs.com/computenest-en.svg
 [deploy-on-alibaba-cloud-link]: https://computenest.console.aliyun.com/service/instance/create/default?type=user&ServiceName=LobeChat%E7%A4%BE%E5%8C%BA%E7%89%88
 [deploy-on-sealos-button-image]: https://raw.githubusercontent.com/labring-actions/templates/main/Deploy-on-Sealos.svg
-[deploy-on-sealos-link]: https://cloud.sealos.io/?openapp=system-template%3FtemplateName%3Dlobe-chat
+[deploy-on-sealos-link]: https://template.hzh.sealos.run/deploy?templateName=lobe-chat-db
 [deploy-on-zeabur-button-image]: https://zeabur.com/button.svg
 [deploy-on-zeabur-link]: https://zeabur.com/templates/VZGGTI
 [discord-link]: https://discord.gg/AYFPHvv2jT
 [discord-shield]: https://img.shields.io/discord/1127171173982154893?color=5865F2&label=discord&labelColor=black&logo=discord&logoColor=white&style=flat-square
 [discord-shield-badge]: https://img.shields.io/discord/1127171173982154893?color=5865F2&label=discord&labelColor=black&logo=discord&logoColor=white&style=for-the-badge
-[docker-pulls-link]: https://hub.docker.com/r/lobehub/lobe-chat
-[docker-pulls-shield]: https://img.shields.io/docker/pulls/lobehub/lobe-chat?color=45cc11&labelColor=black&style=flat-square
-[docker-release-link]: https://hub.docker.com/r/lobehub/lobe-chat
-[docker-release-shield]: https://img.shields.io/docker/v/lobehub/lobe-chat?color=369eff&label=docker&labelColor=black&logo=docker&logoColor=white&style=flat-square
-[docker-size-link]: https://hub.docker.com/r/lobehub/lobe-chat
-[docker-size-shield]: https://img.shields.io/docker/image-size/lobehub/lobe-chat?color=369eff&labelColor=black&style=flat-square
+[docker-pulls-link]: https://hub.docker.com/r/lobehub/lobe-chat-database
+[docker-pulls-shield]: https://img.shields.io/docker/pulls/lobehub/lobe-chat?color=45cc11&labelColor=black&style=flat-square&sort=semver
+[docker-release-link]: https://hub.docker.com/r/lobehub/lobe-chat-database
+[docker-release-shield]: https://img.shields.io/docker/v/lobehub/lobe-chat-database?color=369eff&label=docker&labelColor=black&logo=docker&logoColor=white&style=flat-square&sort=semver
+[docker-size-link]: https://hub.docker.com/r/lobehub/lobe-chat-database
+[docker-size-shield]: https://img.shields.io/docker/image-size/lobehub/lobe-chat-database?color=369eff&labelColor=black&style=flat-square&sort=semver
 [docs]: https://lobehub.com/zh/docs/usage/start
 [docs-dev-guide]: https://github.com/lobehub/lobe-chat/wiki/index
-[docs-docker]: https://lobehub.com/docs/self-hosting/platform/docker
+[docs-docker]: https://lobehub.com/zh/docs/self-hosting/server-database/docker-compose
 [docs-env-var]: https://lobehub.com/docs/self-hosting/environment-variables
 [docs-feat-agent]: https://lobehub.com/docs/usage/features/agent-market
+[docs-feat-artifacts]: https://lobehub.com/docs/usage/features/artifacts
 [docs-feat-auth]: https://lobehub.com/docs/usage/features/auth
+[docs-feat-branch]: https://lobehub.com/docs/usage/features/branching-conversations
+[docs-feat-cot]: https://lobehub.com/docs/usage/features/cot
 [docs-feat-database]: https://lobehub.com/docs/usage/features/database
 [docs-feat-knowledgebase]: https://lobehub.com/blog/knowledge-base
 [docs-feat-local]: https://lobehub.com/docs/usage/features/local-llm
@@ -822,26 +886,32 @@ This project is [Apache 2.0](./LICENSE) licensed.
 [github-release-shield]: https://img.shields.io/github/v/release/lobehub/lobe-chat?color=369eff&labelColor=black&logo=github&style=flat-square
 [github-releasedate-link]: https://github.com/lobehub/lobe-chat/releases
 [github-releasedate-shield]: https://img.shields.io/github/release-date/lobehub/lobe-chat?labelColor=black&style=flat-square
-[github-stars-link]: https://github.com/lobehub/lobe-chat/network/stargazers
+[github-stars-link]: https://github.com/lobehub/lobe-chat/stargazers
 [github-stars-shield]: https://img.shields.io/github/stars/lobehub/lobe-chat?color=ffcb47&labelColor=black&style=flat-square
 [github-trending-shield]: https://trendshift.io/api/badge/repositories/2256
 [github-trending-url]: https://trendshift.io/repositories/2256
-[image-banner]: https://github.com/lobehub/lobe-chat/assets/28616219/9f155dff-4737-429f-9cad-a70a1a860c5f
-[image-feat-agent]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/268670869-f1ffbf66-42b6-42cf-a937-9ce1f8328514.png
-[image-feat-auth]: https://github.com/lobehub/lobe-chat/assets/17870709/8ce70e15-40df-451e-b700-66090fe5b8c2
-[image-feat-database]: https://github.com/lobehub/lobe-chat/assets/17870709/c27a0234-a4e9-40e5-8bcb-42d5ce7e40f9
-[image-feat-knowledgebase]: https://github.com/user-attachments/assets/77e58e1c-c82f-4341-b159-f4eeede9967f
-[image-feat-local]: https://github.com/lobehub/lobe-chat/assets/28616219/ca9a21bc-ea6c-4c90-bf4a-fa53b4fb2b5c
-[image-feat-mobile]: https://gw.alipayobjects.com/zos/kitchen/R441AuFS4W/mobile.webp
-[image-feat-plugin]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/268670883-33c43a5c-a512-467e-855c-fa299548cce5.png
-[image-feat-privoder]: https://github.com/lobehub/lobe-chat/assets/28616219/b164bc54-8ba2-4c1e-b2f2-f4d7f7e7a551
-[image-feat-pwa]: https://gw.alipayobjects.com/zos/kitchen/69x6bllkX3/pwa.webp
-[image-feat-t2i]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/297746445-0ff762b9-aa08-4337-afb7-12f932b6efbb.png
-[image-feat-theme]: https://gw.alipayobjects.com/zos/kitchen/pvus1lo%26Z7/darkmode.webp
-[image-feat-tts]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/284072124-c9853d8d-f1b5-44a8-a305-45ebc0f6d19a.png
-[image-feat-vision]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/284072129-382bdf30-e3d6-4411-b5a0-249710b8ba08.png
-[image-overview]: https://github.com/lobehub/lobe-chat/assets/17870709/56b95d48-f573-41cd-8b38-387bf88bc4bf
-[image-star]: https://github.com/lobehub/lobe-chat/assets/17870709/cb06b748-513f-47c2-8740-d876858d7855
+[image-banner]: https://github.com/user-attachments/assets/6f293c7f-47b4-47eb-9202-fe68a942d35b
+[image-feat-agent]: https://github.com/user-attachments/assets/b3ab6e35-4fbc-468d-af10-e3e0c687350f
+[image-feat-artifacts]: https://github.com/user-attachments/assets/7f95fad6-b210-4e6e-84a0-7f39e96f3a00
+[image-feat-auth]: https://github.com/user-attachments/assets/80bb232e-19d1-4f97-98d6-e291f3585e6d
+[image-feat-branch]: https://github.com/user-attachments/assets/92f72082-02bd-4835-9c54-b089aad7fd41
+[image-feat-cot]: https://github.com/user-attachments/assets/f74f1139-d115-4e9c-8c43-040a53797a5e
+[image-feat-database]: https://github.com/user-attachments/assets/f1697c8b-d1fb-4dac-ba05-153c6295d91d
+[image-feat-desktop]: https://github.com/user-attachments/assets/a7bac8d3-ea96-4000-bb39-fadc9b610f96
+[image-feat-knowledgebase]: https://github.com/user-attachments/assets/7da7a3b2-92fd-4630-9f4e-8560c74955ae
+[image-feat-local]: https://github.com/user-attachments/assets/1239da50-d832-4632-a7ef-bd754c0f3850
+[image-feat-mcp-market]: https://github.com/user-attachments/assets/bb114f9f-24c5-4000-a984-c10d187da5a0
+[image-feat-mobile]: https://github.com/user-attachments/assets/32cf43c4-96bd-4a4c-bfb6-59acde6fe380
+[image-feat-plugin]: https://github.com/user-attachments/assets/66a891ac-01b6-4e3f-b978-2eb07b489b1b
+[image-feat-privoder]: https://github.com/user-attachments/assets/e553e407-42de-4919-977d-7dbfcf44a821
+[image-feat-pwa]: https://github.com/user-attachments/assets/9647f70f-b71b-43b6-9564-7cdd12d1c24d
+[image-feat-t2i]: https://github.com/user-attachments/assets/708274a7-2458-494b-a6ec-b73dfa1fa7c2
+[image-feat-theme]: https://github.com/user-attachments/assets/b47c39f1-806f-492b-8fcb-b0fa973937c1
+[image-feat-tts]: https://github.com/user-attachments/assets/50189597-2cc3-4002-b4c8-756a52ad5c0a
+[image-feat-vision]: https://github.com/user-attachments/assets/18574a1f-46c2-4cbc-af2c-35a86e128a07
+[image-feat-web-search]: https://github.com/user-attachments/assets/cfdc48ac-b5f8-4a00-acee-db8f2eba09ad
+[image-overview]: https://github.com/user-attachments/assets/dbfaa84a-2c82-4dd9-815c-5be616f264a4
+[image-star]: https://github.com/user-attachments/assets/c3b482e7-cef5-4e94-bef9-226900ecfaab
 [issues-link]: https://img.shields.io/github/issues/lobehub/lobe-chat.svg?style=flat
 [lobe-chat-plugins]: https://github.com/lobehub/lobe-chat-plugins
 [lobe-commit]: https://github.com/lobehub/lobe-commit/tree/master/packages/lobe-commit
@@ -1,892 +0,0 @@
-<div align="center"><a name="readme-top"></a>
-
-[![][image-banner]][vercel-link]
-
-<h1>Lobe Chat</h1>
-
-現代風格的開源 ChatGPT/LLMs 使用介面/框架  
-支持語音合成、多模態、可擴展的（[function call][docs-functionc-call]）插件系統  
-一鍵**免費**部署私人的 OpenAI ChatGPT/Claude/Gemini/Groq/Ollama 聊天應用
-
-[English](./README.md) · **繁體中文** · [簡體中文](./README.zh-CN.md) · [日本語](./README.ja-JP.md) · [官網][official-site] · [更新日誌][changelog] · [文檔][docs] · [部落格][blog] · [反饋問題][github-issues-link]
-
-<!-- SHIELD GROUP -->
-
-[![][github-release-shield]][github-release-link]
-[![][docker-release-shield]][docker-release-link]
-[![][vercel-shield]][vercel-link]
-[![][discord-shield]][discord-link]<br/>
-[![][codecov-shield]][codecov-link]
-[![][github-action-test-shield]][github-action-test-link]
-[![][github-action-release-shield]][github-action-release-link]
-[![][github-releasedate-shield]][github-releasedate-link]<br/>
-[![][github-contributors-shield]][github-contributors-link]
-[![][github-forks-shield]][github-forks-link]
-[![][github-stars-shield]][github-stars-link]
-[![][github-issues-shield]][github-issues-link]
-[![][github-license-shield]][github-license-link]<br>
-[![][sponsor-shield]][sponsor-link]
-
-**分享 LobeChat 給你的好友**
-
-[![][share-x-shield]][share-x-link]
-[![][share-telegram-shield]][share-telegram-link]
-[![][share-whatsapp-shield]][share-whatsapp-link]
-[![][share-reddit-shield]][share-reddit-link]
-[![][share-weibo-shield]][share-weibo-link]
-[![][share-mastodon-shield]][share-mastodon-link]
-
-<sup>探索私人生產力的未來，在個體崛起的時代中為你打造。</sup>
-
-[![][github-trending-shield]][github-trending-url]
-[![][github-hello-shield]][github-hello-url]
-
-[![][image-overview]][vercel-link]
-
-</div>
-
-<details>
-<summary><kbd>目錄樹</kbd></summary>
-
-#### TOC
-
- [👋🏻 開始使用 \& 交流](#-開始使用--交流)
- [✨ 特性一覽](#-特性一覽)
-  - [`1` 文件上傳 / 知識庫](#1-文件上傳--知識庫)
-  - [`2` 多模型服務商支持](#2-多模型服務商支持)
-    - [已支持的模型服務商](#已支持的模型服務商)
-  - [`3` 支持本地大型語言模型 (LLM)](#3-支持本地大型語言模型-llm)
-  - [`4` 模型視覺識別 (Model Visual)](#4-模型視覺識別-model-visual)
-  - [`5` TTS \& STT 語音轉化](#5-tts--stt-語音轉化)
-  - [`6` Text to Image 文生圖](#6-text-to-image-文生圖)
-  - [`7` 插件系統 (Tools Calling)](#7-插件系統-tools-calling)
-  - [`8` 助手市集 (GPTs)](#8-助手市集-gpts)
-  - [`9` 支持本地 / 遠程數據庫](#9-支持本地--遠程數據庫)
-  - [`10` 支持多用戶管理](#10-支持多用戶管理)
-  - [`11` 漸進式 Web 應用 (PWA)](#11-漸進式-web-應用-pwa)
-  - [`12` 移動設備適配](#12-移動設備適配)
-  - [`13` 自定義主題](#13-自定義主題)
-  - [更多特性](#更多特性)
- [⚡️ 性能測試](#️-性能測試)
- [🛳 開箱即用](#-開箱即用)
-  - [`A` 使用 Vercel、Zeabur 、Sealos 或 Alibaba Cloud 部署](#a-使用-vercelzeabur-sealos-或-alibaba-cloud-部署)
-    - [Fork 之後](#fork-之後)
-    - [保持更新](#保持更新)
-  - [`B` 使用 Docker 部署](#b-使用-docker-部署)
-  - [環境變量](#環境變量)
-  - [獲取 OpenAI API Key](#獲取-openai-api-key)
-    - [`A` 通過 OpenAI 官方渠道](#a-通過-openai-官方渠道)
-    - [`B` 通過 OpenAI 第三方代理商](#b-通過-openai-第三方代理商)
- [📦 生態系統](#-生態系統)
- [🧩 插件體系](#-插件體系)
- [⌨️ 本地開發](#️-本地開發)
- [🤝 參與貢獻](#-參與貢獻)
- [❤ 社區贊助](#-社區贊助)
- [🔗 更多工具](#-更多工具)
-
-####
-
-<br/>
-
-</details>
-
-## 👋🏻 開始使用 & 交流
-
-我們是一群充滿熱情的設計工程師，希望為 AIGC 提供現代化的設計組件和工具，並以開源的方式分享。
-透過採用Bootstrapping 的方式，我們的目標是為開發人員和使用者提供一個更加開放、透明和使用者友好的產品生態系統。
-
-LobeHub 旨在成為普通用戶與專業開發者測試 AI 助手的場所。LobeChat 目前正在積極開發中，有任何需求或者問題，歡迎提交 [issues][issues-link]
-
-| [![][vercel-shield-badge]][vercel-link]   | 無需安裝或註冊！訪問我們的網站立刻體驗                                     |
-| :---------------------------------------- | :--------------------------------------------------------------------------- |
-| [![][discord-shield-badge]][discord-link] | 加入我們的 Discord 和開發者交流，和其他用戶們分享心得！ |
-
-> \[!IMPORTANT]
->
-> **收藏項目**，你將從 GitHub 上訂閱所有發佈通知～⭐️
-
-[![][image-star]][github-stars-link]
-
-<details><summary><kbd>收藏圖表</kbd></summary>
-  <picture>
-    <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=lobehub%2Flobe-chat&theme=dark&type=Date">
-    <img src="https://api.star-history.com/svg?repos=lobehub%2Flobe-chat&type=Date">
-  </picture>
-</details>
-
-## ✨ 特性一覽
-
-[![][image-feat-knowledgebase]][docs-feat-knowledgebase]
-
-### `1` [文件上傳 / 知識庫][docs-feat-knowledgebase]
-
-LobeChat 支持文件上傳與知識庫功能，你可以上傳文件、圖片、聲音、影片等多種類型的文件，以及創建知識庫，方便用戶管理和查找文件。同時在對話中使用文件和知識庫功能，實現更加豐富的對話體驗。
-
-<https://github.com/user-attachments/assets/faa8cf67-e743-4590-8bf6-ebf6ccc34175>
-
-> \[!TIP]
->
-> 查閱 [📘 LobeChat 知識庫上線 —— 此刻起，跬步千里](https://lobehub.com/zh/blog/knowledge-base) 瞭解詳情。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-privoder]][docs-feat-provider]
-
-### `2` [多模型服務商支持][docs-feat-provider]
-
-在 LobeChat 的不斷發展過程中，我們深刻意識到在提供 AI 會話服務時，模型服務商的多樣性對於滿足社區需求的重要性。因此，我們拓展了對多種模型服務商的支持，為用戶提供更豐富、多樣化的選擇。
-
-通過這種方式，LobeChat 能夠更靈活地適應不同用戶的需求，同時也為開發者提供了更為廣泛的選擇空間。
-
-#### 已支持的模型服務商
-
-我們已經實現了對以下模型服務商的支持：
-
-<!-- PROVIDER LIST -->
-
- **[OpenAI](https://lobechat.com/discover/provider/openai)**: OpenAI 是全球領先的人工智能研究機構，其開發的模型如 GPT 系列推動了自然語言處理的前沿。OpenAI 致力於通過創新和高效的 AI 解決方案改變多個行業。他們的產品具有顯著的性能和經濟性，廣泛用於研究、商業和創新應用。
- **[Ollama](https://lobechat.com/discover/provider/ollama)**: Ollama 提供的模型廣泛涵蓋代碼生成、數學運算、多語種處理和對話互動等領域，支持企業級和本地化部署的多樣化需求。
- **[Anthropic](https://lobechat.com/discover/provider/anthropic)**: Anthropic 是一家專注於人工智能研究和開發的公司，提供了一系列先進的語言模型，如 Claude 3.5 Sonnet、Claude 3 Sonnet、Claude 3 Opus 和 Claude 3 Haiku。這些模型在智能、速度和成本之間取得了理想的平衡，適用於從企業級工作負載到快速響應的各種應用場景。Claude 3.5 Sonnet 作為其最新模型，在多項評估中表現優異，同時保持了較高的性價比。
- **[Bedrock](https://lobechat.com/discover/provider/bedrock)**: Bedrock 是亞馬遜 AWS 提供的一項服務，專注於為企業提供先進的 AI 語言模型和視覺模型。其模型家族包括 Anthropic 的 Claude 系列、Meta 的 Llama 3.1 系列等，涵蓋從輕量級到高性能的多種選擇，支持文本生成、對話、圖像處理等多種任務，適用於不同規模和需求的企業應用。
- **[Google](https://lobechat.com/discover/provider/google)**: Google 的 Gemini 系列是其最先進、通用的 AI 模型，由 Google DeepMind 打造，專為多模態設計，支持文本、代碼、圖像、聲音和影片的無縫理解與處理。適用於從數據中心到移動設備的多種環境，極大提升了 AI 模型的效率與應用廣泛性。
- **[DeepSeek](https://lobechat.com/discover/provider/deepseek)**: DeepSeek 是一家專注於人工智能技術研究和應用的公司，其最新模型 DeepSeek-V3 多項評測成績超越 Qwen2.5-72B 和 Llama-3.1-405B 等開源模型，性能對齊領軍閉源模型 GPT-4o 與 Claude-3.5-Sonnet。
- **[HuggingFace](https://lobechat.com/discover/provider/huggingface)**: HuggingFace Inference API 提供了一種快速且免費的方式，讓您可以探索成千上萬種模型，適用於各種任務。無論您是在為新應用程序進行原型設計，還是在嘗試機器學習的功能，這個 API 都能讓您即時訪問多個領域的高性能模型。
- **[OpenRouter](https://lobechat.com/discover/provider/openrouter)**: OpenRouter 是一個提供多種前沿大模型接口的服務平台，支持 OpenAI、Anthropic、LLaMA 及更多，適合多樣化的開發和應用需求。用戶可根據自身需求靈活選擇最優的模型和價格，助力 AI 體驗的提升。
- **[Cloudflare Workers AI](https://lobechat.com/discover/provider/cloudflare)**: 在 Cloudflare 的全球網絡上運行由無服務器 GPU 驅動的機器學習模型。
- **[GitHub](https://lobechat.com/discover/provider/github)**: 通過 GitHub 模型，開發人員可以成為 AI 工程師，並使用行業領先的 AI 模型進行構建。
-
-<details><summary><kbd>瀏覽更多供應商 (+26)</kbd></summary>
-
- **[Novita](https://lobechat.com/discover/provider/novita)**: Novita AI 是一個提供多種大語言模型與 AI 圖像生成的 API 服務的平台，靈活、可靠且具有成本效益。它支持 Llama3、Mistral 等最新的開源模型，並為生成式 AI 應用開發提供了全面、用戶友好且自動擴展的 API 解決方案，適合 AI 初創公司的快速發展。
- **[Together AI](https://lobechat.com/discover/provider/togetherai)**: Together AI 致力於通過創新的 AI 模型實現領先的性能，提供廣泛的自定義能力，包括快速擴展支持和直觀的部署流程，滿足企業的各種需求。
- **[Fireworks AI](https://lobechat.com/discover/provider/fireworksai)**: Fireworks AI 是一家領先的高級語言模型服務商，專注於功能調用和多模態處理。其最新模型 Firefunction V2 基於 Llama-3，優化用於函數調用、對話及指令跟隨。視覺語言模型 FireLLaVA-13B 支持圖像和文本混合輸入。其他 notable 模型包括 Llama 系列和 Mixtral 系列，提供高效的多語言指令跟隨與生成支持。
- **[Groq](https://lobechat.com/discover/provider/groq)**: Groq 的 LPU 推理引擎在最新的獨立大語言模型（LLM）基準測試中表現卓越，以其驚人的速度和效率重新定義了 AI 解決方案的標準。Groq 是一種即時推理速度的代表，在基於雲的部署中展現了良好的性能。
- **[Perplexity](https://lobechat.com/discover/provider/perplexity)**: Perplexity 是一家領先的對話生成模型提供商，提供多種先進的 Llama 3.1 模型，支持在線和離線應用，特別適用於複雜的自然語言處理任務。
- **[Mistral](https://lobechat.com/discover/provider/mistral)**: Mistral 提供先進的通用、專業和研究型模型，廣泛應用於複雜推理、多語言任務、代碼生成等領域，通過功能調用接口，用戶可以集成自定義功能，實現特定應用。
- **[Ai21Labs](https://lobechat.com/discover/provider/ai21)**: AI21 Labs 為企業構建基礎模型和人工智能系統，加速生成性人工智能在生產中的應用。
- **[Upstage](https://lobechat.com/discover/provider/upstage)**: Upstage 專注於為各種商業需求開發 AI 模型，包括 Solar LLM 和文檔 AI，旨在實現工作的人造通用智能（AGI）。通過 Chat API 創建簡單的對話代理，並支持功能調用、翻譯、嵌入以及特定領域應用。
- **[xAI](https://lobechat.com/discover/provider/xai)**: xAI 是一家致力於構建人工智能以加速人類科學發現的公司。我們的使命是推動我們對宇宙的共同理解。
- **[Qwen](https://lobechat.com/discover/provider/qwen)**: 通義千問是阿里雲自主研發的超大規模語言模型，具有強大的自然語言理解和生成能力。它可以回答各種問題、創作文字內容、表達觀點看法、撰寫代碼等，在多個領域發揮作用。
- **[Wenxin](https://lobechat.com/discover/provider/wenxin)**: 企業級一站式大模型與 AI 原生應用開發及服務平台，提供最全面易用的生成式人工智能模型開發、應用開發全流程工具鏈
- **[Hunyuan](https://lobechat.com/discover/provider/hunyuan)**: 由騰訊研發的大語言模型，具備強大的中文創作能力，複雜語境下的邏輯推理能力，以及可靠的任務執行能力
- **[Spark](https://lobechat.com/discover/provider/spark)**: 科大訊飛星火大模型提供多領域、多語言的強大 AI 能力，利用先進的自然語言處理技術，構建適用於智能硬件、智慧醫療、智慧金融等多種垂直場景的創新應用。
- **[ZhiPu](https://lobechat.com/discover/provider/zhipu)**: 智譜 AI 提供多模態與語言模型的開放平台，支持廣泛的 AI 應用場景，包括文本處理、圖像理解與編程輔助等。
- **[01.AI](https://lobechat.com/discover/provider/zeroone)**: 零一萬物致力於推動以人為本的 AI 2.0 技術革命，旨在通過大語言模型創造巨大的經濟和社會價值，並開創新的 AI 生態與商業模式。
- **[SenseNova](https://lobechat.com/discover/provider/sensenova)**: 商湯日日新，依託商湯大裝置的強大的基礎支撐，提供高效易用的全棧大模型服務。
- **[Stepfun](https://lobechat.com/discover/provider/stepfun)**: 階級星辰大模型具備行業領先的多模態及複雜推理能力，支持超長文本理解和強大的自主調度搜索引擎功能。
- **[Moonshot](https://lobechat.com/discover/provider/moonshot)**: Moonshot 是由北京月之暗面科技有限公司推出的開源平台，提供多種自然語言處理模型，應用領域廣泛，包括但不限於內容創作、學術研究、智能推薦、醫療診斷等，支持長文本處理和複雜生成任務。
- **[Baichuan](https://lobechat.com/discover/provider/baichuan)**: 百川智能是一家專注於人工智能大模型研發的公司，其模型在國內知識百科、長文本處理和生成創作等中文任務上表現卓越，超越了國外主流模型。百川智能還具備行業領先的多模態能力，在多項權威評測中表現優異。其模型包括 Baichuan 4、Baichuan 3 Turbo 和 Baichuan 3 Turbo 128k 等，分別針對不同應用場景進行優化，提供高性價比的解決方案。
- **[Minimax](https://lobechat.com/discover/provider/minimax)**: MiniMax 是 2021 年成立的通用人工智能科技公司，致力於與用戶共創智能。MiniMax 自主研發了不同模態的通用大模型，其中包括萬億參數的 MoE 文本大模型、語音大模型以及圖像大模型。並推出了海螺 AI 等應用。
- **[360 AI](https://lobechat.com/discover/provider/ai360)**: 360 AI 是 360 公司推出的 AI 模型和服務平台，提供多種先進的自然語言處理模型，包括 360GPT2 Pro、360GPT Pro、360GPT Turbo 和 360GPT Turbo Responsibility 8K。這些模型結合了大規模參數和多模態能力，廣泛應用於文本生成、語義理解、對話系統與代碼生成等領域。通過靈活的定價策略，360 AI 滿足多樣化用戶需求，支持開發者集成，推動智能化應用的革新和發展。
- **[Taichu](https://lobechat.com/discover/provider/taichu)**: 中科院自動化研究所和武漢人工智能研究院推出新一代多模態大模型，支持多輪問答、文本創作、圖像生成、3D 理解、信號分析等全面問答任務，擁有更強的認知、理解、創作能力，帶來全新互動體驗。
- **[InternLM](https://lobechat.com/discover/provider/internlm)**: 致力於大模型研究與開發工具鏈的開源組織。為所有 AI 開發者提供高效、易用的開源平台，讓最前沿的大模型與算法技術觸手可及
- **[SiliconCloud](https://lobechat.com/discover/provider/siliconcloud)**: SiliconCloud，基於優秀開源基礎模型的高性價比 GenAI 雲服務
- **[Higress](https://lobechat.com/discover/provider/higress)**: Higress 是一款雲原生 API 網關，在阿里內部為解決 Tengine reload 對長連接業務有損，以及 gRPC/Dubbo 負載均衡能力不足而誕生。
- **[Gitee AI](https://lobechat.com/discover/provider/giteeai)**: Gitee AI 的 Serverless API 為 AI 開發者提供開箱即用的大模型推理 API 服務。
-
-</details>
-
-> 📊 供應商總數: [<kbd>**36**</kbd>](https://lobechat.com/discover/providers)
-
- <!-- PROVIDER LIST -->
-
-同時，我們也在計劃支持更多的模型服務商，以進一步豐富我們的服務商庫。如果你希望讓 LobeChat 支持你喜愛的服務商，歡迎加入我們的 [💬 社區討論](https://github.com/lobehub/lobe-chat/discussions/1284)。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-local]][docs-feat-local]
-
-### `3` [支持本地大型語言模型 (LLM)][docs-feat-local]
-
-為了滿足特定用戶的需求，LobeChat 還基於 [Ollama](https://ollama.ai) 支持了本地模型的使用，讓用戶能夠更靈活地使用自己的或第三方的模型。
-
-> \[!TIP]
->
-> 查閱 [📘 在 LobeChat 中使用 Ollama][docs-usage-ollama] 獲得更多訊息
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-vision]][docs-feat-vision]
-
-### `4` [模型視覺識別 (Model Visual)][docs-feat-vision]
-
-LobeChat 已經支持 OpenAI 最新的 [`gpt-4-vision`](https://platform.openai.com/docs/guides/vision) 支持視覺識別的模型，這是一個具備視覺識別能力的多模態應用。
-用戶可以輕鬆上傳圖片或者拖拽圖片到對話框中，助手將能夠識別圖片內容，並在此基礎上進行智能對話，構建更智能、更多元化的聊天場景。
-
-這一特性打開了新的互動方式，使得交流不再局限於文字，而是可以涵蓋豐富的視覺元素。無論是日常使用中的圖片分享，還是在特定行業內的圖像解讀，助手都能提供出色的對話體驗。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-tts]][docs-feat-tts]
-
-### `5` [TTS & STT 語音轉化][docs-feat-tts]
-
-LobeChat 支持文字轉語音（Text-to-Speech，TTS）和語音轉文字（Speech-to-Text，STT）技術，這使得我們的應用能夠將文本信息轉化為清晰的語音輸出，用戶可以像與真人交談一樣與我們的對話助手進行交流。
-用戶可以從多種聲音中選擇，給助手搭配合適的音源。 同時，對於那些傾向於聽覺學習或者想要在忙碌中獲取信息的用戶來說，TTS 提供了一個極佳的解決方案。
-
-在 LobeChat 中，我們精心挑選了一系列高品質的聲音選項 (OpenAI Audio, Microsoft Edge Speech)，以滿足不同地域和文化背景用戶的需求。用戶可以根據個人喜好或者特定場景來選擇合適的語音，從而獲得個性化的交流體驗。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-t2i]][docs-feat-t2i]
-
-### `6` [Text to Image 文生圖][docs-feat-t2i]
-
-支持最新的文本到圖片生成技術，LobeChat 現在能夠讓用戶在與助手對話中直接調用文生圖工具進行創作。
-通過利用 [`DALL-E 3`](https://openai.com/dall-e-3)、[`MidJourney`](https://www.midjourney.com/) 和 [`Pollinations`](https://pollinations.ai/) 等 AI 工具的能力， 助手們現在可以將你的想法轉化為圖像。
-同時可以更私密和沈浸式地完成你的創作過程。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-plugin]][docs-feat-plugin]
-
-### `7` [插件系統 (Tools Calling)][docs-feat-plugin]
-
-LobeChat 的插件生態系統是其核心功能的重要擴展，它極大地增強了 ChatGPT 的實用性和靈活性。
-
-<video controls src="https://github.com/lobehub/lobe-chat/assets/28616219/f29475a3-f346-4196-a435-41a6373ab9e2" muted="false"></video>
-
-通過利用插件，ChatGPT 能夠實現實時信息的獲取和處理，例如自動獲取最新新聞頭條，為用戶提供即時且相關的資訊。
-
-此外，這些插件不僅局限於新聞聚合，還可以擴展到其他實用的功能，如快速檢索文檔、生成圖象、獲取電商平台數據，以及其他各式各樣的第三方服務。
-
-> 通過文檔瞭解更多 [📘 插件使用][docs-usage-plugin]
-
-<!-- PLUGIN LIST -->
-
-| 最近新增                                                                                                               | 描述                                                                             |
-| ---------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
-| [MintbaseSearch](https://lobechat.com/discover/plugin/mintbasesearch)<br/><sup>By **mintbase** on **2024-12-31**</sup> | 在 NEAR 協議上查找任何 NFT 數據。<br/>`加密貨幣` `nft`                           |
-| [PortfolioMeta](https://lobechat.com/discover/plugin/StockData)<br/><sup>By **portfoliometa** on **2024-12-22**</sup>  | 分析股票並獲取全面的實時投資數據和分析。<br/>`股票`                              |
-| [谷歌自定義搜索引擎](https://lobechat.com/discover/plugin/google-cse)<br/><sup>By **vsnthdev** on **2024-12-02**</sup> | 通過他們的官方自定義搜索引擎 API 搜索谷歌。<br/>`網絡` `搜索`                    |
-| [Speak](https://lobechat.com/discover/plugin/speak)<br/><sup>By **speak** on **2024-12-02**</sup>                      | 使用 Speak，您的 AI 語言導師，學習如何用另一種語言說任何事情。<br/>`教育` `語言` |
-
-> 📊 Total plugins: [<kbd>**48**</kbd>](https://lobechat.com/discover/plugins)
-
- <!-- PLUGIN LIST -->
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-agent]][docs-feat-agent]
-
-### `8` [助手市集 (GPTs)][docs-feat-agent]
-
-在 LobeChat 的助手市集中，創作者們可以發現一個充滿活力和創新的社區，它匯聚了眾多精心設計的助手，這些助手不僅在工作場景中發揮著重要作用，也在學習過程中提供了極大的便利。
-我們的市集不僅是一個展示平台，更是一個協作的空間。在這裡，每個人都可以貢獻自己的智慧，分享個人開發的助手。
-
-> \[!TIP]
->
-> 通過 [🤖/🏪 提交助手][submit-agents-link] ，你可以輕鬆地將你的助手作品提交到我們的平台。我們特別強調的是，LobeChat 建立了一套精密的自動化國際化（i18n）工作流程， 它的強大之處在於能夠無縫地將你的助手轉化為多種語言版本。
-> 這意味著，不論你的用戶使用何種語言，他們都能無障礙地體驗到你的助手。
-
-> \[!IMPORTANT]
->
-> 我歡迎所有用戶加入這個不斷成長的生態系統，共同參與到助手的迭代與優化中來。共同創造出更多有趣、實用且具有創新性的助手，進一步豐富助手的多樣性和實用性。
-
-<!-- AGENT LIST -->
-
-| 最近新增                                                                                                                                                                | 描述                                                                                      |
-| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
-| [系統指令專家](https://lobechat.com/discover/assistant/instructer)<br/><sup>By **[yuyun2000](https://github.com/yuyun2000)** on **2024-12-04**</sup>                    | 擅長精煉與生成高效系統指令<br/>`系統指令` `寫作` `細節優化` `用戶需求`                    |
-| [日語幫助記憶師](https://lobechat.com/discover/assistant/japan-language-helper)<br/><sup>By **[sharkbear212](https://github.com/sharkbear212)** on **2024-12-04**</sup> | 擅長日語五十音，平假名，片假名，單詞和短語解釋與記憶技巧<br/>`解釋` `記憶技巧` `日語教學` |
-| [詩詞卡片設計師](https://lobechat.com/discover/assistant/poetry-card-designer)<br/><sup>By **[lianxin255](https://github.com/lianxin255)** on **2024-12-03**</sup>      | 擅長設計詩詞卡片，提升藝術感與吸引力<br/>`詩詞卡片設計` `卡片` `創意` `藝術表現`          |
-| [日常醫生](https://lobechat.com/discover/assistant/yunchat-docter)<br/><sup>By **[yuyun2000](https://github.com/yuyun2000)** on **2024-11-30**</sup>                    | 擅長外科診療與個性化健康管理<br/>`全科醫學` `外科` `健康咨詢` `個性化治療` `醫學教育`     |
-
-> 📊 助手總數: [<kbd>**453**</kbd> ](https://lobechat.com/discover/assistants)
-
- <!-- AGENT LIST -->
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-database]][docs-feat-database]
-
-### `9` [支持本地 / 遠程數據庫][docs-feat-database]
-
-LobeChat 支持同時使用服務端數據庫和本地數據庫。根據您的需求，您可以選擇合適的部署方案：
-
- 本地數據庫：適合希望對數據有更多掌控感和隱私保護的用戶。LobeChat 採用了 CRDT (Conflict-Free Replicated Data Type) 技術，實現了多端同步功能。這是一項實驗性功能，旨在提供無縫的數據同步體驗。
- 服務端數據庫：適合希望更便捷使用體驗的用戶。LobeChat 支持 PostgreSQL 作為服務端數據庫。關於如何配置服務端數據庫的詳細文檔，請前往 [配置服務端數據庫](https://lobehub.com/zh/docs/self-hosting/advanced/server-database)。
-
-無論您選擇哪種數據庫，LobeChat 都能為您提供卓越的用戶體驗。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-auth]][docs-feat-auth]
-
-### `10` [支持多用戶管理][docs-feat-auth]
-
-LobeChat 支持多用戶管理，提供了兩種主要的用戶認證和管理方案，以滿足不同需求：
-
- **next-auth**：LobeChat 集成了 `next-auth`，一個靈活且強大的身份驗證庫，支持多種身份驗證方式，包括 OAuth、郵件登錄、憑證登錄等。通過 `next-auth`，您可以輕鬆實現用戶的註冊、登錄、會話管理以及社交登錄等功能，確保用戶數據的安全性和隱私性。
-
- [**Clerk**](https://go.clerk.com/exgqLG0)：對於需要更高級用戶管理功能的用戶，LobeChat 還支持 `Clerk`，一個現代化的用戶管理平台。`Clerk` 提供了更豐富的功能，如多因素認證 (MFA)、白名單、用戶管理、登錄活動監控等。通過 `Clerk`，您可以獲得更高的安全性和靈活性，輕鬆應對生產級的用戶管理需求。
-
-您可以根據自己的需求，選擇合適的用戶管理方案。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-pwa]][docs-feat-pwa]
-
-### `11` [漸進式 Web 應用 (PWA)][docs-feat-pwa]
-
-我們深知在當今多設備環境下為用戶提供無縫體驗的重要性。為此，我們採用了漸進式 Web 應用 [PWA](https://support.google.com/chrome/answer/9658361) 技術，
-這是一種能夠將網頁應用提升至接近原生應用體驗的現代 Web 技術。通過 PWA，LobeChat 能夠在桌面和移動設備上提供高度優化的用戶體驗，同時保持輕量級和高性能的特點。
-在視覺和感覺上，我們也經過精心設計，以確保它的界面與原生應用無差別，提供流暢的動畫、響應式佈局和適配不同設備的屏幕分辨率。
-
-> \[!NOTE]
->
-> 若您未熟悉 PWA 的安裝過程，您可以按照以下步驟將 LobeChat 添加為您的桌面應用（也適用於移動設備）：
->
-> - 在電腦上運行 Chrome 或 Edge 瀏覽器 .
-> - 訪問 LobeChat 網頁 .
-> - 在地址欄的右上角，單擊 <kbd>安裝</kbd> 圖標 .
-> - 根據屏幕上的指示完成 PWA 的安裝 .
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-mobile]][docs-feat-mobile]
-
-### `12` [移動設備適配][docs-feat-mobile]
-
-針對移動設備進行了一系列的優化設計，以提升用戶的移動體驗。目前，我們正在對移動端的用戶體驗進行版本迭代，以實現更加流暢和直觀的交互。如果您有任何建議或想法，我們非常歡迎您通過 GitHub Issues 或者 Pull Requests 提供反饋。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-[![][image-feat-theme]][docs-feat-theme]
-
-### `13` [自定義主題][docs-feat-theme]
-
-作為設計工程師出身，LobeChat 在界面設計上充分考慮用戶的個性化體驗，因此引入了靈活多變的主題模式，其中包括日間的亮色模式和夜間的深色模式。
-除了主題模式的切換，還提供了一系列的顏色定制選項，允許用戶根據自己的喜好來調整應用的主題色彩。無論是想要沈穩的深藍，還是希望活潑的桃粉，或者是專業的灰白，用戶都能夠在 LobeChat 中找到匹配自己風格的顏色選擇。
-
-> \[!TIP]
->
-> 默認配置能夠智能地識別用戶系統的顏色模式，自動進行主題切換，以確保應用界面與操作系統保持一致的視覺體驗。對於喜歡手動調控細節的用戶，LobeChat 同樣提供了直觀的設置選項，針對聊天場景也提供了對話氣泡模式和文檔模式的選擇。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-### 更多特性
-
-除了上述功能特性以外，LobeChat 所具有的設計和技術能力將為你帶來更多使用保障：
-
- [x] 💎 **精緻 UI 設計**：經過精心設計的界面，具有優雅的外觀和流暢的交互效果，支持亮暗色主題，適配移動端。支持 PWA，提供更加接近原生應用的體驗。
- [x] 🗣️ **流暢的對話體驗**：流式響應帶來流暢的對話體驗，並且支持完整的 Markdown 渲染，包括代碼高亮、LaTex 公式、Mermaid 流程圖等。
- [x] 💨 **快速部署**：使用 Vercel 平台或者我們的 Docker 鏡像，只需點擊一鍵部署按鈕，即可在 1 分鐘內完成部署，無需複雜的配置過程。
- [x] 🔒 **隱私安全**：所有數據保存在用戶瀏覽器本地，保證用戶的隱私安全。
- [x] 🌐 **自定義域名**：如果用戶擁有自己的域名，可以將其綁定到平台上，方便在任何地方快速訪問對話助手。
-
-> ✨ 隨著產品迭代持續更新，我們將會帶來更多更多令人激動的功能！
-
---
-
-> \[!NOTE]
->
-> 你可以在 Projects 中找到我們後續的 [Roadmap][github-project-link] 計劃
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-## ⚡️ 性能測試
-
-> \[!NOTE]
->
-> 完整測試報告可見 [📘 Lighthouse 性能測試][docs-lighthouse]
-
-|                    Desktop                    |                    Mobile                    |
-| :-------------------------------------------: | :------------------------------------------: |
-|               ![][chat-desktop]               |               ![][chat-mobile]               |
-| [📑 Lighthouse 測試報告][chat-desktop-report] | [📑 Lighthouse 測試報告][chat-mobile-report] |
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-## 🛳 開箱即用
-
-LobeChat 提供了 Vercel 的 自托管版本 和 [Docker 鏡像][docker-release-link]，這使你可以在幾分鐘內構建自己的聊天機器人，無需任何基礎知識。
-
-> \[!TIP]
->
-> 完整教程請查閱 [📘 構建屬於自己的 Lobe Chat][docs-self-hosting]
-
-### `A` 使用 Vercel、Zeabur 、Sealos 或 Alibaba Cloud 部署
-
-如果想在 Vercel 、 Zeabur 或 阿里雲 上部署該服務，可以按照以下步驟進行操作：
-
- 準備好你的 [OpenAI API Key](https://platform.openai.com/account/api-keys) 。
- 點擊下方按鈕開始部署： 直接使用 GitHub 賬號登錄即可，記得在環境變量頁填入 `OPENAI_API_KEY` （必填） and `ACCESS_CODE`（推薦）；
- 部署完畢後，即可開始使用；
- 綁定自定義域名（可選）：Vercel 分配的域名 DNS 在某些區域被污染了，綁定自定義域名即可直連。目前 Zeabur 提供的域名還未被污染，大多數地區都可以直連。
-
-<div align="center">
-
-|            使用 Vercel 部署             |                      使用 Zeabur 部署                       |                      使用 Sealos 部署                       |                           使用 Alibaba Cloud 部署                            |
-| :-------------------------------------: | :---------------------------------------------------------: | :---------------------------------------------------------: | :-----------------------------------------------------------------------: |
-| [![][deploy-button-image]][deploy-link] | [![][deploy-on-zeabur-button-image]][deploy-on-zeabur-link] | [![][deploy-on-sealos-button-image]][deploy-on-sealos-link] | [![][deploy-on-alibaba-cloud-button-image]][deploy-on-alibaba-cloud-link] |
-
-</div>
-
-#### Fork 之後
-
-在 Fork 後，請只保留 "upstream sync" Action 並在你 fork 的 GitHub Repo 中禁用其他 Action。
-
-#### 保持更新
-
-如果你根據 README 中的一鍵部署步驟部署了自己的項目，你可能會發現總是被提示 “有可用更新”。這是因為 Vercel 默認為你創建新項目而非 fork 本項目，這將導致無法準確檢測更新。
-
-> \[!TIP]
->
-> 我們建議按照 [📘 自動同步更新][docs-upstream-sync] 步驟重新部署。
-
-<br/>
-
-### `B` 使用 Docker 部署
-
-[![][docker-release-shield]][docker-release-link]
-[![][docker-size-shield]][docker-size-link]
-[![][docker-pulls-shield]][docker-pulls-link]
-
-我們提供了 Docker 鏡像，供你在自己的個人設備上部署 LobeChat 服務。使用以下命令即可使用一鍵啓動 LobeChat 服務：
-
-```fish
-$ docker run -d -p 3210:3210 \
-  -e OPENAI_API_KEY=sk-xxxx \
-  -e ACCESS_CODE=lobe66 \
-  --name lobe-chat \
-  lobehub/lobe-chat
-```
-
-> \[!TIP]
->
-> 如果你需要通過代理使用 OpenAI 服務，你可以使用 `OPENAI_PROXY_URL` 環境變量來配置代理地址：
-
-```fish
-$ docker run -d -p 3210:3210 \
-  -e OPENAI_API_KEY=sk-xxxx \
-  -e OPENAI_PROXY_URL=https://api-proxy.com/v1 \
-  -e ACCESS_CODE=lobe66 \
-  --name lobe-chat \
-  lobehub/lobe-chat
-```
-
-> \[!NOTE]
->
-> 有關 Docker 部署的詳細說明，詳見 [📘 使用 Docker 部署][docs-docker]
-
-<br/>
-
-### 環境變量
-
-本項目提供了一些額外的配置項，使用環境變量進行設置：
-
-| 環境變量            | 類型 | 描述                                                                                                                          | 示例                                                                                                   |
-| ------------------- | ---- | ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
-| `OPENAI_API_KEY`    | 必選 | 這是你在 OpenAI 賬戶頁面申請的 API 密鑰                                                                                       | `sk-xxxxxx...xxxxxx`                                                                                   |
-| `OPENAI_PROXY_URL`  | 可選 | 如果你手動配置了 OpenAI 接口代理，可以使用此配置項來覆蓋默認的 OpenAI API 請求基礎 URL                                        | `https://api.chatanywhere.cn` 或 `https://aihubmix.com/v1`<br/>默認值:<br/>`https://api.openai.com/v1` |
-| `ACCESS_CODE`       | 可選 | 添加訪問此服務的密碼，你可以設置一個長密碼以防被爆破，該值用逗號分隔時為密碼數組                                              | `awCTe)re_r74` or `rtrt_ewee3@09!` or `code1,code2,code3`                                              |
-| `OPENAI_MODEL_LIST` | 可選 | 用來控制模型列表，使用 `+` 增加一個模型，使用 `-` 來隱藏一個模型，使用 `模型名=展示名` 來自定義模型的展示名，用英文逗號隔開。 | `qwen-7b-chat,+glm-6b,-gpt-3.5-turbo`                                                                  |
-
-> \[!NOTE]
->
-> 完整環境變量可見 [📘 環境變量][docs-env-var]
-
-<br/>
-
-### 獲取 OpenAI API Key
-
-API Key 是使用 LobeChat 進行大語言模型會話的必要信息，本節以 OpenAI 模型服務商為例，簡要介紹獲取 API Key 的方式。
-
-#### `A` 通過 OpenAI 官方渠道
-
- 註冊一個 [OpenAI 賬戶](https://platform.openai.com/signup)，你需要使用國際手機號、非大陸郵箱進行註冊；
- 註冊完畢後，前往 [API Keys](https://platform.openai.com/api-keys) 頁面，點擊 `Create new secret key` 創建新的 API Key:
-
-| 步驟 1：打開創建窗口                                                                                                                               | 步驟 2：創建 API Key                                                                                                                               | 步驟 3：獲取 API Key                                                                                                                               |
-| -------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <img src="https://github-production-user-asset-6210df.s3.amazonaws.com/28616219/296253192-ff2193dd-f125-4e58-82e8-91bc376c0d68.png" height="200"/> | <img src="https://github-production-user-asset-6210df.s3.amazonaws.com/28616219/296254170-803bacf0-4471-4171-ae79-0eab08d621d1.png" height="200"/> | <img src="https://github-production-user-asset-6210df.s3.amazonaws.com/28616219/296255167-f2745f2b-f083-4ba8-bc78-9b558e0002de.png" height="200"/> |
-
- 將此 API Key 填寫到 LobeChat 的 API Key 配置中，即可開始使用。
-
-> \[!TIP]
->
-> 賬戶註冊後，一般有 5 美元的免費額度，但有效期只有三個月。
-> 如果你希望長期使用你的 API Key，你需要完成支付的信用卡綁定。由於 OpenAI 只支持外幣信用卡，因此你需要找到合適的支付渠道，此處不再詳細展開。
-
-<br/>
-
-#### `B` 通過 OpenAI 第三方代理商
-
-如果你發現註冊 OpenAI 賬戶或者綁定外幣信用卡比較麻煩，可以考慮借助一些知名的 OpenAI 第三方代理商來獲取 API Key，這可以有效降低獲取 OpenAI API Key 的門檻。但與此同時，一旦使用三方服務，你可能也需要承擔潛在的風險，
-請根據你自己的實際情況自行決策。以下是常見的第三方模型代理商列表，供你參考：
-
-|                                                                                                                                                   | 服務商       | 特性說明                                                        | Proxy 代理地址            | 鏈接                            |
-| ------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | --------------------------------------------------------------- | ------------------------- | ------------------------------- |
-| <img src="https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/296272721-c3ac0bf3-e433-4496-89c4-ebdc20689c17.jpg" width="48" /> | **AiHubMix** | 使用 OpenAI 企業接口，全站模型價格為官方 **86 折**（含 GPT-4 ） | `https://aihubmix.com/v1` | [獲取](https://lobe.li/XHnZIUP) |
-
-> \[!WARNING]
->
-> **免責申明**: 在此推薦的 OpenAI API Key 由第三方代理商提供，所以我們不對 API Key 的 **有效性** 和 **安全性** 負責，請你自行承擔購買和使用 API Key 的風險。
-
-> \[!NOTE]
->
-> 如果你是模型服務商，並認為自己的服務足夠穩定且價格實惠，歡迎聯繫我們，我們會在自行體驗和測試後酌情推薦。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-## 📦 生態系統
-
-| NPM                               | 倉庫                                    | 描述                                                                                     | 版本                                      |
-| --------------------------------- | --------------------------------------- | ---------------------------------------------------------------------------------------- | ----------------------------------------- |
-| [@lobehub/ui][lobe-ui-link]       | [lobehub/lobe-ui][lobe-ui-github]       | 構建 AIGC 網頁應用程序而設計的開源 UI 組件庫                                             | [![][lobe-ui-shield]][lobe-ui-link]       |
-| [@lobehub/icons][lobe-icons-link] | [lobehub/lobe-icons][lobe-icons-github] | 主流 AI / LLM 模型和公司 SVG Logo 與 Icon 合集                                           | [![][lobe-icons-shield]][lobe-icons-link] |
-| [@lobehub/tts][lobe-tts-link]     | [lobehub/lobe-tts][lobe-tts-github]     | AI TTS / STT 語音合成 / 識別 React Hooks 庫                                              | [![][lobe-tts-shield]][lobe-tts-link]     |
-| [@lobehub/lint][lobe-lint-link]   | [lobehub/lobe-lint][lobe-lint-github]   | LobeHub 代碼樣式規範 ESlint，Stylelint，Commitlint，Prettier，Remark 和 Semantic Release | [![][lobe-lint-shield]][lobe-lint-link]   |
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-## 🧩 插件體系
-
-插件提供了擴展 LobeChat [Function Calling][docs-functionc-call] 能力的方法。可以用於引入新的 Function Calling，甚至是新的消息結果渲染方式。如果你對插件開發感興趣，請在 Wiki 中查閱我們的 [📘 插件開發指引][docs-plugin-dev] 。
-
- [lobe-chat-plugins][lobe-chat-plugins]：插件索引從該倉庫的 index.json 中獲取插件列表並顯示給用戶。
- [chat-plugin-template][chat-plugin-template]：插件開發模版，你可以通過項目模版快速新建插件項目。
- [@lobehub/chat-plugin-sdk][chat-plugin-sdk]：插件 SDK 可幫助您創建出色的 Lobe Chat 插件。
- [@lobehub/chat-plugins-gateway][chat-plugins-gateway]：插件網關是一個後端服務，作為 LobeChat 插件的網關。我們使用 Vercel 部署此服務。主要的 API POST /api/v1/runner 被部署為 Edge Function。
-
-> \[!NOTE]
->
-> 插件系統目前正在進行重大開發。您可以在以下 Issues 中瞭解更多信息:
->
-> - [x] [**插件一期**](https://github.com/lobehub/lobe-chat/issues/73): 實現插件與主體分離，將插件拆分為獨立倉庫維護，並實現插件的動態加載
-> - [x] [**插件二期**](https://github.com/lobehub/lobe-chat/issues/97): 插件的安全性與使用的穩定性，更加精准地呈現異常狀態，插件架構的可維護性與開發者友好
-> - [x] [**插件三期**](https://github.com/lobehub/lobe-chat/issues/149)：更高階與完善的自定義能力，支持插件鑒權與示例
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-## ⌨️ 本地開發
-
-可以使用 GitHub Codespaces 進行在線開發：
-
-[![][codespaces-shield]][codespaces-link]
-
-或者使用以下命令進行本地開發：
-
-```fish
-$ git clone https://github.com/lobehub/lobe-chat.git
-$ cd lobe-chat
-$ pnpm install
-$ pnpm run dev
-```
-
-如果你希望瞭解更多詳情，歡迎可以查閱我們的 [📘 開發指南][docs-dev-guide]
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-## 🤝 參與貢獻
-
-我們非常歡迎各種形式的貢獻。如果你對貢獻代碼感興趣，可以查看我們的 GitHub [Issues][github-issues-link] 和 [Projects][github-project-link]，大展身手，向我們展示你的奇思妙想。
-
-> \[!TIP]
->
-> 我們希望創建一個技術分享型社區，一個可以促進知識共享、想法交流，激發彼此鼓勵和協作的環境。
-> 同時歡迎聯繫我們提供產品功能和使用體驗反饋，幫助我們將 LobeChat 建設得更好。
->
-> **組織維護者:** [@arvinxx](https://github.com/arvinxx) [@canisminor1990](https://github.com/canisminor1990)
-
-[![][pr-welcome-shield]][pr-welcome-link]
-[![][submit-agents-shield]][submit-agents-link]
-[![][submit-plugin-shield]][submit-plugin-link]
-
-<a href="https://github.com/lobehub/lobe-chat/graphs/contributors" target="_blank">
-  <table>
-    <tr>
-      <th colspan="2">
-        <br><img src="https://contrib.rocks/image?repo=lobehub/lobe-chat"><br><br>
-      </th>
-    </tr>
-    <tr>
-      <td>
-        <picture>
-          <source media="(prefers-color-scheme: dark)" srcset="https://next.ossinsight.io/widgets/official/compose-org-active-contributors/thumbnail.png?activity=active&period=past_28_days&owner_id=131470832&repo_ids=643445235&image_size=2x3&color_scheme=dark">
-          <img src="https://next.ossinsight.io/widgets/official/compose-org-active-contributors/thumbnail.png?activity=active&period=past_28_days&owner_id=131470832&repo_ids=643445235&image_size=2x3&color_scheme=light">
-        </picture>
-      </td>
-      <td rowspan="2">
-        <picture>
-          <source media="(prefers-color-scheme: dark)" srcset="https://next.ossinsight.io/widgets/official/compose-org-participants-growth/thumbnail.png?activity=active&period=past_28_days&owner_id=131470832&repo_ids=643445235&image_size=4x7&color_scheme=dark">
-          <img src="https://next.ossinsight.io/widgets/official/compose-org-participants-growth/thumbnail.png?activity=active&period=past_28_days&owner_id=131470832&repo_ids=643445235&image_size=4x7&color_scheme=light">
-        </picture>
-      </td>
-    </tr>
-    <tr>
-      <td>
-        <picture>
-          <source media="(prefers-color-scheme: dark)" srcset="https://next.ossinsight.io/widgets/official/compose-org-active-contributors/thumbnail.png?activity=new&period=past_28_days&owner_id=131470832&repo_ids=643445235&image_size=2x3&color_scheme=dark">
-          <img src="https://next.ossinsight.io/widgets/official/compose-org-active-contributors/thumbnail.png?activity=new&period=past_28_days&owner_id=131470832&repo_ids=643445235&image_size=2x3&color_scheme=light">
-        </picture>
-      </td>
-    </tr>
-  </table>
-</a>
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-## ❤ 社區贊助
-
-每一分支持都珍貴無比，匯聚成我們支持的璀璨銀河！你就像一顆划破夜空的流星，瞬間點亮我們前行的道路。感謝你對我們的信任 —— 你的支持筆就像星辰導航，一次又一次地為項目指明前進的光芒。
-
-<a href="https://opencollective.com/lobehub" target="_blank">
-  <picture>
-    <source media="(prefers-color-scheme: dark)" srcset="https://github.com/lobehub/.github/blob/main/static/sponsor-dark.png?raw=true">
-    <img  src="https://github.com/lobehub/.github/blob/main/static/sponsor-light.png?raw=true">
-  </picture>
-</a>
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
-## 🔗 更多工具
-
- **[🅰️ Lobe SD Theme][lobe-theme]:** Stable Diffusion WebUI 的現代主題，精緻的界面設計，高度可定制的 UI，以及提高效率的功能。
- **[⛵️ Lobe Midjourney WebUI][lobe-midjourney-webui]:** Midjourney WebUI, 能夠根據文本提示快速生成豐富多樣的圖像，激發創造力，增強對話交流。
- **[🌏 Lobe i18n][lobe-i18n]:** Lobe i18n 是一個由 ChatGPT 驅動的 i18n（國際化）翻譯過程的自動化工具。它支持自動分割大文件、增量更新，以及為 OpenAI 模型、API 代理和溫度提供定制選項的功能。
- **[💌 Lobe Commit][lobe-commit]:** Lobe Commit 是一個 CLI 工具，它利用 Langchain/ChatGPT 生成基於 Gitmoji 的提交消息。
-
-<div align="right">
-
-[![][back-to-top]](#readme-top)
-
-</div>
-
---
-
-<details><summary><h4>📝 許可證</h4></summary>
-
-[![][fossa-license-shield]][fossa-license-link]
-
-</details>
-
-Copyright © 2023 [LobeHub][profile-link]. <br />
-This project is [Apache 2.0](./LICENSE) licensed.
-
-<!-- LINK GROUP -->
-
-[back-to-top]: https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square
-[blog]: https://lobehub.com/zh/blog
-[changelog]: https://lobehub.com/changelog
-[chat-desktop]: https://raw.githubusercontent.com/lobehub/lobe-chat/lighthouse/lighthouse/chat/desktop/pagespeed.svg
-[chat-desktop-report]: https://lobehub.github.io/lobe-chat/lighthouse/chat/desktop/chat_preview_lobehub_com_chat.html
-[chat-mobile]: https://raw.githubusercontent.com/lobehub/lobe-chat/lighthouse/lighthouse/chat/mobile/pagespeed.svg
-[chat-mobile-report]: https://lobehub.github.io/lobe-chat/lighthouse/chat/mobile/chat_preview_lobehub_com_chat.html
-[chat-plugin-sdk]: https://github.com/lobehub/chat-plugin-sdk
-[chat-plugin-template]: https://github.com/lobehub/chat-plugin-template
-[chat-plugins-gateway]: https://github.com/lobehub/chat-plugins-gateway
-[codecov-link]: https://codecov.io/gh/lobehub/lobe-chat
-[codecov-shield]: https://img.shields.io/codecov/c/github/lobehub/lobe-chat?labelColor=black&style=flat-square&logo=codecov&logoColor=white
-[codespaces-link]: https://codespaces.new/lobehub/lobe-chat
-[codespaces-shield]: https://github.com/codespaces/badge.svg
-[deploy-button-image]: https://vercel.com/button
-[deploy-link]: https://vercel.com/new/clone?repository-url=https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat&env=OPENAI_API_KEY,ACCESS_CODE&envDescription=Find%20your%20OpenAI%20API%20Key%20by%20click%20the%20right%20Learn%20More%20button.%20%7C%20Access%20Code%20can%20protect%20your%20website&envLink=https%3A%2F%2Fplatform.openai.com%2Faccount%2Fapi-keys&project-name=lobe-chat&repository-name=lobe-chat
-[deploy-on-alibaba-cloud-button-image]: https://service-info-public.oss-cn-hangzhou.aliyuncs.com/computenest-en.svg
-[deploy-on-alibaba-cloud-link]: https://computenest.console.aliyun.com/service/instance/create/default?type=user&ServiceName=LobeChat%E7%A4%BE%E5%8C%BA%E7%89%88
-[deploy-on-sealos-button-image]: https://raw.githubusercontent.com/labring-actions/templates/main/Deploy-on-Sealos.svg
-[deploy-on-sealos-link]: https://cloud.sealos.io/?openapp=system-template%3FtemplateName%3Dlobe-chat
-[deploy-on-zeabur-button-image]: https://zeabur.com/button.svg
-[deploy-on-zeabur-link]: https://zeabur.com/templates/VZGGTI
-[discord-link]: https://discord.gg/AYFPHvv2jT
-[discord-shield]: https://img.shields.io/discord/1127171173982154893?color=5865F2&label=discord&labelColor=black&logo=discord&logoColor=white&style=flat-square
-[discord-shield-badge]: https://img.shields.io/discord/1127171173982154893?color=5865F2&label=discord&labelColor=black&logo=discord&logoColor=white&style=for-the-badge
-[docker-pulls-link]: https://hub.docker.com/r/lobehub/lobe-chat
-[docker-pulls-shield]: https://img.shields.io/docker/pulls/lobehub/lobe-chat?color=45cc11&labelColor=black&style=flat-square
-[docker-release-link]: https://hub.docker.com/r/lobehub/lobe-chat
-[docker-release-shield]: https://img.shields.io/docker/v/lobehub/lobe-chat?color=369eff&label=docker&labelColor=black&logo=docker&logoColor=white&style=flat-square
-[docker-size-link]: https://hub.docker.com/r/lobehub/lobe-chat
-[docker-size-shield]: https://img.shields.io/docker/image-size/lobehub/lobe-chat?color=369eff&labelColor=black&style=flat-square
-[docs]: https://lobehub.com/zh/docs/usage/start
-[docs-dev-guide]: https://github.com/lobehub/lobe-chat/wiki/index
-[docs-docker]: https://lobehub.com/docs/self-hosting/platform/docker
-[docs-env-var]: https://lobehub.com/docs/self-hosting/environment-variables
-[docs-feat-agent]: https://lobehub.com/docs/usage/features/agent-market
-[docs-feat-auth]: https://lobehub.com/docs/usage/features/auth
-[docs-feat-database]: https://lobehub.com/docs/usage/features/database
-[docs-feat-knowledgebase]: https://lobehub.com/blog/knowledge-base
-[docs-feat-local]: https://lobehub.com/docs/usage/features/local-llm
-[docs-feat-mobile]: https://lobehub.com/docs/usage/features/mobile
-[docs-feat-plugin]: https://lobehub.com/docs/usage/features/plugin-system
-[docs-feat-provider]: https://lobehub.com/docs/usage/features/multi-ai-providers
-[docs-feat-pwa]: https://lobehub.com/docs/usage/features/pwa
-[docs-feat-t2i]: https://lobehub.com/docs/usage/features/text-to-image
-[docs-feat-theme]: https://lobehub.com/docs/usage/features/theme
-[docs-feat-tts]: https://lobehub.com/docs/usage/features/tts
-[docs-feat-vision]: https://lobehub.com/docs/usage/features/vision
-[docs-functionc-call]: https://lobehub.com/zh/blog/openai-function-call
-[docs-lighthouse]: https://github.com/lobehub/lobe-chat/wiki/Lighthouse.zh-CN
-[docs-plugin-dev]: https://lobehub.com/docs/usage/plugins/development
-[docs-self-hosting]: https://lobehub.com/docs/self-hosting/start
-[docs-upstream-sync]: https://lobehub.com/docs/self-hosting/advanced/upstream-sync
-[docs-usage-ollama]: https://lobehub.com/docs/usage/providers/ollama
-[docs-usage-plugin]: https://lobehub.com/docs/usage/plugins/basic
-[fossa-license-link]: https://app.fossa.com/projects/git%2Bgithub.com%2Flobehub%2Flobe-chat
-[fossa-license-shield]: https://app.fossa.com/api/projects/git%2Bgithub.com%2Flobehub%2Flobe-chat.svg?type=large
-[github-action-release-link]: https://github.com/lobehub/lobe-chat/actions/workflows/release.yml
-[github-action-release-shield]: https://img.shields.io/github/actions/workflow/status/lobehub/lobe-chat/release.yml?label=release&labelColor=black&logo=githubactions&logoColor=white&style=flat-square
-[github-action-test-link]: https://github.com/lobehub/lobe-chat/actions/workflows/test.yml
-[github-action-test-shield]: https://img.shields.io/github/actions/workflow/status/lobehub/lobe-chat/test.yml?label=test&labelColor=black&logo=githubactions&logoColor=white&style=flat-square
-[github-contributors-link]: https://github.com/lobehub/lobe-chat/graphs/contributors
-[github-contributors-shield]: https://img.shields.io/github/contributors/lobehub/lobe-chat?color=c4f042&labelColor=black&style=flat-square
-[github-forks-link]: https://github.com/lobehub/lobe-chat/network/members
-[github-forks-shield]: https://img.shields.io/github/forks/lobehub/lobe-chat?color=8ae8ff&labelColor=black&style=flat-square
-[github-hello-shield]: https://abroad.hellogithub.com/v1/widgets/recommend.svg?rid=39701baf5a734cb894ec812248a5655a&claim_uid=HxYvFN34htJzGCD&theme=dark&theme=neutral&theme=dark&theme=neutral
-[github-hello-url]: https://hellogithub.com/repository/39701baf5a734cb894ec812248a5655a
-[github-issues-link]: https://github.com/lobehub/lobe-chat/issues
-[github-issues-shield]: https://img.shields.io/github/issues/lobehub/lobe-chat?color=ff80eb&labelColor=black&style=flat-square
-[github-license-link]: https://github.com/lobehub/lobe-chat/blob/main/LICENSE
-[github-license-shield]: https://img.shields.io/badge/license-apache%202.0-white?labelColor=black&style=flat-square
-[github-project-link]: https://github.com/lobehub/lobe-chat/projects
-[github-release-link]: https://github.com/lobehub/lobe-chat/releases
-[github-release-shield]: https://img.shields.io/github/v/release/lobehub/lobe-chat?color=369eff&labelColor=black&logo=github&style=flat-square
-[github-releasedate-link]: https://github.com/lobehub/lobe-chat/releases
-[github-releasedate-shield]: https://img.shields.io/github/release-date/lobehub/lobe-chat?labelColor=black&style=flat-square
-[github-stars-link]: https://github.com/lobehub/lobe-chat/network/stargazers
-[github-stars-shield]: https://img.shields.io/github/stars/lobehub/lobe-chat?color=ffcb47&labelColor=black&style=flat-square
-[github-trending-shield]: https://trendshift.io/api/badge/repositories/2256
-[github-trending-url]: https://trendshift.io/repositories/2256
-[image-banner]: https://github.com/lobehub/lobe-chat/assets/28616219/9f155dff-4737-429f-9cad-a70a1a860c5f
-[image-feat-agent]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/268670869-f1ffbf66-42b6-42cf-a937-9ce1f8328514.png
-[image-feat-auth]: https://github.com/lobehub/lobe-chat/assets/17870709/8ce70e15-40df-451e-b700-66090fe5b8c2
-[image-feat-database]: https://github.com/lobehub/lobe-chat/assets/17870709/c27a0234-a4e9-40e5-8bcb-42d5ce7e40f9
-[image-feat-knowledgebase]: https://github.com/user-attachments/assets/77e58e1c-c82f-4341-b159-f4eeede9967f
-[image-feat-local]: https://github.com/lobehub/lobe-chat/assets/28616219/ca9a21bc-ea6c-4c90-bf4a-fa53b4fb2b5c
-[image-feat-mobile]: https://gw.alipayobjects.com/zos/kitchen/R441AuFS4W/mobile.webp
-[image-feat-plugin]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/268670883-33c43a5c-a512-467e-855c-fa299548cce5.png
-[image-feat-privoder]: https://github.com/lobehub/lobe-chat/assets/28616219/b164bc54-8ba2-4c1e-b2f2-f4d7f7e7a551
-[image-feat-pwa]: https://gw.alipayobjects.com/zos/kitchen/69x6bllkX3/pwa.webp
-[image-feat-t2i]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/297746445-0ff762b9-aa08-4337-afb7-12f932b6efbb.png
-[image-feat-theme]: https://gw.alipayobjects.com/zos/kitchen/pvus1lo%26Z7/darkmode.webp
-[image-feat-tts]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/284072124-c9853d8d-f1b5-44a8-a305-45ebc0f6d19a.png
-[image-feat-vision]: https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/284072129-382bdf30-e3d6-4411-b5a0-249710b8ba08.png
-[image-overview]: https://github.com/lobehub/lobe-chat/assets/17870709/56b95d48-f573-41cd-8b38-387bf88bc4bf
-[image-star]: https://github.com/lobehub/lobe-chat/assets/17870709/cb06b748-513f-47c2-8740-d876858d7855
-[issues-link]: https://img.shields.io/github/issues/lobehub/lobe-chat.svg?style=flat
-[lobe-chat-plugins]: https://github.com/lobehub/lobe-chat-plugins
-[lobe-commit]: https://github.com/lobehub/lobe-commit/tree/master/packages/lobe-commit
-[lobe-i18n]: https://github.com/lobehub/lobe-commit/tree/master/packages/lobe-i18n
-[lobe-icons-github]: https://github.com/lobehub/lobe-icons
-[lobe-icons-link]: https://www.npmjs.com/package/@lobehub/icons
-[lobe-icons-shield]: https://img.shields.io/npm/v/@lobehub/icons?color=369eff&labelColor=black&logo=npm&logoColor=white&style=flat-square
-[lobe-lint-github]: https://github.com/lobehub/lobe-lint
-[lobe-lint-link]: https://www.npmjs.com/package/@lobehub/lint
-[lobe-lint-shield]: https://img.shields.io/npm/v/@lobehub/lint?color=369eff&labelColor=black&logo=npm&logoColor=white&style=flat-square
-[lobe-midjourney-webui]: https://github.com/lobehub/lobe-midjourney-webui
-[lobe-theme]: https://github.com/lobehub/sd-webui-lobe-theme
-[lobe-tts-github]: https://github.com/lobehub/lobe-tts
-[lobe-tts-link]: https://www.npmjs.com/package/@lobehub/tts
-[lobe-tts-shield]: https://img.shields.io/npm/v/@lobehub/tts?color=369eff&labelColor=black&logo=npm&logoColor=white&style=flat-square
-[lobe-ui-github]: https://github.com/lobehub/lobe-ui
-[lobe-ui-link]: https://www.npmjs.com/package/@lobehub/ui
-[lobe-ui-shield]: https://img.shields.io/npm/v/@lobehub/ui?color=369eff&labelColor=black&logo=npm&logoColor=white&style=flat-square
-[official-site]: https://lobehub.com
-[pr-welcome-link]: https://github.com/lobehub/lobe-chat/pulls
-[pr-welcome-shield]: https://img.shields.io/badge/🤯_pr_welcome-%E2%86%92-ffcb47?labelColor=black&style=for-the-badge
-[profile-link]: https://github.com/lobehub
-[share-mastodon-link]: https://mastodon.social/share?text=Check%20this%20GitHub%20repository%20out%20%F0%9F%A4%AF%20LobeChat%20-%20An%20open-source,%20extensible%20(Function%20Calling),%20high-performance%20chatbot%20framework.%20It%20supports%20one-click%20free%20deployment%20of%20your%20private%20ChatGPT/LLM%20web%20application.%20https://github.com/lobehub/lobe-chat%20#chatbot%20#chatGPT%20#openAI
-[share-mastodon-shield]: https://img.shields.io/badge/-share%20on%20mastodon-black?labelColor=black&logo=mastodon&logoColor=white&style=flat-square
-[share-reddit-link]: https://www.reddit.com/submit?title=%E6%8E%A8%E8%8D%90%E4%B8%80%E4%B8%AA%20GitHub%20%E5%BC%80%E6%BA%90%E9%A1%B9%E7%9B%AE%20%F0%9F%A4%AF%20LobeChat%20-%20%E5%BC%80%E6%BA%90%E7%9A%84%E3%80%81%E5%8F%AF%E6%89%A9%E5%B1%95%E7%9A%84%EF%BC%88Function%20Calling%EF%BC%89%E9%AB%98%E6%80%A7%E8%83%BD%E8%81%8A%E5%A4%A9%E6%9C%BA%E5%99%A8%E4%BA%BA%E6%A1%86%E6%9E%B6%E3%80%82%0A%E5%AE%83%E6%94%AF%E6%8C%81%E4%B8%80%E9%94%AE%E5%85%8D%E8%B4%B9%E9%83%A8%E7%BD%B2%E7%A7%81%E4%BA%BA%20ChatGPT%2FLLM%20%E7%BD%91%E9%A1%B5%E5%BA%94%E7%94%A8%E7%A8%8B%E5%BA%8F%20%23chatbot%20%23chatGPT%20%23openAI&url=https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat
-[share-reddit-shield]: https://img.shields.io/badge/-share%20on%20reddit-black?labelColor=black&logo=reddit&logoColor=white&style=flat-square
-[share-telegram-link]: https://t.me/share/url"?text=%E6%8E%A8%E8%8D%90%E4%B8%80%E4%B8%AA%20GitHub%20%E5%BC%80%E6%BA%90%E9%A1%B9%E7%9B%AE%20%F0%9F%A4%AF%20LobeChat%20-%20%E5%BC%80%E6%BA%90%E7%9A%84%E3%80%81%E5%8F%AF%E6%89%A9%E5%B1%95%E7%9A%84%EF%BC%88Function%20Calling%EF%BC%89%E9%AB%98%E6%80%A7%E8%83%BD%E8%81%8A%E5%A4%A9%E6%9C%BA%E5%99%A8%E4%BA%BA%E6%A1%86%E6%9E%B6%E3%80%82%0A%E5%AE%83%E6%94%AF%E6%8C%81%E4%B8%80%E9%94%AE%E5%85%8D%E8%B4%B9%E9%83%A8%E7%BD%B2%E7%A7%81%E4%BA%BA%20ChatGPT%2FLLM%20%E7%BD%91%E9%A1%B5%E5%BA%94%E7%94%A8%E7%A8%8B%E5%BA%8F%20%23chatbot%20%23chatGPT%20%23openAI&url=https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat
-[share-telegram-shield]: https://img.shields.io/badge/-share%20on%20telegram-black?labelColor=black&logo=telegram&logoColor=white&style=flat-square
-[share-weibo-link]: http://service.weibo.com/share/share.php?sharesource=weibo&title=%E6%8E%A8%E8%8D%90%E4%B8%80%E4%B8%AA%20GitHub%20%E5%BC%80%E6%BA%90%E9%A1%B9%E7%9B%AE%20%F0%9F%A4%AF%20LobeChat%20-%20%E5%BC%80%E6%BA%90%E7%9A%84%E3%80%81%E5%8F%AF%E6%89%A9%E5%B1%95%E7%9A%84%EF%BC%88Function%20Calling%EF%BC%89%E9%AB%98%E6%80%A7%E8%83%BD%E8%81%8A%E5%A4%A9%E6%9C%BA%E5%99%A8%E4%BA%BA%E6%A1%86%E6%9E%B6%E3%80%82%0A%E5%AE%83%E6%94%AF%E6%8C%81%E4%B8%80%E9%94%AE%E5%85%8D%E8%B4%B9%E9%83%A8%E7%BD%B2%E7%A7%81%E4%BA%BA%20ChatGPT%2FLLM%20%E7%BD%91%E9%A1%B5%E5%BA%94%E7%94%A8%E7%A8%8B%E5%BA%8F%20%23chatbot%20%23chatGPT%20%23openAI&url=https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat
-[share-weibo-shield]: https://img.shields.io/badge/-share%20on%20weibo-black?labelColor=black&logo=sinaweibo&logoColor=white&style=flat-square
-[share-whatsapp-link]: https://api.whatsapp.com/send?text=%E6%8E%A8%E8%8D%90%E4%B8%80%E4%B8%AA%20GitHub%20%E5%BC%80%E6%BA%90%E9%A1%B9%E7%9B%AE%20%F0%9F%A4%AF%20LobeChat%20-%20%E5%BC%80%E6%BA%90%E7%9A%84%E3%80%81%E5%8F%AF%E6%89%A9%E5%B1%95%E7%9A%84%EF%BC%88Function%20Calling%EF%BC%89%E9%AB%98%E6%80%A7%E8%83%BD%E8%81%8A%E5%A4%A9%E6%9C%BA%E5%99%A8%E4%BA%BA%E6%A1%86%E6%9E%B6%E3%80%82%0A%E5%AE%83%E6%94%AF%E6%8C%81%E4%B8%80%E9%94%AE%E5%85%8D%E8%B4%B9%E9%83%A8%E7%BD%B2%E7%A7%81%E4%BA%BA%20ChatGPT%2FLLM%20%E7%BD%91%E9%A1%B5%E5%BA%94%E7%94%A8%E7%A8%8B%E5%BA%8F%20https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat%20%23chatbot%20%23chatGPT%20%23openAI
-[share-whatsapp-shield]: https://img.shields.io/badge/-share%20on%20whatsapp-black?labelColor=black&logo=whatsapp&logoColor=white&style=flat-square
-[share-x-link]: https://x.com/intent/tweet?hashtags=chatbot%2CchatGPT%2CopenAI&text=%E6%8E%A8%E8%8D%90%E4%B8%80%E4%B8%AA%20GitHub%20%E5%BC%80%E6%BA%90%E9%A1%B9%E7%9B%AE%20%F0%9F%A4%AF%20LobeChat%20-%20%E5%BC%80%E6%BA%90%E7%9A%84%E3%80%81%E5%8F%AF%E6%89%A9%E5%B1%95%E7%9A%84%EF%BC%88Function%20Calling%EF%BC%89%E9%AB%98%E6%80%A7%E8%83%BD%E8%81%8A%E5%A4%A9%E6%9C%BA%E5%99%A8%E4%BA%BA%E6%A1%86%E6%9E%B6%E3%80%82%0A%E5%AE%83%E6%94%AF%E6%8C%81%E4%B8%80%E9%94%AE%E5%85%8D%E8%B4%B9%E9%83%A8%E7%BD%B2%E7%A7%81%E4%BA%BA%20ChatGPT%2FLLM%20%E7%BD%91%E9%A1%B5%E5%BA%94%E7%94%A8%E7%A8%8B%E5%BA%8F&url=https%3A%2F%2Fgithub.com%2Flobehub%2Flobe-chat
-[share-x-shield]: https://img.shields.io/badge/-share%20on%20x-black?labelColor=black&logo=x&logoColor=white&style=flat-square
-[sponsor-link]: https://opencollective.com/lobehub 'Become ❤ LobeHub Sponsor'
-[sponsor-shield]: https://img.shields.io/badge/-Sponsor%20LobeHub-f04f88?logo=opencollective&logoColor=white&style=flat-square
-[submit-agents-link]: https://github.com/lobehub/lobe-chat-agents
-[submit-agents-shield]: https://img.shields.io/badge/🤖/🏪_submit_agent-%E2%86%92-c4f042?labelColor=black&style=for-the-badge
-[submit-plugin-link]: https://github.com/lobehub/lobe-chat-plugins
-[submit-plugin-shield]: https://img.shields.io/badge/🧩/🏪_submit_plugin-%E2%86%92-95f3d9?labelColor=black&style=for-the-badge
-[vercel-link]: https://chat-preview.lobehub.com
-[vercel-shield]: https://img.shields.io/badge/vercel-online-55b467?labelColor=black&logo=vercel&style=flat-square
-[vercel-shield-badge]: https://img.shields.io/badge/TRY%20LOBECHAT-ONLINE-55b467?labelColor=black&logo=vercel&style=for-the-badge
@@ -0,0 +1,8 @@
+node_modules
+dist
+out
+.DS_Store
+.eslintcache
+*.log*
+standalone
+release
@@ -0,0 +1,32 @@
+const { defineConfig } = require('@lobehub/i18n-cli');
+
+module.exports = defineConfig({
+  entry: 'resources/locales/zh-CN',
+  entryLocale: 'zh-CN',
+  output: 'resources/locales',
+  outputLocales: [
+    'ar',
+    'bg-BG',
+    'zh-TW',
+    'en-US',
+    'ru-RU',
+    'ja-JP',
+    'ko-KR',
+    'fr-FR',
+    'tr-TR',
+    'es-ES',
+    'pt-BR',
+    'de-DE',
+    'it-IT',
+    'nl-NL',
+    'pl-PL',
+    'vi-VN',
+    'fa-IR',
+  ],
+  saveImmediately: true,
+  temperature: 0,
+  modelName: 'gpt-4.1-mini',
+  experimental: {
+    jsonMode: true,
+  },
+});
@@ -0,0 +1,6 @@
+lockfile=false
+shamefully-hoist=true
+ignore-workspace-root-check=true
+
+electron_mirror=https://npmmirror.com/mirrors/electron/
+electron_builder_binaries_mirror=https://npmmirror.com/mirrors/electron-builder-binaries/
--- a/Show More
+++ b/Show More