What I like most about Codex is that it provides a clean, well-organized experience while producing high-quality results for engineering work. It does a good job of understanding technical context and turning a request into an output that is structured and practical to work with. This reduces the amount of effort needed to refine or reorganize the result afterward.
Compared with the internal tools I’ve used, Codex generally gives me stronger and more useful results, particularly when working through technical problems or coding-related tasks. The combination of usability, organization, and output quality makes it feel like a more mature and effective engineering assistant. Review collected by and hosted on G2.com.
The biggest limitation for me is the enterprise quota. It is restrictive enough that I have to actively manage my usage and sometimes switch to Lunar to avoid exhausting the quota in a single day. For an engineering tool that I would otherwise use frequently, this significantly limits its practical value.
I also experience occasional stability and accessibility issues in our enterprise environment. There are times when Codex cannot be opened or does not work as expected, apparently due to enterprise policies or controls. This can interrupt the development workflow and makes the experience less predictable.
The other area I would improve is speed. Codex can sometimes feel slow when generating or processing results. A faster and more consistent response time, combined with a more practical enterprise quota and better reliability, would make it much stronger for everyday engineering use. Review collected by and hosted on G2.com.