Add official Computer Use support to the Linux desktop app

What variant of Codex are you using?

Codex desktop app (Linux)

What feature would you like to see?

Problem

Computer Use is currently unavailable in the Linux desktop app, even though the app itself runs natively on Linux. This prevents Linux users from asking Codex to inspect or operate desktop applications when shell commands, browser automation, files, or structured integrations are insufficient.

The current official documentation describes Computer Use support for macOS and Windows, but not Linux.

Requested behavior

Please add official Computer Use support to the Linux desktop app, with:

• packages for both x86_64 and aarch64;
• support for common Wayland and X11 desktop environments;
• explicit per-application approval prompts;
• persistent approvals that users can review and revoke;
• clear diagnostics when screen capture, accessibility, or input-control permissions are unavailable;
• the same plugin, MCP server, and skill activation flow available on supported platforms.

Why this matters

Linux users also need GUI-based workflows that cannot be completed reliably through a terminal or browser-only tool, including:

• inspecting native application state;
• changing settings through graphical interfaces;
• reproducing desktop-only UI bugs;
• moving through workflows involving multiple applications;
• working with tools that do not expose an API, plugin, or command-line interface.

Acceptance criteria

1. Computer Use can be installed and enabled from the Linux desktop app.
2. New local tasks receive the Computer Use skill and tools after activation.
3. Codex can list, inspect, and operate an approved Linux application.
4. Unsupported desktop environments or missing permissions produce actionable errors.
5. Both ARM64 and x86-64 Linux builds are supported.

Additional information

Current environment

• ChatGPT/Codex desktop app: 26.825.51511
• Codex CLI: 0.153.2
• Operating system: Fedora Asahi Remix 44
• Architecture: Linux aarch64
• Current behavior: the Computer Use plugin and tools are not available to the session.

Safety expectations

Linux support should preserve the existing safety model:

• explicit approval before controlling an application;
• clear indication of the active target application;
• additional confirmation for sensitive or disruptive actions;
• an immediately available way for the user to stop the task and regain control;
• no automatic escalation from shell access to desktop control.

No file, test, or entry point is named. Start by locating the Linux desktop app and the existing Computer Use flow on supported platforms, then trace activation, permissions, approvals, diagnostics, and x86_64/aarch64 packaging. Done means Linux users can enable Computer Use, operate an approved application, and receive actionable errors when support or permissions are unavailable.