Codex in ChatGPT desktop app for Linux is now in preview

Original Article ↗ Hacker News Discussion ↗

OpenAI’s Codex coding agent is now available in preview inside the ChatGPT desktop app for Linux, prompting mixed reactions from power users. Many welcome easier access to a GUI with integrated terminals, file views, browser control, and remote use from mobile, but others argue the existing CLI/TUI tools are lighter, more flexible, and easier to isolate. A large portion of the debate centers on security, privacy, and Electron/Chromium bloat, with strong calls to treat the app as untrusted software, sandbox it or run it in VMs, and skepticism over giving a proprietary AI agent broad access to the desktop.

Availability & Platform Support

  • Linux desktop app for ChatGPT with Codex is now in preview; some users report OS-specific landing pages that default to Windows, with separate docs linking Linux downloads.
  • Supports .deb and .rpm; some appreciate native packages over AppImage.
  • Codex CLI/TUI has long worked on Linux (including Raspberry Pi), so this is mainly about GUI and “computer use” features.
  • Some question how many Linux users want a proprietary GUI agent versus CLI tools or local models.

Architecture, Performance & Electron

  • App is built on a Chromium-based stack (often described as Electron-like), not a native toolkit.
  • Many complain about high idle RAM use (2+ GB, many processes), lagginess, and replacing a lighter native Mac app.
  • Others argue browser-based UIs give superior text rendering, images, LaTeX, interactive elements, and accessibility, and are faster to ship cross‑platform.

Security, Sandboxing & Trust

  • Strong advice to treat the app as untrusted code: run it in VMs, separate users, or containers; some call it a “trojan” / “spy device”.
  • Linux app reportedly uses bubblewrap + seccomp sandbox for a “workspace”; CLI already does similar, but bubblewrap inside Docker is tricky and can require weakening container isolation.
  • Confusion over claims that “Codex is open source”: thread clarifies only CLI/TUI parts are; desktop app and hosted service are proprietary.
  • Prior incidents (e.g., a Windows installer creating extra users and changing NTFS permissions) are cited as reasons to apply zero trust.

Use Cases & Productivity

  • Enthusiastic users describe large productivity gains from “computer use”: installing dependencies, driving GUIs, testing web apps, shopping automation, troubleshooting performance issues, and even diagnosing hardware faults.
  • Others prefer tightly scoped, human‑in‑the‑loop workflows where the agent proposes commands and humans execute them.

GUI vs CLI/TUI Debate

  • GUI advantages cited: multi‑agent orchestration, project tabs, richer diffs, inline images/LaTeX, integrated browser, remote control from mobile, better text editing ergonomics.
  • CLI/TUI advantages: easier isolation, lower resource usage, better fit with Linux workflows, and less complexity.
  • Several use both: CLI for “deep work,” GUI for human‑in‑the‑loop or remote sessions.

Community Sentiment & Meta

  • Reactions are polarized: gratitude for Linux support vs. hostility toward Electron, proprietary agents with deep system access, and perceived AI hype.
  • Some note that broader industry cynicism and corporate behavior fuel the negativity, not just this release.