Add browser history introspection to Codex App browser automation
What variant of Codex are you using?
Codex App
Version 26.623.101652 • Released Jul 2, 2026
What feature would you like to see?
Please add read-only browser history introspection to the Codex App browser automation API.
The current browser API supports tab.back() and tab.forward(), but when testing apps that modify browser history, there does not seem to be a supported way to inspect whether back/forward entries exist or what state the browser history stack is in.
Useful APIs would include some subset of:
tab.canGoBack()tab.canGoForward()- current history index, if available
- current URL/title plus adjacent back/forward entries, if available
- whether the current entry was created by full navigation or same-document
pushState/replaceState - clearer
tab.forward()failure details, distinguishing “there is no forward entry” from automation/browser state problems
Additional information
I hit this while testing an htmx UI that modifies browser history.
Codex could call tab.back() and tab.forward(), but when tab.forward() failed with no next page, there was no direct way to inspect whether the forward entry was actually absent, whether htmx history restoration had replaced/consumed an entry, or whether the automation layer had lost track of same-document history state.
Even simple canGoBack / canGoForward access would make these tests much easier to reason about.