Contributing
We welcome community contributions through the openai/codex issue tracker. Bug reports, root-cause analyses, and feature requests help us understand what matters most and improve Codex.
We do not accept external code contributions or pull requests.
Why we do not accept external code contributions
Effective changes to Codex require architectural context, an understanding of system-level constraints, and visibility into the project's roadmap. External pull requests often focus on issues that are lower priority, affect a small number of users, or need substantial changes to fit the broader system. Reviewing and iterating on those changes can take more time than implementing a fix directly, diverting attention from higher-priority work.
Community expertise is most valuable when shared through detailed bug reports, reproduction steps, logs, root-cause analysis, and design discussions in issues. Understanding the problem, identifying the right solution, and prioritizing the work are typically the hard parts; implementation is comparatively straightforward with the help of Codex itself.
For these reasons, we focus community contributions on issue reports, analysis, and feedback, while the Codex team handles code changes.
Reporting bugs
Before opening a new issue, search the issue tracker to see whether the problem has already been reported. If it has, add any new information to the existing issue.
When reporting a bug, include as much relevant detail as possible:
- Clear, detailed steps to reproduce the problem.
- Expected and actual behavior.
- Your Codex version, operating system, and other relevant environment details.
- Logs, error messages, or other diagnostic information, with sensitive information removed.
- Root-cause analysis, technical observations, or potential approaches to a fix, if available.
Requesting features
Open a feature request in the issue tracker, or upvote an existing request that describes the same need. Explain your use case, the behavior you would like, and why it would improve your workflow.
Community values
- Be kind and inclusive. Treat others with respect; we follow the Contributor Covenant.
- Assume good intent. Written communication is hard, so err on the side of generosity.
- Share what you learn. Reproduction details, logs, and analysis help the entire community.
Security
If you discover a security vulnerability, follow the security policy instead of reporting it in a public issue.