"Zed has no Chinese version": a one-person Zed fork adds Simplified Chinese, gains 256 stars in a week

dstrml/wu is a fork of the Zed editor, written mostly by one person. It made the rounds in the English world on Product Hunt and r/rust and picked up 200 stars over two months. In Oct 26 the author added a Simplified Chinese interface, the only language pack in the repo. A week later several Chinese X accounts and a Telegram channel shared it, and it gained 256 stars in 7 days, versus 7 stars in the 7 days before. It took off not because its agent features are impressive but because it added the Chinese interface Zed never provided. Below: what it is, how the stars came in, whether the tactic can be copied, and whether it's worth copying.

Late night Nov 2, a post reading "I uninstalled VS Code"

2026 年 11 月 2 日北京时间晚上 11 点半,X 上的陈大黄(@realchendahuang)发了一条推:

"I uninstalled VsCode and installed Zed. Didn't expect there to be an even more badass Wu?"

The image was the memory comparison from Wu's website. A few hours earlier he had posted that Zed "is already my main reader... the installer is only 50 MB, small but complete." The post got 32k views. The most typical reply, from G 师傅: "This data is brutal: Wu sits at 583MiB when searching a repo, Zed shoots up to around 1.4G, no wonder old machines choke on big repos." Others complained about Zed itself: "What bugs me most is how slowly bug-fix feedback gets merged" and "I really dislike Zed's diff view."

On the same day, the Telegram channel 「可莉日常」 (reposted from the Loon community) posted a line: "a trimmed-down version of the Zed editor, native Chinese support, written in Rust", 9,240 reads. The next afternoon, a big voice in the Chinese open-source circle (@jaywcjlove) posted "Wu - a fast native code editor written in Rust… idle memory use cut by about 49%", 17.3k views. On Nov 5, 陈大黄 posted a second one, this time saying it outright:

"The Zed editor is good, but it has no Chinese version and the author has no plans to add one. Better to use a fork of Zed: Wu, with Chinese built in, even prettier, and more ergonomic."

The link went straight to the Chinese page on the official site, wu.dstrml.org/zh/, with 13.6k views. The four posts together reached roughly 70k views.

What it is

The first line of Wu's README: "A fast native code editor written in Rust, with a clean modern interface and a built-in programming agent." The name comes from "无为" (wuwei). It keeps Zed's Rust/GPUI core and extension ecosystem, and changes these things:

• Removed: multiplayer collaboration, telemetry, Vim mode, Zed's own AI.
• Reshaped around VS Code habits: the layout and default settings lean toward VS Code, aimed at people who find Zed hard to get used to. One reply said exactly that: "I feel Zed's dev experience would be better if it were more like VS Code. After a few days with it I still feel very out of place."
• Agent Chat panel: directly calls Claude Code, Codex, and OpenCode that you're already logged into on your machine, with no API key and no account to register. That said, Zed can also plug in these external agents through the ACP protocol, so this isn't unique to Wu.
• Simplified Chinese interface: merged PR #27 "Add i18n and chinese support" from 10-26. The locale directory contains only zh-CN, the official site launched /zh/ at the same time, and the README got a Chinese version.

Free, GPL-3.0 licensed, no login, no data collection; it can be installed alongside Zed and Zed's extensions still work. The macOS installer is unsigned, so you have to allow it manually the first time you open it. 11-06 has reached v1.1.18, and on the day it was still committing "reduce release package size." The author is Faisal Arshed (GitHub farshed); the repo was first hosted under his personal account and later moved to the dstrml organization.

How the stars came in, day by day

(Daily GitHub star counts, based on when each day's data was scraped, lag about half a day behind the posts. Trendshift counts in UTC; the single-day high was 11-03 at +123. 11-06 The GitHub page shows 502 stars and 33 forks.)

The contrast is clear: in the English world, two months of Product Hunt plus r/rust brought in a few dozen stars total; in the Chinese world, four posts brought over two hundred in a week. It never appeared in big English-language accounts or on Hacker News.

Why this one got shared

First, the demand was already proven. Zed has long had a good reputation among Chinese developers, but official Chinese support still hasn't shipped. Discussions about localization in Zed's repo issues and RFCs have dragged on for a long time, so the community has done translations itself: x6nux/zed-globalization has 1,131 stars, TC999/zed-loc has 440 stars, and AUR has zed-cn-bin. These projects only translate and repackage upstream, and some people find them "bloated." People wanting a Chinese Zed have always been around; Wu is the one that made "built-in Chinese" its selling point and got pushed out by Chinese bloggers.

2. There's a screenshot-ready number set. The official site turns "free memory Wu 383 MiB, Zed 420, VS Code 744" into a comparison chart (the author's own test). Chen Dahuang runs this chart, Xiao Di Diao just writes "about 49% less," and the comments keep arguing over these numbers. This is the kind of thing creators repost.

