AeroSpace is an i3-like tiling window manager for macOS
Public Beta. Feedback is very much welcome
- I encourage you to try AeroSpace and file GitHub issues if something doesn't work for you
- I already use AeroSpace on daily basis and I'm happy with it
- The documentation covers all major things you need to know
- Manual tiling window manager based on a tree paradigm
- i3 inspired
- AeroSpace employs its own emulation of virtual workspaces instead of relying on native macOS Spaces due to their considerable limitations
- Plain text configuration (dotfiles friendly). See: default-config.toml
- CLI scriptable
- Doesn't require disabling SIP (System Integrity Protection)
- Proper multi-monitor support (i3-like paradigm)
- Status menu icon displays current workspace name
Install via Homebrew to get autoupdates (Preferred)
brew install --cask nikitabobko/tap/aerospace
Note
By using AeroSpace, you acknowledge that it's not notarized.
Notarization is a "security" feature by Apple. You send binaries to Apple, and they either approve the binaries or not. In reality, notarization is about building binaries the way Apple likes it.
Let's be honest. Tiling window manager is not something Apple will be totally ok with. Even if they approve one version, it doesn't mean that they won't revoke it (yes, they can do it), or approve further versions.
I don't have anything against notarization as a concept. I specifically don't like the way Apple does notarization. I don't have time to fight Apple.
Homebrew installation script is configured to
automatically delete com.apple.quarantine attribute, that's why the app should work out of the box, without any warnings that
"Apple cannot check AeroSpace for malicious software"
See: CONTRIBUTING.md
A notes on how to setup the project, build it, how to run the tests, etc. can be found here: dev-docs/development.md
Values
- AeroSpace is targeted at advanced users and developers
- Keyboard centric
- Breaking changes (configuration files, CLI, behavior) are avoided as much as possible, but it must not let the software stagnate. Thus breaking changes can happen, but with careful considerations and helpful message. Semver major version is bumped in case of a breaking change (It's all guaranteed once AeroSpace reaches 1.0 version, until then breaking changes just happen)
- AeroSpace doesn't use GUI, unless necessarily
- AeroSpace will never provide a GUI for configuration. For advanced users, it's easier to edit a configuration file in text editor rather than navigating through checkboxes in GUI.
- Status menu icon is ok, because visual feedback is needed
- Provide practical features. Fancy appearance features are not practical (e.g. window borders, transparency, etc)
- If "dark magic" (aka "private APIs", "code injections", etc) can be avoided, it must be avoided
- Right now, AeroSpace uses only a single private API to get window ID of accessibility object
_AXUIElementGetWindow. Everything else is macOS public accessibility API. - AeroSpace will never require you to disable SIP (System Integrity Protection). For example, yabai requires you to disable SIP to use some of its features. AeroSpace will either find another way (such as emulation of workspaces) or will not implement this feature at all (window transparency and window shadowing are not practical features)
- Right now, AeroSpace uses only a single private API to get window ID of accessibility object
Non Values
- Play nicely with existing macOS features. If limitations are imposed then AeroSpace won't play nicely with existing macOS features
- E.g. AeroSpace doesn't acknowledge the existence of macOS Spaces, and it uses emulation of its own workspaces
defaults write -g NSWindowShouldDragOnGesture YESNow, you can move windows by holding ctrl+cmd and dragging any part of the window (not necessarily the window title)
Source: reddit