AeroSpace is an i3-like tiling window manager for macOS

Original Article ↗ Hacker News Discussion ↗

Overall reception

  • Many are excited to see an i3-like tiling WM on macOS and report AeroSpace as the best experience they’ve had on Mac so far.
  • Others remain skeptical, arguing that tiling on macOS is inherently fragile due to OS behavior and limited APIs, and prefer either native windowing or Linux.

Comparison with other macOS window managers

  • Versus yabai:
    • AeroSpace’s main advantages cited: no SIP disabling, instant workspace switching without Mission Control animations, stable “fake workspace” numbering independent of monitors, simpler config.
    • yabai is praised for powerful features (including focus-follows-mouse) but some see it as flaky and strongly coupled to SIP-disabled features.
    • Several say yabai also works “fine” with SIP on, if you accept fewer features and occasional restarts.
  • Versus Amethyst:
    • AeroSpace is described as faster, more reliable at moving windows/workspaces, and having better multi-monitor behavior.
    • Amethyst users like its integration with native Spaces and note it also supports text config, but some find it sluggish or half-baked.
  • Versus snapping tools (Rectangle, Magnet, Spectacle):
    • These are repeatedly mentioned as extremely stable and “good enough” for many users, though they are snapping/tiling hybrids rather than full i3-style WMs.

Workspaces, multi‑monitor, and focus

  • AeroSpace’s emulated workspaces (not real macOS Spaces) are seen as a major strength: fast switching, predictable numbering, better multi-monitor semantics.
  • Some friction arises with other tools (Raycast, alt-tab replacements) because all windows sit in one real macOS Space.
  • Focus-follows-mouse is achieved via companion tools (AutoFocus, AutoRaise, Hammerspoon scripts). It works but can be weird with the global menu bar.

Configuration and extensibility

  • Single-file, text-based config is widely appreciated.
  • The TOML-based “callbacks” are viewed as stretched; some suggest embedding a scripting language like Lua.
  • Hooks (e.g., on workspace/window events) are seen as a promising extension point.

Limitations, bugs, and macOS constraints

  • Several users report flakiness compared to Linux WMs (i3/sway/xmonad), attributing this to macOS’s limited and partly private APIs.
  • Known pain points:
    • Interactions with native fullscreen apps and native tabbed windows (each tab appearing as a “window”).
    • Initial run on an already-messy desktop can produce chaotic layouts.
    • Some specific bugs: oscillating workspace switching, confusion when mixing AeroSpace workspaces with native Spaces navigation.
    • Mouse-based rearrangement is less capable than in sway; some layouts require keyboard “detours.”

Security, SIP, and notarization

  • AeroSpace explicitly avoids requiring SIP to be disabled; features that need it are either approximated or not implemented.
  • The project intentionally avoids notarization due to cost, friction, and the risk of arbitrary revocations; some agree, others argue central signing helps security.
  • Homebrew installation removes the quarantine attribute only from the AeroSpace app, allowing it to run without extra prompts.