ChatGPT desktop app for Linux: Codex in your local repos

OpenAI shipped a ChatGPT desktop app for Linux today, in public preview, worldwide. It carries ChatGPT, ChatGPT Work and Codex — which means OpenAI's coding agent now has a first-party GUI on the operating system most of your build boxes actually run. Anthropic got there about a month earlier with a Claude desktop app for Linux. This is a catch-up release, and it's still the one worth noting.

What actually happened

Per TechCrunch, the app is validated on desktop Ubuntu 24.04 LTS, Ubuntu 26.04 LTS, Debian 13, and Fedora 43 and 44 — with the expectation that downstream flavors of those bases work too. Phoronix notes it ships as closed-source DEB and RPM packages for both x64 and ARM64, downloadable from openai.com/codex.

Two things are worth pinning down before you roll it anywhere.

It is preview, not GA. OpenAI's own framing is that integrations may not work reliably. That's a fine state for a dev laptop and the wrong state for anything on a release path.

And native Computer Use — the agent driving desktop applications outside its own in-app browser — is not in the Linux build at launch. If your mental model of "AI on the desktop" is the model clicking around GIMP or LibreOffice, that isn't what shipped. What shipped is a chat and coding surface that can work in your local repos.

Why this matters for your business

The Linux desktop was the last gap in a pattern that's now complete across every vendor: the coding agent wants to run on your machine, in your checkout, against your files — not in a browser tab pointed at someone else's sandbox. That's a better security posture and a worse governance story, because the boundary moves from "what did we upload" to "what can this process reach from inside the network."

So treat the install like any other agent you let near a repo. Which credentials are on that box? Does the developer's SSH key open production? Is the checkout it can read the same one that holds the .env you never rotated? A preview-quality binary with your git credentials is a different risk than a preview-quality binary in a container.

The portable version of this: pick the harness, not the vendor. Codex on Linux, Claude Code, whatever ships next quarter — they all read the same repos and hit the same APIs. Keep the guardrails at the credential and network layer, where they survive a vendor swap.

Sources: TechCrunch, Phoronix.