Codex Web Screenshots Are Not anymore available
What issue are you seeing?
Web, codex, on Windows (but problem is there also on the IOS app)
Not an enhacement, It seems to be a regression, it stopped working a couple of weeks ago for all react and nodes project.
Getting in each description something on the line:
"⚠️ I couldn’t generate a fresh local screenshot because the browser screenshot tool isn’t available in this environment."
We tried to fix this at env level, by trying to install tools for screenshots, but to no avail.
Screenshots and fast validation of changes was one of the reason for our company to use codex over other tools (we are using codex web)
<img width="1238" height="310" alt="Image" src="https://github.com/user-attachments/assets/de1e01a8-0575-4503-b8f4-834ecc877bec" />
Note this to work just fine until early March (we still have chat thread with full screenshot). This allowed a improved workflow with non technical people being able to validate the outcome without the need to run an environment or switch branch
What steps can reproduce the bug?
On any react, or angular project
request a visual change via web codex, ask to present a screenshot of the outcome
What is the expected behavior?
A screenshot is presented to preview the change in the response
Additional information
Screenshot
⚠️ Not captured in this run because the required browser screenshot tool is not available in this environment.
<img width="1140" height="362" alt="Image" src="https://github.com/user-attachments/assets/ac3fe9d3-434f-49a6-80a1-b7510fe6e59b" />
10 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
https://github.com/openai/codex/issues/15799 is not a duplicated, as the source of problem there is a race. Here the problem is consistent.
Tried also to create the workaround decribed in issue 15799 but it doesn't fix the issue
I'm having the same issue
I have the same issue...
• ⚠️ browser_container screenshot (not run because browser screenshot tooling was not available in this environment)
same issue
Same issue
Can we get some love for a fix?
same issue
How on earth is this ain't fixed yet
same issue here