@lobehub/chat 1.141.6 → 1.141.8

package/.github/PULL_REQUEST_TEMPLATE.md

@@ -12,10 +12,36 @@
 - [ ] 📝 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
 
 <!-- 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
 
 <!-- Add any other context about the Pull Request here. -->
+
+<!-- Breaking changes? Migration guide? Performance impact? -->

package/.github/workflows/e2e.yml

@@ -35,18 +35,18 @@ jobs:
                   PORT: 3010
               run: bun run e2e
 
-            - name: Upload Playwright HTML report (on failure)
+            - name: Upload Cucumber HTML report (on failure)
               if: failure()
               uses: actions/upload-artifact@v4
               with:
-                  name: playwright-report
-                  path: playwright-report
+                  name: cucumber-report
+                  path: e2e/reports
                   if-no-files-found: ignore
 
-            - name: Upload Playwright traces (on failure)
+            - name: Upload screenshots (on failure)
               if: failure()
               uses: actions/upload-artifact@v4
               with:
-                  name: test-results
-                  path: test-results
+                  name: test-screenshots
+                  path: e2e/screenshots
                   if-no-files-found: ignore

package/CHANGELOG.md

@@ -2,6 +2,56 @@
 
 # Changelog
 
+### [Version 1.141.8](https://github.com/lobehub/lobe-chat/compare/v1.141.7...v1.141.8)
+
+<sup>Released on **2025-10-23**</sup>
+
+#### 💄 Styles
+
+- **misc**: Improvement for Agent Team After Alpha Launch \[LOB-517].
+
+<br/>
+
+<details>
+<summary><kbd>Improvements and Fixes</kbd></summary>
+
+#### Styles
+
+- **misc**: Improvement for Agent Team After Alpha Launch \[LOB-517], closes [#9748](https://github.com/lobehub/lobe-chat/issues/9748) ([28245be](https://github.com/lobehub/lobe-chat/commit/28245be))
+
+</details>
+
+<div align="right">
+
+[![](https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square)](#readme-top)
+
+</div>
+
+### [Version 1.141.7](https://github.com/lobehub/lobe-chat/compare/v1.141.6...v1.141.7)
+
+<sup>Released on **2025-10-23**</sup>
+
+#### 💄 Styles
+
+- **misc**: Allow removal of `top_p` and similar request parameters.
+
+<br/>
+
+<details>
+<summary><kbd>Improvements and Fixes</kbd></summary>
+
+#### Styles
+
+- **misc**: Allow removal of `top_p` and similar request parameters, closes [#9498](https://github.com/lobehub/lobe-chat/issues/9498) ([4c313ce](https://github.com/lobehub/lobe-chat/commit/4c313ce))
+
+</details>
+
+<div align="right">
+
+[![](https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square)](#readme-top)
+
+</div>
+
 ### [Version 1.141.6](https://github.com/lobehub/lobe-chat/compare/v1.141.5...v1.141.6)
 
 <sup>Released on **2025-10-22**</sup>

package/changelog/v1.json

@@ -1,4 +1,22 @@
 [
+  {
+    "children": {
+      "improvements": [
+        "Improvement for Agent Team After Alpha Launch [LOB-517]."
+      ]
+    },
+    "date": "2025-10-23",
+    "version": "1.141.8"
+  },
+  {
+    "children": {
+      "improvements": [
+        "Allow removal of top_p and similar request parameters."
+      ]
+    },
+    "date": "2025-10-23",
+    "version": "1.141.7"
+  },
   {
     "children": {},
     "date": "2025-10-22",

package/docs/usage/features/{group-chat.mdx → agent-team.mdx}

@@ -1,26 +1,26 @@
 ---
-title: Group Chat
+title: Agent Team
 description: Turn any conversation into a team effort. Multiple AI agents collaborate naturally to give you richer, more insightful responses.
 tags:
-  - Group Chat
+  - Agent Team
   - Multi-Agent
   - AI Orchestration
   - Agent Coordination
 ---
 
-# Group Chat
+# Agent Team
 
-<Image alt={'Group Chat'} cover src={'https://github.com/user-attachments/assets/6e5599f6-1e39-4b14-a218-4f5ffa2c306a'} />
+<Image alt={'Agent Team'} cover src={'https://github.com/user-attachments/assets/6e5599f6-1e39-4b14-a218-4f5ffa2c306a'} />
 
-Sometimes one perspective isn't enough. Group Chat brings together multiple AI agents, each with their own expertise, to collaborate on your conversations. Richer discussions, diverse viewpoints, and solutions you wouldn't get from any single agent.
+Sometimes one perspective isn't enough. Agent Team brings together multiple AI agents, each with their own expertise, to collaborate on your conversations. Richer discussions, diverse viewpoints, and solutions you wouldn't get from any single agent.
 
 ## Highlights
 
 - Multiple assistants with specialized knowledge work together, each contributing their strengths
-- A built-in host ensures the group chat runs smoothly and organized
+- A built-in host ensures the agent team conversation runs smoothly and organized
 - Private messaging allows seamless coordination between assistants
 - You get comprehensive answers from multiple perspectives
-- Ready to use with your own assistants or rich group chat team templates
+- Ready to use with your own assistants or rich agent team templates
 
 ## Use Cases
 
@@ -30,23 +30,23 @@ Sometimes one perspective isn't enough. Group Chat brings together multiple AI a
 
 **Brainstorming**: Diverse perspectives spark better ideas.
 
-**Problem Solving**: Benefit from insights across different professional fields, with different tools and MCPs, group chat allows you to have the perfect AI team.
+**Problem Solving**: Benefit from insights across different professional fields, with different tools and MCPs, agent team allows you to have the perfect AI team.
 
 ## Quick Start
 
-Click the "Create Group Chat" button, you can choose to create directly from preset group chat templates, or select your own assistants to form a group chat.
+Click the "Create Agent Team" button, you can choose to create directly from preset agent team templates, or select your own assistants to form an agent team.
 
-You can use @ to mention a group member in the group chat, or click their avatar to send them a private message. Everything works just like in a real chat room.
+You can use @ to mention a team member in the agent team, or click their avatar to send them a private message. Everything works just like in a real chat room.
 
-### Interrupt and Resume Group Chat
+### Interrupt and Resume Agent Team
 
-You can interrupt the host's thinking at any time, and the group chat will "pause" after interruption. You can start the moderator at any time, and the group chat will continue.
+You can interrupt the host's thinking at any time, and the agent team will "pause" after interruption. You can start the moderator at any time, and the agent team will continue.
 
 Of course, conversations may also stop naturally.
 
 ### Advanced Options
 
-- Group Chat Speed: Customize the response speed of the group chat
+- Agent Team Speed: Customize the response speed of the agent team
 - Custom Moderator: Guide the moderator's behavior according to specific needs
 
-Group Chat transforms how you interact with AI. Instead of getting one answer, you participate in a conversation—complete with different viewpoints, collaborative problem-solving, and profound insights that emerge when AI agents work together.
+Agent Team transforms how you interact with AI. Instead of getting one answer, you participate in a conversation—complete with different viewpoints, collaborative problem-solving, and profound insights that emerge when AI agents work together.

package/docs/usage/features/agent-team.zh-CN.mdx

@@ -0,0 +1,52 @@
+---
+title: Agent 团队
+description: 让对话变成团队协作。多个 AI 智能体自然配合，为你提供更丰富、更有洞察力的回答。
+tags:
+  - 群组对话
+  - 多智能体
+  - AI 编排
+  - 智能体协调
+---
+
+# Agent 团队
+
+<Image alt={'Agent 团队'} cover src={'https://github.com/user-attachments/assets/6e5599f6-1e39-4b14-a218-4f5ffa2c306a'} />
+
+有时候，一个视角远远不够。Agent 团队功能让多个拥有不同知识和技能的 AI 智能体聚在一起，协作参与你的对话。更丰富的讨论、多元的观点，以及任何单一智能体都无法提供的解决方案。
+
+## 亮点
+
+- 多个具有专业知识的助手协同工作，各取所长
+- 团队内置的主持人将确保整个团队聊天有条不紊的进行
+- 私信功能让助手间无缝协调配合
+- 你将从多个视角获得全面的答案
+- 开箱即用，由你自己的助手组成，或者使用丰富的团队模版
+
+## 适用场景
+
+**学习研究**：不同的助手通过不同的工具收集不同的资料，汇聚一处并自发讨论。
+
+**娱乐**：狼人杀、模拟联合国、海龟汤等多人语聊游戏。
+
+**头脑风暴**：多元观点激发更好的想法。
+
+**问题解决**：受益于不同专业领域的见解，以及不同的工具和 MCP，Agent 团队允许你拥有完美的 AI 团队。
+
+## 快速开始
+
+点击「创建 Agent 团队」按钮，你可以选择直接从预设的团队模版创建，或选择你自己的助手组成团队。
+
+你可以在团队聊天中输入 @ 来提及某个成员，或者点击他们的头像对其私聊。一切就像是在真实的聊天室中一样。
+
+### 中断与继续团队聊天
+
+你可以随时打断主持人的思考，打断后团队聊天将会「暂停」。你可以随时开启主持人，团队聊天便会继续。
+
+当然，对话也有可能自然地停止。
+
+### 高级选项
+
+- 团队速度：自定义团队的回答速度
+- 自定义主持人：根据特定需要指导主持人的行为
+
+Agent 团队改变了你与 AI 的互动方式。不再是获得一个答案，而是参与一场对话 —— 包含不同观点、协作解决问题，以及 AI 智能体协同工作时产生的深刻洞察。

package/e2e/README.md

@@ -0,0 +1,143 @@
+# E2E Tests for LobeChat
+
+This directory contains end-to-end (E2E) tests for LobeChat using Cucumber (BDD) and Playwright.
+
+## Directory Structure
+
+````
+e2e/
+├── src/               # Source files
+│   ├── features/      # Gherkin feature files
+│   │   └── discover/  # Discover page tests
+│   ├── steps/         # Step definitions
+│   │   ├── common/    # Reusable step definitions
+│   │   └── discover/  # Discover-specific steps
+│   └── support/       # Test support files
+│       └── world.ts   # Custom World context
+├── reports/           # Test reports (generated)
+├── cucumber.config.js # Cucumber configuration
+├── tsconfig.json      # TypeScript configuration
+└── package.json       # Dependencies and scripts
+
+## Prerequisites
+
+- Node.js 20, 22, or >=24
+- Dev server running on `http://localhost:3010` (or set `BASE_URL` env var)
+
+## Installation
+
+Install dependencies:
+
+```bash
+cd e2e
+pnpm install
+````
+
+Install Playwright browsers:
+
+```bash
+npx playwright install chromium
+```
+
+## Running Tests
+
+Run all tests:
+
+```bash
+npm test
+```
+
+Run tests in headed mode (see browser):
+
+```bash
+npm run test:headed
+```
+
+Run only smoke tests:
+
+```bash
+npm run test:smoke
+```
+
+Run discover tests:
+
+```bash
+npm run test:discover
+```
+
+## Environment Variables
+
+- `BASE_URL`: Base URL for the application (default: `http://localhost:3010`)
+- `PORT`: Port number (default: `3010`)
+- `HEADLESS`: Run browser in headless mode (default: `true`, set to `false` to see browser)
+
+Example:
+
+```bash
+HEADLESS=false BASE_URL=http://localhost:3000 npm run test:smoke
+```
+
+## Writing Tests
+
+### Feature Files
+
+Feature files are written in Gherkin syntax and placed in the `src/features/` directory:
+
+```gherkin
+@discover @smoke
+Feature: Discover Smoke Tests
+  Critical path tests to ensure the discover module is functional
+
+  @DISCOVER-SMOKE-001 @P0
+  Scenario: Load discover assistant list page
+    Given I navigate to "/discover/assistant"
+    Then the page should load without errors
+    And I should see the page body
+    And I should see the search bar
+    And I should see assistant cards
+```
+
+### Step Definitions
+
+Step definitions are TypeScript files in the `src/steps/` directory that implement the steps from feature files:
+
+```typescript
+import { Given, Then } from '@cucumber/cucumber';
+import { expect } from '@playwright/test';
+
+import { CustomWorld } from '../../support/world';
+
+Given('I navigate to {string}', async function (this: CustomWorld, path: string) {
+  await this.page.goto(path);
+  await this.page.waitForLoadState('domcontentloaded');
+});
+```
+
+## Test Reports
+
+After running tests, HTML and JSON reports are generated in the `reports/` directory:
+
+- `reports/cucumber-report.html` - Human-readable HTML report
+- `reports/cucumber-report.json` - Machine-readable JSON report
+
+## Troubleshooting
+
+### Browser not found
+
+If you see errors about missing browser executables:
+
+```bash
+npx playwright install chromium
+```
+
+### Port already in use
+
+Make sure the dev server is running on the expected port (3010 by default), or set `PORT` or `BASE_URL` environment variable.
+
+### Test timeout
+
+Increase timeout in `cucumber.config.js` or `src/steps/hooks.ts`:
+
+```typescript
+setDefaultTimeout(120000); // 2 minutes
+```

package/e2e/cucumber.config.js

@@ -0,0 +1,20 @@
+/**
+ * @type {import('@cucumber/cucumber').IConfiguration}
+ */
+export default {
+  format: [
+    'progress-bar',
+    'html:reports/cucumber-report.html',
+    'json:reports/cucumber-report.json',
+  ],
+  formatOptions: {
+    snippetInterface: 'async-await',
+  },
+  parallel: process.env.CI ? 1 : 4,
+  paths: ['src/features/**/*.feature'],
+  publishQuiet: true,
+  require: ['src/steps/**/*.ts', 'src/support/**/*.ts'],
+  requireModule: ['tsx/cjs'],
+  retry: 0,
+  timeout: 120_000,
+};

package/e2e/package.json

@@ -0,0 +1,24 @@
+{
+  "name": "@lobechat/e2e-tests",
+  "version": "0.1.0",
+  "private": true,
+  "description": "E2E tests for LobeChat using Cucumber and Playwright",
+  "scripts": {
+    "test": "cucumber-js --config cucumber.config.js",
+    "test:discover": "cucumber-js --config cucumber.config.js src/features/discover/",
+    "test:headed": "HEADLESS=false cucumber-js --config cucumber.config.js",
+    "test:routes": "cucumber-js --config cucumber.config.js --tags '@routes'",
+    "test:routes:ci": "cucumber-js --config cucumber.config.js --tags '@routes and not @ci-skip'",
+    "test:smoke": "cucumber-js --config cucumber.config.js --tags '@smoke'"
+  },
+  "dependencies": {
+    "@cucumber/cucumber": "^12.2.0",
+    "@playwright/test": "^1.56.1",
+    "playwright": "^1.56.1"
+  },
+  "devDependencies": {
+    "@types/node": "^22.10.5",
+    "tsx": "^4.20.6",
+    "typescript": "^5.7.3"
+  }
+}

package/e2e/src/features/discover/smoke.feature

@@ -0,0 +1,11 @@
+@discover @smoke
+Feature: Discover Smoke Tests
+  Critical path tests to ensure the discover module is functional
+
+  @DISCOVER-SMOKE-001 @P0
+  Scenario: Load discover assistant list page
+    Given I navigate to "/discover/assistant"
+    Then the page should load without errors
+    And I should see the page body
+    And I should see the search bar
+    And I should see assistant cards

package/e2e/src/features/routes/core-routes.feature

@@ -0,0 +1,43 @@
+@routes @smoke
+Feature: Core Routes Accessibility
+  As a user
+  I want all core application routes to be accessible
+  So that I can navigate the application without errors
+
+  Background:
+    Given the application is running
+
+  @ROUTES-001 @P0
+  Scenario Outline: Access core routes without errors
+    When I navigate to "<route>"
+    Then the response status should be less than 400
+    And the page should load without errors
+    And I should see the page body
+    And the page title should not contain "error" or "not found"
+
+    Examples:
+      | route      |
+      | /          |
+      | /chat      |
+      | /discover  |
+      | /files     |
+      | /repos     |
+
+  @ROUTES-002 @P0
+  Scenario Outline: Access settings routes without errors
+    When I navigate to "/settings?active=<tab>"
+    Then the response status should be less than 400
+    And the page should load without errors
+    And I should see the page body
+    And the page title should not contain "error" or "not found"
+
+    Examples:
+      | tab          |
+      | about        |
+      | agent        |
+      | hotkey       |
+      | provider     |
+      | proxy        |
+      | storage      |
+      | system-agent |
+      | tts          |

package/e2e/src/steps/common/navigation.steps.ts

@@ -0,0 +1,36 @@
+import { Given, Then } from '@cucumber/cucumber';
+import { expect } from '@playwright/test';
+
+import { CustomWorld } from '../../support/world';
+
+// ============================================
+// Given Steps (Preconditions)
+// ============================================
+
+Given('I navigate to {string}', async function (this: CustomWorld, path: string) {
+  const response = await this.page.goto(path, { waitUntil: 'commit' });
+  this.testContext.lastResponse = response;
+  await this.page.waitForLoadState('domcontentloaded');
+});
+
+// ============================================
+// Then Steps (Assertions)
+// ============================================
+
+Then('the page should load without errors', async function (this: CustomWorld) {
+  // Check for no JavaScript errors
+  expect(this.testContext.jsErrors).toHaveLength(0);
+
+  // Check page didn't navigate to error page
+  const url = this.page.url();
+  expect(url).not.toMatch(/\/404|\/error|not-found/i);
+
+  // Check no error title
+  const title = await this.page.title();
+  expect(title).not.toMatch(/not found|error/i);
+});
+
+Then('I should see the page body', async function (this: CustomWorld) {
+  const body = this.page.locator('body');
+  await expect(body).toBeVisible();
+});

package/e2e/src/steps/discover/smoke.steps.ts

@@ -0,0 +1,34 @@
+import { Then } from '@cucumber/cucumber';
+import { expect } from '@playwright/test';
+
+import { CustomWorld } from '../../support/world';
+
+// ============================================
+// Then Steps (Assertions)
+// ============================================
+
+Then('I should see the search bar', async function (this: CustomWorld) {
+  // Wait for network to be idle to ensure Suspense components are loaded
+  await this.page.waitForLoadState('networkidle', { timeout: 120_000 });
+
+  // The SearchBar component from @lobehub/ui may not pass through data-testid
+  // Try to find the input element within the search component
+  const searchBar = this.page.locator('input[type="text"]').first();
+  await expect(searchBar).toBeVisible({ timeout: 120_000 });
+});
+
+Then('I should see assistant cards', async function (this: CustomWorld) {
+  // Wait for content to load
+  await this.page.waitForLoadState('networkidle', { timeout: 120_000 });
+
+  // After migrating to SPA (react-router), links use relative paths like /assistant/:id
+  // Look for assistant items by data-testid instead of href
+  const assistantItems = this.page.locator('[data-testid="assistant-item"]');
+
+  // Wait for at least one item to be visible
+  await expect(assistantItems.first()).toBeVisible({ timeout: 120_000 });
+
+  // Check we have multiple items
+  const count = await assistantItems.count();
+  expect(count).toBeGreaterThan(0);
+});

package/e2e/src/steps/hooks.ts

@@ -0,0 +1,69 @@
+import { After, AfterAll, Before, BeforeAll, Status, setDefaultTimeout } from '@cucumber/cucumber';
+
+import { startWebServer, stopWebServer } from '../support/webServer';
+import { CustomWorld } from '../support/world';
+
+// Set default timeout for all steps to 120 seconds
+setDefaultTimeout(120_000);
+
+BeforeAll({ timeout: 120_000 }, async function () {
+  console.log('🚀 Starting E2E test suite...');
+
+  const PORT = process.env.PORT ? Number(process.env.PORT) : 3010;
+  const BASE_URL = process.env.BASE_URL || `http://localhost:${PORT}`;
+
+  console.log(`Base URL: ${BASE_URL}`);
+
+  // Start web server if not using external BASE_URL
+  if (!process.env.BASE_URL) {
+    await startWebServer({
+      command: 'npm run dev',
+      port: PORT,
+      reuseExistingServer: !process.env.CI,
+    });
+  }
+});
+
+Before(async function (this: CustomWorld, { pickle }) {
+  await this.init();
+
+  const testId = pickle.tags.find((tag) => tag.name.startsWith('@DISCOVER-'));
+  console.log(`\n📝 Running: ${pickle.name}${testId ? ` (${testId.name.replace('@', '')})` : ''}`);
+});
+
+After(async function (this: CustomWorld, { pickle, result }) {
+  const testId = pickle.tags
+    .find((tag) => tag.name.startsWith('@DISCOVER-'))
+    ?.name.replace('@', '');
+
+  if (result?.status === Status.FAILED) {
+    const screenshot = await this.takeScreenshot(`${testId || 'failure'}-${Date.now()}`);
+    this.attach(screenshot, 'image/png');
+
+    const html = await this.page.content();
+    this.attach(html, 'text/html');
+
+    if (this.testContext.jsErrors.length > 0) {
+      const errors = this.testContext.jsErrors.map((e) => e.message).join('\n');
+      this.attach(`JavaScript Errors:\n${errors}`, 'text/plain');
+    }
+
+    console.log(`❌ Failed: ${pickle.name}`);
+    if (result.message) {
+      console.log(`   Error: ${result.message}`);
+    }
+  } else if (result?.status === Status.PASSED) {
+    console.log(`✅ Passed: ${pickle.name}`);
+  }
+
+  await this.cleanup();
+});
+
+AfterAll(async function () {
+  console.log('\n🏁 Test suite completed');
+
+  // Stop web server if we started it
+  if (!process.env.BASE_URL && process.env.CI) {
+    await stopWebServer();
+  }
+});