Contribute
Report a test result
Run Omarchy on your Intel Mac and tell everyone what works. One test fills in a whole configuration, and every diagnostic report helps the next person decide.
Diagnostic reports arrive through doioma, the DoesItOmarchy test tool. It identifies your exact configuration, walks you through each check, and submits the report for review. It's being built now; this page will link to it when it's ready.
Check your Mac's page
Until the tool is ready, the most useful thing you can do is check that your Mac's model page matches your hardware. If it doesn't, open an issue on GitHub with the output of lspci -nn and lsusb.
Help fix what doesn't work
#WeCanFixEverything. When a test fails, a maintainer opens a fix issue in doesitomarchy/wecanfixeverything, with the failing Macs and what they reported. The Fixes page lists them: comment, ask to be assigned, or link your pull request, and the Mac's page shows who's working on it. When a fix lands, the affected Macs ask for a re-test, and a new passing report is what turns the result green.
For test-tool authors
If you build a tool that tests Omarchy on Macs, it can send diagnostic reports straight to this site. Register your tool for a source key, show testers the required notice, and post reports in our format; maintainers review each one before it counts. The API page has the details, and anyone can read the catalog and results there as JSON.
Fix or improve the catalog
The catalog is plain YAML in the DoesItOmarchy repository: one file per model identifier in data/macs/, shared components in data/components/. Corrections come in as pull requests, and doiomad validate checks every change in CI.
- Cite a source for every fact: Apple Tech Specs, EveryMac, or a hardware probe from a real machine.
- If you're unsure, record your best value with an
uncertainnote rather than guessing. - Configuration IDs are permanent. Rename one by moving the old ID to
aliases, never by deleting it.
See CONTRIBUTING.md for the full rules.