Skip to content

Results and methodology

Preliminary results, October 2026.:

Every score on this page is preliminary. This is the run of October 13, 2026, with the models, the dates and the method attached. Final numbers will replace these.

Every model got the same 49 Omarchy plugin requests. They are held-out test prompts: kept out of Usuba’s own training data and deduplicated against it — no training prompt shares more than half its wording with a test prompt, and no test answer is a near-copy of a training answer.

They are based on real Omarchy 4 plugins — community plugins, and the kinds of things Omarchy’s own shell does. Between them they cover every plugin type: bar widgets, panels, popups and overlays, menus, background services, and full replacement bars.

The task How many
Write a full plugin from a description 26
Add a panel to an existing bar widget 6
Build parts of a larger multi-file plugin 12
Fix a manifest Omarchy’s validator rejects 5

Everyday bar and shell tools: a clipboard manager, a notification daemon, a weather pill with a popup, a battery and power-profile widget, brightness controls, an internet speed test, a Dropbox status widget, a desktop background service, and a Bible verse-of-the-day widget.

Plus recreations of real community plugins: Time Machine (scheduled restic backups), Key Promoter (shows the keyboard shortcuts in play), Vimarchy (Vim-style window control), Omaland (a Hyprland look-and-feel editor), Intemporel (a clock with calendar support), Flush Bar, and Port Watch (dev servers in the bar).

The model is handed an existing bar widget’s manifest and asked to extend it with a detail panel: the same widget, now with somewhere to show more.

Large multi-file plugins, built in pieces rather than all at once: parts of Beam (an app launcher and command menu), Better Bar (a dynamic-island-style bar), and Omarchy Tablet (Surface tablet mode, with a bar, a service and a menu).

Repairing manifests that Omarchy’s own validator rejects: a reserved omarchy.* id, and entry-point paths that are absolute or point outside the plugin directory.

A plugin counts as working only when the Usuba Checker Scripts load it in a real Omarchy environment without errors and it actually does its job: real data rather than faked, controls that do something, and real Omarchy APIs. Loading cleanly is not enough on its own.

  • 49 real plugin requests, given to twelve models. Every first answer was run in real Omarchy and scored by the Checker Scripts.
  • Each model then got the scripts’ report and up to 3 more tries.
  • Omarchy version: 4.0.4. Run date: October 13, 2026, via OpenRouter.
Working plugins out of 49 · Preliminary results, October 2026.We ran the same 49 requests to every model through OpenRouter and ran the Checker Scripts against them up to three times.
  1. GPT-5.6Worked right away: 21Fixed by the scripts: 19Still buggy: 5Fully broken: 4
  2. Claude Opus 5.5Worked right away: 17Fixed by the scripts: 19Still buggy: 10Fully broken: 3
  3. Claude Sonnet 5.5Worked right away: 9Fixed by the scripts: 26Still buggy: 11Fully broken: 3
  4. Meta Muse WonderWorked right away: 12Fixed by the scripts: 21Still buggy: 14Fully broken: 2
  5. Kimi K3Worked right away: 3Fixed by the scripts: 29Still buggy: 9Fully broken: 8
  6. Gemini 4 ArgonWorked right away: 7Fixed by the scripts: 20Still buggy: 19Fully broken: 3
  7. Grok 4.7Worked right away: 1Fixed by the scripts: 26Still buggy: 17Fully broken: 5
  8. Gemini 3.1 ProWorked right away: 2Fixed by the scripts: 15Still buggy: 20Fully broken: 12
  9. DeepSeek V4 ProWorked right away: 4Fixed by the scripts: 6Still buggy: 12Fully broken: 27
  10. Grok 4.3Worked right away: 3Fixed by the scripts: 5Still buggy: 28Fully broken: 13
  11. Qwen3.6 27BWorked right away: 4Fixed by the scripts: 1Still buggy: 14Fully broken: 30
  12. Qwen3-CoderWorked right away: 4Still buggy: 15Fully broken: 30
  • Worked right away
  • Fixed by the scripts
  • Still buggy
  • Fully broken
  • proprietary open

Of 588 answers across the twelve models: 87 worked right away, 187 were fixed by the scripts, 174 stayed buggy and 140 never loaded.

Model Working plugins out of 49 On the first try
GPT-5.6 40 21
Claude Opus 5.5 36 17
Claude Sonnet 5.5 35 9
Meta Muse Wonder * 33 12
Kimi K3 32 3
Grok 4.7 27 1
Gemini 4 Argon 27 7
Gemini 3.1 Pro 17 2
DeepSeek V4 Pro 10 4
Grok 4.3 8 3
Qwen3.6 27B 5 4
Qwen3-Coder 4 4

* Meta Muse Wonder ran without zero data retention: its only provider, Meta, is not ZDR. Every other model ran with ZDR.

Give a model the scripts’ report and up to three more tries, and more of its plugins work. These numbers come from the scripts alone, not from our model.

First try vs. after up to 3 rounds of the scripts’ feedback, out of 49 · Preliminary results, October 2026.
  1. GPT-5.621 of 49 on the first try, 40 after the scripts' feedback21 40
  2. Claude Opus 5.517 of 49 on the first try, 36 after the scripts' feedback17 36
  3. Claude Sonnet 5.59 of 49 on the first try, 35 after the scripts' feedback9 35
  4. Meta Muse Wonder12 of 49 on the first try, 33 after the scripts' feedback12 33
  5. Kimi K33 of 49 on the first try, 32 after the scripts' feedback3 32
  6. Gemini 4 Argon7 of 49 on the first try, 27 after the scripts' feedback7 27
  7. Grok 4.71 of 49 on the first try, 27 after the scripts' feedback1 27
  8. Gemini 3.1 Pro2 of 49 on the first try, 17 after the scripts' feedback2 17
  9. DeepSeek V4 Pro4 of 49 on the first try, 10 after the scripts' feedback4 10
  10. Grok 4.33 of 49 on the first try, 8 after the scripts' feedback3 8
  11. Qwen3.6 27B4 of 49 on the first try, 5 after the scripts' feedback4 5
  12. Qwen3-Coder4 of 49 on the first try, 4 after the scripts' feedback4 4

first try after the scripts’ feedback

The largest gains went to the models that started weakest: Kimi K3 +29 (3 → 32), Claude Sonnet 5.5 +26 (9 → 35), Grok 4.7 +26 (1 → 27), and Meta Muse Wonder +21 (12 → 33).

The figures above are preliminary results from October 2026. [TBD: final numbers, and whether the gains are measured on the same 49 requests].

These are tracked against BRIEF.md > Open questions and must be answered before this page ships as final:

  1. How do the 49 requests, the 90-plugin answer key and the 1,400+ plugin sweep relate?
  2. How was “working” judged, and by whom?
  3. Exact model versions for every entry, and the run date confirmed.