{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiaiuuku6sqsxvbczjexftamlqglrqxx73ik7a326aa6aj6qbwhhjy",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mncmoyjzr772"
  },
  "path": "/t/maximized-codex-window-bleeds-onto-adjacent-monitors-in-a-multi-monitor-setup/1382359#post_1",
  "publishedAt": "2026-06-02T11:58:02.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "@120Hz"
  ],
  "textContent": "When the Codex desktop window is maximized on my primary monitor, a thin\nsliver of the window (roughly 7 to 8 pixels) extends past the left and right\nedges of that monitor and renders onto the two adjacent monitors. The window\ncontent paints into the standard Windows maximize overscan region instead of\nbeing clipped to the monitor’s work area.\n\n## Expected behavior\n\nWhen maximized, the window should fill the primary monitor exactly and remain\nfully contained within its bounds. No part of the window should be visible on\nneighboring monitors.\n\n## Actual behavior\n\nA narrow vertical strip of the window appears on the monitor to the left and\nthe monitor to the right of the primary display. The bleed occurs on the left\nand right edges only.\n\n## Steps to reproduce\n\n  1. Use a multi-monitor setup where monitors sit flush against the left and\nright edges of the primary monitor.\n  2. Move the Codex window to the primary monitor.\n  3. Maximize the window.\n  4. Observe the left and right edges spilling onto the adjacent monitors.\n\n\n\n## Why this appears to happen\n\nWhen Windows maximizes a window, it extends the window rectangle by about 7 to\n8 pixels on every side. Those extra pixels are the invisible resize border, and\non a single monitor they fall harmlessly off the screen edge. Apps that use a\nnative non-client frame leave that region empty, so nothing shows. Codex draws\nits custom titlebar and content edge to edge, so it paints into the overscan\nregion, and on a multi-monitor layout the left and right slivers land on the\nneighboring displays instead of falling off-screen.\n\n\n     Main monitor edge ─┐                           ┌─ Main monitor edge\n                        ▼                           ▼\n     ┌─────────┐  ┌────────────────────────────────────┐  ┌─────────┐\n     │  LEFT   │░░│            CODEX (maximized)       │░░│  RIGHT  │\n     │ monitor │░░│                                    │░░│ monitor │\n     └─────────┘  └────────────────────────────────────┘  └─────────┘\n                ▲                                        ▲\n                └─ ~8px overscan bleeds onto neighbor ───┘\n\n\nA common fix is to clamp the maximized bounds to the monitor work area, or to\naccount for the maximize offset when laying out the window content.\n\n## Environment\n\n### Operating system\n\nProperty | Value\n---|---\nEdition | Windows 11 Home\nVersion | 25H2\nBuild | 10.0.26200.8457\n\n### Graphics\n\n  * NVIDIA GeForce RTX 5080\n  * Intel Graphics (integrated)\n\n\n\n### Monitor layout\n\nAll three monitors run at 100 percent display scaling, so a per-monitor scaling\nmismatch is not a factor.\n\nRole | Device | Resolution | Orientation | Scale | Position (X, Y)\n---|---|---|---|---|---\nPrimary (maximized here) | `DISPLAY1` | 2560 × 1440 @120Hz | Landscape | 100% | (0, 0)\nLeft | `DISPLAY3` | 1920 × 1080 | Landscape | 100% | (−1920, 278)\nRight | `DISPLAY2` | 1080 × 1920 | Portrait | 100% | (2560, −80)\n\nThe left monitor’s right edge meets the primary monitor at x = 0, and the right\nmonitor’s left edge meets the primary monitor at x = 2560. Because both\nneighbors sit directly against the primary monitor’s edges, the maximize\noverscan slivers render onto them rather than falling off-screen.\n\n## Notes\n\n  * The bleed is purely visual; the window otherwise functions normally.\n  * Reproduces consistently on every maximize.\n  * A screenshot showing the slivers can be provided on request.\n\n",
  "title": "Maximized Codex window bleeds onto adjacent monitors in a multi-monitor setup"
}