Hi Carlos,
Thanks for the detailed report, your analysis matches what we are observing on our side.
Codex has recently shifted its behavior quite significantly. It now strongly steers models toward directly editing files, which bypasses Pinegrow’s editing system. This makes the integration increasingly unreliable and harder to control within Pinegrow.
This behavior has become even more pronounced with GPT-5.2 and newer models.
At the same time, Codex with a ChatGPT subscription no longer supports the model that Pinegrow currently relies on (gpt-5-codex ). This results in the error you’re seeing, even when selecting other presets, because they still resolve internally to that model.
These changes are outside of our control and reflect how quickly the AI tooling ecosystem is evolving right now. While there was a time when Codex integration was a viable and interesting solution inside Pinegrow, this no longer seems to be the case today.
In practice, the most reliable model in our tests was the base GPT-5 (non-Codex variant), but it is not usable in this Codex + ChatGPT setup anymore.
This is also why the feature was always labeled as Beta. At this point, it is unlikely that it will ever transition into a stable, production-ready feature.
Given this situation, we will most likely remove Codex from Pinegrow.
The recommended approach going forward is to use Codex outside Pinegrow, via the dedicated app or CLI. This is currently the most reliable setup, especially for tasks like creating or fixing JavaScript.
Thanks again for your report, it helped confirm the situation.
Best,