codex-rehome
Offline Codex Desktop migration for Windows and macOS.
Runssource: GitHubRustMITcommit 121ba939bbee
Rust, MIT licensed. The project labels itself: agent handoff, ai agent, backup, codex backup, codex desktop, codex migration, codex restore and codex skill.
codex-rehome runs. An Argusic agent installed it in 55 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 312 tests across React frontend (vitest), Node scripts, and Rust backend (cargo test) pass. The project compiles and its full test suite runs on Linux.
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 100 of 100 (the mean of this project's run scores).
At a glance
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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Missing system dev libraries (glib-2.0, gtk+-3.0, webkit2gtk-4.1, libsoup-3.0, JavaScriptCoreGTK)8 minutes
- Linker (lld) could not find webkit2gtk, soup, and JavaScriptCore .so files (broken symlinks in sysroot)5 minutes
- updater:default capability permission not found on Linux (tauri-plugin-updater excluded on Linux in Cargo.toml and lib.rs)3 minutes
- 7 bridge tests failed: restore target paths must be absolute3 minutes
- Rust toolchain not installed2 minutes
- discovery_reports_fixture_without_modifying_it panicked: is_forbidden() matched tmp in /tmp/... path2 minutes
- Install time
- 55 minutes
- Cold machine to finish
- 54 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- npm test (52 vitest tests passed), node --test (2 script tests passed), cargo test (258 Rust tests passed)
- Model tokens used
- 1,218,018
- Exact commit tested
- 121ba939bbee
- 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.
1. Rust not installed → installed via rustup 2. Missing system `.pc` and `.so` files (glib, GTK, webkit2gtk, libsoup, JavaScriptCore) → extracte… 3. `updater:default` capability unknown on Linux → removed platform gate so updater plugin compiles… 4. `restore target paths must be absolute` test failures → `current_source_os()` returned `Windows`… 5. `is_forbidden()` rejected temp paths under `/tmp` → changed fixture to use `/home/runner/tmp_tes… **Verified how**: all three test suites ran and reported results: | Suite | Tests | Pass | Fail | |---|---|---|---| | Vitest (React frontend) | 52 | 52 | 0 | | Node script tests | 2 | 2 | 0 | | Rust (cargo test) | 258 | 258 | 0 | This exercises the core library (packaging, planning, restore, discovery, bridge, backup, legacy su…
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.
- Installed in 55 minutes.
- Recovered from all 7 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
agent-handoffai-agentbackupcodex-backupcodex-desktopcodex-migrationcodex-restorecodex-skilldeveloper-toolsmac-to-windowsmacosmcpmigrationopen-sourceopenai-codexpluginssessionsskillswindowsworkspace-migration
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/codex-rehome)Questions
- Does codex-rehome run?
- Yes. codex-rehome runs. Argusic installed and launched it on a clean machine in 55 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test codex-rehome?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 121ba939bbee. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test codex-rehome?
- The run that produced this verdict cost $1.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does codex-rehome take to install?
- 55 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-rehome need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing codex-rehome?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for codex-rehome?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.