Repository navigation
docs: record the closed Codex feature request and narrow upstream requests - #100
Merged
Merged
Conversation
…uests The owner closed openai/codex#53298 on 2026-10-14 as not planned: it asked for a new API in an internal Codex crate that only the DevGuard integration needs. The Upstream row of the downstream patch record now says so and that no upstream request is open. The policy's "Upstream first" section proposes a patch's capability only when Codex's own users need it too, described as their problem, and the first-patch case records the outcome. English and Korean, with the registry hashes recorded. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Seongjae · project thread
Records that the Codex feature request for the PTY observer is closed, and narrows the policy so that a patch's capability is proposed upstream only when Codex's own users need it too. Documentation only.
No pin change. No change to the patch, its patched tree or any code.
Issue
No issue. The owner closed openai/codex#53298 on 2026-10-14 as not planned. Follows #96, which recorded the request.
Summary
docs/upstream-lock.md(EN/KO), the Upstream row of the downstream patch record: the request was filed on 2026-10-12 and closed by the owner on 2026-10-14 as not planned, because only CodeSpace needs the capability. No upstream request is open.docs/upstream-patches.md(EN/KO), "Upstream first": a patch's capability is proposed upstream only when Codex's own users need it too, written as their problem rather than as an API for CodeSpace. A capability that only CodeSpace needs is carried without a request. Submitting a request stays the owner's decision.docs/translations.json: the two documents' hashes, recorded withscripts/check_docs.py record.Contract changes
None.
scripts/codex_patch.pyreads only the Commit, Patch and Patched tree rows, and the patch, its digest and the patched tree are unchanged.Tests
Verified locally on this head (
9966ed7):python3 -B scripts/check_docs.py: registry verified, 20 paired documents.python3 -B -m unittest discover -s scripts/tests -p 'test_*.py': 102 tests pass.npm ci,npm test(5 pass),npm run build, andpython3 -B docs-site/scripts/site.py check(179 hashed files, 43 HTML pages).CI on this head: every leg runs because
docs/upstream-lock.mdis a full path inscripts/ci-policy.json. CI run 38542774246 passed, all 17 jobs, and the documentation site run 38542774991 passed.Security scenarios
None affected: documentation only.
Out of scope