Repository navigation
docs: announce official fix and end of maintenance - #34
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 49137a0088
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| > **Officially fixed — project no longer maintained.** The remote-control issue addressed by this project has been fixed in the official Codex release. This project's mission is complete, and maintenance has ended. Please use the latest official Codex version instead of this workaround. | ||
| > | ||
| > Source code, commit history, and historical releases are retained for reference. The documentation below is preserved as a historical record, not a recommendation to install this workaround. |
There was a problem hiding this comment.
Tell existing users to uninstall the persistent workaround
For users who already installed CodexRemote-fix, upgrading Codex does not remove the workaround: the logon task still starts its supervisor automatically (README.md:69-76), retaining the remote-debugging exposure described in SECURITY.md:5-15. This notice only directs users to the official version, so existing users can reasonably leave obsolete, now-unmaintained code running indefinitely. Add an explicit instruction and link to the uninstall procedure in README.md:168-176, with the equivalent guidance in the Chinese notice.
Useful? React with 👍 / 👎.
Publish bilingual project completion notices. Preserve source code, commit history, and historical releases. Documentation only; no runtime changes.