Codex hangs on agent-browser background sessions for websites with blank pages
Open 💬 3 comments Opened Mar 15, 2026 by eeshansrivastava89
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex CLI is running?
codex-cli 0.114.0
What subscription do you have?
Plus
Which model were you using?
gpt-5.4 high
What platform is your computer?
Darwin 25.3.0 arm64 arm
What terminal emulator and version are you using (if applicable)?
kitty 0.44.0
What issue are you seeing?
Codex can hang for several minutes when using Agent Browser (headless chrome automation) in the background. Steering won't work and even if I cancel the current execution and send a new message, it would take few more minutes to respond back. I think the site had a blank page, and it got stuck on it indefinitely.
What steps can reproduce the bug?
Uploaded thread: 019cef6c-89d4-7bb1-993e-178d616d449a
What is the expected behavior?
If encountering blank pages on websites, codex should stop agent browser session and report back.
Additional information
_No response_
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
we see similar hangs with browser automation sessions. the issue is usually that the browser navigates to a page that either takes forever to load or triggers an infinite redirect loop, and the automation just waits. we added a hard timeout per navigation action (15 seconds) plus a content-loaded check that verifies the page actually has visible elements before trying to interact. blank pages specifically need a fallback that checks document.readyState and gives up if it's stuck in loading.
here's our browser automation layer that handles the timeout and content-loaded checks - prevents hangs on blank or slow-loading pages: https://github.com/mediar-ai/terminator/blob/main/crates/terminator/src/lib.rs