Codex in ChatGPT desktop app for Linux in preview

What happened

I'll pull the official announcement and the HN thread so the paragraphs stay grounded in named facts, not invented versions or dates.The community post is the primary source. I'll pull the official desktop-app docs next so the architecture and product-mechanics paragraphs stay specific.OpenAI posted on August 11, 2026 that the ChatGPT desktop app for Linux is now in preview, putting ChatGPT, ChatGPT Work, and Codex in one native client. The support matrix is Ubuntu 24.04 LTS and 26.04 LTS, Debian 13, and Fedora 43 and 44, with signed .deb and .rpm packages for both x64 and ARM64. The files are chatgpt_amd64.deb, chatgpt_arm64.deb, chatgpt.x86_64.rpm, and chatgpt.aarch64.rpm, and the installer adds OpenAI’s signed package repository so later upgrades go through apt or dnf. An OpenAI spokesperson told The New Stack that Linux had been one of the most-requested platforms for the desktop app. OpenAI’s own account described the preview as a way to use ChatGPT, ChatGPT Work, and Codex on supported Linux systems with local projects and browser workflows. The Hacker News listing for the community thread (item 49266657) showed one point and zero comments when it was filed.

The Linux build is the same three-mode workspace already shipping on macOS and Windows, not a Codex-only sidecar. After you sign in with a ChatGPT account you choose ChatGPT or Codex. Inside ChatGPT a toggle above the composer switches Chat for short questions and Work for longer agent runs that can open a local folder, write files, and keep project history. Codex keeps a separate view and history for developer work: local and cloud projects, diffs, pull-request review, scheduled tasks, plugins, and the built-in browser. The app can treat a folder as a project, search and edit files in that tree, and keep several long-running chats visible at once. Native Computer Use, which lets the agent click and type in other desktop applications, remains macOS and Windows only. OpenAI said that gap also blocks Appshots, Record and Replay, and voice requests that need to drive desktop apps. Voice itself is in the Linux preview. Native Wayland is labeled experimental. In a Wayland session the app uses XWayland when available unless you fully quit it and start chatgpt with --ozone-platform=wayland. Other distributions may run the packages but are not formally supported.

The technical detail

Linux developers already had Codex CLI, the IDE extension, and Codex cloud. Those tools still do the edit-compile-test loop. What they did not have was the visual coordination surface Mac and Windows users got when the standalone Codex app merged into ChatGPT desktop on July 9. The Linux preview is that surface: several repositories and long-running agent jobs in one window, generated artifacts inspectable without leaving the app, and the same ChatGPT account for knowledge-work threads in Work and coding threads in Codex. That matters on machines that are the source of truth for code, not a thin client. A local project can include more than one folder, with a primary folder for Git, AGENTS.md, skills, and config.toml, and secondary folders still searchable. For anyone whose daily box is Ubuntu, Debian, or Fedora, the missing piece was never model access. It was that the product OpenAI now treats as the default Codex workspace simply did not install.

Why it matters for builders

The launch closes a platform hole competitors already treat as table stakes. Anthropic’s Claude desktop app and Claude Code have long been usable on Linux, and Cursor and other IDE-native agents never needed a separate OS port. OpenAI’s July merge of Codex into ChatGPT desktop left Linux as the last major desktop OS without the combined Chat, Work, and Codex shell. The company is not shipping a new model or a new agent harness here. It is shipping parity of the desktop workspace across Ubuntu, Debian, Fedora, macOS, and Windows: the same signed packages, the same account, the same in-app browser and Chrome extension path. It also leaves Arch, NixOS, and other non-deb/rpm distributions unofficial, which is the usual first-wave Linux split and the reason community wrappers for AppImage and pacman already exist. OpenAI says other distributions may work. They are not on the support list.

If you are on a supported distro, the next step is the package for your architecture, then chatgpt from the application menu or a terminal, then sign-in. Check that uname -m reports x86_64 or aarch64 before you pick the file. Watch three things after install. First, whether Codex CLI sessions appear as projects or as orphan standalone chats. Early testers reported CLI work that still had a working directory and git branch showing up as loose chats, and Create project leaving an empty folder. Second, whether Computer Use lands in a later Linux build, because that is the feature that turns the app from a sidecar into an agent that can drive local GUI tools such as OpenOffice or GIMP. Third, Wayland. IME users on Fedora KDE with Fcitx 5 needed --enable-features=UseOzonePlatform --ozone-platform=wayland --enable-wayland-ime to type Japanese or Korean, and some GNOME sessions still started under X11 until a restart. Those are preview bugs, not product theory.

Market and competitive context

The preview also inherits the usual desktop-agent risks. The app can open local folders and run Codex against them, so permission scope and sandbox settings matter more than they do in a browser tab. Computer Use is absent, which limits blast radius for now, but file and shell access through Codex is not. Packaging is another open question. There is no official Flatpak or AppImage, some download pages hide the Linux link unless you are already on Linux, and community users have already asked for a Windows-side download they can copy into a VM. Prior art is the unofficial Linux wrappers that rebuilt the macOS Codex and ChatGPT desktop app for deb, rpm, Arch, Nix, and AppImage before this preview. Those wrappers filled the gap OpenAI has now claimed. The official packages add a signed repo and a named support matrix. They do not yet match the unofficial builds on distro coverage.

What to watch next

What to treat as the real milestone is not “Codex runs on Linux,” which it already did from a terminal. It is whether the desktop workspace becomes the place Linux engineers actually coordinate multi-repo, multi-hour agent work, or whether they keep Codex CLI as the daily driver and treat the preview as a review pane. Watch the Computer Use port, the CLI-to-desktop project sync, default Wayland behavior, and whether OpenAI adds a distribution-neutral package. Until those land, the Linux app is a supported preview of the macOS and Windows workspace, not a finished replacement for the tools Linux users already run.