Why does MasterSpaces need Accessibility?
macOS requires Accessibility permission for apps that read, move, or resize other app windows. MasterSpaces uses it for snapping, saved layouts, restore flows, and display-aware placement.
FAQ
The practical questions before giving a window manager Accessibility access.
Does MasterSpaces manage native Spaces?
No. The current release observes display topology and active-space changes through public APIs, but it does not create, delete, or control native macOS Spaces.
Does it work with multiple monitors?
Yes, the current MVP includes orientation-aware snapping, display topology inspection, and drag-to-edge target selection based on the pointer display. Final release sign-off still requires clean-machine multi-monitor QA.
Does MasterSpaces send layout data anywhere?
No. Layouts, workspaces, tips, and preferences are stored locally in the current release candidate. Export/import is manual.
Is there an App Store version?
Not in the current release. This milestone is built for direct-download distribution with Developer ID signing and notarization.
What is the pricing?
The public pricing model is still being finalized. Internal planning includes free and Pro concepts, but this site avoids presenting unfinished tiers as launch terms.