OpenAI has released an official Linux preview of the ChatGPT desktop app. As of August 13, 2026, Linux users no longer need an unofficial wrapper to get the desktop interface: OpenAI provides signed packages for a defined set of Ubuntu, Debian, and Fedora releases on both x64 and ARM64. The practical payoff is bigger than a dedicated chat window. The app can open local folders, work with files, and expose Codex for repository-aware development. The important qualification is "preview." Computer Use is not available on Linux yet, native Wayland support is experimental, and distributions outside the supported list are on their own. This guide separates the useful new workflow from the launch-day ambiguity.
What OpenAI Actually Shipped
The product is the ChatGPT desktop app for Linux, not a separate Linux-only Codex client. Inside the app, developers can select Codex for codebase work, while ChatGPT and Work cover general chat and longer document or research tasks. OpenAI's desktop quickstart says the app can start a chat, create a project, or open a folder; a chosen folder can then be read and modified by the agent.
That distinction matters. Linux already had the Codex CLI and IDE extension. The new release adds the unified desktop surface for projects, local files, long-running tasks, and Codex rather than replacing those terminal-first tools. Developers who are happy in a shell do not suddenly need a GUI. Teams that want one place to switch between code work and broader project context now have an official option.
Supported Linux Matrix
OpenAI's Linux installation guide lists a deliberately narrow support matrix:
| Distribution | Supported desktop releases | Package | Architectures |
|---|---|---|---|
| Ubuntu | 24.04 LTS, 26.04 LTS | .deb |
x64, ARM64 |
| Debian | 13 | .deb |
x64, ARM64 |
| Fedora | 43, 44 | .rpm |
x64, ARM64 |
Check the machine architecture before downloading:
uname -m
x86_64 means the x64 build. aarch64 or arm64 means the ARM64 build. This check is boring but worthwhile: it avoids downloading the right distribution package for the wrong processor.
Arch Linux, openSUSE, NixOS, and other distributions are not in OpenAI's supported matrix. They may run community packages, but that is a different trust and support path. For a work machine, prefer the package linked by OpenAI over a newly created third-party repackaging.
Install It Without Breaking the Update Path
For Ubuntu or Debian, download the matching .deb from the official guide and install the local file with apt:
cd ~/Downloads
sudo apt install ./chatgpt_amd64.deb
Use chatgpt_arm64.deb instead on ARM64. For Fedora x64, the documented command is:
cd ~/Downloads
sudo dnf install ./chatgpt.x86_64.rpm
On Fedora ARM64, use chatgpt.aarch64.rpm. The package registers OpenAI's signed package repository, so future updates should continue through the normal package manager rather than repeated manual downloads.
# Ubuntu or Debian
sudo apt update
sudo apt install --only-upgrade chatgpt
# Fedora
sudo dnf upgrade --refresh chatgpt
Launch it from the desktop menu or run chatgpt, then sign in with a ChatGPT account. OpenAI also permits Codex authentication with an API key, but its quickstart warns that some features may not be available through that route. Do not assume API-key login and a ChatGPT plan expose identical desktop capabilities.
Treat Folder Access as a Security Decision
The desktop app can read and modify files in a folder you select. That is the feature that makes Codex useful, and it is also the point where an installation guide should stop being casual. Start with a disposable repository or a clean worktree, inspect the proposed changes, and avoid opening a broad home directory as the project root.
Codex supports permission profiles on Linux. The built-in :read-only profile limits local commands to inspection, :workspace allows writes within active workspace roots and temporary directories, and :danger-full-access removes local sandbox restrictions. For normal repository work, workspace-scoped access is the sensible default. Full access should be an explicit exception, not a setup shortcut.
This is also why the official package matters. Installing an agent that can execute commands and modify files from an unverified repackaging expands the trust boundary before the first prompt is sent. Package provenance is part of the security model, not a cosmetic preference.
What Is Missing in the Preview
The biggest missing feature is Computer Use. OpenAI says it is available on macOS and Windows but not yet in the Linux preview. Codex can still work with selected folders and developer tools; it cannot yet take over the Linux desktop interaction layer in the same way.
Wayland is the second caveat. Native Wayland support is experimental, and the app uses XWayland when it is available. Users can force the native path with:
chatgpt --ozone-platform=wayland
OpenAI warns that floating windows, positioning, focus, and keyboard shortcuts may not behave fully under native Wayland. If the app feels unreliable, test the default XWayland path before blaming the Codex workflow itself.
The final limitation is distribution coverage. An official preview is not the same as broad Linux support. The absence of an official Flatpak, Snap, AppImage, Arch, or Nix package means many developers still face a choice between waiting and trusting community maintenance. OpenAI has closed the largest gap, but not the packaging fragmentation that makes Linux desktop support difficult.
Who Should Install It Now?
Install the preview now if you use a supported distribution, want Codex alongside ChatGPT projects and local files, and are comfortable testing early desktop software. It is especially useful for developers who previously kept a browser, terminal agent, and project notes in separate contexts.
Wait if Computer Use is the reason you want the app, your workflow depends on flawless native Wayland behavior, or your distribution is outside the official matrix. The Codex CLI and IDE extension remain the lower-friction choices for terminal- and editor-centric work.
The release is meaningful because Linux developers finally have a first-party desktop route. It is not meaningful because a desktop shell is inherently better than the browser or CLI. The value is the integrated context; the cost is accepting preview-grade platform coverage.
The Bottom Line
ChatGPT Desktop for Linux is worth trying on supported Ubuntu, Debian, and Fedora systems, particularly if Codex is already part of your development workflow. Use OpenAI's package, keep permissions scoped to the repository, and let the package manager handle updates. Just set the right expectation: this is an official starting point, not feature parity with macOS and Windows. Computer Use, mature native Wayland behavior, and broad distribution packaging are still unfinished.
