Codex marketplace registration succeeds, but Webwright does not appear in /plugins
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 64/100
Línea de trabajo
Comienza con los archivos existentes .claude-plugin/marketplace.json, .codex-plugin/plugin.json y skills/webwright/SKILL.md; después revisa la convención indicada de .agents/plugins/marketplace.json y la ruta verificada plugins/webwright. Ejecuta los comandos marketplace add, list e install mencionados en la issue; estará hecho cuando Webwright aparezca en la lista y en /plugins, y se instale con su skill disponible.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
codex plugin marketplace add microsoft/Webwright succeeds, but Webwright does not appear in codex plugin list or /plugins, so it cannot be installed from the Codex marketplace flow documented in the README.
@n-seiji has reviewed and confirmed all of the issue details below.
Environment
- Repository:
microsoft/Webwright - Tested upstream commit:
734bc60ea73653498215694d0cc4bc96fbc09e9c - Codex CLI:
codex-cli 0.134.0 - Date tested: 2026-05-30
Reproduction
codex plugin marketplace add microsoft/Webwright
codex plugin list | rg -i webwright
codex plugin add webwright@webwright
Actual behavior
The marketplace is registered successfully, but no Webwright plugin is listed.
codex plugin add webwright@webwright fails because the plugin cannot be found in the marketplace.
The current repository contains:
.claude-plugin/marketplace.json
.claude-plugin/plugin.json
.codex-plugin/plugin.json
skills/webwright/SKILL.md
but it does not contain a Codex marketplace index at:
.agents/plugins/marketplace.json
Expected behavior
After adding the marketplace, Webwright should appear in codex plugin list and /plugins, and it should be installable with Codex.
Investigation
From the local Codex plugin creator guidance and bundled marketplace examples, Codex repo/team marketplaces are expected to expose a marketplace index at:
.agents/plugins/marketplace.json
The marketplace entries commonly point to plugin roots using:
./plugins/<plugin-name>
The plugin root then contains:
.codex-plugin/plugin.json
I also tested more direct root paths such as . and ./, but those did not make the plugin discoverable. This appears related to the Codex behavior discussed in openai/codex#17066, where root plugin source paths are not accepted as expected.
Verified workaround
I verified a fork-based fix using:
.agents/plugins/marketplace.json
plugins/webwright -> ..
The marketplace entry points to:
./plugins/webwright
Because plugins/webwright is a symlink to the repository root, the existing files remain authoritative:
.codex-plugin/plugin.json
skills/webwright/SKILL.md
This avoids duplicating the skills/webwright tree under plugins/webwright/skills/webwright.
With that layout, the following worked locally:
codex plugin marketplace add n-seiji/Webwright
codex plugin list | rg -i webwright
codex plugin add webwright@webwright
The installed cache included:
skills/webwright/SKILL.md
Suggested fix
Add a Codex marketplace index and expose the existing plugin root through a ./plugins/webwright path, for example:
.agents/plugins/marketplace.json
plugins/webwright -> ..
This keeps the existing .codex-plugin/plugin.json and skills/webwright layout intact, while matching the Codex marketplace path convention.
This should not affect the Claude Code plugin path because .claude-plugin/marketplace.json and .claude-plugin/plugin.json remain unchanged.
One tradeoff is that the symlink approach may cause Codex to cache the repository root as the plugin root, rather than a smaller dedicated plugin subdirectory. The benefit is avoiding duplicate skill files and duplicate maintenance.
- Lenguaje dominante
- Python
- Estrellas
- 6k
- Forks
- 383
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoft/Webwright
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
-
Memory leak: page.on() event listeners never removed on closePosiblemente ocupada @rahulrao85 la tomó hace 84 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
SKILL.md says Firefox is a prerequisite, but README.md doesn't.Posiblemente ocupada @nuthalapativarun la tomó hace 130 días. Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
-
playwright_patterns.md 'Browser launch skeleton' crashes with UnicodeEncodeError on Windows when aria_snapshot output contains non-cp1252 charactersPosiblemente ocupada @raykuo998 la tomó hace 133 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
Todos los issues de microsoft/Webwright
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Los mantenedores suelen responder en 3 días
-
Negation with "not" and "no" is ignored during sentiment analysisPosiblemente ocupada @vivek-3728 la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
techcsispit/mess-mood#11 · 1 comentario ·
-
changelog investigate
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
ramnes/notion-sdk-py#408 ·
-
good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
btclib-org/btclib-wallet#267 ·
Los mantenedores suelen responder en 1 día
-
good first issue tech-debt
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
knnmelprop/YAADO#111 ·