Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Codex marketplace registration succeeds, but Webwright does not appear in /plugins

未关闭
#37 2 条评论 4 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
64/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
冷清
领域
cli, tooling

调研方向

从现有的 .claude-plugin/marketplace.json、.codex-plugin/plugin.json 和 skills/webwright/SKILL.md 开始,然后检查报告中的 .agents/plugins/marketplace.json 约定和已验证的 plugins/webwright 路径。运行 issue 中的 marketplace add、list 和 install 命令;当 Webwright 出现在列表和 /plugins 中,并且安装后其 skill 可用时,即表示完成。

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Python
星标
6k
派生
385
PR 合并指标
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

microsoft/Webwright 的其他 Issue

查看 microsoft/Webwright 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。