WinShun
Win顺：免费开源的 Windows 快速搜索启动器。双击 Ctrl，拼音秒搜文件、全文搜索 Word/Excel/PDF、剪贴板历史（代替 Win+V）、对话框搜索、任务栏搜索、插件、AI 助手 MCP。Free Windows search launcher: pinyin file search, full-text search, clipboard history, MCP server. Everything/Listary alternative.
Not yet verifiedsource: GitHubC++MITcommit 911f6876a0f6
C++, MIT licensed. The project labels itself: chinese, clipboard history, clipboard manager, cpp, everything, file search, full text search and launcher.
WinShun has not been verified yet.
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 20 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 most recent recorded attempt, which did not reach a 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.
- Top-level CMake hard-fails on Linux: 'WinShun targets Windows only' (Ubuntu 24.04 container, no root, no MSVC/Windows SDK)20 minutes
- Official WinShun 0.11.0 portable exited code 53 under wine (missing ICU DLLs followed by unimplemented mscms WcsCreateIccProfile/OpenColorProfileW)15 minutes
- Install time
- 45 minutes
- Cold machine to finish
- 35 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- wine64 (9.0) tst_tools.exe (cross-compiled from tests/tst_tools.cpp + src/tools-plugin) printed 'Totals: 14 passed, 0 failed, 0 skipped, 0 blacklisted'; wine64 extract_harness.exe (built from src/extract) printed status=ok 'Hello WinShun 你好世界' for gen.docx and 'Revenue 2025 收入' for gen.xlsx; wine64 WinShun.exe stayed alive on DISPLAY=:99 for 20s+ with WinShun.exe PID observed
- Model tokens used
- 4,726,313
- Exact commit tested
- 911f6876a0f6
- 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.
# 3. Official portable release (v0.11.0) WinShun.exe runs under wine 9.0 + Xvfb after fixing missin… # missing mscms WCS function; process stayed alive 20-40s, created AppData cache, QML pipeline c… # 4. Repo's own test file tests/tst_tools.cpp built against real src/tools-plugin sources cross-com… # Totals 14 passed, 0 failed, 0 skipped, 0 blacklisted - ran under wine as a real Windows binary. # 5. Repo's own src/extract document parsers cross-compiled unchanged for Windows; extract_harness … # \"Hello WinShun 你好世界\" from a docx and \"Revenue 2025 收入\" from an xlsx. # 6. The repo's demo screenshots files are 0-byte placeholders (no fixture docs shipped). echo \"done\"" in /work/repo succeeded in 0ms: done tokens used 4,726,313
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.
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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.99 |
Topics (from GitHub)
chineseclipboard-historyclipboard-managercppeverythingfile-searchfull-text-searchlauncherlistarymcpmcp-serverntfsocrpinyinproductivityqt6searchwindows
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/winshun)Questions
- Does WinShun run?
- WinShun has not been fully verified yet. No recorded run has produced a verdict yet.
- How did Argusic test WinShun?
- On a fresh, disposable machine, with every command recorded. One attempt is recorded, and the full method is on the methodology page.
- Where is the evidence for WinShun?
- 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.