openai / openai/codex

Open Source docs point to the deprecated skills repo and overstate codex-universal parity

Open Beginner friendly
#40,185 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation skills
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What is the type of issue?

Documentation is incorrect

What is the issue?
What is the type of issue?
  • Documentation is incorrect
What is the issue?

The Open Source documentation currently has two rows that do not match the repositories they link to:

  1. The Skills row points to openai/skills and describes it as the location for reusable skills. The repository README now marks that repository as deprecated and directs current Codex skill and plugin examples to openai/plugins.
  2. The Universal cloud environment row describes openai/codex-universal as the base environment used by Codex cloud. Its README describes the image as a reference implementation that is similar to, but not identical to, the Codex environment and intended for approximation and local debugging.

Sources:

Suggested wording
  • Skills: "Deprecated archive of skill examples; current skill and plugin examples live in openai/plugins."
  • Universal cloud environment: "Reference implementation that approximates the Codex cloud base environment; it is not identical to the hosted environment."

Alternatively, the Skills row could be removed if Plugins is now the sole current distribution repository.

Why this matters

The current wording can send prospective contributors to a deprecated repository and can lead developers to expect exact parity from codex-universal when debugging environment differences.

I searched open and closed Issues and PRs in openai/codex, plus the related openai/skills and openai/codex-universal issue trackers, using the repository names and the phrases open source, deprecated, universal cloud environment, and reference implementation. I did not find an existing report for these two rows.

Where did you find it?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Open Source documentation page and compare its Skills and Universal cloud environment rows with the openai/skills and openai/codex-universal README statements. Update the Skills link and wording to reflect the deprecated repository and current openai/plugins location, and clarify that codex-universal approximates rather than exactly matches the hosted environment. Done means both rows accurately match their linked repositories.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
76/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.