test(playwright): probe playwright-cli attach --extension against a real signed-in Chrome on a local machine
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 55/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- playwright, shell
- 领域
- documentation, testing
调研方向
Run the three probes as written: playwright-cli attach --extension=chrome from a Windows shell and from WSL2 against a signed-in Chrome with the Playwright extension installed, plus attach --cdp on a non-default profile with a debug port, recording command, OS/shell, Chrome version and exact error for each. Then read docs/adr/0056-verify-ui-with-linux-side-playwright-and-attach-produced-demo-evidence-to-prs.md (Open items and Alternatives considered) and context/e2e.md under testing:run-e2e to see where the result belongs: a rubric row for the logged-in-session case if a probe passes, otherwise an Alternatives-considered entry with the failure reason. The blocker is access to a local Windows machine with a signed-in Chrome profile — confirm you have that before starting, and check the linked issue comment for maintainer guidance.
由索引模型根据 Issue 内容生成。
描述
Goal
Find out whether @playwright/cli 0.1.22's attach --extension (and attach --cdp) can drive the user's own signed-in Chrome on a local workstation, as a candidate for ADR 0056's "Needs a logged-in session" rubric row (now in testing:run-e2e context/e2e.md).
It cannot be tried from a cloud container: it needs a real Chrome profile with the Playwright browser extension installed, which only exists on a local machine.
What 0.1.22 documents
playwright-cli attach --help:
--cdp connect to an existing browser via cdp endpoint url.
--extension connect to browser extension, optionally specify browser name (e.g. --extension=chrome)
--session session name (defaults to bound browser name or "default")
--idle-timeout detach after this many milliseconds without a command. attached browsers are never detached by default.
Probes (run each and record pass/fail with the exact command and error)
- Windows shell, native Chrome: install the Playwright extension in the signed-in Chrome profile, run
playwright-cli attach --extension=chrome, thengotoa site the profile is signed in to,snapshot, andscreenshot. Does it reuse the signed-in session? What consent prompt appears, and does it need a human click every time? - WSL2 (NAT networking), same Windows Chrome: repeat probe 1 from WSL2. ADR 0056 notes Chrome 136+ ignores remote-debugging switches on the default profile, so
--cdpto the default profile is expected to fail. Check whether--extensiongets around that from WSL2. attach --cdpagainst a separate, non-default Chrome profile started with a debugging port (Windows shell, then WSL2 via the gateway IP). Record what works.
The former probe 4 (agent-browser on WSL2) is dropped: the 2026-10-07 benchmark found no reliability winner and agent-browser was not adopted, so it is no longer a candidate.
Done when
- Each probe has a recorded result (command, OS/shell, Chrome version, outcome, error text).
- If probe 1 or 2 passes, propose a rubric row for the logged-in-session case in
testing:run-e2e(context/e2e.md) and an ADR 0056 note. If both fail, add them to ADR 0056 "Alternatives considered" with the reason.
Related
- ADR 0056 (
docs/adr/0056-verify-ui-with-linux-side-playwright-and-attach-produced-demo-evidence-to-prs.md), Open items: the Claude in Chrome from WSL live test needs the same machine and can run in the same sitting. - melodic-software/claude-code-plugins#6477 (the agent-browser vs playwright-cli benchmark, which deferred
attach --extensionand a Playwright MCP arm to this local probe).
- 主要语言
- Shell
- 星标
- 22
- 派生
- 2
- 平均合并
- 6 小时 58 分钟
- 30 天内合并 PR
- 951
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
melodic-software/claude-code-plugins 的其他 Issue
-
priority: medium status: needs-decision work-class: scoped
难度 2/5 1-3 小时 新手友好度 78/100
melodic-software/claude-code-plugins#9339 · 2 条评论 ·
维护者通常 1 天内回复
-
pipeline-canary priority: low status: ready work-class: mechanical
难度 1/5 1 小时以内 新手友好度 88/100
melodic-software/claude-code-plugins#9263 · 1 条评论 ·
维护者通常 1 天内回复
-
good first issue priority: low
难度 1/5 1 小时以内 新手友好度 90/100
melodic-software/claude-code-plugins#9251 · 1 条评论 ·
维护者通常 1 天内回复
-
area: security needs-triage priority: low
难度 2/5 1-3 小时 新手友好度 79/100
melodic-software/claude-code-plugins#9211 · 1 条评论 ·
维护者通常 1 天内回复
-
priority: low
难度 2/5 1-3 小时 新手友好度 68/100
melodic-software/claude-code-plugins#9202 · 1 条评论 ·
维护者通常 1 天内回复
查看 melodic-software/claude-code-plugins 的全部 Issue
相似的 Issue
-
Python Volcengine provider returns failures instead of raising them可能已有人在做 @Ricardo-M-L 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 79/100
agent-infra/sandbox#248 ·
-
chore priority:low size:S
难度 2/5 1-3 小时 新手友好度 74/100
celo-org/celopedia-skills#98 ·
维护者通常 1 天内回复
-
Git for Windows shouldn't be locked on their `.windows.1` versions可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭git windows
难度 2/5 1-3 小时 新手友好度 78/100
jenkins-infra/packer-images#3179 ·
维护者通常 1 天内回复
-
ready-for-pr
难度 2/5 1-3 小时 新手友好度 72/100
kunchenguid/firstmate#7679 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
MISP/misp-docker#478 ·
维护者通常 1 天内回复