Codex App annotation overlay hit targets are misaligned at 67% browser zoom

Open 💬 2 comments Opened Jul 7, 2026 by nullvoid10

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

26.623.141536 (bundle version 4753)

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

In the Codex desktop app, the built-in browser annotation overlay becomes misaligned when the browser zoom is set to 67%.

When I enter Annotating mode, the blue annotation squares/targets do not line up with the actual mouse position or the UI element under the cursor. This makes annotation inaccurate because clicking/selecting does not correspond to the visible blue squares.

In the screenshot I captured, Codex is in Annotating mode inside the built-in browser at 67% zoom. The hover/annotation target appears offset from where the mouse is interacting with the page.

What steps can reproduce the bug?

  1. Open the Codex desktop app.
  2. Open the built-in browser.
  3. Navigate to any page with normal UI elements. In my case, I used a local Vite app at http://127.0.0.1:5173/admin/merchant-settlements-admin.
  4. Set the built-in browser zoom to 67%.
  5. Click Annotate / enter Annotating mode.
  6. Move the mouse over elements and try to click/select.
  7. Observe that the mouse position does not match the blue annotation squares/targets.

What is the expected behavior?

The annotation overlay should account for browser zoom. The blue annotation squares/targets should line up exactly with the actual mouse cursor position and the element being selected, regardless of zoom level.

Additional information

  • Reproduced at 67% browser zoom.
  • The screenshot file I used locally is named photo_2026-07-07_18-33-51.jpg.
  • This appears to be a coordinate-scaling issue between the built-in browser zoom level and the annotation overlay hit-testing.

Screenshot reference:

!Codex annotation overlay misalignment at 67% browser zoom

View original on GitHub ↗

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