{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreic6k3c2rvoki6iq7f3v72hcy6fmevwwgefl3taq4q57a6fqf5baai",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mjm3dw3avm62"
  },
  "path": "/t/codex-windows-app-ui-closes-but-background-processes-remain-blocking-relaunch/1379095#post_1",
  "publishedAt": "2026-04-16T09:01:19.000Z",
  "site": "https://community.openai.com",
  "textContent": "I’ve run into a consistent issue with the Codex desktop app on Windows that looks like a process lifecycle bug.\n\n**Behavior:**\n\n  * I close the Codex UI window normally.\n  * The application appears to exit.\n  * However, one or more background processes remain running.\n  * Attempting to reopen Codex does nothing — presumably because it detects an already running instance.\n  * The only way to recover is to manually kill the leftover processes in Task Manager.\n\n\n\n**Notes:**\n\n  * This happens consistently, not sporadically.\n  * Feels like either:\n    * The app is not properly shutting down its process tree, or\n    * The single-instance guard is too strict and doesn’t recover from orphaned processes.\n  * If this is intentional (e.g., tray/minimized behavior), it’s not clear to the user and there’s no visible way to properly “quit” the app.\n\n\n\nThis isn’t a blocker, but it’s disruptive enough to break normal workflow.",
  "title": "Codex Windows App – UI closes but background processes remain, blocking relaunch"
}