jin-playwright-mcp
Inspect and exercise the Jin GUI through the repository's deterministic Playwright MCP setup. Use for browser-driven GUI investigation, interaction checks, console inspection, or reproducible local frontend verification; do not use it as proof of native Tauri behavior.
- License 许可
- AGPL-3.0
- 所属仓库
- Rynaro/jin
- 最近更新
- 2026-11-03
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- jin-playwright-mcp
- description
- Inspect and exercise the Jin GUI through the repository's deterministic Playwright MCP setup. Use for browser-driven GUI investigation, interaction checks, console inspection, or reproducible local frontend verification; do not use it as proof of native Tauri behavior.
03 SKILL.md 正文
Jin Playwright MCP
Use the repository-registered playwright MCP against the existing Vite dev server.
Start the application
- From the repository root, run
npm --prefix jin-gui run dev:agentand leave it running. - Navigate only to
http://127.0.0.1:1420. The MCP network allowlist rejects other origins. - If the MCP is absent after configuration changed, restart the agent/client so it reloads
.mcp.jsonor.codex/config.toml.
The browser is headless, isolated, UTC, en-US, fixed at 1280×800, and uses reduced motion. jin-gui/tools/tauri-fixture-init.js supplies deterministic tasks, notes, folders, and basic shell responses. It installs only on the local Vite origin and does not replace a real Tauri bridge.
Work with the page
- Begin with an accessibility snapshot and inspect browser console errors before interacting.
- Prefer roles, accessible names, labels, and test ids over CSS selectors or coordinates.
- Re-snapshot after navigation or state changes instead of reusing stale element references.
- Treat
Unsupported Jin fixture commandas an explicit harness gap. Do not hide it with a permissive fallback; extend the fixture only when the task requires that command and its deterministic result is known. - Save screenshots, traces, and other MCP output under
.artifacts/playwright-mcp/.
This harness validates the web frontend with a mock command bridge. It does not exercise the native Tauri runtime, filesystem, jin-core, OAuth, or platform rendering.