openwork-chrome-mcp-testing
Use Chrome MCP to verify OpenWork UI flows, especially any feature that touches remote behavior. Triggers when user mentions: - "test with chrome mcp" - "ui verification" - "remote behavior test"
소스 정보
- 저장소
- different-ai/openwork-hub
- 최근 소스 활동
- 2026년 2월 11일 01:43
- 감지된 SKILL.md 언어
- 영어
- 스타
- 34
- 포크
- 13
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
파일 탐색기
3 개 파일SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- openwork-chrome-mcp-testing
- description
- Use Chrome MCP to verify OpenWork UI flows, especially any feature that touches remote behavior. Triggers when user mentions: - "test with chrome mcp" - "ui verification" - "remote behavior test"
## Quick Usage (Already Configured)
### 1) Start headless + web UI
Start the OpenWork dev stack via Docker and open the UI:
- Use `skills/openwork-docker-chrome-mcp/SKILL.md` step 1.
- Confirm the Web UI loads and a session/chat view is accessible.
### 2) Test the feature in the UI
- Navigate to the relevant screen.
- Perform the feature flow end-to-end.
- If the change touches remote behavior, verify the remote effect is visible in the UI.
### 3) Capture evidence
- Take a Chrome MCP snapshot.
- Pull console logs with Chrome MCP.
- Attach logs if something fails:
- capture Chrome console output via Chrome MCP
- optionally capture Docker logs for the dev stack
## Required Gate (Non-Negotiable)
- Any feature that changes remote behavior MUST be validated through Chrome MCP.
- The feature is NOT done until the UI action succeeds in the browser via Chrome MCP.
- If Chrome MCP validation is skipped, the change is considered incomplete and must not be merged.
## Common Gotchas
- If OpenCode Engine stays disconnected, ensure the OpenWork URL is clean and the client token is correct.
- If you see CORS errors, check OpenWork server CORS headers for custom OpenCode headers.
GitHub에서 보기