Codex-X

OpenAI Codex 桌面端/CLI 的可视化管理工具,具有Provider/API 切换、会话同步、提示词注入、Skills/MCP 管理、TOML 配置可视化的跨平台工具。

Runssource: GitHubhomepageRustMITcommit 8f018fddd3ee

Rust, MIT licensed.

Codex-X runs. An Argusic agent installed it in 40 minutes and hit 9 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The UI fixture serves the React app on port 1421; the Rust backend tests pass (683/683); the JS tests pass (79/79); the star-history worker tests pass (13/13); the Tauri desktop binary compiles and launches but cannot render its WebKit window due to the hardcoded /usr/lib/x86_64-linux-gnu/webkit2gtk-4.1/ helper path requiring root to install the runtime.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.15 (measured)
recorded runs
2
last tested
stars
4,539
forks
593
open issues
13
watchers
16
size
14 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing Codex-X, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Rust build: pkg-config could not find glib-2.0, gio-2.0, gtk+-3.0, webkit2gtk-4.1, libsoup-3.0, etc.5 minutes
  • Rust build: rust-lld unable to find libraries (lgdk-3, lz, lwebkit2gtk-4.1, etc.)5 minutes
  • Node.js v18.19.1 too old for Vite 7 (requires 20.19+)3 minutes
  • Runtime: undefined symbol gst_context_set_gl_display from stub libgstgl3 minutes
  • Runtime: libdw.so.1 and liborc-0.4.so.0 not found2 minutes
  • pnpm not found in PATH1 minute
Install time
40 minutes
Cold machine to finish
40 minutes
Errors hit and fixed
9 hit, 9 fixed with no human help
How the result was proved
cargo test --lib exited 0 with 683 passed; npx tsx --test tests/*.test.mjs across 11 files reported 79 passed, 0 failed; node --test in star-history-worker reported 13 passed, 0 failed; Vite build succeeded (1728 modules), tsc --noEmit passed, UI fixture server started on port 1421
Model tokens used
549,020
Exact commit tested
8f018fddd3ee
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

drwxrwxr-x 2 runner runner  176 Nov  8 13:53 provider-logos
-rw-r--r-- 1 runner runner  327 Nov  8 13:53 theme-init.js
=== Time elapsed check ===
Sun Nov  8 13:55:26 UTC 2026
exec
/bin/sh -lc 'echo "Install succeeded: pnpm install completed, npm packages installed globally, Node…
echo "Launch: Desktop app binary starts but fails due to hardcoded WebKit helper path requiring roo…
 succeeded in 0ms:
Install succeeded: pnpm install completed, npm packages installed globally, Node 20.19 downloaded, …
Launch: Desktop app binary starts but fails due to hardcoded WebKit helper path requiring root; UI …
tokens used
549,020

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Recovered from all 9 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 40 minutes to install, slower than the median of the 17 comparable projects Argusic has measured.

Of the 18 Rust projects Argusic has installed and timed, Codex-X was the 17th fastest to reach a running state, and 17 of 18 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.15
Argusic Runner1/3Runs with mocks92.000.05

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/Codex-X.svg)](https://argusic.com/subject/codex-x)

Questions

Does Codex-X run?
Yes. Codex-X runs. Argusic installed and launched it on a clean machine in 40 minutes, hitting 9 errors on the way, and recorded the session.
How did Argusic test Codex-X?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8f018fddd3ee. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test Codex-X?
The run that produced this verdict cost $0.15: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does Codex-X take to install?
40 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does Codex-X need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing Codex-X?
9 things broke in the recorded run, and 9 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does Codex-X compare with the alternatives?
Of the 18 Rust projects Argusic has installed and timed, Codex-X was the 17th fastest to reach a running state, and 17 of 18 reached one at all.
Where is the evidence for Codex-X?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion