Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Codex Desktop stays on 'Starting your task' and never dispatches thread/start
Reported by ipoel21 · filed Sep 30, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
System details
- CPU: AMD Ryzen 5 5600G with Radeon Graphics
- GPUs: NVIDIA GeForce RTX 3060 Ti (driver 610.57.04) and AMD Cezanne iGPU (
amdgpu) - Omarchy: 4.0.4-1
- Kernel: 7.2.5-3-omarchy
- Session: Wayland / Hyprland 0.56.2
- Codex Desktop package:
openai-codex-desktop 26.924.22138-1(Omarchy repository) - Bundled app-server:
codex-cli 0.158.0-alpha.2.1 - Separately installed Codex CLI:
codex-cli 0.159.2
What's wrong?
Codex mode in ChatGPT Desktop accepts a prompt in the UI, changes to “Starting your task”, and remains there indefinitely. No response or visible error is produced.
Regular ChatGPT mode works, and Codex CLI works normally with the same account and connection.
Steps to reproduce
- Install ChatGPT/Codex Desktop through Omarchy (
openai-codex-desktop). - Launch the Desktop app and use Codex mode.
- Select/open a local project and send a simple prompt such as
hello. - Observe that the UI remains on “Starting your task” indefinitely.
Expected behavior
The prompt should create a Codex thread/turn and produce a response.
Actual behavior
The Desktop frontend never dispatches the task to the bundled app-server:
- The app-server initializes successfully and reports a connected state.
- Authentication is detected successfully.
- Codex model requests return HTTP 200.
- After reproducing the hang, app-server logs contain no `thread/start` or `turn/start` request.
- The Codex
threadsdatabase contains no new Desktop-origin thread; its newest entries remain CLI-origin threads.
Troubleshooting already performed
The issue remains reproducible after each of these tests:
- Fully terminating all ChatGPT and bundled Codex processes.
- Removing and reinstalling
openai-codex-desktop. - Moving
~/.config/Codexaside and allowing the app to generate completely fresh Desktop state. - Launching on native Wayland.
- Launching explicitly with
--ozone-platform=x11. - Selecting a local project before submitting.
Codex CLI continues to work normally throughout, isolating the failure to the Desktop frontend-to-app-server dispatch path rather than the account, network, or Codex backend.
A secondary observation: one Wayland run of /usr/lib/chatgpt/ChatGPT --ozone-platform=wayland dumped core with SIGILL, although the persistent “Starting your task” failure also reproduces without a crash and under X11.
Diagnostics note
The documented omarchy debug --no-sudo --print command is unavailable on this installation and returns Unknown Omarchy command under Omarchy 4.0.4-1.
View raw text
## System details - CPU: AMD Ryzen 5 5600G with Radeon Graphics - GPUs: NVIDIA GeForce RTX 3060 Ti (driver 610.57.04) and AMD Cezanne iGPU (`amdgpu`) - Omarchy: 4.0.4-1 - Kernel: 7.2.5-3-omarchy - Session: Wayland / Hyprland 0.56.2 - Codex Desktop package: `openai-codex-desktop 26.924.22138-1` (Omarchy repository) - Bundled app-server: `codex-cli 0.158.0-alpha.2.1` - Separately installed Codex CLI: `codex-cli 0.159.2` ## What's wrong? Codex mode in ChatGPT Desktop accepts a prompt in the UI, changes to **“Starting your task”**, and remains there indefinitely. No response or visible error is produced. Regular ChatGPT mode works, and Codex CLI works normally with the same account and connection. ### Steps to reproduce 1. Install ChatGPT/Codex Desktop through Omarchy (`openai-codex-desktop`). 2. Launch the Desktop app and use Codex mode. 3. Select/open a local project and send a simple prompt such as `hello`. 4. Observe that the UI remains on **“Starting your task”** indefinitely. ### Expected behavior The prompt should create a Codex thread/turn and produce a response. ### Actual behavior The Desktop frontend never dispatches the task to the bundled app-server: - The app-server initializes successfully and reports a connected state. - Authentication is detected successfully. - Codex model requests return HTTP 200. - After reproducing the hang, app-server logs contain **no `thread/start` or `turn/start` request**. - The Codex `threads` database contains no new Desktop-origin thread; its newest entries remain CLI-origin threads. ### Troubleshooting already performed The issue remains reproducible after each of these tests: - Fully terminating all ChatGPT and bundled Codex processes. - Removing and reinstalling `openai-codex-desktop`. - Moving `~/.config/Codex` aside and allowing the app to generate completely fresh Desktop state. - Launching on native Wayland. - Launching explicitly with `--ozone-platform=x11`. - Selecting a local project before submitting. Codex CLI continues to work normally throughout, isolating the failure to the Desktop frontend-to-app-server dispatch path rather than the account, network, or Codex backend. A secondary observation: one Wayland run of `/usr/lib/chatgpt/ChatGPT --ozone-platform=wayland` dumped core with `SIGILL`, although the persistent “Starting your task” failure also reproduces without a crash and under X11. ### Diagnostics note The documented `omarchy debug --no-sudo --print` command is unavailable on this installation and returns `Unknown Omarchy command` under Omarchy 4.0.4-1.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 20:20 UTC