OpenAI's Linux Client Is Now Something You Can Package. It Still Gets Spec Sheets Wrong.

OpenAI has released the ChatGPT desktop app for Linux as DEB and RPM packages against a stated support matrix: Ubuntu 24.04 LTS and 26.04 LTS, Debian 13, and Fedora 43 and 44, on both x86-64 and Arm64 ^[1][2]. That is the operationally interesting part, because the alternative on Linux until now was a browser tab plus shell tools, API integrations, unofficial Electron wrappers, and editor extensions ^[3].

A first-party DEB or RPM with a named matrix is something an IT group can put in an internal repo and reason about. In practice, ZDNET's reviewer notes, DEB and RPM coverage means it runs on most Debian and Red Hat family distributions, including his own Linux Mint, which is not on the list ^[4]. Arch and NixOS users are left out for now, and some would-be users want Flatpak or AppImage builds instead ^[5][6]. OpenAI's framing is that Linux was one of the most-requested platforms and that the launch extends ChatGPT and Codex across every major desktop operating system ^[7].

The baseline is narrower than the competition's. Anthropic shipped a Linux Claude desktop client roughly a month earlier supporting Ubuntu 22.04 or later and Debian 12 or later ^[8]. On Ubuntu, that is a two-version gap in minimum supported release ^[9], which matters if your fleet is still on the older LTS. There is also a licensing constraint that no packaging pipeline solves: the client is proprietary and closed-source, which the reviewer expects to be a non-starter for many open-source developers ^[10].

For anyone writing the security review, the permission model is the substance. Codex can examine and modify files, run commands, and work inside selected project directories, bounded by chosen permission modes ^[11]. It does not automatically scan all local disks, folders, or applications; it does not drive arbitrary Linux GUI applications through native computer use; it does not reach an online service merely because you hold an account there, absent an authorized browser connection, plugin, uploaded data, or explicit task; and running commands in a coding workspace does not confer root ^[12]. Each connected service's access request is approved separately ^[13]. The optional integrations are the usual corporate surface: Google Calendar, Gmail, Outlook, Teams, Slack, and Google Drive ^[14].

What you cannot yet plan around is parity. OpenAI has not published a Linux-versus-macOS/Windows feature table, availability may vary in the Linux preview, and the fullest-featured version still requires a Mac ^[15].

The accuracy problem ships unchanged. Asked for technical specifications of the forthcoming SpaceX and Nvidia Starmind AI datacenter satellites, with a link to the satellite's site supplied, the app returned 20m height and 70m wing-width against SpaceX's stated 30m and 75m ^[16]. That is a 33 percent understatement on height and about 7 percent on width, on a document the model was pointed at ^[17]. The reviewer's conclusion is that he will stay in the browser ^[18]. Note also that ZDNET's parent, Ziff Davis, sued OpenAI in April 2025 over alleged copyright infringement in training and operating its systems ^[19].

Watch for Flatpak or AppImage builds and an Arch or NixOS story, since those decide whether this stays an enterprise-fleet artifact or reaches the developers who asked loudest. Watch for a published parity table; without one, "supported on Linux" is a procurement claim you cannot verify.