A PhD student with 1 followers, a package name and one plea ("please, star it") got a DeepSeek plugin 25 stars a day

dsh-computer-use-win is the Windows PC-control plugin for DeepSeek Harness (DSH). The author has no followers, no group and no chart placements. It reached 554 stars in 82 days (GitHub, 11-06). Dozens of similar plugins are competing for the same slot, and it has the most stars of the Windows half. Its growth has no breakout moment, just a straight line. Below I break down how that line came about and which parts others can learn from.

Nov 1, a user drew a mockup

On the evening of Nov 1, 2026, a user named alar13050 made a wish in the plugin's issues: when DSH controls the computer, the agent often freezes for long stretches, and you can't tell whether it's thinking or stuck. Bringing up the DSH main window to check interrupts its actions. Could a semi-transparent overlay in a corner show what it's thinking? He even had an AI draw two mockups and posted them.

五分钟后作者回复:「谢谢建议,还专门做了效果图,很直观!」三天后的 11 月 4 日,0.5.4 发布,浮窗做好了:每一步一个小标题,比如「第 3 步 · 连续执行 7 个操作:滚动页面、等待」,做完显示「已完成 · 10 步 · 41 秒」,鼠标可以从上面穿过去。同一个版本里还有两条:另一个用户 10-31 许愿「确定不会跳转的页面一次多点几下」,做成了批量动作,填一张表从 5 次工具调用减到 1 次;有人报告截图以 base64 塞进上下文、三张图就把 1M 上下文撑爆,也修了。三个 issue 在同一分钟关闭。

That's the project's daily rhythm: 19 npm versions in 82 days, and 12 between 10-13 and 10-25 over two weeks. The author, Yu-tao-Li, has "PhD candidate" as the only text in the GitHub bio. The account was registered 2023 years ago, holds only this repo, and has 1 followers.

What it is

DSH is an agent framework open-sourced by DeepSeek in August, where everything is a plugin. Its main repo grew past 270k stars in just over a month. In mid-September the official project shipped computer use (letting the agent see the screen and move the mouse), but only on macOS 14 and later, marked experimental and off by default. Third-party tutorials say "Windows support is in development." Most Chinese-speaking users are on Windows, so this gap was open from day one.

This plugin fills the Windows gap:

• It reads buttons and input fields through Windows' built-in UI Automation, recognizes text with the system OCR, simulates clicks and typing, and manages windows. 25 operation tools plus 1 management entry points in total.
• Web pages go to DSH's own browser by default. Through the debugging protocol it fills forms and clicks buttons in the background, without moving your mouse or taking focus.
• When mouse or keyboard input is in use, the screen edges glow, a "DSH is controlling your computer" bar appears, and pressing Esc stops it immediately.
• Inside DSH there's a dedicated computer-control settings page, a record and screenshot for each step in the conversation, and the overlay described above.
• It also works outside DSH as a standard MCP server (npx -y dsh-computer-use-win).

MIT-licensed and forked from a 32-star Windows computer-use project. The third-party notes make clear which parts come from upstream and which were added. The README leads in Chinese, is bilingual, and uses only real screenshots from DSH.

How the stars came in: a straight line

Star counts come from GitHub's daily numbers; download counts come from npm's official stats. 10-24 is the turning point: before it, 67 days brought 107 stars; after it, 13 days brought over 400. On the same day, daily npm downloads jumped from 300–500 to 1,000–1,700 (10-28 at 1,714, 11-05 at 1,725), and last week saw 8,743 downloads. It never made any trending list, no one discusses it on X, and several "must-install DSH plugins" posts on Zhihu don't mention it. Three things stacking together explain the line:

The package name is the search term. In DSH, install a plugin by searching its name in the plugin market, or run dsh plugin add <name> in a terminal. dsh-computer-use-win is "DSH + computer use + Windows" joined together; on npm it has no prefix. The shorter dsh-computer-use was taken by another project that created its repo one day earlier (66 stars, no updates after mid-September), so this one got -win. How much that name is worth shows in a same-name repo: secretxuan/dsh-computer-use-win was created two days later and has only 5 stars, and it has to state in its README that the same-name npm package belongs to a different repo. Search "DSH 电脑操控 插件 Windows" on a Chinese search engine and this one is the first result.