Third, it can be explained in three sentences. A fork of Zed, with Chinese built in, using half the memory of VS Code. The Chinese posts barely mentioned agents. The agent panel is a bonus; what made people click was "Chinese" and "light."

Fourth, switching costs nothing. It's free, needs no login, extensions still work, and you don't have to uninstall Zed. After reading the post, you can install it and try it at zero cost.

Who else is in the space

(GitHub star counts and Hacker News scores as of 11-06.)

The table shows there are already several Zed forks, and in the English world Wu is just one of them. It broke out in the Chinese world through one combination: fork + Chinese + promotion. Translation-only localization projects have stars, but nobody shared them as new products.

How long it lasts

Daily growth has already fallen from +130 to +40. I haven't seen anyone copy it, but its edge is thin:

• Anyone can add Chinese. Localization projects can keep their builds small too, and if Zed ships official Chinese someday, this opening is gone. Under 陈大黄's post, someone already commented "Other authors made Chinese versions... I'm using openidea now, it feels even more resource-efficient than wu."
• One person chasing a fast-moving upstream. Zed updates quickly, and every upstream merge means resolving conflicts. People on r/ZedEditor have already complained that maintaining the fork is exhausting.
• A few facts are still unclear: whether the bloggers posted it on their own or the author reached out to them, which I couldn't find out, and the real download numbers are unknown.

If it were you

C: There's a good playbook to learn here, but cloning Zed into another Chinese fork isn't worth it. The playbook: find an open-source tool with a good reputation that the official team won't localize, add one language, and get the big accounts in that language community to share it. It really is cheap and it works. But Wu got only two or three hundred stars from it, and it comes with the heavy job of maintaining a Zed fork. The Chinese gap is already being filled by Wu and several other localization projects, and zed-i18n even covers Japanese and Korean.

Who it's for: developers who already use an English open-source tool heavily and find it lacks Chinese (or Japanese, Korean); people who want a few hundred stars to build a track record and an audience, and who know one or two Chinese recommendation accounts.

Who it's not for: anyone who wants to build yet another Chinese fork of Zed (the Chinese gap is taken, and you'd have to keep chasing upstream); anyone aiming for thousands of stars (a localized fork's ceiling is the small slice of upstream users who don't want to read English); anyone not planning to maintain it long-term (once the fork stops updating, nobody uses it).

How to do it, from best to worst:

1. Switch upstream: look for developer tools that have a good reputation in the Chinese community, where the official team has been slow to add Chinese and localizing is painful. Ideally they're smaller than Zed so a fork won't wear you out. For desktop tools like terminals, database clients, API debuggers, note apps, and Git clients, first search their issues for "i18n" or "Chinese". If people keep asking and the maintainers don't respond, that's a candidate. If upstream supports plugins or language packs, make a language pack instead of a fork.
2. Do what it does poorly: Wu's agent panel isn't much different from what Zed can do. The real differences are Chinese and lightweight. If you go the editor route, do a thorough job on what Chinese users need: connect domestic models and Chinese agent CLIs, set up domestic mirrors by default, so "Chinese" means more than translated menus.
3. Copy its packaging: whichever option you pick, you need a comparison chart you can screenshot (memory, package size, startup time), a line like "X has no Chinese, mine does", a Chinese landing page, and a one-line install command.

How to get users: send the Chinese page and comparison chart straight to Chinese open-source recommendation accounts and Telegram channels, like 小弟调调, 陈大黄, and the many "open-source finds" accounts. Write the copy so they can paste it as is. Product Hunt and Reddit in the English world barely work for this kind of project; Wu already tested that.

How early you need to be: the window depends on upstream. The moment upstream ships official Chinese, the window closes. Before you start, check whether upstream's i18n discussions have anything scheduled. If nothing is scheduled, the earlier you build, the better.

Signs you've misread it: ① your project gets shared by a major Chinese account and still hasn't reached 100 stars a week later, meaning "adding Chinese" is no longer new enough for bloggers and readers; ② Wu's daily growth stays in the double digits or higher through late December and it passes a thousand stars, meaning this gap is bigger than estimated here and a Chinese-localized editor direction deserves a second look; ③ the reverse: if Zed officially ships a Chinese interface in the coming months and Wu's growth stalls, the playbook only lasts as long as upstream ignores it, so when choosing upstream, pick one that has clearly stated it won't do localization.