Codex in ChatGPT desktop app for Linux in preview

What happened

I'll pull the official community post and the site's post-writing rules so the paragraphs stay factual and match TechBytes style.Official preview notes are in. Next I’ll pull the desktop-app docs and HN thread so the technical and competitive paragraphs stay grounded.OpenAI has put Codex in the ChatGPT desktop app for Linux into preview. The company posted the news on the OpenAI Developer Community and pointed Linux users at a single native app that now holds ChatGPT, Work, and Codex together. Official support is Ubuntu 24.04 LTS and 26.04 LTS, Debian 13, and Fedora 43 and 44, on both x64 and ARM64, shipped as .deb and .rpm packages. OpenAI describes the app as a workspace for managing projects, working with files, using browser workflows, and running Codex next to ChatGPT. Downloads go through openai.com/codex, with install steps in the official ChatGPT desktop app documentation. The Hacker News thread that carried the same headline (item 49266657) had 1 point and 0 comments when this write-up was sourced.

The Linux package is named chatgpt, not a separate Codex installer. After you install it you launch chatgpt from the applications menu or a terminal and sign in with a ChatGPT account. Ubuntu and Debian take chatgpt_amd64.deb or chatgpt_arm64.deb through apt; Fedora takes chatgpt.x86_64.rpm or chatgpt.aarch64.rpm through dnf. The installer adds a signed OpenAI package repository so later updates come through the same package manager. Inside the window you pick ChatGPT or Codex. ChatGPT has a Chat or Work toggle above the composer. Codex starts from New chat, with a Quick chat path for short questions. Each chat has an integrated terminal scoped to the current project or worktree, opened from a terminal icon or with Ctrl+`. The app can read that terminal output, so a failed test or a running dev server stays in the same workspace as the agent. Official docs say the preview works with projects, local files, and Codex, and they point to a Chrome extension for browser integration. Computer Use is not in the Linux preview. OpenAI says that capability is on macOS and Windows today and that a later release will add Linux. Native Wayland is experimental. In a Wayland session the app uses XWayland when it can; you can force native Wayland by launching chatgpt --ozone-platform=wayland, at the cost of incomplete floating windows, positioning, focus, and keyboard shortcuts. Other distributions may run the packages but are not formally supported.

The technical detail

For engineers this is client parity, not a new model. The Codex CLI and the Codex IDE extension already ran on Linux. What was missing was the same desktop workspace Mac and Windows users had for parallel projects, file inspection, and agent work sitting next to ChatGPT. A builder who keeps repos on Ubuntu 24.04, Ubuntu 26.04, Debian 13, or Fedora 43 or 44 can now keep Chat, Work, and Codex on the machine that actually compiles the code, instead of remoting to another OS or bouncing between a browser tab and a terminal agent. The integrated terminal is the practical hinge: git status, tests, and lint stay in-app, and the agent can see the output. Work stays available in the same window for non-code tasks on a machine that is both a workstation and a personal desktop. ARM64 packages matter on ARM laptops and Ampere-class boxes. The supported matrix is also a limit. Rolling and independent distributions are outside the preview contract.

Why it matters for builders

The competitive frame is the Linux coding-agent client, not a model bake-off. Claude Code already lives in the terminal where many Linux engineers work. Cursor and similar editors wrap a model inside the IDE. GitHub Copilot sits in VS Code and JetBrains. OpenAI’s move is to stop treating Linux as CLI-only while ChatGPT desktop on other platforms gets projects, files, and browser workflows. That is a distribution play: one ChatGPT login, one chatgpt binary, three modes. The thin HN thread (1 point, 0 comments) is not a market read. The real pressure is completeness. If Computer Use, native Wayland, and continuity with existing Codex CLI sessions stay weaker on Linux, people who already run Codex in a terminal will not switch surfaces.

Market and competitive context

If you are on a supported distro, install the matching chatgpt package, sign in, and treat the preview as a second client next to the CLI rather than a replacement. Confirm uname -m before you pick amd64 versus arm64. Point Codex at a real repo and use the in-app terminal for the same checks you already run. Watch three official gaps: Computer Use landing on Linux, Wayland becoming the default instead of an ozone flag plus XWayland fallback, and whether OpenAI ever publishes a Windows-versus-Linux feature sheet. The community announcement said no such comparison existed at post time. Also watch whether desktop projects pick up folders and chats you already have in the Codex CLI, and whether a Flatpak or AppImage ever appears for distributions that do not want .deb or .rpm.

What to watch next

Preview status is the binding constraint. The app can see local files and run commands in a project-scoped terminal, so permissions and sandbox settings are part of the install, not a later hardening step. Wayland users should expect IME, scaling, and shortcut bugs while native Wayland is experimental; Fedora and KDE reports on the announcement thread already needed extra ozone and Wayland IME flags for Fcitx. Arch, NixOS, and other non-.deb/.rpm systems are unofficial by design. Unofficial community Linux builds of the desktop app existed before this preview; they are prior art, not a substitute for the signed OpenAI repo. Until Computer Use ships on Linux, the desktop app is a ChatGPT plus Codex workspace with files and a browser path, not a full desktop-control agent. Keep the Codex CLI installed. Use the preview where a visual project list and an in-app terminal help, and keep the CLI for the machines and distros the preview does not name.