claude-desktop-zh-cn
Claude Desktop Chinese Patch (macOS & Windows & Linux)
Could not verifysource: GitHubhomepagePythonMITcommit ef9202da36da
Python, MIT licensed.
Argusic could not get claude-desktop-zh-cn running. An Argusic agent installed it in 18 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Repository resources validated (16 JSON files, 3 Python scripts compile OK). Core patching logic verified with mock asar injection: __claudeZhOnlineLocaleMain and __claudeZhLocaleLock markers confirmed, frontend bundle language whitelist patched. Full install requires sudo-access to /usr/lib/claude-desktop which is unavailable.
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 10 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.
- Claude Desktop (official deb) not installed; sudo unavailable; cannot run install_linux.sh
- Install time
- 18 minutes
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- patch_linux_asar.py /tmp/claude-mock/resources/app.asar zh-CN /tmp/claude-mock/resources exited 0; asar byte scan confirms __claudeZhOnlineLocaleMain and __claudeZhLocaleLock markers present in .vite/build/index.js; frontend bundle confirms zh-CN whitelist + label patch injected; merge_json produces valid output
- Model tokens used
- 401,120
- Exact commit tested
- ef9202da36da
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
patch_linux_asar.py: compiles OK install_linux.sh: exists (9381 bytes) exec /bin/sh -lc 'date +%s && echo "---" && echo "Started around epoch: $(date -r 1695918547)" && echo "… succeeded in 0ms: 1790614032 date: 1695918547: No such file or directory Started around epoch: Current time: Mon Sep 28 16:47:12 UTC 2026 tokens used 401,120
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
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- 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
- An agent with no time limit did not get it running.
- Took 18 minutes to install, slower than the median of the 16 comparable projects Argusic has measured.
Of the 17 Python projects Argusic has installed and timed, claude-desktop-zh-cn was the 17th fastest to reach a running state, and 9 of 17 reached one at all.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Did not run | 20.00 | 0.14 | |
| Argusic Runner | 1/3 | Did not run | 0.00 | 0.11 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/claude-desktop-zh-cn)Questions
- Does claude-desktop-zh-cn run?
- Argusic could not verify that claude-desktop-zh-cn runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test claude-desktop-zh-cn?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ef9202da36da. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test claude-desktop-zh-cn?
- The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does claude-desktop-zh-cn take to install?
- 18 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 claude-desktop-zh-cn need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing claude-desktop-zh-cn?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does claude-desktop-zh-cn compare with the alternatives?
- Of the 17 Python projects Argusic has installed and timed, claude-desktop-zh-cn was the 17th fastest to reach a running state, and 9 of 17 reached one at all.
- Where is the evidence for claude-desktop-zh-cn?
- 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.