Repository navigation
Triage data: 78 open PRs are 16 distinct fixes (verified by shared file) #11049
Description
Not a bug report - triage data, in case it is useful for the open-PR queue.
I clustered all 2091 open PRs by title, then verified every candidate against the files each PR actually changes. Below are only the groups where the PRs touch the same primary file for the same stated purpose. Tests, docs, READMEs and assets were excluded from the file comparison, since two PRs both adding a test file is not evidence of anything.
78 open PRs, 16 distinct fixes
| # | What | PRs |
|---|---|---|
| 10 | omarchy-windows-vm setgid / set-ID on mount sources |
#9414, #9504, #9564, #9605, #10046, #10411, #10489, #10595, #10906 (+1) |
| 8 | Grok usage collector | #6485, #6902, #7200, #8280, #8649, #9498, #9840, #10074 |
| 8 | Antigravity usage collector | #7701, #8446, #8479, #8693, #8911, #9216, #10515, #10554 |
| 8 | omarchy toggle bar on/off inverted |
#7023, #9074, #9102, #9455, #10099, #10623, #10635, #10932 |
| 7 | OpenCode usage collector | #6526, #7082, #7687, #7765, #8065, #8823, #9944 |
| 4 | Sunshine canonical systemd unit | #8136, #8879, #9104, #9979 |
| 4 | Idle-inhibit Steam games | #7334, #9651, #9667, #10447 |
| 4 | Universal clipboard on non-Latin layouts | #6419, #7285, #7375, #10247 |
| 4 | Combined dual-battery reporting | #7138, #7186, #10384, #10392 |
| 4 | Dismiss low-battery warning on charge | #7688, #8838, #8895, #10900 |
| 3 | Vivaldi browser support | #5774, #6593, #9430 |
| 3 | Fuzzy menu search | #7016, #7358, #8987 |
| 3 | Hermes usage collector | #6645, #6647, #9871 |
| 3 | Copilot usage collector | #7798, #8972, #9945 |
| 3 | Remember menu position when navigating back | #7074, #7800, #7954 |
| 2 | Sublime Text default editor (subl) |
#9656, #9673 |
The omarchy-windows-vm group is the sharpest: all ten change only bin/omarchy-windows-vm, for the same setgid clearing. One of them (#9605) is omarchybot's own.
The larger pattern behind it
At least 67 open PRs touch bin/omarchy-agent-usage-*, across 24 providers:
grok 11 codex 11 update 10 opencode 10 claude 9 antigravity 7
cursor 4 kimi 3 hermes 3 fireworks 3 copilot 3 agy 3
zai 1 synthetic 1 snapshot 1 pi 1 openrouter 1 openclaw 1
omp 1 ollama 1 muse 1 minimax 1 kiro 1 deepseek 1
Half of those providers appear exactly once, so they are not duplicates of anything — they are 24 people independently writing the same shape of script.
A further 10 PRs add a provider to the coding-agent picker in bin/omarchy-agent (#6827, #6844, #6969, #7261, #7693, #8051, #8450, #9257, #10079, #10913) — those are not duplicates of each other, they add different agents.
Where the same provider appears many times over, that is duplication. Where many different providers each need a near-identical script plus SVG pair plus manifest entry plus scanner test, that reads more like a missing extension point than sixty separate contributions. That is a design call, not something triage data can settle.
Method and limits
- Clustered titles by shared rare tokens, then required a shared primary file before calling anything a duplicate.
- Groups here were additionally checked by hand.
- False positives the file check caught, listed so the method's failure mode is visible: Add speaker tuning for the ThinkPad X1 Carbon Gen 11 #9495 / Add ThinkPad X1 Carbon Gen 6 speaker tuning #9348 look like duplicate ThinkPad speaker tuning but are
gen11vsgen6, different directories; Confirm destructive power actions in the system menu #9838 clusters with the menu-ranking PRs but addsConfirmDialog.qml, a different feature; the/tmphardening PRs ([Security] Keep the 1Password lock flock out of world-writable /tmp #10503-[Security] Stage menu IPC files out of world-writable /tmp #10506) name different targets and are a deliberate series. - The automated pass produced ~146 candidate groups covering ~349 PRs. I am deliberately not publishing that list, because the heuristic mislabels in both directions and the wider set has not been hand-checked. The 16 above have.
- Snapshot taken 2026-09-09.
Happy to share the full candidate list, the scripts, or re-run it whenever it would help. No action needed on this issue itself — close it whenever it has served its purpose.
Activity
aholbreich commentedon Sep 9, 2026
Deep Seek PR: #10683
aholbreich commentedon Sep 27, 2026
Update 2026-09-27
Most of the groups above were closed in the 09-20/21 duplicate sweep: 62 of the 92 PRs listed here are closed now, and #9656 (Sublime Text) was merged. I re-ran the same method against today's 2,598 open PRs (2,091 at the first snapshot). Everything below was checked by diff, not just by title.
Groups that grew back
omarchy-windows-vmclear setgid on mount sourcesomarchy toggle baron/off invertedagyvsantigravityfile name)All eight windows-vm PRs make the same
chmodchange at the same two call sites. #10113 fixes the same bug the other way round, by accepting the mode instead of clearing it. #11803 documents the current toggle bar behaviour instead of flipping it.New groups
shell.jsonomarchy update -yOMARCHY_PATHin update-devPlus 27 pairs where two PRs change the same lines for the same fix:
#7783/#12658, #11069/#11470, #8429/#12957, #10413/#13214, #13041/#13100, #13044/#13094, #8875/#12569, #11235/#12196, #11344/#13236, #11364/#12089, #11893/#12021, #11918/#12544, #11273/#12420, #12585/#13204, #10749/#12241, #12649/#12755, #11565/#12831, #11933/#12870, #10159/#11169, #9847/#13314, #8692/#13090, #8414/#12936, #10877/#11624, #8406/#13364, #11728/#12533, #8023/#12574, #7833/#11338
Usage collectors
Open PRs touching
bin/omarchy-agent-usage-*went from 67 to 94, and providers from 24 to 30. #12353 (collectors discovered from~/.config/omarchy/agents/collectors, with #8267 as an older take on~/.local/bin) is the extension point the first post was hinting at. My own DeepSeek collector (#10683) is one of the 94 and would not need to live inbin/if that lands.Method
Same as before: shared primary file first, then a manual read of each diff. Left out on purpose: same-author resubmissions, deliberate series (the Intel Mac P13 work), and larger PRs where the fix is one part of something bigger (#12109, #11580, #10400).
Add a first real-backlog trial with independently checked Omarchy cas…
aholbreich commentedon Oct 6, 2026
Update 2026-10-07
The Oct 1–4 sweeps did most of the work: of the 147 PRs in the Sep 27 update, 47 are closed and 3 merged. I re-ran the same method against today's 2,746 open PRs, checking every group by diff.
Leftovers: winner chosen, same fix still open
Sunshine got two different winners: #12472 was closed for #12358, #13331 for #12505. #12358 makes #12505's unit-name change and also removes the duplicate Hyprland autostart, with a migration. #13230 and the new #13925 are the unit-name fix only, and #12271 adds a security-floor upgrade on top.
Already fixed: #14133 (merged Oct 3) keeps the Wi-Fi icon on
wifiDevice.connected, so #10630 and #12126 are redundant, and #13738 only restyles the merged lines.New groups
expireTimeoutomarchy-restart-bluetoothrestarts the servicefont-setkeeps the Foot sizefont-setsilencespgrepomarchy debugoutside$OMARCHY_BIN_DIRnvidia_wmi_ec_backlightSome of these are competing approaches rather than identical changes (noon vs UTC for the calendar, process groups vs a parent check for the speedtest, DRM connector vs name filter for FALLBACK).
The Sep 27 groups that had no closures are all still open: Vivaldi, fuzzy search, Wi-Fi passphrase toggle, keyboard backlight after blanks, last valid
shell.json, fontconfig drop-in, keybindings Lua scan, app ranking, Ctrl-N/P, lock reveal,OMARCHY_PATHin update-dev, and 11 of the pairs. 21 PRs in these groups need a rebase after #14253, but none of their fixes has landed.Usage collectors: open PRs touching
bin/omarchy-agent-usage-*went from 94 to 44 after the consolidation into #13992, #14039 and #14040.Method
Same as before: 494 PRs opened since Sep 27, scored against all open PRs by shared primary files weighted by rarity (tests, docs and assets excluded), then every candidate diff read. Same-author resubmissions, backports and deliberate series are left out.
jandrusk commentedon Oct 13, 2026
Thanks for the clustering work — it has been useful for the open-PR queue. Most of the groups you listed were already closed in the Sep/Oct duplicate sweeps.
I'd close this as informational/done unless you want to keep posting periodic re-runs as comments on a fresh issue.
aholbreich commentedon Oct 13, 2026
I'm not sure how much value is it to post it here. Let me know.
aholbreich commentedon Oct 20, 2026
Agreed. Most of these groups are gone after the sweeps, and duplicate clusters now reach the team as Basecamp tickets, so a running issue adds little. Closing.