Codex in ChatGPT desktop app for Linux in preview

What happened

I'll pull the official OpenAI community thread and the HN listing so the paragraphs stay grounded in named facts rather than invented details.The community thread has the distro matrix and a few first-install reports. I’ll check OpenAI’s desktop docs next so the mechanics stay tied to what they actually shipped.There's a dedicated Linux desktop-app doc. I'll pull that plus a couple of independent writeups so the competitive context stays factual.OpenAI put the ChatGPT desktop app for Linux into preview on August 11, 2026, announcing it on the OpenAI Developer Community and on X. The preview folds ChatGPT, ChatGPT Work, and Codex into one native desktop client. Official support is limited to Ubuntu 24.04 LTS and 26.04 LTS, Debian 13, and Fedora 43 and 44, with x64 and ARM64 builds shipped as .deb and .rpm packages. An OpenAI spokesperson told The New Stack that Linux was one of the most-requested platforms for the desktop app and that the launch extends ChatGPT and Codex across every major desktop operating system. Downloads are pointed at openai.com/codex, with product documentation on the ChatGPT desktop app pages. The Hacker News item that linked the community thread sat at one point and zero comments when it was listed.

The Linux client is framed as a workspace, not a browser tab with a window chrome. OpenAI says it is for managing projects, working with files, using browser workflows, and running Codex alongside ChatGPT. The documented path after install is to sign in with a ChatGPT account, then start a chat, create a project, or open a folder so the app can use files and context from that location. Users pick ChatGPT or Codex. Inside ChatGPT a toggle above the composer selects Chat or Work. In Codex the starting point is New chat, with a Quick chat control next to it for short questions. Like the macOS and Windows clients, the Linux build includes OpenAI’s in-app browser and Chrome extension support, and Voice is included. Native Computer Use is not. OpenAI confirmed to The New Stack that the agent cannot drive desktop applications such as OpenOffice or GIMP at launch, and that this also blocks Appshots, Record and Replay, and voice requests that involve desktop apps or the system browser. Phoronix noted the Linux app is closed source.

The technical detail

Linux users were not waiting for a coding agent. Codex CLI already runs there, as does the IDE extension, and Codex cloud can take work without any desktop client. What was missing was the visual coordination layer those surfaces never provided: several projects and long-running tasks on screen, file and artifact inspection, and a single place to move between chat, knowledge work, and agent coding. For people who live on Ubuntu, Debian, or Fedora workstations, that removes the Mac-or-Windows tax that sat on the visual Codex workflow after the macOS and Windows desktop apps shipped in July with ChatGPT Work. Tibo, posting as thsottiaux, treated the wait as over and said impatient buyers could cancel a MacBook order. The change is not a new model. It is local folder context, project lists, and browser workflows sitting next to the same Codex sessions that previously lived in a terminal or a remote cloud box.

Why it matters for builders

The agent-desktop market has been a Mac-first race. Anthropic’s Claude app has the same product-shape problem The New Stack called out for ChatGPT: a chat surface stretched over hour-long agent runs, approvals, file edits, and artifacts. Cursor, Claude Code, and Gemini CLI already treat Linux as a first-class engineering environment, which made Codex look terminal-only on the operating system where a large share of backend and infrastructure work actually happens. Shipping .deb and .rpm packages, not another chatgpt.com tab, is OpenAI saying the coding agent belongs on the same machine as the repo. The packaging choice also draws a line. Community replies asked for Flatpak or AppImage because Arch Linux and NixOS sit outside the official matrix, and one user could not fetch the Linux package from a Windows browser to carry into a VM because several download pages only show the installer for the OS they detect.

Market and competitive context

If you are on a supported distro, the install path is a native package from openai.com/codex or the persistent.oaistatic.com Codex Linux package URLs community members already mirrored, then a sign-in and a folder or project. Treat preview as preview. Early reports already matter for anyone planning a team rollout. One user said Codex CLI projects on the same machine do not appear in the desktop project list and show up as standalone chats even when working directory and git branch are preserved, and creating a project from the same folder left it empty. Another report said the official x64 package ran under WSL Ubuntu 24.04 with WSLg. OpenAI staff said a Windows-versus-Linux feature sheet does not exist yet. Tibo’s public note is the closest thing to a parity claim. Watch whether Computer Use, Appshots, and Record and Replay land on Linux, whether CLI sessions start hydrating the desktop project list, and whether download pages stop hiding the Linux package from non-Linux browsers.

What to watch next

The first-week thread is a Linux desktop preview in miniature. Japanese and Korean Fcitx 5 input on Fedora KDE and EndeavourOS Wayland failed until users launched the binary with Chromium Ozone flags that force the Wayland platform and Wayland IME. A Fedora 44 GNOME user saw an X11 fallback and broken 4K scaling until a restart. That pattern matches other Electron-style clients, and because the app is closed source those compositor and IME issues cannot be patched locally. Computer Use staying off Linux is the larger product hole: the selling point of a native workspace is driving local tools, and at launch that is limited to the in-app browser. Unofficial community packages already exist for people outside the .deb and .rpm matrix, which is the usual Linux story when a vendor ships a closed client against a short distro list. HN had not produced discussion. The signal is in the OpenAI forum, not the orange site.