PR status panel stops updating after a new push to the same PR

Open 💬 2 comments Opened Jun 27, 2026 by iAchilles

What version of the Codex App are you using (From “About Codex” dialog)?

26.623.41415

What subscription do you have?

PROX20

What platform is your computer?

MacOS Silicon

What issue are you seeing?

PR status panel stops updating after a new push to the same PR

Description

There appears to be a regression in Codex App where the right-side PR status panel updates only once.

The affected block includes:

  • Check status
  • Comments to fix
  • PR status

After the initial update completes, if I push new changes to the same PR, the panel gets stuck. The PR status remains yellow, as if CI checks are still running, and new follow-up comments do not appear.

The only way to refresh the state is to fully restart the Codex App.

Expected behavior

After pushing new changes to an existing PR, the right-side PR status panel should refresh automatically and show the latest CI status, PR state, and follow-up comments.

Actual behavior

After a second push to the same PR:

  • PR status remains stuck in yellow / pending CI state
  • New follow-up comments do not appear
  • The panel does not refresh
  • Restarting the whole app fixes the issue temporarily

Regression

This used to work correctly before, so this looks like a regression.

Steps to reproduce

  1. Open a PR in Codex App.
  2. Wait until the right-side PR status panel updates successfully.
  3. Push additional changes to the same PR.
  4. Wait for CI/checks and follow-up comments.
  5. Observe that the right-side panel does not refresh.
  6. Restart Codex App.
  7. Observe that the latest status/comments appear after restart.

Impact

This makes the PR review flow unreliable because Codex App shows stale PR state and misses new follow-up comments unless the whole application is restarted.

What steps can reproduce the bug?

-

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