test(playwright): probe playwright-cli attach --extension against a real signed-in Chrome on a local machine
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 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
- 平均マージ
- 5時間 15分
- マージ済み PR（30日）
- 833
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
melodic-software/claude-code-plugins のほかの issue
-
good first issue needs-triage priority: medium
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
melodic-software/claude-code-plugins#6631 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
needs-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
melodic-software/claude-code-plugins#6547 ·
メンテナーはふだん 1 日以内に返信
-
needs-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
melodic-software/claude-code-plugins#6535 ·
メンテナーはふだん 1 日以内に返信
-
test_comment_census.py: SccArgv flag-shaped-filename test errors on Windows (#!/bin/sh scc shim)オープンgood first issue needs-triage priority: low
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
melodic-software/claude-code-plugins#6532 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
good first issue needs-triage priority: low
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
melodic-software/claude-code-plugins#6390 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
melodic-software/claude-code-plugins の issue をすべて見る
似ている issue
-
good first issue need help packaging
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
phonology024/babelscribe#23 ·
-
難易度 1/5 1時間未満 初心者へのやさしさ 85/100
influxdata/openapi#660 ·
-
難易度 1/5 1時間未満 初心者へのやさしさ 85/100
メンテナーはふだん 1 日以内に返信
-
documentation
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
メンテナーはふだん 3 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
tornadoweb/tornado#3781 ·
メンテナーはふだん 1 日以内に返信