It asks for stars inside the plugin itself. 10-24's 0.5.1 put this line at the top of the settings page: "Your Star is what keeps me updating, please, it really matters to me! For problems, open an Issue; you make the wishes, I'll build them!" Everyone who has the plugin sees it when they open the settings to adjust options; if it's annoying they can collapse it to a link. 1,000+ downloads a day (including upgrades) line up with 25–30 stars a day, with about 2% conversion (estimated). Stars and downloads turn on the same day, so the timing fits; but GitHub doesn't show who starred on which day, so "stars mostly come from the settings page" is an inference.

"Wishes, built" keeps people around. The second half of that settings-page line is not just politeness. The floating panel above went from mockup to release in three days. The issues section has specific bug reports from specific machines and scenarios (remote-controlling a PC through a QQ bot, 2560×1600 screens), and the author's replies are long, explaining the cause, the fix, and the test results. Users who see their input taken seriously are more likely to star.

Who it's competing with

In the DSH community's plugin roundup list (awesome-dsh-plugin), about 40 plugins relate to PC control, and more than half of them are for Windows.

By both stars and downloads, it is first among Windows PC-control plugins in the DSH community: its stars are more than 5× the second place, and its downloads are about 3× @copylee's. Someone is already using it as a base: nalikip/dsh-unified-desktop (10-29) merges it with Windows-MCP into one entry point. Others are copying its interaction design: the blue glow, Esc emergency stop, and the "observe–act–verify" loop, which also show up in other repos starting late October.

The features themselves have no moat. What others can't quickly catch up on is the name it grabbed first, and the level of polish built from more than two months of frequent iteration.

If it were you

B: anyone can use this playbook, and the author started from zero; but the Windows PC-control spot in DSH is already taken, so don't try to squeeze in. It didn't borrow anyone's traffic: 1 followers, 0 appearances on charts. It relied on a platform gap, an exact package name, asking for stars inside the product, and quick responses, and any follower can get all four. The weak point is the ceiling: in the same ecosystem, top plugins routinely have tens of thousands of stars, and this one got 554 stars in 82 days; and once the official Windows version ships, the gap closes.

Who it suits: developers who want a first project with a few hundred stars but have no followers or community; people willing to watch a new platform, answer issues every two or three days, and ship several releases a week.

Who it doesn't suit: anyone aiming for thousands of stars at once; this path is a straight line with no breakout moment. Also anyone planning another Windows PC-control plugin in DSH: forty similar ones are ahead, and the name is already gone.

How to do it: find a platform that just opened plugins and is picking up momentum (outside DSH, the AI agent tools, editors, and browsers are all opening plugin markets), then check which half the official side covered: only macOS, only English, only one IDE, only cloud. Build the other half, and before launch, claim an unprefixed package name that matches the search term exactly. In DSH, look at what neither official nor community has done well, like PC control on Linux desktops (nothing solid found, unverified), or companion tools for this kind of plugin (screenshot compression to save context, progress reporting when remote-controlling a PC); people are already asking for both in the issues section.

How to get users: no need to post; let the platform's search find you. The package name equals the search term, the README opens in Chinese with real screenshots, and you submit it to the platform's plugin directory and awesome lists. Then add a line in the plugin's own settings page or first-run prompt asking for a star; make it collapsible, not a pop-up. Add "you make the wishes, I'll build them," and actually build them, treating the issues section as your product roadmap.

When is "before": the earlier the better. A name can only be claimed once; the day the official side fills the other half, the gap is gone. In DSH, the official Windows computer use has already been announced as in progress, and it's likely to arrive within one to two months.

What would show the read is wrong: ① after DSH officially ships a Windows computer-use version, this plugin still adds 20+ stars a day, which would mean the product's reputation drives growth rather than the gap, and better-made competitors still have a chance; ② if the plugin collapses or removes the line in its settings page and star growth doesn't change, then "asking inside the product" matters less than assumed and stars mostly come from plugin-market search; ③ if someone copies this approach on another platform, fills a gap, and claims the exact name, but gets fewer than 100 stars in a month, then the path depends on DSH's platform heat (270k stars a month) and may not transfer to other platforms.