macOS traffic-light window controls ignore clicks because title-bar drag region captures them

Open
#34,154 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, rust
Domain
desktop, operating-systems

Research direction

Reproduce the issue in the Codex desktop window, then locate the macOS title-bar and draggable-region handling; no file or test entry point is named in the report. Done means single clicks on the native red, yellow, and green controls close, minimize, or zoom the window, while title-bar dragging still works.

Written by the indexing model from the issue text.

Description

app bug

Environment

  • Codex desktop: 26.715.31925 (build 5551)
  • macOS: 26.5.2 (25F84)

Reproduction

  1. Open the main Codex desktop window on macOS.
  2. Move the pointer over the red, yellow, and green traffic-light controls.
  3. The normal hover symbols appear, confirming that hover state is detected.
  4. Single-click any of the three controls.

Actual behavior

None of the three controls performs its action. The window does not close, minimize, or zoom.

Double-clicking the yellow control is handled like a title-bar double-click: the window changes size/position and the right content pane reflows. This strongly indicates that the draggable title-bar hit region is capturing clicks over the native traffic-light controls.

Keyboard equivalents work normally:

  • Cmd-W closes the window
  • Cmd-M minimizes
  • Control-Cmd-F toggles full screen
  • Cmd-Q quits the app

The issue reproduces consistently across launches.

Expected behavior

The native traffic-light controls should receive clicks and close, minimize, or zoom the window.

Feedback reference

Codex feedback thread ID: 019f79e4-d0e9-7611-8cb7-512162552d5e

No diagnostic logs were uploaded.

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.