🔖 chore(release): v1.95.2 [skip ci]

### [Version 1.95.2](https://github.com/jaworldwideorg/OneJA-Bot/compare/v1.95.1...v1.95.2)
<sup>Released on **2025-07-07**</sup>

#### 🐛 Bug Fixes

- **misc**: Change the wrong github checkmodel name, pin `officeparser@5.1.1` to fix server error.

#### 💄 Styles

- **misc**: Files hello pages should scroll.

<br/>

<details>
<summary><kbd>Improvements and Fixes</kbd></summary>

#### What's fixed

* **misc**: Change the wrong github checkmodel name, closes [#8339](https://github.com/jaworldwideorg/OneJA-Bot/issues/8339) ([f07d912](https://github.com/jaworldwideorg/OneJA-Bot/commit/f07d912))
* **misc**: Pin `officeparser@5.1.1` to fix server error, closes [#8354](https://github.com/jaworldwideorg/OneJA-Bot/issues/8354) ([3f4e935](https://github.com/jaworldwideorg/OneJA-Bot/commit/3f4e935))

#### Styles

* **misc**: Files hello pages should scroll, closes [#8340](https://github.com/jaworldwideorg/OneJA-Bot/issues/8340) ([df9b7df](https://github.com/jaworldwideorg/OneJA-Bot/commit/df9b7df))

</details>

<div align="right">

[![](https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square)](#readme-top)

</div>

.claude/commands/dedupe.md

@@ -1,38 +0,0 @@
----
-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
-
----

.claude/prompts/auto-testing.md

@@ -1,228 +0,0 @@
-# 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.

.claude/prompts/issue-triage.md

@@ -1,253 +0,0 @@
-# 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".

.claude/prompts/team-assignment.md

@@ -1,135 +0,0 @@
-# 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.
-```

.claude/prompts/translate-comments.md

@@ -1,89 +0,0 @@
-# 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

.cursor/rules/add-provider-doc.mdc

@@ -1,183 +0,0 @@
----
-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`

.cursor/rules/add-setting-env.mdc

@@ -1,175 +0,0 @@
----
-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
-```
-

.cursor/rules/backend-architecture.mdc

@@ -0,0 +1,100 @@
+---
+description: 
+globs: src/services/**/*,src/database/**/*,src/server/**/*
+alwaysApply: false
+---
+# LobeChat 后端技术架构指南
+
+本指南旨在阐述 LobeChat 项目的后端分层架构，重点介绍各核心目录的职责以及它们之间的协作方式。
+
+## 目录结构映射
+
+```
+src/
+├── server/
+│   ├── routers/          # tRPC API 路由定义
+│   └── services/         # 业务逻辑服务层
+│       └── */impls/      # 平台特定实现
+├── database/
+│   ├── models/           # 数据模型 (单表 CRUD)
+│   ├── repositories/     # 仓库层 (复杂查询/聚合)
+│   └── schemas/          # Drizzle ORM 表定义
+└── services/             # 客户端服务 (调用 tRPC 或直接访问 Model)
+```
+
+## 核心架构分层
+
+LobeChat 的后端设计注重模块化、可测试性和灵活性，以适应不同的运行环境（如浏览器端 PGLite、服务端远程 PostgreSQL 以及 Electron 桌面应用）。
+
+其主要分层如下：
+
+1.  客户端服务层 (`src/services`):
+
+    - 位于 src/services/。
+    - 这是客户端业务逻辑的核心层，负责封装各种业务操作和数据处理逻辑。
+    - 环境适配: 根据不同的运行环境，服务层会选择合适的数据访问方式：
+        - 本地数据库模式: 直接调用 `Model` 层进行数据操作，适用于浏览器 PGLite 和本地 Electron 应用。
+        - 远程数据库模式: 通过 `tRPC` 客户端调用服务端 API，适用于需要云同步的场景。
+    - 类型转换: 对于简单的数据类型转换，直接在此层进行类型断言，如 `this.pluginModel.query() as Promise<LobeTool[]>`
+    - 每个服务模块通常包含 `client.ts`（本地模式）、`server.ts`（远程模式）和 `type.ts`（接口定义）文件，在实现时应该确保本地模式和远程模式业务逻辑实现一致，只是数据库不同。
+
+2.  API 接口层 (`TRPC`):
+
+    - 位于 src/server/routers/
+    - 使用 `tRPC` 构建类型安全的 API。Router 根据运行时环境（如 Edge Functions, Node.js Lambda）进行组织。
+    - 负责接收客户端请求，并将其路由到相应的 `Service` 层进行处理。
+    - 新建 lambda 端点时可以参考 src/server/routers/lambda/\_template.ts
+
+3.  仓库层 (`Repositories`):
+
+    - 位于 src/database/repositories/。
+    - 主要处理复杂的跨表查询和数据聚合逻辑，特别是当需要从多个 `Model` 获取数据并进行组合时。
+    - 与 `Model` 层不同，`Repository` 层专注于复杂的业务查询场景，而不涉及简单的领域模型转换。
+    - 当业务逻辑涉及多表关联、复杂的数据统计或需要事务处理时，会使用 `Repository` 层。
+    - 如果数据操作简单（仅涉及单个 `Model`），则通常直接在 `src/services` 层调用 `Model` 并进行简单的类型断言。
+
+4.  模型层 (`Models`):
+
+    - 位于 src/database/models/ (例如 src/database/models/plugin.ts 和 src/database/models/document.ts)。
+    - 提供对数据库中各个表（由 src/database/schemas/ 中的 Drizzle ORM schema 定义）的基本 CRUD (创建、读取、更新、删除) 操作和简单的查询能力。
+    - `Model` 类专注于单个数据表的直接操作，不涉及复杂的领域模型转换，这些转换通常在上层的 `src/services` 中通过类型断言完成。
+    - model（例如 Topic） 层接口经常需要从对应的 schema 层导入 NewTopic 和 TopicItem
+    - 创建新的 model 时可以参考 src/database/models/\_template.ts
+
+5.  数据库 (`Database`):
+    - 客户端模式 (浏览器/PWA): 使用 PGLite (基于 WASM 的 PostgreSQL)，数据存储在用户浏览器本地。
+    - 服务端模式 (云部署): 使用远程 PostgreSQL 数据库。
+    - Electron 桌面应用:
+        - Electron 客户端会启动一个本地 Node.js 服务。
+        - 本地服务通过 `tRPC` 与 Electron 的渲染进程通信。
+        - 数据库选择依赖于是否开启云同步功能：
+            - 云同步开启: 连接到远程 PostgreSQL 数据库。
+            - 云同步关闭: 使用 PGLite (通过 Node.js 的 WASM 实现) 在本地存储数据。
+
+## 数据流向说明
+
+### 浏览器/PWA 模式
+
+```
+UI (React) → Zustand action -> Client Service → Model Layer → PGLite (本地数据库)
+```
+
+### 服务端模式
+
+```
+UI (React) → Zustand action → Client Service -> TRPC Client → TRPC Routers  → Repositories/Models → Remote PostgreSQL
+```
+
+### Electron 桌面应用模式
+
+```
+UI (Electron Renderer) → Zustand action → Client Service -> TRPC Client → 本地 Node.js 服务 → TRPC Routers → Repositories/Models → PGLite/Remote PostgreSQL (取决于云同步设置)
+```
+
+## 服务层 (Server Services)
+
+-  位于 src/server/services/。
+-  核心职责是封装独立的、可复用的业务逻辑单元。这些服务应易于测试。
+-  平台差异抽象: 一个关键特性是通过其内部的 `impls` 子目录（例如 src/server/services/file/impls 包含 s3.ts 和 local.ts）来抹平不同运行环境带来的差异（例如云端使用 S3 存储，桌面版使用本地文件系统）。这使得上层（如 `tRPC` routers）无需关心底层具体实现。
+-  目标是使 `tRPC` router 层的逻辑尽可能纯粹，专注于请求处理和业务流程编排。
+-  服务可能会调用 `Repository` 层或直接调用 `Model` 层进行数据持久化和检索，也可能调用其他服务。

.cursor/rules/code-review.mdc

@@ -0,0 +1,69 @@
+---
+description: How to code review
+globs: 
+alwaysApply: false
+---
+# Role Description
+
+- You are a senior full-stack engineer skilled in performance optimization, security, and design systems.  
+- You excel at reviewing code and providing constructive feedback.  
+- Your task is to review submitted Git diffs **in Chinese** and return a structured review report.  
+- Review style: concise, direct, focused on what matters most, with actionable suggestions.
+
+## Before the Review
+
+Gather the modified code and context. Please strictly follow the process below:
+
+1. Use `read_file` to read [package.json](mdc:package.json)
+2. Use terminal to run command `git diff HEAD | cat` to obtain the diff and list the changed files. If you recieived empty result, run the same command once more.
+3. Use `read_file` to open each changed file.  
+4. Use `read_file` to read  [rules-attach.mdc](mdc:.cursor/rules/rules-attach.mdc). Even if you think it's unnecessary, you must read it.
+5. combine changed files, step3 and `agent_requestable_workspace_rules`, list the rules which need to read 
+6. Use `read_file` to read the rules list in step 5
+
+## Review
+
+### Code Style
+
+- Ensure JSDoc comments accurately reflect the implementation; update them when needed.  
+- Look for opportunities to simplify or modernize code with the latest JavaScript/TypeScript features.  
+- Prefer `async`/`await` over callbacks or chained `.then` promises.  
+- Use consistent, descriptive naming—avoid obscure abbreviations.  
+- Replace magic numbers or strings with well-named constants.  
+- Use semantically meaningful variable, function, and class names.
+- Ignore purely formatting issues and other autofixable lint problems.
+
+### Code Optimization
+
+- Prefer `for…of` loops to index-based `for` loops when feasible.  
+- Decide whether callbacks should be **debounced** or **throttled**.  
+- Use components from `@lobehub/ui`, Ant Design, or the existing design system instead of raw HTML tags (e.g., `Button` vs. `button`).  
+- reuse npm packages already installed (e.g., `lodash/omit`) rather than reinventing the wheel.  
+- Design for dark mode and mobile responsiveness:  
+  - Use the `antd-style` token system instead of hard-coded colors.  
+  - Select the proper component variants.  
+- Performance considerations:  
+  - Where safe, convert sequential async flows to concurrent ones with `Promise.all`, `Promise.race`, etc.  
+  - Query only the required columns from a database rather than selecting entire rows.
+
+### Obvious Bugs
+
+- Do not silently swallow errors in `catch` blocks; at minimum, log them.  
+- Revert temporary code used only for testing (e.g., debug logs, temporary configs).  
+- Remove empty handlers (e.g., an empty `onClick`).  
+- Confirm the UI degrades gracefully for unauthenticated users.
+
+## After the Review: output
+
+1. Summary
+    - Start with a brief explanation of what the change set does.  
+    - Summarize the changes for each modified file (or logical group).
+2. Comments Issues
+    - List the most critical issues first.  
+    - Use an ordered list, which will be convenient for me to reference later.
+    - For each issue:
+      - Mark severity tag (`❌ Must fix`, `⚠️ Should fix`, `💅 Nitpick`)  
+      - Provode file path to the relevant file.
+      - Provide recommended fix  
+    - End with a **git commit** command, instruct the author to run it.  
+      - We use gitmoji to label commit messages, format: [emoji] <type>(<scope>): <subject>

.cursor/rules/cursor-ux.mdc

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

.cursor/rules/db-migrations.mdc

@@ -1,25 +0,0 @@
----
-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`.

.cursor/rules/debug-usage.mdc

@@ -1,6 +1,6 @@
 ---
-description: 包含添加 console.log 日志请求时
-globs:
+description: 包含添加 debug 日志请求时
+globs: 
 alwaysApply: false
 ---
 # Debug 包使用指南

.cursor/rules/debug.mdc

@@ -0,0 +1,193 @@
+---
+description: Debug 调试指南
+globs: 
+alwaysApply: false
+---
+# Debug 调试指南
+
+## 💡 调试流程概览
+
+当遇到问题时，请按照以下优先级进行处理：
+
+1. **快速判断** - 对于熟悉的错误，直接提供解决方案
+2. **信息收集** - 使用工具搜索相关代码和配置
+3. **网络搜索** - 查找现有解决方案
+4. **定位调试** - 添加日志进行问题定位
+5. **临时方案** - 如果找不到根本解决方案，提供临时解决方案
+6. **解决实施** - 提供可维护的最终解决方案
+
+## 🔍 错误信息分析
+
+### 错误来源识别
+
+错误信息可能来自：
+
+- **Terminal 输出** - 构建、运行时错误
+- **浏览器控制台** - 前端 JavaScript 错误
+- **开发工具** - ESLint、TypeScript、测试框架等
+- **服务器日志** - API、数据库连接等后端错误
+- **截图或文本** - 用户直接提供的错误信息
+
+## 🛠️ 信息收集工具
+
+### 代码搜索工具
+
+使用以下工具收集相关信息，并根据场景选择最合适的工具：
+
+- **`codebase_search` (语义搜索)**
+    - **何时使用**: 当你不确定具体的代码实现，想要寻找相关概念、功能或逻辑时。
+    - **示例**: `查询"文件上传"功能的实现`
+- **`grep_search` (精确/正则搜索)**
+    - **何时使用**: 当你知道要查找的确切字符串、函数名、变量名或一个特定的模式时。
+    - **示例**: `查找所有使用了 'useState' 的地方`
+- **`file_search` (文件搜索)**
+    - **何时使用**: 当你知道文件名的一部分，需要快速定位文件时。
+    - **示例**: `查找 'Button.tsx' 组件`
+- **`read_file` (内容读取)**
+    - **何时使用**: 在定位到具体文件后，用于查看其完整内容和上下文。
+- **`web_search` (网络搜索)**
+    - **何时使用**: 当错误信息可能与第三方库、API 或常见问题相关时，用于获取外部信息。
+
+### 环境与依赖检查
+
+- **检查 `package.json`**: 查看 `scripts` 了解项目如何运行、构建和测试。查看 `dependencies` 和 `devDependencies` 确认库版本，版本冲突有时是问题的根源。
+- **运行测试**: 使用 `ni vitest` 运行单元测试和集成测试，这可以快速定位功能回归或组件错误。
+
+### 项目特定搜索目标
+
+针对 lobe-chat 项目，重点关注：
+
+- **配置文件**: [package.json](mdc:package.json), [next.config.mjs](mdc:next.config.mjs)
+- **核心功能**: `src/features/` 下的相关模块
+- **状态管理**: `src/store/` 下的 Zustand stores
+- **数据库**: `src/database/` 和 `src/migrations/`
+- **类型定义**: `src/types/` 下的类型文件
+- **服务层**: `src/services/` 下的 API 服务
+- **启动流程**: [apps/desktop/src/main/core/App.ts](mdc:apps/desktop/src/main/core/App.ts) - 了解应用启动流程
+
+## 🌐 网络搜索策略
+
+### 搜索顺序优先级
+
+1. **和问题相关的项目的 github issue**
+
+2. **技术社区**
+    - Stack Overflow
+    - GitHub Discussions
+    - Reddit
+
+3. **官方文档**
+    - 使用 `mcp_context7_resolve-library-id` 和 `mcp_context7_get-library-docs` 工具
+    - 查阅官方文档网站
+
+### 搜索关键词策略
+
+- **错误信息**: 完整的错误消息
+- **技术栈**: "Next.js 15" + "error message"
+- **上下文**: 添加功能相关的关键词
+
+## 🔧 问题定位与结构化思考
+
+如果问题比较复杂，我们要按照先定位问题，再解决问题的大方向进行。
+
+### 结构化思考工具
+
+对于复杂或多步骤的调试任务，使用 `mcp_sequential-thinking_sequentialthinking` 工具来结构化思考过程。这有助于：
+
+- **分解问题**: 将大问题拆解成可管理的小步骤。
+- **清晰追踪**: 记录每一步的发现和决策，避免遗漏。
+- **自我修正**: 在过程中评估和调整调试路径。
+
+### 日志调试
+
+在问题产生的路径上添加日志，可以简单使用 `console.log` 或者参考 [debug-usage.mdc](mdc:.cursor/rules/debug-usage.mdc) 使用 `debug` 模块。添加完日志后，请求我运行相关的代码并提供关键输出和错误信息。
+
+### 引导式交互调试
+
+虽然我无法直接操作浏览器开发者工具，但我可以引导你进行交互式调试：
+
+1.  **设置断点**: 我会告诉你可以在哪些关键代码行设置断点。
+2.  **检查变量**: 我会请你在断点处检查特定变量的值或 `props`/`state`。
+3.  **分析调用栈**: 我会请你提供调用栈信息，以帮助理解代码执行流程。
+
+## 💡 临时解决方案策略
+
+当无法找到根本解决方案时，提供临时解决方案：
+
+### 临时方案准则
+
+- **快速修复** - 优先让功能可用
+- **最小修改** - 减少对现有代码的影响
+- **清晰标记** - 明确标注这是临时方案
+- **后续计划** - 说明后续如何找到更好的解决方案
+
+### 临时方案模板
+
+```markdown
+## 临时解决方案 ⚠️
+
+**问题**: [简要描述问题]
+
+**临时修复**:
+[具体的临时修复步骤]
+
+**风险说明**:
+
+- [可能的副作用或限制]
+- [需要注意的事项]
+
+**后续计划**:
+
+- [ ] 深入调研根本原因
+- [ ] 寻找更优雅的解决方案
+- [ ] 监控是否有其他影响
+```
+
+## ✅ 解决方案准则
+
+### 方案质量标准
+
+提供的解决方案应该：
+
+- **✅ 低侵入性** - 最小化对现有代码的修改
+- **✅ 可维护性** - 易于理解和后续维护
+- **✅ 类型安全** - 符合 TypeScript 规范
+- **✅ 最佳实践** - 遵循项目的编码规范
+- **✅ 测试友好** - 便于编写和运行测试
+- **❌ 避免长期 Hack** - 临时方案可以 hack，但要明确标注
+
+### 解决方案模板
+
+```markdown
+## 问题原因
+
+[简要说明问题产生的根本原因]
+
+## 解决方案
+
+[详细的解决步骤]
+
+## 代码修改
+
+[具体的代码变更]
+
+## 验证方法
+
+[如何验证问题已解决]
+
+## 预防措施
+
+[如何避免类似问题再次发生]
+```
+
+## 🔄 迭代调试流程
+
+如果初次解决方案无效：
+
+1.  **重新收集信息** - 基于新的错误信息搜索
+2.  **深入代码分析** - 查看更多相关代码文件
+3.  **运行相关测试** - 编写或运行一个失败的测试来稳定复现问题。
+4.  **扩大搜索范围** - 搜索更广泛的相关问题
+5.  **请求更多日志** - 添加更详细的调试信息
+6.  **提供临时方案** - 如果根本解决方案复杂，先提供临时修复
+7.  **分解问题** - 将复杂问题拆解为更小的子问题

.cursor/rules/define-database-model.mdc

@@ -0,0 +1,8 @@
+---
+description: 
+globs: src/database/models/**/*
+alwaysApply: false
+---
+1. first read [lobe-chat-backend-architecture.mdc](mdc:.cursor/rules/lobe-chat-backend-architecture.mdc)
+2. refer to the [_template.ts](mdc:src/database/models/_template.ts) to create new model
+3. if an operation involves multiple models or complex queries, consider defining it in the `repositories` layer under `src/database/repositories/`

.cursor/rules/group-chat.mdc

@@ -1,35 +0,0 @@
----
-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);
-```

.cursor/rules/i18n.mdc

@@ -1,182 +0,0 @@
----
-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 中导出

.cursor/rules/i18n/i18n-auto-attached.mdc

@@ -0,0 +1,6 @@
+---
+description: 
+globs: src/locales/**/*
+alwaysApply: false
+---
+read [i18n.mdc](mdc:.cursor/rules/i18n/i18n.mdc)

.cursor/rules/i18n/i18n.mdc

@@ -0,0 +1,181 @@
+---
+description: i18n workflow and troubleshooting
+globs: 
+alwaysApply: false
+---
+# LobeChat 国际化指南
+
+## 架构概览
+
+LobeChat 使用 react-i18next 进行国际化，采用良好的命名空间架构：
+
+- 默认语言：中文（zh-CN），作为源语言
+- 支持语言：18 种语言，包括英语、日语、韩语、阿拉伯语等
+- 框架：react-i18next 配合 Next.js app router
+- 翻译自动化：@lobehub/i18n-cli 用于自动翻译，配置文件：.i18nrc.js
+
+## 目录结构
+
+```
+src/locales/
+├── default/           # 源语言文件（zh-CN）
+│   ├── index.ts      # 命名空间导出
+│   ├── common.ts     # 通用翻译
+│   ├── chat.ts       # 聊天相关翻译
+│   ├── setting.ts    # 设置翻译
+│   └── ...           # 其他命名空间文件
+└── resources.ts      # 类型定义和语言配置
+
+locales/               # 翻译文件
+├── en-US/            # 英语翻译
+│   ├── common.json   # 通用翻译
+│   ├── chat.json     # 聊天翻译
+│   ├── setting.json  # 设置翻译
+│   └── ...           # 其他命名空间 JSON 文件
+├── ja-JP/            # 日语翻译
+│   ├── common.json
+│   ├── chat.json
+│   └── ...
+└── ...               # 其他语言文件夹
+```
+
+## 添加新翻译的工作流程
+
+### 1. 添加新的翻译键
+
+第一步：在 src/locales/default 目录下的相应命名空间文件中添加翻译键
+
+```typescript
+// 示例：src/locales/default/common.ts
+export default {
+    // ... 现有键
+    newFeature: {
+        title: "新功能标题",
+        description: "功能描述文案",
+        button: "操作按钮",
+    },
+};
+```
+
+第二步：如果创建新命名空间，需要在 src/locales/default/index.ts 中导出
+
+```typescript
+import newNamespace from "./newNamespace";
+
+const resources = {
+    // ... 现有命名空间
+    newNamespace,
+} as const;
+```
+
+### 2. 翻译过程
+
+开发模式：
+
+一般情况下不需要你帮我跑自动翻译工具，跑一次很久，需要的时候我会自己跑。
+但是为了立马能看到效果，还是需要先翻译 `locales/zh-CN/namespace.json`，不需要翻译其它语言。
+
+生产模式：
+
+```bash
+# 为所有语言生成翻译
+npm run i18n
+```
+
+## 在组件中使用
+
+### 基本用法
+
+```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>
+    );
+};
+```
+
+### 带参数的用法
+
+```tsx
+const { t } = useTranslation("common");
+
+<p>{t("welcome.message", { name: "John" })}</p>;
+
+// 对应的语言文件：
+// welcome: { message: '欢迎 {{name}} 使用!' }
+```
+
+### 多个命名空间
+
+```tsx
+const { t } = useTranslation(['common', 'chat']);
+
+<button>{t('common:save')}</button>
+<span>{t('chat:typing')}</span>
+```
+
+## 类型安全
+
+项目使用 TypeScript 实现类型安全的翻译，类型从 src/locales/resources.ts 自动生成：
+
+```typescript
+import type { DefaultResources, NS, Locales } from "@/locales/resources";
+
+// 可用类型：
+// - NS: 可用命名空间键 ('common' | 'chat' | 'setting' | ...)
+// - Locales: 支持的语言代码 ('en-US' | 'zh-CN' | 'ja-JP' | ...)
+
+const namespace: NS = "common";
+const locale: Locales = "en-US";
+```
+
+## 最佳实践
+
+### 1. 命名空间组织
+
+- common: 共享 UI 元素（按钮、标签、操作）
+- chat: 聊天特定功能
+- setting: 配置和设置
+- error: 错误消息和处理
+- [feature]: 功能特定或页面特定的命名空间
+- components: 可复用组件文案
+
+### 2. 键命名约定
+
+```typescript
+// ✅ 好：层次结构
+export default {
+    modal: {
+        confirm: {
+            title: "确认操作",
+            message: "确定要执行此操作吗？",
+            actions: {
+                confirm: "确认",
+                cancel: "取消",
+            },
+        },
+    },
+};
+
+// ❌ 避免：扁平结构
+export default {
+    modalConfirmTitle: "确认操作",
+    modalConfirmMessage: "确定要执行此操作吗？",
+};
+```
+
+## 故障排除
+
+### 缺少翻译键
+
+- 检查键是否存在于 src/locales/default/namespace.ts 中
+- 确保在组件中正确导入命名空间
+- 确保新命名空间已在 src/locales/default/index.ts 中导出

.cursor/rules/project-introduce.mdc

@@ -1,36 +1,47 @@
 ---
+description: 
+globs: 
 alwaysApply: true
 ---
-
 ## Project Description
 
-You are developing an open-source, modern-design AI chat framework: lobehub(previous lobe-chat).
+You are developing an open-source, modern-design AI chat framework: lobe chat. 
 
-Supported platforms:
+Emoji logo: 🤯 
 
-- 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
+read [package.json](mdc:package.json) to know all npm packages you can use.
+read [folder-structure.mdx](mdc:docs/development/basic/folder-structure.mdx) to learn project structure.
+
+The project uses the following technologies:
+
+- pnpm as package manager
+- Next.js 15 for frontend and backend, using app router instead of pages router
+- react 19, using hooks, functional components, react server components
+- TypeScript programming language
+- antd, @lobehub/ui 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-layout-kit for flex layout
 - react-i18next for i18n
-- zustand for state management
-- nuqs for search params management
-- SWR for data fetch
+- lucide-react, @ant-design/icons for icons
+- @lobehub/icons for AI provider/model logo icon
+- @formkit/auto-animate for react list animation
+- zustand for global state management
+- nuqs for type-safe search params state manager
+- SWR for react data fetch
 - aHooks for react hooks library
-- dayjs for time library
+- dayjs for date and time library
 - lodash-es for utility library
+- fast-deep-equal for deep comparison of JavaScript objects
+- zod for data validation
 - TRPC for type safe backend
-- PGLite for client DB and Neon PostgreSQL for backend DB
+- PGLite for client DB and PostgreSQL for backend DB
 - Drizzle ORM
-- Vitest for testing
+- Vitest for testing, testing-library for react component test
+- Prettier for code formatting
+- ESLint for code linting
+- Cursor AI for code editing and AI coding assistance
+
+Note: All tools and libraries used are the latest versions. The application only needs to be compatible with the latest browsers;

.cursor/rules/project-structure.mdc

@@ -1,122 +0,0 @@
----
-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)

.cursor/rules/react-component.mdc

@@ -3,13 +3,11 @@ 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
 
@@ -22,20 +20,18 @@ import { useTheme } from 'antd-style';
 
 const MyComponent = () => {
   const theme = useTheme();
-
+  
   return (
-    <div
-      style={{
-        color: theme.colorPrimary,
-        backgroundColor: theme.colorBgContainer,
-        padding: theme.padding,
-        borderRadius: theme.borderRadius,
-      }}
-    >
+    <div style={{ 
+      color: theme.colorPrimary,
+      backgroundColor: theme.colorBgContainer,
+      padding: theme.padding,
+      borderRadius: theme.borderRadius
+    }}>
       使用主题 token 的组件
     </div>
   );
-};
+}
 ```
 
 #### 使用 antd-style 的 createStyles
@@ -57,13 +53,13 @@ const useStyles = createStyles(({ css, token }) => {
     content: css`
       font-size: ${token.fontSize}px;
       line-height: ${token.lineHeight};
-    `,
+    `
   };
 });
 
 const Card: FC<CardProps> = ({ title, content }) => {
   const { styles } = useStyles();
-
+  
   return (
     <Flexbox className={styles.container}>
       <div className={styles.title}>{title}</div>
@@ -78,96 +74,80 @@ const Card: FC<CardProps> = ({ title, content }) => {
 请注意使用下面的 token 而不是 css 字面值。可以访问 https://ant.design/docs/react/customize-theme-cn 了解所有 token
 
 - 动画类
-  - token.motionDurationMid
-  - token.motionEaseInOut
+    - token.motionDurationMid
+    - token.motionEaseInOut
 - 包围盒属性
-  - token.paddingSM
-  - token.marginLG
+    - token.paddingSM
+    - token.marginLG
+
 
 ## Lobe UI 包含的组件
 
-- 不知道 `@lobehub/ui` 的组件怎么用，有哪些属性，就自己搜下这个项目其它地方怎么用的，不要瞎猜，大部分组件都是在 antd 的基础上扩展了属性
+- 不知道 @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
+  ActionIcon
+  ActionIconGroup
+  Block
+  Button
+  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
+  Avatar
+  Collapse
+  FileTypeIcon
+  FluentEmoji
+  GuideCard
+  Highlighter
+  Hotkey
+  Image
+  List
+  Markdown
+  MaterialFileTypeIcon
+  Mermaid
+  Segmented
+  Snippet
+  SortableList
+  Tag
+  Tooltip
+  Video
 - Data Entry
-  - AutoComplete
-  - CodeEditor
-  - ColorSwatches
-  - CopyButton
-  - DatePicker
-  - EditableText
-  - EmojiPicker
-  - Form
-  - FormModal
-  - HotkeyInput
-  - ImageSelect
-  - Input
-  - SearchBar
-  - Select
-  - SliderWithInput
-  - ThemeSwitch
+  AutoComplete
+  CodeEditor
+  ColorSwatches
+  CopyButton
+  DatePicker
+  EditableText
+  EmojiPicker
+  Form
+  FormModal
+  HotkeyInput
+  ImageSelect
+  Input
+  SearchBar
+  Select
+  SliderWithInput
+  ThemeSwitch
 - Feedback
-  - Alert
-  - Drawer
-  - Modal
+  Alert
+  Drawer
+  Modal
 - Layout
-  - DraggablePanel
-  - DraggablePanelBody
-  - DraggablePanelContainer
-  - DraggablePanelFooter
-  - DraggablePanelHeader
-  - Footer
-  - Grid
-  - Header
-  - Layout
-  - LayoutFooter
-  - LayoutHeader
-  - LayoutMain
-  - LayoutSidebar
-  - LayoutSidebarInner
-  - LayoutToc
-  - MaskShadow
-  - ScrollShadow
+  DraggablePanel
+  Footer
+  Grid
+  Header
+  Layout
+  MaskShadow
+  ScrollShadow
 - Navigation
-  - Burger
-  - Dropdown
-  - Menu
-  - SideNav
-  - Tabs
-  - Toc
+  Burger
+  Dropdown
+  Menu
+  SideNav
+  Tabs
+  Toc
 - Theme
-  - ConfigProvider
-  - FontLoader
-  - ThemeProvider
+  ConfigProvider
+  FontLoader
+  ThemeProvider

.cursor/rules/rules-attach.mdc

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

.cursor/rules/rules-index.mdc

@@ -1,43 +0,0 @@
----
-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

.cursor/rules/system-role.mdc

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

.cursor/rules/testing-guide.mdc

@@ -0,0 +1,881 @@
+---
+description: 
+globs: *.test.ts,*.test.tsx
+alwaysApply: false
+---
+---
+type: agent-requested
+title: 测试指南 - LobeChat Testing Guide
+description: LobeChat 项目的 Vitest 测试环境配置、运行方式、修复原则指南
+---
+
+# 测试指南 - 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)
+
+- **配置文件**: [vitest.config.server.ts](mdc:vitest.config.server.ts)
+- **环境**: Node.js
+- **数据库**: 真实的 PostgreSQL 数据库
+- **并发限制**: 单线程运行 (`singleFork: true`)
+- **用途**: 测试数据库模型、服务端逻辑、API 端点等
+- **设置文件**: [tests/setup-db.ts](mdc:tests/setup-db.ts)
+
+## 🚀 测试运行命令
+
+### package.json 脚本说明
+
+查看 [package.json](mdc:package.json) 中的测试相关脚本：
+
+```json
+{
+    "test": "npm run test-app && npm run test-server",
+    "test-app": "vitest run --config vitest.config.ts",
+    "test-app:coverage": "vitest run --config vitest.config.ts --coverage",
+    "test-server": "vitest run --config vitest.config.server.ts",
+    "test-server:coverage": "vitest run --config vitest.config.server.ts --coverage"
+}
+```
+
+### 推荐的测试运行方式
+
+#### ✅ 正确的命令格式
+
+```bash
+# 运行所有客户端测试
+npx vitest run --config vitest.config.ts
+
+# 运行所有服务端测试
+npx vitest run --config vitest.config.server.ts
+
+# 运行特定测试文件 (支持模糊匹配)
+npx vitest run --config vitest.config.ts basic
+npx vitest run --config vitest.config.ts user.test.ts
+
+# 运行特定文件的特定行号
+npx vitest run --config vitest.config.ts src/utils/helper.test.ts:25
+npx vitest run --config vitest.config.ts basic/foo.test.ts:10,basic/foo.test.ts:25
+
+# 过滤特定测试用例名称
+npx vitest -t "test case name" --config vitest.config.ts
+
+# 组合使用文件和测试名称过滤
+npx vitest run --config vitest.config.ts filename.test.ts -t "specific test"
+```
+
+#### ❌ 避免的命令格式
+
+```bash
+# ❌ 不要使用 pnpm test xxx (这不是有效的 vitest 命令)
+pnpm test some-file
+
+# ❌ 不要使用裸 vitest (会进入 watch 模式)
+vitest test-file.test.ts
+
+# ❌ 不要混淆测试环境
+npx vitest run --config vitest.config.server.ts client-component.test.ts
+```
+
+### 关键运行参数说明
+
+- **`vitest run`**: 运行一次测试然后退出 (避免 watch 模式)
+- **`vitest`**: 默认进入 watch 模式，持续监听文件变化
+- **`--config`**: 指定配置文件，选择正确的测试环境
+- **`-t`**: 过滤测试用例名称，支持正则表达式
+- **`--coverage`**: 生成测试覆盖率报告
+
+## 🔧 测试修复原则
+
+### 核心原则 ⚠️
+
+1. **充分阅读测试代码**: 在修复测试之前，必须完整理解测试的意图和实现
+2. **测试优先修复**: 如果是测试本身写错了，修改测试而不是实现代码
+3. **专注单一问题**: 只修复指定的测试，不要添加额外测试或功能
+4. **不自作主张**: 不要因为发现其他问题就直接修改，先提出再讨论
+
+### 测试修复流程
+
+```mermaid
+flowchart TD
+    subgraph "阶段一：分析与复现"
+        A[开始：收到测试失败报告] --> B[定位并运行失败的测试];
+        B --> C{是否能在本地复现?};
+        C -->|否| D[检查测试环境/配置/依赖];
+        C -->|是| E[分析：阅读测试代码、错误日志、Git 历史];
+    end
+
+    subgraph "阶段二：诊断与调试"
+        E --> F[建立假设：问题出在测试、代码还是环境?];
+        F --> G["调试：使用 console.log 或 debugger 深入检查"];
+        G --> H{假设是否被证实?};
+        H -->|否, 重新假设| F;
+    end
+
+    subgraph "阶段三：修复与验证"
+        H -->|是| I{确定根本原因};
+        I -->|测试逻辑错误| J[修复测试代码];
+        I -->|实现代码 Bug| K[修复实现代码];
+        I -->|环境/配置问题| L[修复配置或依赖];
+        J --> M[验证修复：重新运行失败的测试];
+        K --> M;
+        L --> M;
+        M --> N{测试是否通过?};
+        N -->|否, 修复无效| F;
+        N -->|是| O[扩大验证：运行当前文件内所有测试];
+        O --> P{是否全部通过?};
+        P -->|否, 引入新问题| F;
+    end
+
+    subgraph "阶段四：总结"
+        P -->|是| Q[完成：撰写修复总结];
+    end
+
+    D --> F;
+```
+
+### 修复完成后的总结
+
+测试修复完成后，应该提供简要说明，包括：
+
+1. **错误原因分析**: 说明测试失败的根本原因
+    - 测试逻辑错误
+    - 实现代码bug
+    - 环境配置问题
+    - 依赖变更导致的问题
+
+2. **修复方法说明**: 简述采用的修复方式
+    - 修改了哪些文件
+    - 采用了什么解决方案
+    - 为什么选择这种修复方式
+
+**示例格式**:
+
+```markdown
+## 测试修复总结
+
+**错误原因**: 测试中的 mock 数据格式与实际 API 返回格式不匹配，导致断言失败。
+
+**修复方法**: 更新了测试文件中的 mock 数据结构，使其与最新的 API 响应格式保持一致。具体修改了 `user.test.ts` 中的 `mockUserData` 对象结构。
+```
+
+## 📂 测试文件组织
+
+### 文件命名约定
+
+- **客户端测试**: `*.test.ts`, `*.test.tsx` (任意位置)
+- **服务端测试**: `src/database/models/**/*.test.ts`, `src/database/server/**/*.test.ts` (限定路径)
+
+### 测试文件组织风格
+
+项目采用 **测试文件与源文件同目录** 的组织风格：
+
+- 测试文件放在对应源文件的同一目录下
+- 命名格式：`原文件名.test.ts` 或 `原文件名.test.tsx`
+
+例如：
+
+```
+src/components/Button/
+├── index.tsx           # 源文件
+└── index.test.tsx      # 测试文件
+```
+
+## 🛠️ 测试调试技巧
+
+### 运行失败测试的步骤
+
+1. **确定测试类型**: 查看文件路径确定使用哪个配置
+2. **运行单个测试**: 使用 `-t` 参数隔离问题
+3. **检查错误日志**: 仔细阅读错误信息和堆栈跟踪
+4. **查看最近修改记录**: 检查相关文件的最近变更情况
+5. **添加调试日志**: 在测试中添加 `console.log` 了解执行流程
+
+### 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 方法是否被正确调用
+
+### 检查最近修改记录 🔍
+
+为了更好地判断测试失败的根本原因，需要**系统性地检查相关文件的修改历史**。这是问题定位的关键步骤。
+
+#### 第一步：确定需要检查的文件范围
+
+1. **测试文件本身**: `path/to/component.test.ts`
+2. **对应的实现文件**: `path/to/component.ts` 或 `path/to/component/index.ts`
+3. **相关依赖文件**: 测试或实现中导入的其他模块
+
+#### 第二步：检查当前工作目录状态
+
+```bash
+# 查看所有未提交的修改状态
+git status
+
+# 重点关注测试文件和实现文件是否有未提交的修改
+git status | grep -E "(test|spec)"
+```
+
+#### 第三步：检查未提交的修改内容
+
+```bash
+# 查看测试文件的未提交修改 (工作区 vs 暂存区)
+git diff path/to/component.test.ts | cat
+
+# 查看对应实现文件的未提交修改
+git diff path/to/component.ts | cat
+
+# 查看已暂存但未提交的修改
+git diff --cached path/to/component.test.ts | cat
+git diff --cached path/to/component.ts | cat
+```
+
+#### 第四步：检查提交历史和时间相关性
+
+**首先查看提交时间，判断修改的时效性**：
+
+```bash
+# 查看测试文件的最近提交历史，包含提交时间
+git log --pretty=format:"%h %ad %s" --date=relative -5 path/to/component.test.ts | cat
+
+# 查看实现文件的最近提交历史，包含提交时间
+git log --pretty=format:"%h %ad %s" --date=relative -5 path/to/component.ts | cat
+
+# 查看详细的提交时间（ISO格式，便于精确判断）
+git log --pretty=format:"%h %ad %an %s" --date=iso -3 path/to/component.ts | cat
+git log --pretty=format:"%h %ad %an %s" --date=iso -3 path/to/component.test.ts | cat
+```
+
+**判断提交的参考价值**：
+
+1. **最近提交（24小时内）**: 🔴 **高度相关** - 很可能是导致测试失败的直接原因
+2. **近期提交（1-7天内）**: 🟡 **中等相关** - 可能相关，需要仔细分析修改内容
+3. **较早提交（超过1周）**: ⚪ **低相关性** - 除非是重大重构，否则不太可能是直接原因
+
+#### 第五步：基于时间相关性查看具体修改内容
+
+**根据提交时间的远近，优先查看最近的修改**：
+
+```bash
+# 如果有24小时内的提交，重点查看这些修改
+git show HEAD -- path/to/component.test.ts | cat
+git show HEAD -- path/to/component.ts | cat
+
+# 查看次新的提交（如果最新提交时间较远）
+git show HEAD~1 -- path/to/component.ts | cat
+git show <recent-commit-hash> -- path/to/component.ts | cat
+
+# 对比最近两次提交的差异
+git diff HEAD~1 HEAD -- path/to/component.ts | cat
+```
+
+#### 第六步：分析修改与测试失败的关系
+
+基于修改记录和时间相关性判断：
+
+1. **最近修改了实现代码**:
+
+    ```bash
+    # 重点检查实现逻辑的变化
+    git diff HEAD~1 path/to/component.ts | cat
+    ```
+
+    - 很可能是实现代码的变更导致测试失败
+    - 检查实现逻辑是否正确
+    - 确认测试是否需要相应更新
+
+2. **最近修改了测试代码**:
+
+    ```bash
+    # 重点检查测试逻辑的变化
+    git diff HEAD~1 path/to/component.test.ts | cat
+    ```
+
+    - 可能是测试本身写错了
+    - 检查测试逻辑和断言是否正确
+    - 确认测试是否符合实现的预期行为
+
+3. **两者都有最近修改**:
+
+    ```bash
+    # 对比两个文件的修改时间
+    git log --pretty=format:"%ad %f" --date=iso -1 path/to/component.ts | cat
+    git log --pretty=format:"%ad %f" --date=iso -1 path/to/component.test.ts | cat
+    ```
+
+    - 需要综合分析两者的修改
+    - 确定哪个修改更可能导致问题
+    - 优先检查时间更近的修改
+
+4. **都没有最近修改**:
+    - 可能是依赖变更或环境问题
+    - 检查 `package.json`、配置文件等的修改
+    - 查看是否有全局性的代码重构
+
+#### 修改记录检查示例
+
+```bash
+# 完整的检查流程示例
+echo "=== 检查文件修改状态 ==="
+git status | grep component
+
+echo "=== 检查未提交修改 ==="
+git diff src/components/Button/index.test.tsx | cat
+git diff src/components/Button/index.tsx | cat
+
+echo "=== 检查提交历史和时间 ==="
+git log --pretty=format:"%h %ad %s" --date=relative -3 src/components/Button/index.test.tsx | cat
+git log --pretty=format:"%h %ad %s" --date=relative -3 src/components/Button/index.tsx | cat
+
+echo "=== 根据时间优先级查看修改内容 ==="
+# 如果有24小时内的提交，重点查看
+git show HEAD -- src/components/Button/index.tsx | cat
+```
+
+## 🗃️ 数据库 Model 测试指南
+
+### 测试环境选择 💡
+
+数据库 Model 层通过环境变量控制数据库类型，在两种测试环境下有不同的数据库后端：客户端环境 (PGLite) 和 服务端环境 (PostgreSQL)
+
+### ⚠️ 双环境验证要求
+
+**对于所有 Model 测试，必须在两个环境下都验证通过**：
+
+#### 完整验证流程
+
+```bash
+# 1. 先在客户端环境测试（快速验证）
+npx vitest run --config vitest.config.ts src/database/models/__tests__/myModel.test.ts
+
+# 2. 再在服务端环境测试（兼容性验证）
+npx vitest run --config vitest.config.server.ts 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 { NewGenerationBatch, NewGeneration } 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 方法都必须包含用户权限检查，且必须有对应的安全测试来验证这些检查的有效性**。
+
+## 🎯 总结
+
+修复测试时，记住以下关键点：
+
+- **使用正确的命令**: `npx vitest run --config [config-file]`
+- **理解测试意图**: 先读懂测试再修复
+- **查看最近修改**: 检查相关文件的 git 修改记录，判断问题根源
+- **选择正确环境**: 客户端测试用 `vitest.config.ts`，服务端用 `vitest.config.server.ts`
+- **专注单一问题**: 只修复当前的测试失败
+- **验证修复结果**: 确保修复后测试通过且无副作用
+- **提供修复总结**: 说明错误原因和修复方法
+- **Model 测试安全第一**: 必须包含用户权限检查和对应的安全测试
+- **Model 双环境验证**: 必须在 PGLite 和 PostgreSQL 两个环境下都验证通过

.cursor/rules/testing-guide/db-model-test.mdc

@@ -1,455 +0,0 @@
----
-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 方法都必须包含用户权限检查，且必须有对应的安全测试来验证这些检查的有效性**。

.cursor/rules/testing-guide/electron-ipc-test.mdc

@@ -1,80 +0,0 @@
----
-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 方法是否被正确调用

.cursor/rules/testing-guide/testing-guide.mdc

@@ -1,510 +0,0 @@
----
-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 测试必须包含权限检查，并在双环境下验证通过

.cursor/rules/testing-guide/zustand-store-action-test.mdc

@@ -1,579 +0,0 @@
----
-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)

.cursor/rules/typescript.mdc

@@ -1,58 +1,19 @@
 ---
-description: TypeScript code style and optimization guidelines
+description: 
 globs: *.ts,*.tsx,*.mts
 alwaysApply: false
 ---
 
-# TypeScript Code Style Guide
+TypeScript Code Style Guide:
 
-## Types and Type Safety
-
-- avoid explicit type annotations when TypeScript can infer types.
-- avoid 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.
+- Avoid explicit type annotations when TypeScript can infer types.
+- Avoid defining `any` type variables (e.g., `let a: number;` instead of `let a;`).
+- Use the most accurate type possible (e.g., use `Record<PropertyKey, unknown>` instead of `object`).
+- Prefer `interface` over `type` (e.g., define react component props).
+- Use `as const satisfies XyzInterface` instead of `as const` when suitable
+- import index.ts module(directory module) like `@/db/index` instead of `@/db`
+- Instead of calling Date.now() multiple times, assign it to a constant once and reuse it. This ensures consistency and improves readability
+- Always refactor repeated logic into a reusable function
+- Don't remove meaningful code comments, be sure to keep original comments when providing applied code
+- Update the code comments when needed after you modify the related code
+- Please respect my prettier preferences when you provide code

.devcontainer/devcontainer.json

@@ -1,7 +1,6 @@
 {
+  "image": "mcr.microsoft.com/devcontainers/typescript-node",
   "features": {
-    "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"
+    "ghcr.io/devcontainer-community/devcontainer-features/bun.sh:1": {}
+  }
 }

.env.desktop

@@ -4,5 +4,6 @@ FEATURE_FLAGS=-check_updates,+pin_list
 KEY_VAULTS_SECRET=oLXWIiR/AKF+rWaqy9lHkrYgzpATbW3CtJp3UfkVgpE=
 DATABASE_URL=postgresql://postgres@localhost:5432/postgres
 SEARCH_PROVIDERS=search1api
+NEXT_PUBLIC_SERVICE_MODE='server'
 NEXT_PUBLIC_IS_DESKTOP_APP=1
-NEXT_PUBLIC_ENABLE_NEXT_AUTH=0
+NEXT_PUBLIC_ENABLE_NEXT_AUTH=0

.env.example

@@ -4,25 +4,6 @@
 # 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
 
 ########################################
 ########## AI Provider Service #########
@@ -159,48 +140,6 @@ OPENAI_API_KEY=sk-xxxxxxxxx
 
 # 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 ############
 ########################################
@@ -267,9 +206,6 @@ 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
@@ -284,6 +220,9 @@ 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
 
@@ -293,10 +232,3 @@ OPENAI_API_KEY=sk-xxxxxxxxx
 
 # 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

.env.example.development

@@ -1,120 +0,0 @@
-# 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=...

.eslintignore

@@ -29,20 +29,3 @@ 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/**

.eslintrc.js

@@ -36,16 +36,6 @@ 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;

.github/ISSUE_TEMPLATE/1_bug_report.yml

@@ -5,17 +5,34 @@ type: Bug
 body:
   - type: dropdown
     attributes:
-      label: '📱 Client Type'
-      description: 'Select how you are accessing LobeChat'
+      label: '📦 Platform'
       multiple: true
       options:
-        - 'Web (Desktop Browser)'
-        - 'Web (Mobile Browser)'
-        - 'Desktop App (Electron)'
-        - 'Mobile App (React Native)'
+        - 'Official Preview'
+        - 'Official Cloud'
+        - 'Vercel'
+        - 'Zeabur'
+        - 'Sealos'
+        - 'Netlify'
+        - 'Self hosting Docker'
         - 'Other'
     validations:
       required: true
+  - type: dropdown
+    attributes:
+      label: '📦 Deploymenet 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:
@@ -31,39 +48,6 @@ 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'
@@ -76,49 +60,21 @@ 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

.github/ISSUE_TEMPLATE/1_bug_report_cn.yml

@@ -0,0 +1,87 @@
+name: '🐛 反馈缺陷'
+description: '反馈一个问题缺陷'
+labels: ['unconfirm']
+type: Bug
+body:
+  - type: markdown
+    attributes:
+      value: |
+        在创建新的 Issue 之前，请先[搜索已有问题](https://github.com/lobehub/lobe-chat/issues)，如果发现已有类似的问题，请给它 **👍 点赞**，这样可以帮助我们更快地解决问题。  
+        如果你在使用过程中遇到问题，可以尝试以下方式获取帮助：  
+        - 在 [GitHub Discussions](https://github.com/lobehub/lobe-chat/discussions) 的版块发起讨论。  
+        - 在 [LobeChat 社区](https://discord.gg/AYFPHvv2jT) 提问，与其他用户交流。 
+  - type: dropdown
+    attributes:
+      label: '📦 部署环境'
+      multiple: true
+      options:
+        - 'Official Preview'
+        - 'Official Cloud'
+        - 'Vercel'
+        - 'Zeabur'
+        - 'Sealos'
+        - 'Netlify'
+        - 'Docker'
+        - 'Other'
+    validations:
+      required: true
+  - type: dropdown
+    attributes:
+      label: '📦 部署模式'
+      multiple: true
+      options:
+        - '客户端模式(lobe-chat 镜像)'
+        - '客户端 Pglite 模式(lobe-chat-pglite 镜像)'
+        - '服务端模式(lobe-chat-database 镜像)'
+    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: 如果您的问题需要进一步说明，或者您遇到的问题无法在一个简单的示例中复现，请在这里添加更多信息。

.github/ISSUE_TEMPLATE/2_feature_request_cn.yml

@@ -0,0 +1,21 @@
+name: '🌠 功能需求'
+description: '提出需求或建议'
+title: '[Request] '
+type: Feature
+body:
+  - type: textarea
+    attributes:
+      label: '🥰 需求描述'
+      description: 请添加一个清晰且简洁的问题描述，阐述您希望通过这个功能需求解决的问题。
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: '🧐 解决方案'
+      description: 请清晰且简洁地描述您想要的解决方案。
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: '📝 补充信息'
+      description: 在这里添加关于问题的任何其他背景信息。

.github/ISSUE_TEMPLATE/config.yml

@@ -1,7 +1,7 @@
 contact_links:
-  - name: Ask a question for self-hosting
+  - 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
+    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. | 请在讨论区发布问题和想法。

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,4 +1,4 @@
-#### 💻 Change Type
+#### 💻 变更类型 | Change Type
 
 <!-- For change type, change [ ] to [x]. -->
 
@@ -8,40 +8,13 @@
 - [ ] 💄 style
 - [ ] 👷 build
 - [ ] ⚡️ perf
-- [ ] ✅ test
 - [ ] 📝 docs
 - [ ] 🔨 chore
 
-#### 🔗 Related Issue
-
-<!-- Link to the issue that is fixed by this PR -->
-
-<!-- Example: Fixes #123, Closes #456, Related to #789 -->
-
-#### 🔀 Description of Change
+#### 🔀 变更说明 | Description of Change
 
 <!-- Thank you for your Pull Request. Please provide a description above. -->
 
-#### 🧪 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
+#### 📝 补充信息 | Additional Information
 
 <!-- Add any other context about the Pull Request here. -->
-
-<!-- Breaking changes? Migration guide? Performance impact? -->

.github/scripts/auto-close-duplicates.ts

@@ -1,260 +0,0 @@
-#!/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 {};

.github/scripts/docker-pr-comment.js

@@ -1,89 +0,0 @@
-/**
- * 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 };
-};

.github/scripts/lock-closed-issues.js

@@ -1,78 +0,0 @@
-// @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}`);
-};

.github/scripts/pr-comment.js

@@ -36,19 +36,10 @@ module.exports = async ({ github, context, releaseUrl, version, tag }) => {
       // Generate combined download table
       let assetTable = '| Platform | File | Size |\n| --- | --- | --- |\n';
 
-      // Add macOS assets with architecture detection
+      // Add macOS assets
       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`;
+        assetTable += `| macOS | [${asset.name}](${asset.browser_download_url}) | ${sizeInMB} MB |\n`;
       });
 
       // Add Windows assets

.github/workflows/auto-i18n.yml

@@ -21,12 +21,12 @@ jobs:
           git config --global user.name "lobehubbot"
           git config --global user.email "i@lobehub.com"
 
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v4
         with:
           ref: ${{ github.event.pull_request.head.ref }}
 
       - name: Install bun
-        uses: oven-sh/setup-bun@v2
+        uses: oven-sh/setup-bun@v1
         with:
           bun-version: ${{ secrets.BUN_VERSION }}
 

.github/workflows/claude-auto-testing.yml

@@ -1,73 +0,0 @@
-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.**

.github/workflows/claude-dedupe-issues.yml

@@ -1,33 +0,0 @@
-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 }}'

.github/workflows/claude-issue-triage.yml

@@ -1,65 +0,0 @@
-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 }}

.github/workflows/claude-translate-comments.yml

@@ -1,67 +0,0 @@
-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.**

.github/workflows/claude-translator.yml

@@ -1,121 +0,0 @@
-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

.github/workflows/claude.yml

@@ -1,64 +0,0 @@
-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

.github/workflows/desktop-pr-build.yml

@@ -1,18 +1,16 @@
 name: Desktop PR Build
 
 on:
-  pull_request_target:
+  pull_request:
     types: [synchronize, labeled, unlabeled] # PR 更新或标签变化时触发
 
-# 确保同一 PR 同一时间只运行一个相同的 workflow，取消正在进行的旧的运行
+# 确保同一时间只运行一个相同的 workflow，取消正在进行的旧的运行
 concurrency:
-  group: pr-${{ github.event.pull_request.number }}-${{ github.workflow }}
+  group: ${{ github.ref }}-${{ github.workflow }}
   cancel-in-progress: true
 
 # Add default permissions
-permissions:
-  contents: write
-  pull-requests: write
+permissions: read-all
 
 env:
   PR_TAG_PREFIX: pr- # PR 构建版本的前缀标识
@@ -20,54 +18,52 @@ env:
 jobs:
   test:
     name: Code quality check
-    # 添加 PR label 触发条件，只有添加了 trigger:build-desktop 标签的 PR 才会触发构建
-    if: contains(github.event.pull_request.labels.*.name, 'trigger:build-desktop')
+    # 添加 PR label 触发条件，只有添加了 Build Desktop 标签的 PR 才会触发构建
+    if: contains(github.event.pull_request.labels.*.name, 'Build Desktop')
     runs-on: ubuntu-latest # 只在 ubuntu 上运行一次检查
     steps:
       - name: Checkout base
-        uses: actions/checkout@v5
+        uses: actions/checkout@v4
         with:
           fetch-depth: 0
 
       - name: Setup Node.js
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@v4
         with:
-          node-version: 24
-          package-manager-cache: false
+          node-version: 22
 
-      - name: Install bun
-        uses: oven-sh/setup-bun@v2
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v2
         with:
-          bun-version: 1.2.23
+          version: 9
 
       - name: Install deps
-        run: bun i
+        run: pnpm install
         env:
           NODE_OPTIONS: --max-old-space-size=6144
 
       - name: Lint
-        run: bun run lint
+        run: pnpm 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')
+    if: contains(github.event.pull_request.labels.*.name, 'Build Desktop')
     runs-on: ubuntu-latest
     outputs:
       # 输出版本信息，供后续 job 使用
       version: ${{ steps.set_version.outputs.version }}
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v4
         with:
           fetch-depth: 0
 
       - name: Setup Node.js
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@v4
         with:
-          node-version: 24
-          package-manager-cache: false
+          node-version: 22
 
       # 主要逻辑：确定构建版本号
       - name: Set version
@@ -97,25 +93,24 @@ jobs:
     runs-on: ${{ matrix.os }}
     strategy:
       matrix:
-        os: [macos-latest, macos-15-intel, windows-2025, ubuntu-latest]
+        os: [macos-latest, windows-2025, ubuntu-latest]
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v4
         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
+        uses: actions/setup-node@v4
         with:
-          node-version: 24
-          package-manager-cache: false
+          node-version: 22
+
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v2
+        with:
+          version: 9
 
       # node-linker=hoisted 模式将可以确保 asar 压缩可用
-      - name: Install dependencies
+      - name: Install deps
         run: pnpm install --node-linker=hoisted
 
       - name: Install deps on Desktop
@@ -131,11 +126,11 @@ jobs:
         run: npm run desktop:build
         env:
           # 设置更新通道，PR构建为nightly，否则为stable
-          UPDATE_CHANNEL: "nightly"
+          UPDATE_CHANNEL: 'nightly'
           APP_URL: http://localhost:3015
-          DATABASE_URL: "postgresql://postgres@localhost:5432/postgres"
+          DATABASE_URL: 'postgresql://postgres@localhost:5432/postgres'
           # 默认添加一个加密 SECRET
-          KEY_VAULTS_SECRET: "oLXWIiR/AKF+rWaqy9lHkrYgzpATbW3CtJp3UfkVgpE="
+          KEY_VAULTS_SECRET: 'oLXWIiR/AKF+rWaqy9lHkrYgzpATbW3CtJp3UfkVgpE='
           # macOS 签名和公证配置
           CSC_LINK: ${{ secrets.APPLE_CERTIFICATE_BASE64 }}
           CSC_KEY_PASSWORD: ${{ secrets.APPLE_CERTIFICATE_PASSWORD }}
@@ -154,15 +149,15 @@ jobs:
         run: npm run desktop:build
         env:
           # 设置更新通道，PR构建为nightly，否则为stable
-          UPDATE_CHANNEL: "nightly"
+          UPDATE_CHANNEL: 'nightly'
           APP_URL: http://localhost:3015
-          DATABASE_URL: "postgresql://postgres@localhost:5432/postgres"
-          KEY_VAULTS_SECRET: "oLXWIiR/AKF+rWaqy9lHkrYgzpATbW3CtJp3UfkVgpE="
+          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
+          # 将 TEMP 和 TMP 目录设置到 D 盘
+          TEMP: D:\temp
+          TMP: D:\temp
 
       # Linux 平台构建处理
       - name: Build artifact on Linux
@@ -170,38 +165,16 @@ jobs:
         run: npm run desktop:build
         env:
           # 设置更新通道，PR构建为nightly，否则为stable
-          UPDATE_CHANNEL: "nightly"
+          UPDATE_CHANNEL: 'nightly'
           APP_URL: http://localhost:3015
-          DATABASE_URL: "postgresql://postgres@localhost:5432/postgres"
-          KEY_VAULTS_SECRET: "oLXWIiR/AKF+rWaqy9lHkrYgzpATbW3CtJp3UfkVgpE="
+          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
+        uses: actions/upload-artifact@v4
         with:
           name: release-${{ matrix.os }}
           path: |
@@ -210,70 +183,10 @@ jobs:
             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]
+    needs: [build, version]
     name: Publish PR Build
     runs-on: ubuntu-latest
     # Grant write permissions for creating release and commenting on PR
@@ -283,25 +196,26 @@ jobs:
     outputs:
       artifact_path: ${{ steps.set_path.outputs.path }}
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v4
         with:
           fetch-depth: 0
 
-      # 下载合并后的构建产物
-      - name: Download merged artifacts
-        uses: actions/download-artifact@v6
+      # 下载所有平台的构建产物
+      - name: Download artifacts
+        uses: actions/download-artifact@v4
         with:
-          name: merged-release-pr
           path: release
+          pattern: release-*
+          merge-multiple: true
 
       # 列出所有构建产物
-      - name: List final artifacts
+      - name: List artifacts
         run: ls -R release
 
       # 生成PR发布描述
       - name: Generate PR Release Body
         id: pr_release_body
-        uses: actions/github-script@v8
+        uses: actions/github-script@v7
         with:
           result-encoding: string
           script: |
@@ -331,16 +245,12 @@ jobs:
             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
+        uses: actions/github-script@v7
         with:
           github-token: ${{ secrets.GITHUB_TOKEN }}
           script: |

.github/workflows/docker-database.yml

@@ -0,0 +1,164 @@
+name: Publish Database Docker Image
+
+on:
+  workflow_dispatch:
+  release:
+    types: [published]
+  pull_request:
+    types: [synchronize, labeled, unlabeled]
+
+concurrency:
+  group: ${{ github.ref }}-${{ github.workflow }}
+  cancel-in-progress: true
+
+env:
+  REGISTRY_URL: jaworldwide.azurecr.io
+  REGISTRY_IMAGE: jaworldwide.azurecr.io/oneja/ai/bot-database
+  PR_TAG_PREFIX: pr-
+
+jobs:
+  build:
+    # 添加 PR label 触发条件
+    if: |
+      (github.event_name == 'pull_request' &&
+       contains(github.event.pull_request.labels.*.name, 'Build Docker')) ||
+      github.event_name != 'pull_request'
+
+    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: Prepare
+        run: |
+          platform=${{ matrix.platform }}
+          echo "PLATFORM_PAIR=${platform//\//-}" >> $GITHUB_ENV
+
+      - name: Checkout base
+        uses: actions/checkout@v4
+        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'
+        id: pr_meta
+        run: |
+          branch_name="${{ github.head_ref }}"
+          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' }}
+            # release 构建使用版本号
+            type=semver,pattern={{version}},enable=${{ github.event_name != 'pull_request' }}
+            type=raw,value=latest,enable=${{ github.event_name != 'pull_request' }}
+
+      - name: Docker login
+        uses: docker/login-action@v3
+        with:
+          registry: ${{ env.REGISTRY_URL }}
+          username: ${{ secrets.CONTAINER_REGISTRY_USER }}
+          password: ${{ secrets.CONTAINER_REGISTRY_PASSWORD }}
+
+      - name: Get commit SHA
+        if: github.ref == 'refs/heads/main'
+        id: vars
+        run: echo "sha_short=$(git rev-parse --short HEAD)" >> $GITHUB_OUTPUT
+
+      - name: Build and export
+        id: build
+        uses: docker/build-push-action@v5
+        with:
+          platforms: ${{ matrix.platform }}
+          context: .
+          file: ./Dockerfile.database
+          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@v4
+        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@v4
+        with:
+          fetch-depth: 0
+
+      - name: Download digests
+        uses: actions/download-artifact@v4
+        with:
+          path: /tmp/digests
+          pattern: digest-*
+          merge-multiple: true
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v3
+
+      # 为 merge job 添加 PR metadata 生成
+      - name: Generate PR metadata
+        if: github.event_name == 'pull_request'
+        id: pr_meta
+        run: |
+          branch_name="${{ github.head_ref }}"
+          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: |
+            type=raw,value=${{ env.PR_TAG_PREFIX }}${{ steps.pr_meta.outputs.pr_tag }},enable=${{ github.event_name == 'pull_request' }}
+            type=semver,pattern={{version}},enable=${{ github.event_name != 'pull_request' }}
+            type=raw,value=latest,enable=${{ github.event_name != 'pull_request' }}
+
+      - name: Docker login
+        uses: docker/login-action@v3
+        with:
+          registry: ${{ env.REGISTRY_URL }}
+          username: ${{ secrets.CONTAINER_REGISTRY_USER }}
+          password: ${{ secrets.CONTAINER_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 }}

.github/workflows/docker-pglite.yml

@@ -0,0 +1,161 @@
+name: Publish Docker Pglite Image
+
+on:
+  workflow_dispatch:
+  release:
+    types: [published]
+  pull_request:
+    types: [synchronize, labeled, unlabeled]
+
+concurrency:
+  group: ${{ github.ref }}-${{ github.workflow }}
+  cancel-in-progress: true
+
+env:
+  REGISTRY_IMAGE: lobehub/lobe-chat-pglite
+  PR_TAG_PREFIX: pr-
+
+jobs:
+  build:
+    # 添加 PR label 触发条件
+    if: |
+      (github.event_name == 'pull_request' &&
+       contains(github.event.pull_request.labels.*.name, 'Build Docker')) ||
+      github.event_name != 'pull_request'
+
+    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: Prepare
+        run: |
+          platform=${{ matrix.platform }}
+          echo "PLATFORM_PAIR=${platform//\//-}" >> $GITHUB_ENV
+
+      - name: Checkout base
+        uses: actions/checkout@v4
+        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'
+        id: pr_meta
+        run: |
+          branch_name="${{ github.head_ref }}"
+          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' }}
+            # release 构建使用版本号
+            type=semver,pattern={{version}},enable=${{ github.event_name != 'pull_request' }}
+            type=raw,value=latest,enable=${{ github.event_name != 'pull_request' }}
+
+      - name: Docker login
+        uses: docker/login-action@v3
+        with:
+          username: ${{ secrets.DOCKER_REGISTRY_USER }}
+          password: ${{ secrets.DOCKER_REGISTRY_PASSWORD }}
+
+      - name: Get commit SHA
+        if: github.ref == 'refs/heads/main'
+        id: vars
+        run: echo "sha_short=$(git rev-parse --short HEAD)" >> $GITHUB_OUTPUT
+
+      - name: Build and export
+        id: build
+        uses: docker/build-push-action@v5
+        with:
+          platforms: ${{ matrix.platform }}
+          context: .
+          file: ./Dockerfile.pglite
+          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@v4
+        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@v4
+        with:
+          fetch-depth: 0
+
+      - name: Download digests
+        uses: actions/download-artifact@v4
+        with:
+          path: /tmp/digests
+          pattern: digest-*
+          merge-multiple: true
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v3
+
+      # 为 merge job 添加 PR metadata 生成
+      - name: Generate PR metadata
+        if: github.event_name == 'pull_request'
+        id: pr_meta
+        run: |
+          branch_name="${{ github.head_ref }}"
+          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: |
+            type=raw,value=${{ env.PR_TAG_PREFIX }}${{ steps.pr_meta.outputs.pr_tag }},enable=${{ github.event_name == 'pull_request' }}
+            type=semver,pattern={{version}},enable=${{ github.event_name != 'pull_request' }}
+            type=raw,value=latest,enable=${{ github.event_name != 'pull_request' }}
+
+      - 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 }}

.github/workflows/docker.yml

@@ -1,32 +1,27 @@
 name: Publish Docker Image
-permissions:
-  contents: read
-  pull-requests: write
 
 on:
   workflow_dispatch:
   release:
     types: [published]
-  pull_request_target:
+  pull_request:
     types: [synchronize, labeled, unlabeled]
 
 concurrency:
   group: ${{ github.ref }}-${{ github.workflow }}
-  # PR 构建时取消旧的运行,但 release 构建不取消
-  cancel-in-progress: ${{ github.event_name != 'release' }}
+  cancel-in-progress: true
 
 env:
-  REGISTRY_IMAGE: lobehub/lobehub
+  REGISTRY_IMAGE: lobehub/lobe-chat
   PR_TAG_PREFIX: pr-
 
 jobs:
   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'))
+      (github.event_name == 'pull_request' &&
+       contains(github.event.pull_request.labels.*.name, 'Build Docker')) ||
+      github.event_name != 'pull_request'
 
     strategy:
       matrix:
@@ -44,7 +39,7 @@ jobs:
           echo "PLATFORM_PAIR=${platform//\//-}" >> $GITHUB_ENV
 
       - name: Checkout base
-        uses: actions/checkout@v5
+        uses: actions/checkout@v4
         with:
           fetch-depth: 0
 
@@ -53,12 +48,11 @@ jobs:
 
       # 为 PR 生成特殊的 tag
       - name: Generate PR metadata
-        if: github.event_name == 'pull_request_target'
+        if: github.event_name == 'pull_request'
         id: pr_meta
-        env:
-          BRANCH_NAME: ${{ github.head_ref }}
         run: |
-          sanitized_branch=$(echo "${BRANCH_NAME}" | sed -E 's/[^a-zA-Z0-9_.-]+/-/g')
+          branch_name="${{ github.head_ref }}"
+          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
@@ -68,10 +62,10 @@ jobs:
           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' }}
+            type=raw,value=${{ env.PR_TAG_PREFIX }}${{ steps.pr_meta.outputs.pr_tag }},enable=${{ github.event_name == 'pull_request' }}
             # release 构建使用版本号
-            type=semver,pattern={{version}},enable=${{ github.event_name != 'pull_request_target' }}
-            type=raw,value=latest,enable=${{ github.event_name != 'pull_request_target' }}
+            type=semver,pattern={{version}},enable=${{ github.event_name != 'pull_request' }}
+            type=raw,value=latest,enable=${{ github.event_name != 'pull_request' }}
 
       - name: Docker login
         uses: docker/login-action@v3
@@ -86,7 +80,7 @@ jobs:
 
       - name: Build and export
         id: build
-        uses: docker/build-push-action@v6
+        uses: docker/build-push-action@v5
         with:
           platforms: ${{ matrix.platform }}
           context: .
@@ -104,7 +98,7 @@ jobs:
           touch "/tmp/digests/${digest#sha256:}"
 
       - name: Upload artifact
-        uses: actions/upload-artifact@v5
+        uses: actions/upload-artifact@v4
         with:
           name: digest-${{ env.PLATFORM_PAIR }}
           path: /tmp/digests/*
@@ -117,12 +111,12 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout base
-        uses: actions/checkout@v5
+        uses: actions/checkout@v4
         with:
           fetch-depth: 0
 
       - name: Download digests
-        uses: actions/download-artifact@v6
+        uses: actions/download-artifact@v4
         with:
           path: /tmp/digests
           pattern: digest-*
@@ -133,12 +127,11 @@ jobs:
 
       # 为 merge job 添加 PR metadata 生成
       - name: Generate PR metadata
-        if: github.event_name == 'pull_request_target'
+        if: github.event_name == 'pull_request'
         id: pr_meta
-        env:
-          BRANCH_NAME: ${{ github.head_ref }}
         run: |
-          sanitized_branch=$(echo "${BRANCH_NAME}" | sed -E 's/[^a-zA-Z0-9_.-]+/-/g')
+          branch_name="${{ github.head_ref }}"
+          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
@@ -147,9 +140,9 @@ jobs:
         with:
           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' }}
+            type=raw,value=${{ env.PR_TAG_PREFIX }}${{ steps.pr_meta.outputs.pr_tag }},enable=${{ github.event_name == 'pull_request' }}
+            type=semver,pattern={{version}},enable=${{ github.event_name != 'pull_request' }}
+            type=raw,value=latest,enable=${{ github.event_name != 'pull_request' }}
 
       - name: Docker login
         uses: docker/login-action@v3
@@ -166,21 +159,3 @@ jobs:
       - 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}`);

.github/workflows/e2e.yml

@@ -1,66 +0,0 @@
-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

.github/workflows/issue-auto-close-duplicates.yml

@@ -1,30 +0,0 @@
-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 }}

.github/workflows/issue-auto-comments.yml

@@ -28,7 +28,8 @@ 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.
+            Please make sure you have given us as much context as possible.\
+            非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。
       - name: Auto Comment on Issues Closed
         uses: wow-actions/auto-comment@v1
         with:
@@ -36,7 +37,8 @@ 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:
@@ -46,7 +48,9 @@ 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
@@ -55,7 +59,8 @@ 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.
+            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 消息。
           emoji: 'hooray'
           pr-emoji: '+1, heart'
       - name: Remove inactive

.github/workflows/issue-close-require.yml

@@ -38,7 +38,8 @@ 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.
+            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，若有任何问题，可评论回复。
       - name: need reproduce
         uses: actions-cool/issues-helper@v3
         with:
@@ -49,7 +50,8 @@ 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.
+            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，若有任何问题，可评论回复。
       - name: need reproduce
         uses: actions-cool/issues-helper@v3
         with:
@@ -60,4 +62,5 @@ 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.
+            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，若有任何问题，可评论回复。

.github/workflows/issues-translate.yml

@@ -0,0 +1,14 @@
+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 }}

.github/workflows/lighthouse.yml

@@ -2,7 +2,7 @@ name: Lighthouse Badger
 
 env:
   TOKEN_NAME: 'GH_TOKEN'
-  REPO_BRANCH: 'lobehub/lobe-chat lighthouse'
+  REPO_BRANCH: 'jaworldwideorg/OneJA-Bot lighthouse'
   USER_NAME: 'lobehubbot'
   USER_EMAIL: 'i@lobehub.com'
   AUDIT_TYPE: 'both'
@@ -42,12 +42,12 @@ jobs:
           echo "BRANCH=$BRANCH" >> $GITHUB_ENV
         env:
           REPO_BRANCH: ${{ matrix.REPO_BRANCH || env.REPO_BRANCH }}
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v4
         with:
           repository: ${{ env.REPOSITORY }}
           token: ${{ secrets[matrix.TOKEN_NAME] || secrets[env.TOKEN_NAME] }}
           ref: ${{ env.BRANCH }}
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v4
         with:
           repository: 'myactionway/lighthouse-badges'
           path: temp_lighthouse_badges_nested

.github/workflows/lock-closed-issues.yml

@@ -1,26 +0,0 @@
-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 });

.github/workflows/release-desktop-beta.yml

@@ -15,30 +15,29 @@ permissions: read-all
 jobs:
   test:
     name: Code quality check
-    # 添加 PR label 触发条件，只有添加了 trigger:build-desktop 标签的 PR 才会触发构建
+    # 添加 PR label 触发条件，只有添加了 Build Desktop 标签的 PR 才会触发构建
     runs-on: ubuntu-latest # 只在 ubuntu 上运行一次检查
     steps:
       - name: Checkout base
-        uses: actions/checkout@v5
+        uses: actions/checkout@v4
         with:
           fetch-depth: 0
 
       - name: Setup Node.js
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@v4
         with:
-          node-version: 24
-          package-manager-cache: false
+          node-version: 22
 
-      - name: Install bun
-        uses: oven-sh/setup-bun@v2
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v2
         with:
-          bun-version: 1.2.23
+          version: 9
 
       - name: Install deps
-        run: bun i
+        run: pnpm install
 
       - name: Lint
-        run: bun run lint
+        run: pnpm run lint
 
   version:
     name: Determine version
@@ -48,15 +47,14 @@ jobs:
       version: ${{ steps.set_version.outputs.version }}
       is_pr_build: ${{ steps.set_version.outputs.is_pr_build }}
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v4
         with:
           fetch-depth: 0
 
       - name: Setup Node.js
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@v4
         with:
-          node-version: 24
-          package-manager-cache: false
+          node-version: 22
 
       # 主要逻辑：确定构建版本号
       - name: Set version
@@ -82,25 +80,24 @@ jobs:
     runs-on: ${{ matrix.os }}
     strategy:
       matrix:
-        os: [macos-latest, macos-15-intel, windows-2025, ubuntu-latest]
+        os: [macos-latest, windows-2025, ubuntu-latest]
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v4
         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
+        uses: actions/setup-node@v4
         with:
-          node-version: 24
-          package-manager-cache: false
+          node-version: 22
+
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v2
+        with:
+          version: 9
 
       # node-linker=hoisted 模式将可以确保 asar 压缩可用
-      - name: Install dependencies
+      - name: Install deps
         run: pnpm install --node-linker=hoisted
 
       - name: Install deps on Desktop
@@ -116,9 +113,9 @@ jobs:
         run: npm run desktop:build
         env:
           APP_URL: http://localhost:3015
-          DATABASE_URL: "postgresql://postgres@localhost:5432/postgres"
+          DATABASE_URL: 'postgresql://postgres@localhost:5432/postgres'
           # 默认添加一个加密 SECRET
-          KEY_VAULTS_SECRET: "oLXWIiR/AKF+rWaqy9lHkrYgzpATbW3CtJp3UfkVgpE="
+          KEY_VAULTS_SECRET: 'oLXWIiR/AKF+rWaqy9lHkrYgzpATbW3CtJp3UfkVgpE='
           # macOS 签名和公证配置
           CSC_LINK: ${{ secrets.APPLE_CERTIFICATE_BASE64 }}
           CSC_KEY_PASSWORD: ${{ secrets.APPLE_CERTIFICATE_PASSWORD }}
@@ -137,14 +134,14 @@ jobs:
         run: npm run desktop:build
         env:
           APP_URL: http://localhost:3015
-          DATABASE_URL: "postgresql://postgres@localhost:5432/postgres"
-          KEY_VAULTS_SECRET: "oLXWIiR/AKF+rWaqy9lHkrYgzpATbW3CtJp3UfkVgpE="
+          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
+          # 将 TEMP 和 TMP 目录设置到 D 盘
+          TEMP: D:\temp
+          TMP: D:\temp
 
       # Linux 平台构建处理
       - name: Build artifact on Linux
@@ -152,36 +149,14 @@ jobs:
         run: npm run desktop:build
         env:
           APP_URL: http://localhost:3015
-          DATABASE_URL: "postgresql://postgres@localhost:5432/postgres"
-          KEY_VAULTS_SECRET: "oLXWIiR/AKF+rWaqy9lHkrYgzpATbW3CtJp3UfkVgpE="
+          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 钩子)
+      # 上传构建产物，移除了 zip 相关部分
       - name: Upload artifact
-        uses: actions/upload-artifact@v5
+        uses: actions/upload-artifact@v4
         with:
           name: release-${{ matrix.os }}
           path: |
@@ -190,88 +165,32 @@ jobs:
             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:
+  # 正式版发布 job
+  publish-release:
     needs: [build, version]
-    name: Merge macOS Release Files
+    name: Publish Beta Release
     runs-on: ubuntu-latest
+    # Grant write permission to contents for uploading release assets
     permissions:
       contents: write
+    outputs:
+      artifact_path: ${{ steps.set_path.outputs.path }}
     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
+        uses: actions/download-artifact@v4
         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
+      - name: List artifacts
         run: ls -R release
 
-      # 将构建产物上传到现有 release (现在包含合并后的 latest-mac.yml)
+      # 将构建产物上传到现有 release
       - name: Upload to Release
         uses: softprops/action-gh-release@v1
         with:
@@ -282,9 +201,5 @@ jobs:
             release/*.zip*
             release/*.exe*
             release/*.AppImage
-            release/*.deb*
-            release/*.snap*
-            release/*.rpm*
-            release/*.tar.gz*
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/release.yml

@@ -3,13 +3,13 @@ name: Release CI
 permissions:
   contents: write
   issues: write
-  pull-requests: write
+  actions: write
 
 on:
   push:
     branches:
       - main
-      - next
+  workflow_dispatch:
 
 jobs:
   release:
@@ -18,30 +18,26 @@ jobs:
 
     services:
       postgres:
-        image: paradedb/paradedb:latest
+        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
 
     steps:
-      - uses: actions/checkout@v5
-        with:
-          token: ${{ secrets.GH_TOKEN }}
+      - uses: actions/checkout@v4
 
       - name: Setup Node.js
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@v4
         with:
-          node-version: 24
-          package-manager-cache: false
+          node-version: 22
 
       - name: Install bun
-        uses: oven-sh/setup-bun@v2
+        uses: oven-sh/setup-bun@v1
         with:
-          bun-version: 1.2.23
+          bun-version: ${{ secrets.BUN_VERSION }}
 
       - name: Install deps
         run: bun i
@@ -49,17 +45,18 @@ jobs:
       - name: Lint
         run: bun run lint
 
-      - name: Test Database Coverage
-        run: bun run --filter @lobechat/database test
+      - name: Test Server Coverage
+        run: bun run test-server:coverage
         env:
           DATABASE_TEST_URL: postgresql://postgres:postgres@localhost:5432/postgres
           DATABASE_DRIVER: node
-          KEY_VAULTS_SECRET: Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ=
+          NEXT_PUBLIC_SERVICE_MODE: server
+          KEY_VAULTS_SECRET: LA7n9k3JdEcbSgml2sxfw+4TV1AzaaFU5+R176aQz4s=
           S3_PUBLIC_DOMAIN: https://example.com
           APP_URL: https://home.com
 
-      - name: Test App
-        run: bun run test-app
+      - name: Test App Coverage
+        run: bun run test-app:coverage
 
       - name: Release
         run: bun run release

.github/workflows/sync-database-schema.yml

@@ -1,6 +1,4 @@
 name: Database Schema Visualization CI
-permissions:
-  contents: read
 
 on:
   push:
@@ -13,15 +11,13 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v4
 
-      - name: Install bun
-        uses: oven-sh/setup-bun@v2
-        with:
-          bun-version: ${{ secrets.BUN_VERSION }}
+      - name: Install dbdocs
+        run: sudo npm install -g dbdocs
 
-      - name: Install deps
-        run: bun i
+      - name: Check dbdocs
+        run: dbdocs
 
       - name: sync database schema to dbdocs
         env:

.github/workflows/sync.yml

@@ -9,6 +9,12 @@ on:
   schedule:
     - cron: '0 */6 * * *' # every 6 hours
   workflow_dispatch:
+    inputs:
+      ignore_files:
+        description: 'Files to ignore during sync (comma-separated)'
+        required: false
+        default: 'changelog/*,CHANGELOG.md'
+        type: string
 
 jobs:
   sync_latest_from_upstream:
@@ -17,13 +23,50 @@ jobs:
     if: ${{ github.event.repository.fork }}
 
     steps:
-      - uses: actions/checkout@v5
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
 
       - name: Clean issue notice
         uses: actions-cool/issues-helper@v3
         with:
           actions: 'close-issues'
-          labels: '🚨 Sync Fail'
+          labels: '🚨 Sync Failed'
+
+      - name: Extract ignore files
+        id: extract_ignore
+        run: |
+          # Default files to ignore
+          DEFAULT_IGNORE="Changelog.md"
+
+          # Get input files to ignore or use default
+          if [ "${{ github.event_name }}" == "workflow_dispatch" ]; then
+            IGNORE_FILES="${{ github.event.inputs.ignore_files }}"
+          else
+            IGNORE_FILES="$DEFAULT_IGNORE"
+          fi
+
+          # Convert to array and prepare for output
+          echo "IGNORE_FILES=$IGNORE_FILES" >> $GITHUB_ENV
+          echo "ignore_files=$IGNORE_FILES" >> $GITHUB_OUTPUT
+
+          # Create a backup of files to be preserved
+          mkdir -p .file_backup
+
+          # Process each pattern (comma-separated)
+          for pattern in $(echo $IGNORE_FILES | tr ',' ' '); do
+            # Use find to handle wildcards
+            for file in $(find . -type f -path "./$pattern" 2>/dev/null || echo "$pattern"); do
+              # Skip if the file doesn't exist or if it's the find command returning the pattern
+              if [ -f "$file" ]; then
+                echo "Backing up $file"
+                # Create directory structure in backup
+                mkdir -p ".file_backup/$(dirname "$file")"
+                cp "$file" ".file_backup/$file" || true
+              fi
+            done
+          done
 
       - name: Sync upstream changes
         id: sync
@@ -32,23 +75,58 @@ jobs:
           upstream_sync_repo: lobehub/lobe-chat
           upstream_sync_branch: main
           target_sync_branch: main
-          target_repo_token: ${{ secrets.GITHUB_TOKEN }} # automatically generated, no need to set
+          target_repo_token: ${{ secrets.GITHUB_TOKEN }}
           test_mode: false
 
+      - name: Restore ignored files
+        if: steps.sync.outputs.has_new_commits == 'true'
+        run: |
+          # Process each pattern (comma-separated)
+          for pattern in $(echo $IGNORE_FILES | tr ',' ' '); do
+            # Find all matching files in the backup
+            for file in $(find .file_backup -type f -path ".file_backup/$pattern" 2>/dev/null || find .file_backup -type f -name "$(basename "$pattern")" 2>/dev/null); do
+              # Get the original file path
+              original_file="${file#.file_backup/}"
+              if [ -f "$file" ]; then
+                echo "Restoring $original_file"
+                # Ensure directory exists
+                mkdir -p "$(dirname "$original_file")"
+                cp "$file" "$original_file"
+                git add "$original_file"
+              fi
+            done
+          done
+
+          # Commit the restored files if there are changes
+          if [ -n "$(git status --porcelain)" ]; then
+            git config --local user.email "action@github.com"
+            git config --local user.name "GitHub Action"
+            git commit -m "Restore ignored files after sync: ${{ steps.extract_ignore.outputs.ignore_files }}"
+            git push
+          fi
+
       - name: Sync check
         if: failure()
         uses: actions-cool/issues-helper@v3
         with:
           actions: 'create-issue'
-          title: '🚨 同步失败 | Sync Fail'
-          labels: '🚨 Sync Fail'
+          title: '🚨 Sync Failed'
+          labels: '🚨 Sync Failed'
           body: |
-            Due to a change in the workflow file of the [LobeChat][lobechat] upstream repository, GitHub has automatically suspended the scheduled automatic update. You need to manually sync your fork. Please refer to the detailed [Tutorial][tutorial-en-US] for instructions.
+            Due to a change in the workflow file of the upstream repository, GitHub has automatically suspended the scheduled automatic update. You need to manually sync your fork.
 
-            由于 [LobeChat][lobechat] 上游仓库的 workflow 文件变更，导致 GitHub 自动暂停了本次自动更新，你需要手动 Sync Fork 一次，请查看 [详细教程][tutorial-zh-CN]
+            To manually sync your fork:
+            1. Go to your fork's GitHub page
+            2. Click on "Sync fork" button
+            3. Click on "Update branch"
 
-            ![](https://github-production-user-asset-6210df.s3.amazonaws.com/17870709/273954625-df80c890-0822-4ac2-95e6-c990785cbed5.png)
+            If you encounter any issues, please contact the repository maintainers.
 
-            [lobechat]: https://github.com/lobehub/lobe-chat
-            [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
+      - name: Trigger Release Workflow
+        if: success() && steps.sync.outputs.has_new_commits == 'true'
+        run: |
+          curl -X POST \
+            -H "Authorization: token ${{ secrets.GH_TOKEN }}" \
+            -H "Accept: application/vnd.github.v3+json" \
+            https://api.github.com/repos/${{ github.repository }}/actions/workflows/release.yml/dispatches \
+            -d '{"ref":"main"}'

.github/workflows/test.yml

@@ -2,164 +2,8 @@ name: Test CI
 
 on: [push, pull_request]
 
-permissions:
-  contents: read
-
 jobs:
-  # 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
-
-    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: ${{ secrets.BUN_VERSION }}
-
-      - name: Install deps
-        run: bun i
-
-      - name: Test ${{ matrix.package }} package with coverage
-        run: bun run --filter @lobechat/${{ 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 }}
-
-  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@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
-
+  test:
     runs-on: ubuntu-latest
 
     services:
@@ -170,46 +14,52 @@ jobs:
         options: >-
           --health-cmd pg_isready --health-interval 10s --health-timeout 5s  --health-retries 5
 
+
         ports:
           - 5432:5432
 
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v4
 
       - name: Setup Node.js
-        uses: actions/setup-node@v6
+        uses: actions/setup-node@v4
         with:
-          node-version: 24
-          package-manager-cache: false
+          node-version: 22
 
-      - name: Install pnpm
-        uses: pnpm/action-setup@v4
+      - name: Install bun
+        uses: oven-sh/setup-bun@v1
+        with:
+          bun-version: ${{ secrets.BUN_VERSION }}
 
       - name: Install deps
-        run: pnpm i
+        run: bun i
 
       - name: Lint
-        run: npm run lint
+        run: bun 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
+      - name: Test Server Coverage
+        run: bun run test-server:coverage
         env:
           DATABASE_TEST_URL: postgresql://postgres:postgres@localhost:5432/postgres
           DATABASE_DRIVER: node
-          KEY_VAULTS_SECRET: Kix2wcUONd4CX51E/ZPAd36BqM4wzJgKjPtz2sGztqQ=
+          NEXT_PUBLIC_SERVICE_MODE: server
+          KEY_VAULTS_SECRET: LA7n9k3JdEcbSgml2sxfw+4TV1AzaaFU5+R176aQz4s=
           S3_PUBLIC_DOMAIN: https://example.com
           APP_URL: https://home.com
 
-      - name: Upload Database coverage to Codecov
-        uses: codecov/codecov-action@v5
+      - name: Upload Server coverage to Codecov
+        uses: codecov/codecov-action@v4
         with:
           token: ${{ secrets.CODECOV_TOKEN }}
-          files: ./packages/database/coverage/lcov.info
-          flags: database
+          files: ./coverage/server/lcov.info
+          flags: server
+
+      - name: Test App Coverage
+        run: bun run test-app:coverage
+
+      - name: Upload App Coverage to Codecov
+        uses: codecov/codecov-action@v4
+        with:
+          token: ${{ secrets.CODECOV_TOKEN }}
+          files: ./coverage/app/lcov.info
+          flags: app

.github/workflows/wiki-sync.yml

@@ -0,0 +1,19 @@
+name: Wiki Sync
+
+on:
+  workflow_dispatch:
+  push:
+    paths:
+      - 'docs/wiki/**'
+    branches:
+      - main
+
+jobs:
+  update-wiki:
+    runs-on: ubuntu-latest
+    name: Wiki sync
+    steps:
+      - uses: OrlovM/Wiki-Action@v1
+        with:
+          path: 'docs/wiki'
+          token: ${{ secrets.GH_TOKEN }}

.gitignore

@@ -1,120 +1,73 @@
 # Gitignore for LobeHub
 ################################################################
 
-# System files
+# general
 .DS_Store
-Thumbs.db
-ehthumbs.db
-Desktop.ini
-
-# 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
+.idea
+.vscode
+.history
+.temp
 .env.local
-.env*.local
-.env.development
-venv/
-.venv/
+venv
+temp
+tmp
+.windsurfrules
 
-# Dependencies
-node_modules/
+# dependencies
+node_modules
+*.log
 *.lock
 package-lock.json
-bun.lockb
-.pnpm-store/
 
-# 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/
+# ci
+coverage
+.coverage
 .eslintcache
 .stylelintcache
 
-# Service Worker
+# 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
+
 # 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
+.pnpm-store
 ./packages/lobe-ui
-*.ppt*
-*.doc*
-*.xls*
-
-prd
-GEMINI.md
-e2e/reports

.husky/pre-commit

@@ -1,2 +1,5 @@
-npm run type-check
-npx --no-install lint-staged
+# .husky/post-merge
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+npm run type-check || echo "Type check failed, please fix issues!"

.i18nrc.js

@@ -25,7 +25,7 @@ module.exports = defineConfig({
   ],
   temperature: 0,
   saveImmediately: true,
-  modelName: 'chatgpt-4o-latest',
+  modelName: 'gpt-4.1-mini',
   experimental: {
     jsonMode: true,
   },

.npmrc

@@ -1,10 +1,3 @@
-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*

.nvmrc

@@ -1 +1 @@
-lts/Krypton
+lts/jod

.prettierignore

@@ -5,6 +5,7 @@
 .DS_Store
 .editorconfig
 .idea
+.vscode
 .history
 .temp
 .env.local

.releaserc.cjs

@@ -1,18 +0,0 @@
-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;

.releaserc.js

@@ -0,0 +1,43 @@
+const config = require('@lobehub/lint').semanticRelease;
+
+// Remove NPM publishing by excluding "@semantic-release/npm" plugin
+// Keep or add other plugins like GitHub Releases
+config.plugins = config.plugins.filter((plugin) => plugin !== '@semantic-release/npm');
+
+// Add GitHub only if required
+config.plugins.push([
+  '@semantic-release/exec',
+  {
+    prepareCmd: 'npm run workflow:changelog',
+  },
+]);
+
+// Override GitHub repository URL without modifying package.json
+// Make sure @semantic-release/github is present in the plugins
+if (!config.plugins.some(plugin => Array.isArray(plugin) ? plugin[0] === '@semantic-release/github' : plugin === '@semantic-release/github')) {
+  config.plugins.push([
+    '@semantic-release/github',
+    {
+      repositoryUrl: 'https://github.com/jaworldwideorg/OneJA-Bot.git'
+    }
+  ]);
+} else {
+  // Find and update the existing GitHub plugin configuration
+  config.plugins = config.plugins.map(plugin => {
+    if (Array.isArray(plugin) && plugin[0] === '@semantic-release/github') {
+      return [
+        '@semantic-release/github',
+        {
+          ...(plugin[1] || {}),
+          repositoryUrl: 'https://github.com/jaworldwideorg/OneJA-Bot.git'
+        }
+      ];
+    }
+    return plugin;
+  });
+}
+
+// Set repository URL in global config
+config.repositoryUrl = 'https://github.com/jaworldwideorg/OneJA-Bot.git';
+
+module.exports = config;

.stylelintignore

@@ -1,39 +0,0 @@
-# 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/**

.vscode/extensions.json

@@ -1,13 +0,0 @@
-{
-    "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",
-    ]
-}

.vscode/settings.json

@@ -1,96 +0,0 @@
-{
-  "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}"
-  }
-}

AGENTS.md

@@ -1,109 +0,0 @@
-# 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

CLAUDE.md

@@ -1,59 +0,0 @@
-# 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

Dockerfile

@@ -1,5 +1,5 @@
 ## Set global build ENV
-ARG NODEJS_VERSION="24"
+ARG NODEJS_VERSION="22"
 
 ## Base image for all building stages
 FROM node:${NODEJS_VERSION}-slim AS base
@@ -37,9 +37,6 @@ 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
@@ -51,16 +48,6 @@ ARG FEATURE_FLAGS
 
 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}" \
     SENTRY_ORG="" \
@@ -77,7 +64,7 @@ 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=6144"
+ENV NODE_OPTIONS="--max-old-space-size=8192"
 
 WORKDIR /app
 
@@ -101,12 +88,7 @@ RUN \
     # Use pnpm for corepack
     && corepack use $(sed -n 's/.*"packageManager": "\(.*\)".*/\1/p' package.json) \
     # Install the dependencies
-    && pnpm i \
-    # Add db migration dependencies
-    && mkdir -p /deps \
-    && cd /deps \
-    && pnpm init \
-    && pnpm add pg drizzle-orm
+    && pnpm i
 
 COPY . .
 
@@ -122,16 +104,6 @@ COPY --from=base /distroless/ /
 # https://nextjs.org/docs/advanced-features/output-file-tracing
 COPY --from=builder /app/.next/standalone /app/
 
-# 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
 
@@ -152,7 +124,7 @@ ENV NODE_ENV="production" \
     NODE_OPTIONS="--dns-result-order=ipv4first --use-openssl-ca" \
     NODE_EXTRA_CA_CERTS="" \
     NODE_TLS_REJECT_UNAUTHORIZED="" \
-    SSL_CERT_FILE="/etc/ssl/certs/ca-certificates.crt"
+    SSL_CERT_DIR="/etc/ssl/certs/ca-certificates.crt"
 
 # Make the middleware rewrite through local as default
 # refs: https://github.com/lobehub/lobe-chat/issues/5876
@@ -164,37 +136,11 @@ 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="" \
-    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=""
+    PROXY_URL=""
 
 # Model Variables
 ENV \
@@ -202,12 +148,10 @@ 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
-    ENABLED_AWS_BEDROCK="" AWS_ACCESS_KEY_ID="" AWS_SECRET_ACCESS_KEY="" AWS_REGION="" AWS_BEDROCK_MODEL_LIST="" \
+    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
@@ -216,9 +160,6 @@ ENV \
     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
@@ -249,10 +190,6 @@ ENV \
     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
@@ -260,7 +197,7 @@ ENV \
     # Ollama
     ENABLED_OLLAMA="" OLLAMA_MODEL_LIST="" OLLAMA_PROXY_URL="" \
     # OpenAI
-    ENABLED_OPENAI="" OPENAI_API_KEY="" OPENAI_MODEL_LIST="" OPENAI_PROXY_URL="" \
+    OPENAI_API_KEY="" OPENAI_MODEL_LIST="" OPENAI_PROXY_URL="" \
     # OpenRouter
     OPENROUTER_API_KEY="" OPENROUTER_MODEL_LIST="" \
     # Perplexity
@@ -306,17 +243,7 @@ ENV \
     # 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=""
+    INFINIAI_API_KEY="" INFINIAI_MODEL_LIST=""
 
 USER nextjs
 

Dockerfile.database

@@ -0,0 +1,298 @@
+## 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_ENABLE_NEXT_AUTH
+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
+ARG FEATURE_FLAGS
+
+ENV NEXT_PUBLIC_BASE_PATH="${NEXT_PUBLIC_BASE_PATH}" \
+    FEATURE_FLAGS="${FEATURE_FLAGS}"
+
+ENV NEXT_PUBLIC_SERVICE_MODE="${NEXT_PUBLIC_SERVICE_MODE:-server}" \
+    NEXT_PUBLIC_ENABLE_NEXT_AUTH="${NEXT_PUBLIC_ENABLE_NEXT_AUTH:-1}" \
+    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 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
+    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/\/$//') \
+    # Update corepack to latest (nodejs/corepack#612)
+    && npm i -g corepack@latest \
+    # Enable corepack
+    && corepack enable \
+    # Use pnpm for corepack
+    && corepack use $(sed -n 's/.*"packageManager": "\(.*\)".*/\1/p' package.json) \
+    # Install the dependencies
+    && pnpm i \
+    # Add db migration dependencies
+    && mkdir -p /deps \
+    && cd /deps \
+    && pnpm init \
+    && pnpm add pg drizzle-orm
+
+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/ /
+
+# 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 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 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
+
+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"
+
+# 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" \
+    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="" \
+    # Cohere
+    COHERE_API_KEY="" COHERE_MODEL_LIST="" COHERE_PROXY_URL="" \
+    # 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="" \
+    # 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="" \
+    # 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="" \
+    # 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_PROXY_URL="" SPARK_SEARCH_MODE="" \
+    # 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="" \
+    # v0 (Vercel)
+    V0_API_KEY="" V0_MODEL_LIST="" \
+    # vLLM
+    VLLM_API_KEY="" VLLM_MODEL_LIST="" VLLM_PROXY_URL="" \
+    # Wenxin
+    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="" \
+    # Tencent Cloud
+    TENCENT_CLOUD_API_KEY="" TENCENT_CLOUD_MODEL_LIST="" \
+    # Infini-AI
+    INFINIAI_API_KEY="" INFINIAI_MODEL_LIST=""
+
+USER nextjs
+
+EXPOSE 3210/tcp
+
+ENTRYPOINT ["/bin/node"]
+
+CMD ["/app/startServer.js"]

Dockerfile.pglite

@@ -0,0 +1,252 @@
+## 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_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
+ARG FEATURE_FLAGS
+
+ENV NEXT_PUBLIC_CLIENT_DB="pglite"
+ENV NEXT_PUBLIC_BASE_PATH="${NEXT_PUBLIC_BASE_PATH}" \
+    FEATURE_FLAGS="${FEATURE_FLAGS}"
+
+# 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 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
+    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/\/$//') \
+    # Update corepack to latest (nodejs/corepack#612)
+    && npm i -g corepack@latest \
+    # Enable corepack
+    && corepack enable \
+    # Use pnpm for corepack
+    && corepack use $(sed -n 's/.*"packageManager": "\(.*\)".*/\1/p' package.json) \
+    # Install the dependencies
+    && pnpm i
+
+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/ /
+
+# 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 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"
+
+# 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" \
+    PORT="3210"
+
+# General Variables
+ENV ACCESS_CODE="" \
+    API_KEY_SELECT_MODE="" \
+    DEFAULT_AGENT_CONFIG="" \
+    SYSTEM_AGENT="" \
+    FEATURE_FLAGS="" \
+    PROXY_URL=""
+
+# 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="" \
+    # Cohere
+    COHERE_API_KEY="" COHERE_MODEL_LIST="" COHERE_PROXY_URL="" \
+    # 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="" \
+    # 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="" \
+    # 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="" \
+    # OpenRouter
+    OPENROUTER_API_KEY="" OPENROUTER_MODEL_LIST="" \
+    # Perplexity
+    PERPLEXITY_API_KEY="" PERPLEXITY_MODEL_LIST="" PERPLEXITY_PROXY_URL="" \
+    # 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="" \
+    # 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_PROXY_URL="" SPARK_SEARCH_MODE="" \
+    # 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="" \
+    # v0 (Vercel)
+    V0_API_KEY="" V0_MODEL_LIST="" \
+    # vLLM
+    VLLM_API_KEY="" VLLM_MODEL_LIST="" VLLM_PROXY_URL="" \
+    # Wenxin
+    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="" \
+    # Tencent Cloud
+    TENCENT_CLOUD_API_KEY="" TENCENT_CLOUD_MODEL_LIST="" \
+    # Infini-AI
+    INFINIAI_API_KEY="" INFINIAI_MODEL_LIST=""
+
+USER nextjs
+
+EXPOSE 3210/tcp
+
+ENTRYPOINT ["/bin/node"]
+
+CMD ["/app/startServer.js"]

LICENSE

@@ -1,10 +1,10 @@
-LobeHub Community License
+Apache License Version 2.0
 
 Copyright (c) 2024/06/17 - current LobeHub LLC. All rights reserved.
 
 ----------
 
-From 1.0, LobeChat is licensed under the LobeHub Community License, based on Apache License 2.0 with the following additional conditions:
+From 1.0, LobeChat is licensed under the Apache License 2.0, with the following additional conditions:
 
 1. The commercial usage of LobeChat:
 
@@ -22,3 +22,17 @@ 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.

README.md

@@ -1,10 +1,3 @@
-> \[!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]
@@ -59,26 +52,22 @@ One-click **FREE** deployment of your private OpenAI ChatGPT/Claude/Gemini/Groq/
 
 - [👋🏻 Getting Started & Join Our Community](#-getting-started--join-our-community)
 - [✨ Features](#-features)
-  - [✨ 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)
+  - [`1` Chain of Thought](#1-chain-of-thought)
+  - [`2` Branching Conversations](#2-branching-conversations)
+  - [`3` Artifacts Support](#3-artifacts-support)
+  - [`4` File Upload /Knowledge Base](#4-file-upload-knowledge-base)
+  - [`5` Multi-Model Service Provider Support](#5-multi-model-service-provider-support)
+  - [`6` Local Large Language Model (LLM) Support](#6-local-large-language-model-llm-support)
+  - [`7` Model Visual Recognition](#7-model-visual-recognition)
+  - [`8` TTS & STT Voice Conversation](#8-tts--stt-voice-conversation)
+  - [`9` Text to Image Generation](#9-text-to-image-generation)
+  - [`10` Plugin System (Function Calling)](#10-plugin-system-function-calling)
+  - [`11` Agent Market (GPTs)](#11-agent-market-gpts)
+  - [`12` Support Local / Remote Database](#12-support-local--remote-database)
+  - [`13` Support Multi-User Management](#13-support-multi-user-management)
+  - [`14` Progressive Web App (PWA)](#14-progressive-web-app-pwa)
+  - [`15` Mobile Device Adaptation](#15-mobile-device-adaptation)
+  - [`16` Custom Themes](#16-custom-themes)
   - [`*` What's more](#-whats-more)
 - [⚡️ Performance](#️-performance)
 - [🛳 Self Hosting](#-self-hosting)
@@ -125,59 +114,9 @@ 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]
+### `1` [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.
 
@@ -187,7 +126,7 @@ By breaking down complex reasoning into clear, logical steps, you can better und
 
 [![][image-feat-branch]][docs-feat-branch]
 
-### [Branching Conversations][docs-feat-branch]
+### `2` [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.
 
@@ -202,7 +141,7 @@ This groundbreaking feature transforms linear conversations into dynamic, tree-l
 
 [![][image-feat-artifacts]][docs-feat-artifacts]
 
-### [Artifacts Support][docs-feat-artifacts]
+### `3` [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.
 
@@ -216,7 +155,7 @@ Create and visualize with unprecedented flexibility:
 
 [![][image-feat-knowledgebase]][docs-feat-knowledgebase]
 
-### [File Upload /Knowledge Base][docs-feat-knowledgebase]
+### `4` [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.
 
@@ -234,7 +173,7 @@ LobeChat supports file upload and knowledge base functionality. You can upload v
 
 [![][image-feat-privoder]][docs-feat-provider]
 
-### [Multi-Model Service Provider Support][docs-feat-provider]
+### `5` [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.
 
@@ -244,13 +183,56 @@ In this way, LobeChat can more flexibly adapt to the needs of different users, w
 
 We have implemented support for the following model service providers:
 
-<!-- PROVIDER LIST -->
+<!-- PROVIDER LIST --> 
 
-<details><summary><kbd>See more providers (+-10)</kbd></summary>
+- **[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 (+31)</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.
+- **[PPIO](https://lobechat.com/discover/provider/ppio)**: PPIO supports stable and cost-efficient open-source LLM APIs, such as DeepSeek, Llama, Qwen etc.
+- **[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.
+- **[ModelScope](https://lobechat.com/discover/provider/modelscope)**: ModelScope is a model-as-a-service platform launched by Alibaba Cloud, offering a wide range of AI models and inference services.
+- **[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 (Grok)](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.
+- **[Aliyun Bailian](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.
+- **[Search1API](https://lobechat.com/discover/provider/search1api)**: Search1API provides access to the DeepSeek series of models that can connect to the internet as needed, including standard and fast versions, supporting a variety of model sizes.
+- **[InfiniAI](https://lobechat.com/discover/provider/infiniai)**: Provides high-performance, easy-to-use, and secure large model services for application developers, covering the entire process from large model development to service deployment.
+- **[Qiniu](https://lobechat.com/discover/provider/qiniu)**: Qiniu, as a long-established cloud service provider, delivers cost-effective and reliable AI inference services for both real-time and batch processing, with a simple and user-friendly experience.
 
 </details>
 
-> 📊 Total providers: [<kbd>**0**</kbd>](https://lobechat.com/discover/providers)
+> 📊 Total providers: [<kbd>**41**</kbd>](https://lobechat.com/discover/providers)
 
  <!-- PROVIDER LIST -->
 
@@ -264,7 +246,7 @@ At the same time, we are also planning to support more model service providers.
 
 [![][image-feat-local]][docs-feat-local]
 
-### [Local Large Language Model (LLM) Support][docs-feat-local]
+### `6` [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.
 
@@ -280,7 +262,7 @@ To meet the specific needs of users, LobeChat also supports the use of local mod
 
 [![][image-feat-vision]][docs-feat-vision]
 
-### [Model Visual Recognition][docs-feat-vision]
+### `7` [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,
@@ -298,7 +280,7 @@ Whether it's sharing images in daily use or interpreting images within specific
 
 [![][image-feat-tts]][docs-feat-tts]
 
-### [TTS & STT Voice Conversation][docs-feat-tts]
+### `8` [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.
@@ -315,7 +297,7 @@ Users can choose the voice that suits their personal preferences or specific sce
 
 [![][image-feat-t2i]][docs-feat-t2i]
 
-### [Text to Image Generation][docs-feat-t2i]
+### `9` [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.
 
@@ -329,7 +311,7 @@ This enables a more private and immersive creative process, allowing for the sea
 
 [![][image-feat-plugin]][docs-feat-plugin]
 
-### [Plugin System (Function Calling)][docs-feat-plugin]
+### `10` [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.
 
@@ -343,14 +325,14 @@ In addition, these plugins are not limited to news aggregation, but can also ext
 >
 > Learn more about [📘 Plugin Usage][docs-usage-plugin] by checking it out.
 
-<!-- PLUGIN LIST -->
+<!-- PLUGIN LIST --> 
 
-| 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`                   |
+| Recent Submits                                                                                                               | Description                                                                                                             |
+| ---------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
+| [PortfolioMeta](https://lobechat.com/discover/plugin/StockData)<br/><sup>By **portfoliometa** on **2025-05-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` |
+| [Bing_websearch](https://lobechat.com/discover/plugin/Bingsearch-identifier)<br/><sup>By **FineHow** on **2024-12-22**</sup> | Search for information from the internet base BingApi<br/>`bingsearch`                                                  |
+| [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`                                                      |
 
 > 📊 Total plugins: [<kbd>**42**</kbd>](https://lobechat.com/discover/plugins)
 
@@ -364,7 +346,7 @@ In addition, these plugins are not limited to news aggregation, but can also ext
 
 [![][image-feat-agent]][docs-feat-agent]
 
-### [Agent Market (GPTs)][docs-feat-agent]
+### `11` [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.
@@ -382,7 +364,7 @@ Our marketplace is not just a showcase platform but also a collaborative space.
 > We welcome all users to join this growing ecosystem and participate in the iteration and optimization of agents.
 > Together, we can create more interesting, practical, and innovative agents, further enriching the diversity and practicality of the agent offerings.
 
-<!-- AGENT LIST -->
+<!-- AGENT LIST --> 
 
 | Recent Submits                                                                                                                                                                 | Description                                                                                                                                                                                                              |
 | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
@@ -403,7 +385,7 @@ Our marketplace is not just a showcase platform but also a collaborative space.
 
 [![][image-feat-database]][docs-feat-database]
 
-### [Support Local / Remote Database][docs-feat-database]
+### `12` [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:
 
@@ -420,7 +402,7 @@ Regardless of which database you choose, LobeChat can provide you with an excell
 
 [![][image-feat-auth]][docs-feat-auth]
 
-### [Support Multi-User Management][docs-feat-auth]
+### `13` [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:
 
@@ -438,13 +420,13 @@ Regardless of which user management solution you choose, LobeChat can provide yo
 
 [![][image-feat-pwa]][docs-feat-pwa]
 
-### [Progressive Web App (PWA)][docs-feat-pwa]
+### `14` [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 high-performance characteristics.
+Through PWA, LobeChat can offer a highly optimized user experience on both desktop and mobile devices while maintaining its lightweight and 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.
 
@@ -465,7 +447,7 @@ providing smooth animations, responsive layouts, and adapting to different devic
 
 [![][image-feat-mobile]][docs-feat-mobile]
 
-### [Mobile Device Adaptation][docs-feat-mobile]
+### `15` [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.
 
@@ -477,7 +459,7 @@ We have carried out a series of optimization designs for mobile devices to enhan
 
 [![][image-feat-theme]][docs-feat-theme]
 
-### [Custom Themes][docs-feat-theme]
+### `16` [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.
@@ -782,7 +764,7 @@ Every bit counts and your one-time donation sparkles in our galaxy of support! Y
 </details>
 
 Copyright © 2025 [LobeHub][profile-link]. <br />
-This project is [LobeHub Community License](./LICENSE) licensed.
+This project is [Apache 2.0](./LICENSE) licensed.
 
 <!-- LINK GROUP -->
 
@@ -865,7 +847,7 @@ This project is [LobeHub Community License](./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/stargazers
+[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
@@ -876,11 +858,8 @@ This project is [LobeHub Community License](./LICENSE) licensed.
 [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
@@ -889,7 +868,6 @@ This project is [LobeHub Community License](./LICENSE) licensed.
 [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

README.zh-CN.md

@@ -1,10 +1,3 @@
-> \[!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]
@@ -59,26 +52,22 @@
 
 - [👋🏻 开始使用 & 交流](#-开始使用--交流)
 - [✨ 特性一览](#-特性一览)
-  - [✨ 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)
-  - [移动设备适配](#移动设备适配)
-  - [自定义主题](#自定义主题)
+  - [`1` 思维链 (CoT)](#1-思维链-cot)
+  - [`2` 分支对话](#2-分支对话)
+  - [`3` 支持白板 (Artifacts)](#3-支持白板-artifacts)
+  - [`4` 文件上传 / 知识库](#4-文件上传--知识库)
+  - [`5` 多模型服务商支持](#5-多模型服务商支持)
+  - [`6` 支持本地大语言模型 (LLM)](#6-支持本地大语言模型-llm)
+  - [`7` 模型视觉识别 (Model Visual)](#7-模型视觉识别-model-visual)
+  - [`8` TTS & STT 语音会话](#8-tts--stt-语音会话)
+  - [`9` Text to Image 文生图](#9-text-to-image-文生图)
+  - [`10` 插件系统 (Tools Calling)](#10-插件系统-tools-calling)
+  - [`11` 助手市场 (GPTs)](#11-助手市场-gpts)
+  - [`12` 支持本地 / 远程数据库](#12-支持本地--远程数据库)
+  - [`13` 支持多用户管理](#13-支持多用户管理)
+  - [`14` 渐进式 Web 应用 (PWA)](#14-渐进式-web-应用-pwa)
+  - [`15` 移动设备适配](#15-移动设备适配)
+  - [`16` 自定义主题](#16-自定义主题)
   - [`*` 更多特性](#-更多特性)
 - [⚡️ 性能测试](#️-性能测试)
 - [🛳 开箱即用](#-开箱即用)
@@ -125,59 +114,9 @@
 
 ## ✨ 特性一览
 
-通过 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]
+### `1` [思维链 (CoT)][docs-feat-cot]
 
 体验前所未有的 AI 推理过程。通过创新的思维链（CoT）可视化功能，您可以实时观察复杂问题是如何一步步被解析的。这项突破性的功能为 AI 的决策过程提供了前所未有的透明度，让您能够清晰地了解结论是如何得出的。
 
@@ -187,7 +126,7 @@
 
 [![][image-feat-branch]][docs-feat-branch]
 
-### [分支对话][docs-feat-branch]
+### `2` [分支对话][docs-feat-branch]
 
 为您带来更自然、更灵活的 AI 对话方式。通过分支对话功能，您的讨论可以像人类对话一样自然延伸。在任意消息处创建新的对话分支，让您在保留原有上下文的同时，自由探索不同的对话方向。
 
@@ -202,7 +141,7 @@
 
 [![][image-feat-artifacts]][docs-feat-artifacts]
 
-### [支持白板 (Artifacts)][docs-feat-artifacts]
+### `3` [支持白板 (Artifacts)][docs-feat-artifacts]
 
 体验集成于 LobeChat 的 Claude Artifacts 能力。这项革命性功能突破了 AI 人机交互的边界，让您能够实时创建和可视化各种格式的内容。
 
@@ -216,7 +155,7 @@
 
 [![][image-feat-knowledgebase]][docs-feat-knowledgebase]
 
-### [文件上传 / 知识库][docs-feat-knowledgebase]
+### `4` [文件上传 / 知识库][docs-feat-knowledgebase]
 
 LobeChat 支持文件上传与知识库功能，你可以上传文件、图片、音频、视频等多种类型的文件，以及创建知识库，方便用户管理和查找文件。同时在对话中使用文件和知识库功能，实现更加丰富的对话体验。
 
@@ -234,7 +173,7 @@ LobeChat 支持文件上传与知识库功能，你可以上传文件、图片
 
 [![][image-feat-privoder]][docs-feat-provider]
 
-### [多模型服务商支持][docs-feat-provider]
+### `5` [多模型服务商支持][docs-feat-provider]
 
 在 LobeChat 的不断发展过程中，我们深刻理解到在提供 AI 会话服务时模型服务商的多样性对于满足社区需求的重要性。因此，我们不再局限于单一的模型服务商，而是拓展了对多种模型服务商的支持，以便为用户提供更为丰富和多样化的会话选择。
 
@@ -244,13 +183,56 @@ LobeChat 支持文件上传与知识库功能，你可以上传文件、图片
 
 我们已经实现了对以下模型服务商的支持：
 
-<!-- PROVIDER LIST -->
+<!-- PROVIDER LIST --> 
 
-<details><summary><kbd>See more providers (+-10)</kbd></summary>
+- **[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 (+31)</kbd></summary>
+
+- **[Novita](https://lobechat.com/discover/provider/novita)**: Novita AI 是一个提供多种大语言模型与 AI 图像生成的 API 服务的平台，灵活、可靠且具有成本效益。它支持 Llama3、Mistral 等最新的开源模型，并为生成式 AI 应用开发提供了全面、用户友好且自动扩展的 API 解决方案，适合 AI 初创公司的快速发展。
+- **[PPIO](https://lobechat.com/discover/provider/ppio)**: PPIO 派欧云提供稳定、高性价比的开源模型 API 服务，支持 DeepSeek 全系列、Llama、Qwen 等行业领先大模型。
+- **[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 提供先进的通用、专业和研究型模型，广泛应用于复杂推理、多语言任务、代码生成等领域，通过功能调用接口，用户可以集成自定义功能，实现特定应用。
+- **[ModelScope](https://lobechat.com/discover/provider/modelscope)**: ModelScope是阿里云推出的模型即服务平台，提供丰富的AI模型和推理服务。
+- **[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 (Grok)](https://lobechat.com/discover/provider/xai)**: xAI 是一家致力于构建人工智能以加速人类科学发现的公司。我们的使命是推动我们对宇宙的共同理解。
+- **[Aliyun Bailian](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 满足多样化用户需求，支持开发者集成，推动智能化应用的革新和发展。
+- **[Search1API](https://lobechat.com/discover/provider/search1api)**: Search1API 提供可根据需要自行联网的 DeepSeek 系列模型的访问，包括标准版和快速版本，支持多种参数规模的模型选择。
+- **[InfiniAI](https://lobechat.com/discover/provider/infiniai)**: 为应用开发者提供高性能、易上手、安全可靠的大模型服务，覆盖从大模型开发到大模型服务化部署的全流程。
+- **[Qiniu](https://lobechat.com/discover/provider/qiniu)**: 七牛作为老牌云服务厂商，提供高性价比稳定的实时、批量 AI 推理服务，简单易用。
 
 </details>
 
-> 📊 Total providers: [<kbd>**0**</kbd>](https://lobechat.com/discover/providers)
+> 📊 Total providers: [<kbd>**41**</kbd>](https://lobechat.com/discover/providers)
 
  <!-- PROVIDER LIST -->
 
@@ -264,7 +246,7 @@ LobeChat 支持文件上传与知识库功能，你可以上传文件、图片
 
 [![][image-feat-local]][docs-feat-local]
 
-### [支持本地大语言模型 (LLM)][docs-feat-local]
+### `6` [支持本地大语言模型 (LLM)][docs-feat-local]
 
 为了满足特定用户的需求，LobeChat 还基于 [Ollama](https://ollama.ai) 支持了本地模型的使用，让用户能够更灵活地使用自己的或第三方的模型。
 
@@ -280,7 +262,7 @@ LobeChat 支持文件上传与知识库功能，你可以上传文件、图片
 
 [![][image-feat-vision]][docs-feat-vision]
 
-### [模型视觉识别 (Model Visual)][docs-feat-vision]
+### `7` [模型视觉识别 (Model Visual)][docs-feat-vision]
 
 LobeChat 已经支持 OpenAI 最新的 [`gpt-4-vision`](https://platform.openai.com/docs/guides/vision) 支持视觉识别的模型，这是一个具备视觉识别能力的多模态应用。
 用户可以轻松上传图片或者拖拽图片到对话框中，助手将能够识别图片内容，并在此基础上进行智能对话，构建更智能、更多元化的聊天场景。
@@ -295,7 +277,7 @@ LobeChat 已经支持 OpenAI 最新的 [`gpt-4-vision`](https://platform.openai.
 
 [![][image-feat-tts]][docs-feat-tts]
 
-### [TTS & STT 语音会话][docs-feat-tts]
+### `8` [TTS & STT 语音会话][docs-feat-tts]
 
 LobeChat 支持文字转语音（Text-to-Speech，TTS）和语音转文字（Speech-to-Text，STT）技术，这使得我们的应用能够将文本信息转化为清晰的语音输出，用户可以像与真人交谈一样与我们的对话助手进行交流。
 用户可以从多种声音中选择，给助手搭配合适的音源。 同时，对于那些倾向于听觉学习或者想要在忙碌中获取信息的用户来说，TTS 提供了一个极佳的解决方案。
@@ -310,7 +292,7 @@ LobeChat 支持文字转语音（Text-to-Speech，TTS）和语音转文字（Spe
 
 [![][image-feat-t2i]][docs-feat-t2i]
 
-### [Text to Image 文生图][docs-feat-t2i]
+### `9` [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 工具的能力， 助手们现在可以将你的想法转化为图像。
@@ -324,7 +306,7 @@ LobeChat 支持文字转语音（Text-to-Speech，TTS）和语音转文字（Spe
 
 [![][image-feat-plugin]][docs-feat-plugin]
 
-### [插件系统 (Tools Calling)][docs-feat-plugin]
+### `10` [插件系统 (Tools Calling)][docs-feat-plugin]
 
 LobeChat 的插件生态系统是其核心功能的重要扩展，它极大地增强了 ChatGPT 的实用性和灵活性。
 
@@ -336,14 +318,14 @@ LobeChat 的插件生态系统是其核心功能的重要扩展，它极大地
 
 > 通过文档了解更多 [📘 插件使用][docs-usage-plugin]
 
-<!-- PLUGIN LIST -->
+<!-- PLUGIN LIST --> 
 
-| 最近新增                                                                                                              | 描述                                                                                                               |
-| --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
-| [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/>`网页` `搜索`                                 |
+| 最近新增                                                                                                                  | 描述                                               |
+| --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ |
+| [PortfolioMeta](https://lobechat.com/discover/plugin/StockData)<br/><sup>By **portfoliometa** on **2025-05-27**</sup> | 分析股票并获取全面的实时投资数据和分析。<br/>`股票`                    |
+| [网页](https://lobechat.com/discover/plugin/web)<br/><sup>By **Proghit** on **2025-01-24**</sup>                        | 智能网页搜索，读取和分析页面，以提供来自Google结果的全面答案。<br/>`网页` `搜索` |
+| [必应网页搜索](https://lobechat.com/discover/plugin/Bingsearch-identifier)<br/><sup>By **FineHow** on **2024-12-22**</sup>  | 通过BingApi搜索互联网上的信息<br/>`bingsearch`              |
+| [谷歌自定义搜索引擎](https://lobechat.com/discover/plugin/google-cse)<br/><sup>By **vsnthdev** on **2024-12-02**</sup>         | 通过他们的官方自定义搜索引擎API搜索谷歌。<br/>`网络` `搜索`             |
 
 > 📊 Total plugins: [<kbd>**42**</kbd>](https://lobechat.com/discover/plugins)
 
@@ -357,7 +339,7 @@ LobeChat 的插件生态系统是其核心功能的重要扩展，它极大地
 
 [![][image-feat-agent]][docs-feat-agent]
 
-### [助手市场 (GPTs)][docs-feat-agent]
+### `11` [助手市场 (GPTs)][docs-feat-agent]
 
 在 LobeChat 的助手市场中，创作者们可以发现一个充满活力和创新的社区，它汇聚了众多精心设计的助手，这些助手不仅在工作场景中发挥着重要作用，也在学习过程中提供了极大的便利。
 我们的市场不仅是一个展示平台，更是一个协作的空间。在这里，每个人都可以贡献自己的智慧，分享个人开发的助手。
@@ -371,14 +353,14 @@ LobeChat 的插件生态系统是其核心功能的重要扩展，它极大地
 >
 > 我欢迎所有用户加入这个不断成长的生态系统，共同参与到助手的迭代与优化中来。共同创造出更多有趣、实用且具有创新性的助手，进一步丰富助手的多样性和实用性。
 
-<!-- AGENT LIST -->
+<!-- AGENT LIST --> 
 
-| 最近新增                                                                                                                                                         | 描述                                                                                                              |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
+| 最近新增                                                                                                                                                       | 描述                                                                 |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ |
 | [海龟汤主持人](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`                                          |
+| [美食评论员🍟](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>**505**</kbd> ](https://lobechat.com/discover/assistants)
 
@@ -392,7 +374,7 @@ LobeChat 的插件生态系统是其核心功能的重要扩展，它极大地
 
 [![][image-feat-database]][docs-feat-database]
 
-### [支持本地 / 远程数据库][docs-feat-database]
+### `12` [支持本地 / 远程数据库][docs-feat-database]
 
 LobeChat 支持同时使用服务端数据库和本地数据库。根据您的需求，您可以选择合适的部署方案：
 
@@ -409,7 +391,7 @@ LobeChat 支持同时使用服务端数据库和本地数据库。根据您的
 
 [![][image-feat-auth]][docs-feat-auth]
 
-### [支持多用户管理][docs-feat-auth]
+### `13` [支持多用户管理][docs-feat-auth]
 
 LobeChat 支持多用户管理，提供了两种主要的用户认证和管理方案，以满足不同需求：
 
@@ -427,7 +409,7 @@ LobeChat 支持多用户管理，提供了两种主要的用户认证和管理
 
 [![][image-feat-pwa]][docs-feat-pwa]
 
-### [渐进式 Web 应用 (PWA)][docs-feat-pwa]
+### `14` [渐进式 Web 应用 (PWA)][docs-feat-pwa]
 
 我们深知在当今多设备环境下为用户提供无缝体验的重要性。为此，我们采用了渐进式 Web 应用 [PWA](https://support.google.com/chrome/answer/9658361) 技术，
 这是一种能够将网页应用提升至接近原生应用体验的现代 Web 技术。通过 PWA，LobeChat 能够在桌面和移动设备上提供高度优化的用户体验，同时保持轻量级和高性能的特点。
@@ -440,6 +422,7 @@ LobeChat 支持多用户管理，提供了两种主要的用户认证和管理
 > - 在电脑上运行 Chrome 或 Edge 浏览器 .
 > - 访问 LobeChat 网页 .
 > - 在地址栏的右上角，单击 <kbd>安装</kbd> 图标 .
+> - 根据屏幕上的指示完成 PWA 的安装 .
 
 <div align="right">
 
@@ -449,7 +432,7 @@ LobeChat 支持多用户管理，提供了两种主要的用户认证和管理
 
 [![][image-feat-mobile]][docs-feat-mobile]
 
-### [移动设备适配][docs-feat-mobile]
+### `15` [移动设备适配][docs-feat-mobile]
 
 针对移动设备进行了一系列的优化设计，以提升用户的移动体验。目前，我们正在对移动端的用户体验进行版本迭代，以实现更加流畅和直观的交互。如果您有任何建议或想法，我们非常欢迎您通过 GitHub Issues 或者 Pull Requests 提供反馈。
 
@@ -461,7 +444,7 @@ LobeChat 支持多用户管理，提供了两种主要的用户认证和管理
 
 [![][image-feat-theme]][docs-feat-theme]
 
-### [自定义主题][docs-feat-theme]
+### `16` [自定义主题][docs-feat-theme]
 
 作为设计工程师出身，LobeChat 在界面设计上充分考虑用户的个性化体验，因此引入了灵活多变的主题模式，其中包括日间的亮色模式和夜间的深色模式。
 除了主题模式的切换，还提供了一系列的颜色定制选项，允许用户根据自己的喜好来调整应用的主题色彩。无论是想要沉稳的深蓝，还是希望活泼的桃粉，或者是专业的灰白，用户都能够在 LobeChat 中找到匹配自己风格的颜色选择。
@@ -548,7 +531,7 @@ LobeChat 提供了 Vercel 的 自托管版本 和 [Docker 镜像][docker-release
 
 #### 保持更新
 
-如果你根据 README 中的一键部署步骤部署了自己的项目，你可能会发现总是被提示 "有可用更新"。这是因为 Vercel 默认为你创建新项目而非 fork 本项目，这将导致无法准确检测更新。
+如果你根据 README 中的一键部署步骤部署了自己的项目，你可能会发现总是被提示 “有可用更新”。这是因为 Vercel 默认为你创建新项目而非 fork 本项目，这将导致无法准确检测更新。
 
 > \[!TIP]
 >
@@ -562,9 +545,9 @@ LobeChat 提供了 Vercel 的 自托管版本 和 [Docker 镜像][docker-release
 [![][docker-size-shield]][docker-size-link]
 [![][docker-pulls-shield]][docker-pulls-link]
 
-我们提供了一个用于在您自己的私有设备上部署 LobeChat 服务的 Docker 镜像。请使用以下命令启动 LobeChat 服务：
+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. 创建一个用于存储文件的文件夹
+1. create a folder to for storage files
 
 ```fish
 $ mkdir lobe-chat-db && cd lobe-chat-db
@@ -803,7 +786,7 @@ $ pnpm run dev
 </details>
 
 Copyright © 2025 [LobeHub][profile-link]. <br />
-This project is [LobeHub Community License](./LICENSE) licensed.
+This project is [Apache 2.0](./LICENSE) licensed.
 
 <!-- LINK GROUP -->
 
@@ -886,7 +869,7 @@ This project is [LobeHub Community License](./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/stargazers
+[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
@@ -897,10 +880,8 @@ This project is [LobeHub Community License](./LICENSE) licensed.
 [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
@@ -909,7 +890,6 @@ This project is [LobeHub Community License](./LICENSE) licensed.
 [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

apps/desktop/.i18nrc.js

@@ -23,9 +23,8 @@ module.exports = defineConfig({
     'vi-VN',
     'fa-IR',
   ],
-  saveImmediately: true,
   temperature: 0,
-  modelName: 'gpt-4.1-mini',
+  modelName: 'gpt-4o-mini',
   experimental: {
     jsonMode: true,
   },

apps/desktop/.npmrc

@@ -1,6 +1,4 @@
 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/

apps/desktop/README.md

@@ -1,353 +1,60 @@
-# 🤯 LobeHub Desktop Application
+# LobeHub Desktop Application
 
-LobeHub Desktop is a cross-platform desktop application for [LobeChat](https://github.com/lobehub/lobe-chat), built with Electron, providing a more native desktop experience and functionality.
+LobeHub Desktop 是 [LobeChat](https://github.com/lobehub/lobe-chat) 的跨平台桌面应用程序，使用 Electron 构建，提供了更加原生的桌面体验和功能。
 
-## ✨ Features
+## 功能特点
 
-- **🌍 Cross-platform Support**: Supports macOS (Intel/Apple Silicon), Windows, and Linux systems
-- **🔄 Auto Updates**: Built-in update mechanism ensures you always have the latest version
-- **🌐 Multi-language Support**: Complete i18n support for 18+ languages with lazy loading
-- **🎨 Native Integration**: Deep OS integration with native menus, shortcuts, and notifications
-- **🔒 Secure & Reliable**: macOS notarized, encrypted token storage, secure OAuth flow
-- **📦 Multiple Release Channels**: Stable, beta, and nightly build versions
-- **⚡ Advanced Window Management**: Multi-window architecture with theme synchronization
-- **🔗 Remote Server Sync**: Secure data synchronization with remote LobeChat instances
-- **🎯 Developer Tools**: Built-in development panel and comprehensive debugging tools
+- **跨平台支持**：支持 macOS (Intel/Apple Silicon)、Windows 和 Linux 系统
+- **自动更新**：内置更新机制，确保您始终使用最新版本
+- **多语言支持**：完整的国际化支持，包括中文、英文等多种语言
+- **原生集成**：与操作系统深度集成，提供原生菜单、快捷键和通知
+- **安全可靠**：macOS 版本经过公证，确保安全性
+- **多渠道发布**：提供稳定版、测试版和每日构建版本
 
-## 🚀 Development Setup
+## 开发环境设置
 
-### Prerequisites
+### 前提条件
 
-- **Node.js** 22+
-- **pnpm** 10+
-- **Electron** compatible development environment
+- Node.js 22+
+- pnpm 10+
 
-### Quick Start
+### 安装依赖
 
 ```bash
-# Install dependencies
 pnpm install-isolated
+```
 
-# Start development server
+### 开发模式运行
+
+```bash
 pnpm electron:dev
-
-# Type checking
-pnpm typecheck
-
-# Run tests
-pnpm test
 ```
 
-### Environment Configuration
+### 构建应用
 
-Copy `.env.desktop` to `.env` and configure as needed:
+构建所有平台：
 
 ```bash
-cp .env.desktop .env
+pnpm build
 ```
 
-> \[!WARNING]
-> Backup your `.env` file before making changes to avoid losing configurations.
-
-### Build Commands
-
-| Command            | Description                             |
-| ------------------ | --------------------------------------- |
-| `pnpm build`       | Build for all platforms                 |
-| `pnpm build:mac`   | Build for macOS (Intel + Apple Silicon) |
-| `pnpm build:win`   | Build for Windows                       |
-| `pnpm build:linux` | Build for Linux                         |
-| `pnpm build-local` | Local development build                 |
-
-### Development Workflow
+构建特定平台：
 
 ```bash
-# 1. Development
-pnpm electron:dev # Start with hot reload
+# macOS
+pnpm build:mac
 
-# 2. Code Quality
-pnpm lint      # ESLint checking
-pnpm format    # Prettier formatting
-pnpm typecheck # TypeScript validation
+# Windows
+pnpm build:win
 
-# 3. Testing
-pnpm test # Run Vitest tests
-
-# 4. Build & Package
-pnpm build       # Production build
-pnpm build-local # Local testing build
+# Linux
+pnpm build:linux
 ```
 
-## 🎯 Release Channels
+## 发布渠道
 
-| Channel     | Description                      | Stability | Auto-Updates |
-| ----------- | -------------------------------- | --------- | ------------ |
-| **Stable**  | Thoroughly tested releases       | 🟢 High   | ✅ Yes       |
-| **Beta**    | Pre-release with new features    | 🟡 Medium | ✅ Yes       |
-| **Nightly** | Daily builds with latest changes | 🟠 Low    | ✅ Yes       |
+应用提供三个发布渠道：
 
-## 🛠 Technology Stack
-
-### Core Framework
-
-- **Electron** `37.1.0` - Cross-platform desktop framework
-- **Node.js** `22+` - Backend runtime
-- **TypeScript** `5.7+` - Type-safe development
-- **Vite** `6.2+` - Build tooling
-
-### Architecture & Patterns
-
-- **Dependency Injection** - IoC container with decorator-based registration
-- **Event-Driven Architecture** - IPC communication between processes
-- **Module Federation** - Dynamic controller and service loading
-- **Observer Pattern** - State management and UI synchronization
-
-### Development Tools
-
-- **Vitest** - Unit testing framework
-- **ESLint** - Code linting
-- **Prettier** - Code formatting
-- **electron-builder** - Application packaging
-- **electron-updater** - Auto-update mechanism
-
-### Security & Storage
-
-- **Electron Safe Storage** - Encrypted token storage
-- **OAuth 2.0 + PKCE** - Secure authentication flow
-- **electron-store** - Persistent configuration
-- **Custom Protocol Handler** - Secure callback handling
-
-## 🏗 Architecture
-
-The desktop application uses a sophisticated dependency injection and event-driven architecture:
-
-### 📁 Core Structure
-
-```
-src/main/core/
-├── App.ts                    # 🎯 Main application orchestrator
-├── IoCContainer.ts           # 🔌 Dependency injection container
-├── window/                   # 🪟 Window management modules
-│   ├── WindowThemeManager.ts     # 🎨 Theme synchronization
-│   ├── WindowPositionManager.ts  # 📐 Position persistence
-│   ├── WindowErrorHandler.ts     # ⚠️  Error boundaries
-│   └── WindowConfigBuilder.ts    # ⚙️  Configuration builder
-├── browser/                  # 🌐 Browser management modules
-│   ├── Browser.ts               # 🪟 Individual window instances
-│   └── BrowserManager.ts        # 👥 Multi-window coordinator
-├── ui/                       # 🎨 UI system modules
-│   ├── Tray.ts                  # 📍 System tray integration
-│   ├── TrayManager.ts           # 🔧 Tray management
-│   ├── MenuManager.ts           # 📋 Native menu system
-│   └── ShortcutManager.ts       # ⌨️  Global shortcuts
-└── infrastructure/           # 🔧 Infrastructure services
-    ├── StoreManager.ts          # 💾 Configuration storage
-    ├── I18nManager.ts           # 🌍 Internationalization
-    ├── UpdaterManager.ts        # 📦 Auto-update system
-    └── StaticFileServerManager.ts # 🗂️ Local file serving
-```
-
-### 🔄 Application Lifecycle
-
-The `App.ts` class orchestrates the entire application lifecycle through key phases:
-
-#### 1. 🚀 Initialization Phase
-
-- **System Information Logging** - Captures OS, CPU, RAM, and locale details
-- **Store Manager Setup** - Initializes persistent configuration storage
-- **Dynamic Module Loading** - Auto-discovers controllers and services via glob imports
-- **IPC Event Registration** - Sets up inter-process communication channels
-
-#### 2. 🏃 Bootstrap Phase
-
-- **Single Instance Check** - Ensures only one application instance runs
-- **IPC Server Launch** - Starts the communication server
-- **Core Manager Initialization** - Sequential initialization of all managers:
-  - 🌍 I18n for internationalization
-  - 📋 Menu system for native menus
-  - 🗂️ Static file server for local assets
-  - ⌨️ Global shortcuts registration
-  - 🪟 Browser window management
-  - 📍 System tray (Windows only)
-  - 📦 Auto-updater system
-
-### 🔧 Core Components Deep Dive
-
-#### 🌐 Browser Management System
-
-- **Multi-Window Architecture** - Supports chat, settings, and devtools windows
-- **Window State Management** - Handles positioning, theming, and lifecycle
-- **WebContents Mapping** - Bidirectional mapping between WebContents and identifiers
-- **Event Broadcasting** - Centralized event distribution to all or specific windows
-
-#### 🔌 Dependency Injection & Event System
-
-- **IoC Container** - WeakMap-based container for decorated controller methods
-- **Decorator Registration** - `@ipcClientEvent` and `@ipcServerEvent` decorators
-- **Automatic Event Mapping** - Events registered during controller loading
-- **Service Locator** - Type-safe service and controller retrieval
-
-#### 🪟 Window Management
-
-- **Theme-Aware Windows** - Automatic adaptation to system dark/light mode
-- **Platform-Specific Styling** - Windows title bar and overlay customization
-- **Position Persistence** - Save and restore window positions across sessions
-- **Error Boundaries** - Centralized error handling for window operations
-
-#### 🔧 Infrastructure Services
-
-##### 🌍 I18n Manager
-
-- **18+ Language Support** with lazy loading and namespace organization
-- **System Integration** with Electron's locale detection
-- **Dynamic UI Refresh** on language changes
-- **Resource Management** with efficient loading strategies
-
-##### 📦 Update Manager
-
-- **Multi-Channel Support** (stable, beta, nightly) with configurable intervals
-- **Background Downloads** with progress tracking and user notifications
-- **Rollback Protection** with error handling and recovery mechanisms
-- **Channel Management** with automatic channel switching
-
-##### 💾 Store Manager
-
-- **Type-Safe Storage** using electron-store with TypeScript interfaces
-- **Encrypted Secrets** via Electron's Safe Storage API
-- **Configuration Validation** with default value management
-- **File System Integration** with automatic directory creation
-
-##### 🗂️ Static File Server
-
-- **Local HTTP Server** for serving application assets and user files
-- **Security Controls** with request filtering and access validation
-- **File Management** with upload, download, and deletion capabilities
-- **Path Resolution** with intelligent routing between storage locations
-
-#### 🎨 UI System Integration
-
-- **Global Shortcuts** - Platform-aware keyboard shortcut registration with conflict detection
-- **System Tray** - Native integration with context menus and notifications
-- **Native Menus** - Platform-specific application and context menus with i18n
-- **Theme Synchronization** - Automatic theme updates across all UI components
-
-### 🏛 Controller & Service Architecture
-
-#### 🎮 Controller Pattern
-
-- **IPC Event Handling** - Processes events from renderer with decorator-based registration
-- **Lifecycle Hooks** - `beforeAppReady` and `afterAppReady` for initialization phases
-- **Type-Safe Communication** - Strong typing for all IPC events and responses
-- **Error Boundaries** - Comprehensive error handling with proper propagation
-
-#### 🔧 Service Pattern
-
-- **Business Logic Encapsulation** - Clean separation of concerns
-- **Dependency Management** - Managed through IoC container
-- **Cross-Controller Sharing** - Services accessible via service locator pattern
-- **Resource Management** - Proper initialization and cleanup
-
-### 🔗 Inter-Process Communication
-
-#### 📡 IPC System Features
-
-- **Bidirectional Communication** - Main↔Renderer and Main↔Next.js server
-- **Type-Safe Events** - TypeScript interfaces for all event parameters
-- **Context Awareness** - Events include sender context for window-specific operations
-- **Error Propagation** - Centralized error handling with proper status codes
-
-#### 🛡️ Security Features
-
-- **OAuth 2.0 + PKCE** - Secure authentication with state parameter validation
-- **Encrypted Token Storage** - Using Electron's Safe Storage API when available
-- **Custom Protocol Handler** - Secure callback handling for OAuth flows
-- **Request Filtering** - Security controls for web requests and external links
-
-## 🧪 Testing
-
-### Test Structure
-
-```bash
-apps/desktop/src/main/controllers/__tests__/ # Controller unit tests
-tests/                                       # Integration tests
-```
-
-### Running Tests
-
-```bash
-pnpm test       # Run all tests
-pnpm test:watch # Watch mode
-pnpm typecheck  # Type validation
-```
-
-### Test Coverage
-
-- **Controller Tests** - IPC event handling validation
-- **Service Tests** - Business logic verification
-- **Integration Tests** - End-to-end workflow testing
-- **Type Tests** - TypeScript interface validation
-
-## 🔒 Security Features
-
-### Authentication & Authorization
-
-- **OAuth 2.0 Flow** with PKCE for secure token exchange
-- **State Parameter Validation** to prevent CSRF attacks
-- **Encrypted Token Storage** using platform-native secure storage
-- **Automatic Token Refresh** with fallback to re-authentication
-
-### Application Security
-
-- **Code Signing** - macOS notarization for enhanced security
-- **Sandboxing** - Controlled access to system resources
-- **CSP Controls** - Content Security Policy management
-- **Request Filtering** - Security controls for external requests
-
-### Data Protection
-
-- **Encrypted Configuration** - Sensitive data encrypted at rest
-- **Secure IPC** - Type-safe communication channels
-- **Path Validation** - Secure file system access controls
-- **Network Security** - HTTPS enforcement and proxy support
-
-## 🤝 Contribution
-
-Desktop application development involves complex cross-platform considerations and native integrations. We welcome community contributions to improve functionality, performance, and user experience. You can participate in improvements through:
-
-### How to Contribute
-
-1. **Platform Support**: Enhance cross-platform compatibility and native integrations
-2. **Performance Optimization**: Improve application startup time, memory usage, and responsiveness
-3. **Feature Development**: Add new desktop-specific features and capabilities
-4. **Bug Fixes**: Fix platform-specific issues and edge cases
-5. **Security Improvements**: Enhance security measures and authentication flows
-6. **UI/UX Enhancements**: Improve desktop user interface and experience
-
-### Contribution Process
-
-1. Fork the [LobeChat repository](https://github.com/lobehub/lobe-chat)
-2. Set up the desktop development environment following our setup guide
-3. Make your changes to the desktop application
-4. Submit a Pull Request describing:
-
-- Platform compatibility testing results
-- Performance impact analysis
-- Security considerations
-- User experience improvements
-- Breaking changes (if any)
-
-### Development Areas
-
-- **Core Architecture**: Dependency injection, event system, and lifecycle management
-- **Window Management**: Multi-window support, theme synchronization, and state persistence
-- **IPC Communication**: Type-safe inter-process communication between main and renderer
-- **Platform Integration**: Native menus, shortcuts, notifications, and system tray
-- **Security Features**: OAuth flows, token encryption, and secure storage
-- **Auto-Update System**: Multi-channel updates and rollback mechanisms
-
-## 📚 Additional Resources
-
-- **Development Guide**: [`Development.md`](./Development.md) - Comprehensive development documentation
-- **Architecture Docs**: [`/docs`](../../docs/) - Detailed technical specifications
-- **Contributing**: [`CONTRIBUTING.md`](../../CONTRIBUTING.md) - Contribution guidelines
-- **Issues & Support**: [GitHub Issues](https://github.com/lobehub/lobe-chat/issues)
+- **稳定版**：经过充分测试的正式版本
+- **测试版 (Beta)**：预发布版本，包含即将发布的新功能
+- **每日构建版 (Nightly)**：包含最新开发进展的构建版本

apps/desktop/README.zh-CN.md

@@ -1,353 +0,0 @@
-# 🤯 LobeHub 桌面应用程序
-
-LobeHub Desktop 是 [LobeChat](https://github.com/lobehub/lobe-chat) 的跨平台桌面应用程序，使用 Electron 构建，提供了更加原生的桌面体验和功能。
-
-## ✨ 功能特点
-
-- **🌍 跨平台支持**：支持 macOS (Intel/Apple Silicon)、Windows 和 Linux 系统
-- **🔄 自动更新**：内置更新机制，确保您始终使用最新版本
-- **🌐 多语言支持**：完整的 i18n 支持，包含 18+ 种语言的懒加载
-- **🎨 原生集成**：与操作系统深度集成，提供原生菜单、快捷键和通知
-- **🔒 安全可靠**：macOS 公证认证，加密令牌存储，安全的 OAuth 流程
-- **📦 多渠道发布**：提供稳定版、测试版和每日构建版本
-- **⚡ 高级窗口管理**：多窗口架构，支持主题同步
-- **🔗 远程服务器同步**：与远程 LobeChat 实例的安全数据同步
-- **🎯 开发者工具**：内置开发面板和全面的调试工具
-
-## 🚀 开发环境设置
-
-### 前提条件
-
-- **Node.js** 22+
-- **pnpm** 10+
-- **Electron** 兼容的开发环境
-
-### 快速开始
-
-```bash
-# 安装依赖
-pnpm install-isolated
-
-# 启动开发服务器
-pnpm electron:dev
-
-# 类型检查
-pnpm typecheck
-
-# 运行测试
-pnpm test
-```
-
-### 环境变量配置
-
-复制 `.env.desktop` 到 `.env` 并根据需要配置：
-
-```bash
-cp .env.desktop .env
-```
-
-> \[!WARNING]
-> 在进行更改之前请备份您的 `.env` 文件，避免丢失配置。
-
-### 构建命令
-
-| 命令               | 描述                               |
-| ------------------ | ---------------------------------- |
-| `pnpm build`       | 构建所有平台                       |
-| `pnpm build:mac`   | 构建 macOS (Intel + Apple Silicon) |
-| `pnpm build:win`   | 构建 Windows                       |
-| `pnpm build:linux` | 构建 Linux                         |
-| `pnpm build-local` | 本地开发构建                       |
-
-### 开发工作流
-
-```bash
-# 1. 开发
-pnpm electron:dev # 启动热重载开发服务器
-
-# 2. 代码质量
-pnpm lint      # ESLint 检查
-pnpm format    # Prettier 格式化
-pnpm typecheck # TypeScript 验证
-
-# 3. 测试
-pnpm test # 运行 Vitest 测试
-
-# 4. 构建和打包
-pnpm build       # 生产构建
-pnpm build-local # 本地测试构建
-```
-
-## 🎯 发布渠道
-
-| 渠道                     | 描述                   | 稳定性 | 自动更新 |
-| ------------------------ | ---------------------- | ------ | -------- |
-| **稳定版**               | 经过充分测试的正式版本 | 🟢 高  | ✅ 是    |
-| **测试版 (Beta)**        | 包含新功能的预发布版本 | 🟡 中  | ✅ 是    |
-| **每日构建版 (Nightly)** | 包含最新更改的每日构建 | 🟠 低  | ✅ 是    |
-
-## 🛠 技术栈
-
-### 核心框架
-
-- **Electron** `37.1.0` - 跨平台桌面框架
-- **Node.js** `22+` - 后端运行时
-- **TypeScript** `5.7+` - 类型安全开发
-- **Vite** `6.2+` - 构建工具
-
-### 架构和模式
-
-- **依赖注入** - 基于装饰器注册的 IoC 容器
-- **事件驱动架构** - 进程间 IPC 通信
-- **模块联邦** - 动态控制器和服务加载
-- **观察者模式** - 状态管理和 UI 同步
-
-### 开发工具
-
-- **Vitest** - 单元测试框架
-- **ESLint** - 代码检查
-- **Prettier** - 代码格式化
-- **electron-builder** - 应用程序打包
-- **electron-updater** - 自动更新机制
-
-### 安全和存储
-
-- **Electron Safe Storage** - 加密令牌存储
-- **OAuth 2.0 + PKCE** - 安全认证流程
-- **electron-store** - 持久化配置
-- **自定义协议处理器** - 安全回调处理
-
-## 🏗 架构设计
-
-桌面应用程序采用了复杂的依赖注入和事件驱动架构：
-
-### 📁 核心结构
-
-```
-src/main/core/
-├── App.ts                    # 🎯 主应用程序协调器
-├── IoCContainer.ts           # 🔌 依赖注入容器
-├── window/                   # 🪟 窗口管理模块
-│   ├── WindowThemeManager.ts     # 🎨 主题同步
-│   ├── WindowPositionManager.ts  # 📐 位置持久化
-│   ├── WindowErrorHandler.ts     # ⚠️  错误边界
-│   └── WindowConfigBuilder.ts    # ⚙️  配置构建器
-├── browser/                  # 🌐 浏览器管理模块
-│   ├── Browser.ts               # 🪟 单个窗口实例
-│   └── BrowserManager.ts        # 👥 多窗口协调器
-├── ui/                       # 🎨 UI 系统模块
-│   ├── Tray.ts                  # 📍 系统托盘集成
-│   ├── TrayManager.ts           # 🔧 托盘管理
-│   ├── MenuManager.ts           # 📋 原生菜单系统
-│   └── ShortcutManager.ts       # ⌨️  全局快捷键
-└── infrastructure/           # 🔧 基础设施服务
-    ├── StoreManager.ts          # 💾 配置存储
-    ├── I18nManager.ts           # 🌍 国际化
-    ├── UpdaterManager.ts        # 📦 自动更新系统
-    └── StaticFileServerManager.ts # 🗂️ 本地文件服务
-```
-
-### 🔄 应用程序生命周期
-
-`App.ts` 类通过几个关键阶段协调整个应用程序的生命周期：
-
-#### 1. 🚀 初始化阶段
-
-- **系统信息记录** - 捕获操作系统、CPU、内存和区域设置详细信息
-- **存储管理器设置** - 初始化持久配置存储
-- **动态模块加载** - 通过 glob 导入自动发现控制器和服务
-- **IPC 事件注册** - 设置进程间通信通道
-
-#### 2. 🏃 引导阶段
-
-- **单实例检查** - 确保只运行一个应用程序实例
-- **IPC 服务器启动** - 启动通信服务器
-- **核心管理器初始化** - 按顺序初始化所有管理器：
-  - 🌍 国际化管理器
-  - 📋 原生菜单系统
-  - 🗂️ 本地资源服务器
-  - ⌨️ 全局快捷键注册
-  - 🪟 浏览器窗口管理
-  - 📍 系统托盘（仅 Windows）
-  - 📦 自动更新系统
-
-### 🔧 核心组件深度解析
-
-#### 🌐 浏览器管理系统
-
-- **多窗口架构** - 支持聊天、设置和开发工具窗口
-- **窗口状态管理** - 处理定位、主题和生命周期
-- **WebContents 映射** - WebContents 和标识符之间的双向映射
-- **事件广播** - 向所有或特定窗口的集中事件分发
-
-#### 🔌 依赖注入和事件系统
-
-- **IoC 容器** - 基于 WeakMap 的装饰控制器方法容器
-- **装饰器注册** - `@ipcClientEvent` 和 `@ipcServerEvent` 装饰器
-- **自动事件映射** - 控制器加载期间注册的事件
-- **服务定位器** - 类型安全的服务和控制器检索
-
-#### 🪟 窗口管理
-
-- **主题感知窗口** - 自动适应系统深色 / 浅色模式
-- **平台特定样式** - Windows 标题栏和覆盖自定义
-- **位置持久化** - 跨会话保存和恢复窗口位置
-- **错误边界** - 窗口操作的集中错误处理
-
-#### 🔧 基础设施服务
-
-##### 🌍 国际化管理器
-
-- **18+ 语言支持** 懒加载和命名空间组织
-- **系统集成** 与 Electron 的区域检测集成
-- **动态 UI 刷新** 语言更改时的 UI 更新
-- **资源管理** 高效的加载策略
-
-##### 📦 更新管理器
-
-- **多渠道支持** （稳定版、测试版、每日构建）可配置间隔
-- **后台下载** 进度跟踪和用户通知
-- **回滚保护** 错误处理和恢复机制
-- **渠道管理** 自动渠道切换
-
-##### 💾 存储管理器
-
-- **类型安全存储** 使用带有 TypeScript 接口的 electron-store
-- **加密机密** 通过 Electron 的安全存储 API
-- **配置验证** 默认值管理
-- **文件系统集成** 自动目录创建
-
-##### 🗂️ 静态文件服务器
-
-- **本地 HTTP 服务器** 用于提供应用程序资源和用户文件
-- **安全控制** 请求过滤和访问验证
-- **文件管理** 上传、下载和删除功能
-- **路径解析** 存储位置之间的智能路由
-
-#### 🎨 UI 系统集成
-
-- **全局快捷键** - 平台感知的键盘快捷键注册与冲突检测
-- **系统托盘** - 带有上下文菜单和通知的原生集成
-- **原生菜单** - 带有 i18n 的平台特定应用程序和上下文菜单
-- **主题同步** - 所有 UI 组件的自动主题更新
-
-### 🏛 控制器和服务架构
-
-#### 🎮 控制器模式
-
-- **IPC 事件处理** - 通过基于装饰器的注册处理来自渲染器的事件
-- **生命周期钩子** - 初始化阶段的 `beforeAppReady` 和 `afterAppReady`
-- **类型安全通信** - 所有 IPC 事件和响应的强类型
-- **错误边界** - 具有适当传播的全面错误处理
-
-#### 🔧 服务模式
-
-- **业务逻辑封装** - 关注点的清晰分离
-- **依赖管理** - 通过 IoC 容器管理
-- **跨控制器共享** - 通过服务定位器模式访问的服务
-- **资源管理** - 适当的初始化和清理
-
-### 🔗 进程间通信
-
-#### 📡 IPC 系统功能
-
-- **双向通信** - Main↔Renderer 和 Main↔Next.js 服务器
-- **类型安全事件** - 所有事件参数的 TypeScript 接口
-- **上下文感知** - 事件包含用于窗口特定操作的发送者上下文
-- **错误传播** - 具有适当状态码的集中错误处理
-
-#### 🛡️ 安全功能
-
-- **OAuth 2.0 + PKCE** - 具有状态参数验证的安全认证
-- **加密令牌存储** - 在可用时使用 Electron 的安全存储 API
-- **自定义协议处理器** - OAuth 流程的安全回调处理
-- **请求过滤** - 网络请求和外部链接的安全控制
-
-## 🧪 测试
-
-### 测试结构
-
-```bash
-apps/desktop/src/main/controllers/__tests__/ # 控制器单元测试
-tests/                                       # 集成测试
-```
-
-### 运行测试
-
-```bash
-pnpm test       # 运行所有测试
-pnpm test:watch # 监视模式
-pnpm typecheck  # 类型验证
-```
-
-### 测试覆盖
-
-- **控制器测试** - IPC 事件处理验证
-- **服务测试** - 业务逻辑验证
-- **集成测试** - 端到端工作流测试
-- **类型测试** - TypeScript 接口验证
-
-## 🔒 安全功能
-
-### 认证和授权
-
-- **OAuth 2.0 流程** 使用 PKCE 进行安全令牌交换
-- **状态参数验证** 防止 CSRF 攻击
-- **加密令牌存储** 使用平台原生安全存储
-- **自动令牌刷新** 在失败时回退到重新认证
-
-### 应用程序安全
-
-- **代码签名** - macOS 公证认证以增强安全性
-- **沙盒** - 对系统资源的受控访问
-- **CSP 控制** - 内容安全策略管理
-- **请求过滤** - 外部请求的安全控制
-
-### 数据保护
-
-- **加密配置** - 敏感数据静态加密
-- **安全 IPC** - 类型安全的通信通道
-- **路径验证** - 安全的文件系统访问控制
-- **网络安全** - HTTPS 强制和代理支持
-
-## 🤝 参与贡献
-
-桌面应用程序开发涉及复杂的跨平台考虑和原生集成。我们欢迎社区贡献来改进功能、性能和用户体验。您可以通过以下方式参与改进：
-
-### 如何贡献
-
-1. **平台支持**：增强跨平台兼容性和原生集成
-2. **性能优化**：改进应用程序启动时间、内存使用和响应性
-3. **功能开发**：添加新的桌面特定功能和能力
-4. **错误修复**：修复平台特定问题和边缘情况
-5. **安全改进**：增强安全措施和认证流程
-6. **UI/UX 增强**：改进桌面用户界面和体验
-
-### 贡献流程
-
-1. Fork [LobeChat 仓库](https://github.com/lobehub/lobe-chat)
-2. 按照我们的设置指南建立桌面开发环境
-3. 对桌面应用程序进行修改
-4. 提交 Pull Request 并描述：
-
-- 平台兼容性测试结果
-- 性能影响分析
-- 安全考虑
-- 用户体验改进
-- 破坏性更改（如有）
-
-### 开发领域
-
-- **核心架构**：依赖注入、事件系统和生命周期管理
-- **窗口管理**：多窗口支持、主题同步和状态持久化
-- **IPC 通信**：主进程和渲染进程之间的类型安全进程间通信
-- **平台集成**：原生菜单、快捷键、通知和系统托盘
-- **安全功能**：OAuth 流程、令牌加密和安全存储
-- **自动更新系统**：多渠道更新和回滚机制
-
-## 📚 其他资源
-
-- **开发指南**：[`Development.md`](./Development.md) - 全面的开发文档
-- **架构文档**：[`/docs`](../../docs/) - 详细的技术规范
-- **贡献指南**：[`CONTRIBUTING.md`](../../CONTRIBUTING.md) - 贡献指导
-- **问题和支持**：[GitHub Issues](https://github.com/lobehub/lobe-chat/issues)