nikitabobko/AeroSpace

AeroSpace is an i3-like tiling window manager for macOS

Videos:

• YouTube 91 sec Demo
• YouTube Guide by Josean Martinez

Docs:

• AeroSpace Guide
• AeroSpace Commands
• AeroSpace Goodies

• Tiling window manager based on a tree paradigm
• i3 inspired
• Fast workspaces switching without animations and without the necessity to disable SIP
• 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 first (manpages and shell completion included)
• Doesn't require disabling SIP (System Integrity Protection)
• Proper multi-monitor support (i3-like paradigm)

Install via Homebrew to get autoupdates (Preferred)

brew install --cask nikitabobko/tap/aerospace

In multi-monitor setup please make sure that monitors are properly arranged.

Other installation options: https://nikitabobko.github.io/AeroSpace/guide#installation

AeroSpace project doesn't accept Issues directly - we ask you to create a Discussion first. Please read CONTRIBUTING.md for more details.

Community discussions happen at GitHub Discussions. There you can discuss bugs, propose new features, ask your questions, show off your setup, or just chat.

There are 7 channels:

• #all. RSS. Feed with all discussions.
• #announcements. RSS. Only maintainers can post here. Highly moderated traffic.
• #announcements-releases. RSS. Announcements about non-patch releases. Only maintainers can post here.
• #feature-ideas. RSS.
• #general. RSS.
• #potential-bugs. RSS. If you think that you have encountered a bug, you can discuss your bugs here.
• #questions-and-answers. RSS. Everyone is welcome to ask questions. Everyone is encouraged to answer other people's questions.

Public Beta. AeroSpace can be used as a daily driver, but expect breaking changes until 1.0 is reached.

What stops us from 1.0 release:

• #131 Performance. Implement thread-per-application to circumvent macOS blocking AX API.
• #1215 Big refactoring. Rewrite mutable double-linked core tree data structure to immutable single-linked persistent tree. Important for: stability and potential performance
  • #1216 The big refactoring will help us to fix stability issue that windows may randomly jump to the focused workspace
  • #68 The big refactoring will help us to support macOS native tabs
• #278 Implement shell-like combinators. Ignore a lot of crazy fuss in the issue, We are most probably going with the minimal approach to only introduce common shell-combinators: ||, &&, ; and eval command to send multiple commands in one go.
• #1012 Investigate a possibility to use CGEvent.tapCreate API for global hotkeys
  • #28 Maybe it will allow to distinguish left and right modifiers. Maybe not

Big and important issues which will go after 1.0 release:

• #2 sticky windows
• #260 Dynamic TWM

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, animations, etc.)
• "dark magic" (aka "private APIs", "code injections", etc.) must be avoided as much as possible
  • 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).
  • The goal is to make AeroSpace easily maintainable, and resistant to macOS updates.

Non Values

• Play nicely with existing macOS features. If limitations are imposed then AeroSpace won't play nicely with existing macOS features (For example, AeroSpace doesn't acknowledge the existence of macOS Spaces, and it uses emulation of its own workspaces)
• Ricing. AeroSpace provides only a very minimal support for ricing - gaps and a few callbacks for integrations with bars. The current maintainer doesn't care about ricing. Ricing issues are not a priority, and they are mostly ignored. The ricing stance can change only with the appearance of more maintainers.

• AeroSpace binary runs on: macOS 13+
• AeroSpace debug build from sources is supported on: macOS 14+
• AeroSpace release build from sources is supported on: macOS 15+ (Requires: Swift 6.4, Xcode 26.6+)

AeroSpace is developed and maintained in my free time. If you find it useful, consider sponsoring.

In alphabetical order:

• @mobile-ar
• @nikitabobko
• @rickyz

defaults write -g NSWindowShouldDragOnGesture -bool true

Now, you can move windows by holding ctrl+cmd and dragging any part of the window (not necessarily the window title)

Source: reddit

In alphabetical order:

• Amethyst - Beginners friendly GUI-configurable tiling window manager with automatic layouts à la xmonad.
• InstantSpaceSwitcher - Instant space switching by synthesizing trackpad gesture with an artificially high velocity.
• rift - Virtual workspaces + private APIs.
• yabai - A window manager that provides tight integration with native macOS Spaces and goes all the way to private APIs and code injection. yabai is a source of inspiration for a lot of other OSS projects.