从当前安装包查询 Cherry Studio 产品信息并排查运行问题。当用户询问功能、路由、快捷键、Provider、语言、Agent、频道、定时任务、Code CLI、当前版本,或报告运行错误、连接失败、配置异常并需要诊断时触发。
日本語の概要は準備中です。原文の説明を表示しています。
Run Cherry Studio critical-path system regression tasks through the repository-owned Playwright E2E workflow. Use for full regression, release acceptance, development-branch system validation, or a named cherry-regression-test task on GitHub-hosted macOS and Windows runners.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Run deterministic Playwright E2E tests against one driver-owned Cherry Studio process per platform. The tested product includes Chat, Agents, MCP, Skills, knowledge bases, translation, image generation, and code tools; an LLM test agent does not control the test run.
Use .github/workflows/e2e-regression-test.yml as the entry point. It:
tests/e2e/regression/ from simple to complex.Do not add an LLM tool loop, MCP control server, turn limit, or a second Electron launch for each test. A restart is allowed only where the case contract explicitly verifies persistence or switches from the clean startup profile to the authenticated shared profile.
The workflow reads these repository variables and secrets:
CHERRY_TEST_CUSTOM_PROVIDER_BASE_URLCHERRY_TEST_CUSTOM_PROVIDER_ANTHROPIC_BASE_URLCHERRY_TEST_CUSTOM_PROVIDER_API_KEYCHERRY_TEST_CUSTOM_PROVIDER_CHAT_MODELCHERRY_TEST_CUSTOM_PROVIDER_EMBEDDING_BASE_URLCHERRY_TEST_CUSTOM_PROVIDER_EMBEDDING_API_KEYCHERRY_TEST_CUSTOM_PROVIDER_EMBEDDING_MODELCHERRY_TEST_CHERRYIN_CHAT_MODELCHERRY_TEST_CHERRYIN_IMAGE_MODELCHERRY_TEST_CHERRYIN_ACCOUNTCHERRY_TEST_CHERRYIN_PASSWORDThe custom chat provider requires both URLs: CHERRY_TEST_CUSTOM_PROVIDER_BASE_URL
fills OpenAI, and CHERRY_TEST_CUSTOM_PROVIDER_ANTHROPIC_BASE_URL fills Anthropic.
Both endpoints share CHERRY_TEST_CUSTOM_PROVIDER_API_KEY.
Chat and embedding providers are independent. Never print literal credentials, write them to fixtures, attach them to Playwright artifacts, or pass them to an unrelated action.
Read scenario organization and the controller contract before making changes.
Register each case from the manifest:
test(...caseDefinition('S-01'), async ({ mainWindow }) => {
// Assert the user-visible outcome.
})
cases.ts owns case IDs, titles, task tags, phases, and capability requirements.
The workflow accepts a task ID and delegates selection to the controller.
Prefer accessible roles, labels, placeholders, test IDs,
and visible text. Native dialogs and cross-application interactions must use
the repository-owned helpers in systemAutomation.ts.
Record assertions in Playwright, not prose. The custom reporter writes case and phase
status into run.json and feeds the English Markdown/JUnit reports. The fixture
saves failure screenshots. Executor errors and interrupted phases block a passing verdict. Do not enable Playwright Trace for credential-bearing
tests because action parameters can expose secrets. A passing result does not
depend on a model's judgment.
With an initialized run directory and its owned Electron process running:
pnpm exec tsx scripts/e2e/regression/cli.ts run-phase \
--run-dir /absolute/run-directory --phase 02-basic-features
The task selected when initializing the run determines which cases execute.
For a Notes-only run, initialize with --task notes. Enumeration is read-only:
set CHERRY_TEST_RUN_DIR to an absolute path, but no initialized run directory
or running Electron process is required because --list does not execute fixtures.
CHERRY_TEST_RUN_DIR=/tmp/cherry-regression-list pnpm test:e2e:regression --list
Do not call the regression cleanup command for an Electron instance owned by
cherry-electron-dev; cleanup is only for an app record created by this driver.
Run the focused script suite and enumerate Playwright cases:
pnpm exec vitest run --project scripts scripts/e2e/regression
CHERRY_TEST_RUN_DIR=/tmp/cherry-regression-list \
pnpm test:e2e:regression --list
pnpm typecheck:e2e
pnpm test:lint
Do not use pnpm test or pnpm build:check for this focused workflow change.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
从当前安装包查询 Cherry Studio 产品信息并排查运行问题。当用户询问功能、路由、快捷键、Provider、语言、Agent、频道、定时任务、Code CLI、当前版本,或报告运行错误、连接失败、配置异常并需要诊断时触发。
日本語の概要は準備中です。原文の説明を表示しています。
Interact with the user's visible Agent browser in Cherry Studio. Use for page navigation, authenticated websites, screenshots, forms, clicks, and browser debugging. Check live browser tools first; browser control requires the Browser setting and an available Agent pane.
日本語の概要は準備中です。原文の説明を表示しています。
Develop, fix, and profile Cherry Studio in a tracked Electron instance. Use for everyday implementation, UI and interaction work, bug fixing, runtime debugging, DevTools inspection, lag or jank investigation, CPU and memory monitoring, leak checks, and startup-performance analysis; reuse a verified workspace instance across instructions and launch or replace one only when required.
日本語の概要は準備中です。原文の説明を表示しています。
Test Cherry Studio PRs by resolving and checking out a PR, statically inspecting its changes, running interactive UI tests against a safely tracked Electron instance through CDP, producing a structured report, cleaning up only the owned test instance, and restoring the original branch.
日本語の概要は準備中です。原文の説明を表示しています。
当用户明确要求搜索、安装、查看、卸载或创建 Skill,或内置 Skill / 工具出现能力缺口、无法完成当前任务时触发。通过 `mcp__skills__search_skills` 搜索并用 `mcp__skills__install_skill` 安装;已安装 Skill 的查看和删除通过产品清单导航到 Skills UI;没有合适结果时调用内置 `skill-creator` 创建并验证自定义 Skill,再继续原任务。普通任务仍先尝试内置能力。
日本語の概要は準備中です。原文の説明を表示しています。
Use when Cherry Studio 用户希望报告、提交或整理 BUG、UI/UX 问题或功能建议,但未明确要求创建 GitHub Issue。
日本語の概要は準備中です。原文の説明を表示しています。