OpenAI ChatGPT desktop app for Linux

The framing of this release - 'ChatGPT finally comes to Linux' - overstates what's actually new. The Codex CLI and IDE extension already worked on Linux before this app existed ^[1]; what shipped on August 11 is primarily a visual interface layer for people who prefer a windowed app over a terminal workflow ^[1].

Once installed via the .deb or .rpm package, the app is a single native window that switches between two modes through a menu in its upper-left corner: a ChatGPT/Work mode for everyday chat and tasks, and a Codex mode that opens a full development environment for writing and debugging code, running tests, reviewing changes, and working directly with local repos, folders, and terminals ^[2]. Compared with the browser version of ChatGPT, the desktop build can run Codex against local repositories, hook into and control other installed apps through extensions, and read local files without requiring users to upload them anywhere first ^[3].

One detail didn't make OpenAI's own announcement. The top comment on the r/linux discussion of the launch claims the app's embedded browsing surface runs on Owl, the browser engine OpenAI originally built for its now-discontinued Atlas browser, repurposed here as an in-app sidebar. If that holds up, the 'new' Linux app is less a from-scratch build for Linux and more an assembly of two things OpenAI already had lying around: Codex's existing CLI tooling and a browser engine from a product it shut down.

OpenAI's own line on the release is that Linux has been one of its most-requested desktop platforms, extending ChatGPT and Codex across every major desktop operating system ^[4]. That's true, but it skips the more immediate context: Anthropic shipped a Claude desktop app for Linux about a month earlier, and multiple outlets frame OpenAI's launch as catching up to that move rather than as an independently timed decision ^[1].

The comparison isn't as one-sided as 'OpenAI is late' suggests, though. Anthropic's Claude Linux app supports Ubuntu 22.04+ and Debian 12+ - a lower minimum version requirement than OpenAI's Ubuntu 24.04+ and Debian 13 floor ^[4]- which in practice means Claude runs on more existing Linux installs today. Reddit discussion of the launch on r/codex noted that OpenAI's app explicitly targets Fedora, a distro family Anthropic's app doesn't officially cover - so on distro-family breadth rather than version-floor breadth, OpenAI's coverage is arguably wider at launch. Two companies racing to the same feature can still end up optimizing for different slices of the same audience.

OpenAI isn't pretending this preview matches the Mac and Windows apps feature-for-feature. Native Computer Use - letting ChatGPT drive other desktop apps like GIMP or OpenOffice directly - isn't available on Linux at launch, and neither are Appshots, Record & Replay, or voice commands for desktop apps ^[1]. On X, an OpenAI-affiliated engineer confirmed the app otherwise has feature parity, with agents still able to drive the in-app browser as a stand-in while Computer Use is finished.

The bigger tension shows up in how the app is being received rather than in what OpenAI disclosed. Reaction on r/linux skewed skeptical from the start - commenters joked it's another Electron/webview wrapper, and a recurring thread of comments pushed back on the idea of running an AI assistant with deep file-system access on a machine people specifically chose for user control. That distrust lines up with an independent review from Linuxiac, which cautioned that granting Codex full file-system and terminal access hands the app 'too much power' and should be done carefully ^[5]. Meanwhile, on r/codex - a subreddit self-selected for people who already use OpenAI's coding tools - the same access model reads as a feature rather than a risk, with users confirming the app ships remote control and Chrome connection even without full computer-use. Same product, same access model, two audiences reading it in opposite directions.

OpenAI's official release ships only .deb and .rpm packages, with no AppImage or Flatpak build; official support also excludes distros like Arch Linux and NixOS at launch ^[5]. That gap didn't stay empty for long. Within hours of the announcement, six competing AUR (Arch User Repository) packages appeared for the app, several of them declaring conflicts over who gets to own the plain 'chatgpt' package name; one submitter deleted and resubmitted their package under a different name barely half an hour later, leaving the orphaned original still listed. Comparing the six build scripts turned up real technical forking, not just duplication - some auto-add a Wayland compatibility flag and are otherwise identical scripts with reworded comments, one reads a differently named configuration file than the rest, and although all six ship an AppArmor security profile, only one of them actually loads it. More pointed: one of the new submitting accounts had been created only a day earlier, prompting other community members to flag it as a possible malware risk in a distribution channel with no official gatekeeper.

This is exactly the gap a pre-existing unofficial project, codex-desktop-linux, was built to fill - a community port that repackaged OpenAI's own macOS app with builds for Debian/Ubuntu, Fedora/openSUSE, Arch, and Nix/NixOS before OpenAI shipped anything official ^[6]. One YouTube analysis of the launch argued the real contest isn't which AI lab ships a Linux app first, but whether AI coding assistants become the default layer developers reach for on Linux at all. On Windows or macOS, that fight would largely be settled by whichever app ships through the platform's own store. On Linux, distribution is contested territory that no single vendor, including OpenAI, actually controls - and the AUR scramble is what that contest looks like in its first 24 hours.