client-smoke: drive the Inspector web UI with Playwright instead of calling it hand-only
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript, playwright
- Domain
- documentation, testing
Research direction
Find the client-smoke skill and update its Inspector web UI section using the launch, connection, select, result, elicitation, isolation, and era details in the issue. Start by checking the existing CLI recipe for its Inspector and Playwright version pins. Done when the web UI instructions provide a pinned Playwright recipe that covers both protocol eras and their stated differences.
Written by the indexing model from the issue text.
Description
The client-smoke skill says the Inspector web UI is "the hand-driven path. It needs a person at a browser; this repo configures no browser automation". So an agent defers elicitation, sampling, URL-elicitation, progress and tasks checks to a maintainer. During the v2.0.0 release, that left those round-trips unverified and listed as a ledger finding.
They don't need a person. The v2.0.0 ledger drove Inspector 2.11.0's web UI with Playwright (headless Chromium) in both eras: 11 scenarios in legacy and 15 in modern, including the tasks tools.
Change
Replace the web UI section's "by hand" framing with a Playwright recipe:
- Launch: start
--web --protocol-era legacy|modern, and read the tokenized URL from stdout. - Connect: the Mantine switch needs
check({ force: true }). Screen tabs are reached by clickinglabel[for$="-Tools"]. - Selects: a Mantine Select is read-only. Click it, then press ArrowDown and Enter.
- Results: the panel's heading is "Results", or "Tool Call Failed" for a tool error.
- URL elicitation: "I've completed it" appears only after "Open in Browser", which opens a popup page.
- Multi-step elicitation: the open dialog is reused between steps, so wait for its text to change, not for it to close.
- Isolation: use one fresh page and connection per scenario.
- Era differences: in legacy,
trigger-url-elicitation errorPath=trueshows two dialogs (the -32042 path, then the retry). Modern shows one.
Keep the version pins (Inspector, Playwright) in the recipe, as the CLI section does.
- Dominant language
- JavaScript
- Stars
- 91.2k
- Forks
- 11.8k
- Avg merge
- 7h 51m
- Merged PRs (30d)
- 121
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from modelcontextprotocol/servers
-
documentation v2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
modelcontextprotocol/servers#5164 ·
Maintainers usually reply within 1 day
-
memory: persistence EISDIR test fails on Node 26.7 (the path suffix depends on the Node minor, not the major)Possibly taken @ace-ify claimed this today. Openbug server-memory v2
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
modelcontextprotocol/servers#5162 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
modelcontextprotocol/servers#5156 ·
Maintainers usually reply within 1 day
-
memory: create_entities, create_relations and add_observations could declare idempotentHint: truePossibly taken @syedmustafan claimed this 1 day ago. Openenhancement v2
Difficulty 1/5 Under an hour Newbie friendliness 78/100
modelcontextprotocol/servers#5153 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
modelcontextprotocol/servers#5134 · 1 comment ·
Maintainers usually reply within 1 day
All issues in modelcontextprotocol/servers
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SwiftKickMobile/skai#84 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Billionmail/BillionMail#389 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Uniswap/tokenlists-org#3331 ·
-
beginner-friendly category:finding-titles community enhancement first-timers-only good first issue hacktoberfest help wanted low hanging fruit micro-contribution type: task up-for-grabs
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
Berserk-hub150/skillhawk#227 · 1 comment ·
Maintainers usually reply within 8 days
-
Remove responsibilities not working in Custom Roles & BadgesPossibly taken @thomasgwatson claimed this today. Openagent-ready agent:needs-test
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days