Koolson/Qure: the policy icon set for Quantumult X, and what it does not do

What Qure actually is, and who it is for

Qure is not a tool. It is a set of images and two index files that tell Quantumult X which image to draw next to which policy group. The README describes it as a set of icons designed specifically for policy groups inside Quantumult X, and the repository layout confirms that shape: an IconSet/ directory, an Other/ directory holding the JSON indexes and the preview images, and a README. There is no source code, no build step and no runtime.

The audience is narrow by design. You need Quantumult X installed, you need to be editing a policy group, and you need to care that the group shows a flag or a service logo rather than a default glyph. If you use Surge, Clash or sing-box, the icons are still PNG files you could point at, but nothing in the README claims support for those clients, and the subscription files are shaped for Quantumult X. Treat the project as a Quantumult X asset, not a general icon library.

The value is legibility. A policy group list with twenty entries is hard to scan; the same list with a Hong Kong flag, a Netflix mark and a Telegram mark is not. That is the whole product.

How the subscription mechanism works

The mechanism is deliberately thin, and that is the point. Two JSON files in Other/ act as manifests. Quremini.json points at the white icon set, and QureColor.json points at the colour set. Each entry in those manifests maps an icon name to a raw image URL under IconSet/. Quantumult X reads the manifest, resolves the URLs, and caches the images locally against the policy group names you have configured.

Because the manifest is a remote file, updates flow without you touching the app: when the repository changes, the next refresh of the subscription picks up the new mapping. That is also the failure mode. If a manifest entry is renamed or removed, a group that referenced the old name falls back to whatever Quantumult X shows for an unmatched icon. The v2.7 changelog records exactly this kind of churn: icons renamed (ITV_Hub.png, x0.1.png, x1.png and others), icons archived (Direct.png, Proxy.png, Reject.png), and one icon deleted (ITV Hub.png, the spaced version). Anyone whose config referenced the archived capitalised names lost the match at that point.

The naming convention is worth noting because it is the interface. Icons come in a plain form and a _Letter form (SS.png and SS_Letter.png, YouTube.png and YouTube_Letter.png), which lets you pick a logo-only tile or a logo with a wordmark. Area icons exist in both full-name and short-code forms (Hong_Kong.png and HK.png, United_States.png and US.png). The README says all icon names can be learned from the preview image, which is the only complete index the project publishes.

Adding Qure to Quantumult X: the two subscription URLs

There is nothing to install in the package-manager sense. The README gives two subscription URLs and says which one to use where: Qure mini (pure white) is recommended for the PROXY subscription, and Qure Color is recommended for custom policy groups. You paste the URL into Quantumult X's icon subscription field and refresh.

The two raw URLs are the entire interface:

https://raw.githubusercontent.com/Koolson/Qure/master/Other/Quremini.json
https://raw.githubusercontent.com/Koolson/Qure/master/Other/QureColor.json

The first is the white set for the PROXY group; the second is the colour set for custom policy groups. Beyond these two URLs, the README documents no fetch command, no local path and no configuration key. The repository does show that the icons themselves live under IconSet/ and that the manifests and preview images live under Other/, so if you want to inspect the set before subscribing, that is where to look in the repository tree. The README does not document rollback, does not document pinning to a specific commit, and does not describe how Quantumult X caches or expires the fetched images. If you need a frozen set, the README offers no documented route.

The naming trap, and other cases where Qure is the wrong tool

The most common way to get a broken result is a name mismatch. Qure does not guess. If your policy group is called "Streaming" and the icon file is Streaming.png, it matches; if you renamed the group to "StreamingSE" and expected the Streaming icon, it does not. The v2.7 changelog shows the project itself renaming and archiving files, so a config that worked in 2020 may not work now.

Second, the project is stale in content even though the repository has been pushed more recently. The last changelog entry in the README is v2.7, dated 2020-4-12. The repository's last push was on 2026-06-30, but no release has been published and the README documents no icon additions after v2.7. If you need an icon for a service that became prominent after April 2020, the README gives you no reason to expect it here. Do not read the recent push date as a promise of new icons; read the changelog instead.

Third, the licensing position is a genuine blocker for some users. The disclaimer states that the icons and logos are shared for reference and learning, that their legality and accuracy are not guaranteed, and that the project must not be used for any commercial purpose or for profit. There is no LICENSE file at the top level of the repository, and the field is reported as unknown. If you are building a product, an internal commercial tool, or anything you bill for, the README's own terms rule Qure out. That is not a legal opinion, it is what the disclaimer says.

How Qure differs from a general icon pack

The obvious alternative is not another proxy icon set; it is an icon library such as the ones shipped for dashboards and app UIs, or simply your own PNGs. The difference in approach is real. A general icon library gives you a licence, a versioning scheme, a changelog you can trust and a searchable index. Qure gives you a curated set that already speaks the vocabulary of proxy use: region codes, airline and cloud provider marks, streaming services, and the default policy names Quantumult X itself uses (Direct, Proxy, Reject, Static, Round_Robin, SSID, Available).

That vocabulary is the reason to pick Qure over a generic pack. A generic pack has no HK.png, no CN2_GIA.png, no IEPL.png, and no _Letter variants sized for a policy row. You would spend an afternoon assembling the same set by hand. The trade is that you inherit the project's staleness and its non-commercial disclaimer, which a permissively licensed icon library would not impose.

A second alternative is to fork the repository. The disclaimer asks that you credit the source when reposting, and says infringement reports should go to Issues. Forking gives you a private manifest you control, at the cost of maintaining the icon set yourself.

Maintenance, upgrade cost and licence implications

Upgrading is close to free if you subscribe to the raw URLs: you change nothing and Quantumult X re-fetches. It becomes expensive only when you pin, because pinning means you own the copy. The repository has no releases, so there is no versioned tarball to pin to; the only stable reference is a commit hash from master.

The maintenance burden sits with the upstream project, and the README does not describe a contribution process beyond the disclaimer's note that infringement reports go to Issues. There is no stated policy on adding icons, no template, and no release cadence. The changelog ends at v2.7 in April 2020, so a reader should assume that new icons arrive, if at all, without a documented schedule.

On licensing: the README's disclaimer says the icons and logos are for sharing and learning, that no commercial use or profit is permitted, and that copyright belongs to the original authors and their sites. The repository has no LICENSE file. If your use is commercial, the README's own terms are the constraint you have to read, and if the answer matters to your organisation, that is a question for your own counsel rather than for this article.

Editorial conclusion

Adopt Qure if you run Quantumult X and want policy groups to be readable at a glance: subscribe to Quremini.json for the PROXY group and QureColor.json for custom policy groups, and you are done in two pastes. Do not adopt it if you need icons for a client other than Quantumult X, if you need any icon added after v2.7 in April 2020, or if you need a licence that permits commercial use, because the README grants none and the repository carries no licence file. Before you subscribe, verify three things yourself: that both raw.githubusercontent.com URLs still return JSON, that the icon names in the JSON match the group names in your config, and that you are willing to keep the subscription pointed at a branch whose last push was on 2026-06-30 with no release ever published.

Frequently asked questions

Official sources

1. Issues
2. Koolson/Qure on GitHub
3. README