AeroSpace Problems & Issues

Real user-reported problems, complaints, and limitations for AeroSpace. Based on analysis of 14 signals.

Overall score: 67/100

Issues by Category

reliability5 issues

AeroSpace won't start after a macOS or AeroSpace update

v0.20.3 changed the code-signing certificate and required re-granting Accessibility permission, and one user had macOS disable the permission 8-20 times until resetting it with tccutil. GitHub discussions also cover AeroSpace not starting on macOS 26.1.

Frequency: 5%Sentiment: -0.60/1003 sources
Impact
8

AeroSpace windows randomly jump to another workspace

The README itself lists 'windows may randomly jump to the focused workspace' (#1216) as a known stability bug that waits on a core tree refactor before 1.0. A separate discussion reports apps moving between workspaces and the visible workspace changing on its own.

Frequency: 6%Sentiment: -0.60/1003 sources
Impact
7

AeroSpace focuses the wrong window on multiple monitors

With macOS 'Displays have separate Spaces' left on (the default), the guide lists wrong-window focus, focus jumping back and performance problems. Disabling it means windows can't span monitors and the menu bar shows only on the main display.

Frequency: 6%Sentiment: -0.50/1003 sources
Impact
6

AeroSpace floating windows disappear when switching workspaces

A 44-comment discussion reports floating windows disappearing when moving between workspaces, and recent releases (0.20.3, 0.21.2) fixed floating windows getting stuck in a corner or snapping to the top-left.

Frequency: 5%Sentiment: -0.50/1002 sources
Impact
5

AeroSpace is still a beta with breaking changes

Every release is tagged Beta and the README warns of breaking changes until 1.0. v0.21.0 changed the socket protocol, rewrote the binding parser and started rejecting some on-window-detected rules, so configs and scripts can break on update.

Frequency: 5%Sentiment: -0.30/1002 sources
Impact
5
usability4 issues

AeroSpace keybindings not working

Hotkeys can silently fail when another global key listener (skhd, Karabiner-Elements, Raycast) grabs the same combo, and a discussion titled 'Alt key bindings stop working randomly' has 31 comments. Accessibility permission loss after updates also stops bindings.

Frequency: 6%Sentiment: -0.50/1003 sources
Impact
6

AeroSpace hides windows in the screen corner instead of using Spaces

Inactive workspaces are emulated by parking their windows in the bottom-right or bottom-left corner, so a 1-pixel sliver stays visible and a bad monitor arrangement shows parts of hidden windows on other screens. After a crash, windows can be left in the corner until dragged back.

Frequency: 7%Sentiment: -0.40/1003 sources
Impact
5

Mission Control shows tiny windows with AeroSpace

Because hidden windows sit in the screen corner, Mission Control renders them very small. The official guide's workaround is turning on 'Group windows by application'.

Frequency: 5%Sentiment: -0.30/1002 sources
Impact
4

AeroSpace tiles popups and dialogs that should float

Dialog detection is heuristic: windows without a fullscreen button are treated as dialogs, but some apps and Apple dialogs (like Finder's copy progress) are misdetected, and small windows such as System Settings get tiled. Users fix it with per-app on-window-detected rules.

Frequency: 6%Sentiment: -0.40/1003 sources
Impact
4
performance1 issue

Why is AeroSpace slow when switching workspaces?

A long-running GitHub issue (#131, 51 upvotes) tracked delays from hundreds of milliseconds up to 10-15 seconds when switching focus or workspaces, worst under high CPU load and with JetBrains IDEs, Spotify, Firefox or Godot open. The 0.18 release targeted it and the issue was closed in April 2025, but some users still reported freezes on later versions.

Frequency: 7%Sentiment: -0.60/1003 sources
Impact
8
integrations1 issue

AeroSpace treats native macOS tabs as separate windows

Apps using native tabs (Ghostty, Alacritty, Finder-style tabs) expose each tab as a window, so each one gets tiled. Ghostty's docs call it a macOS API limitation; native tabs support (#68) waits on the same pre-1.0 refactor.

Frequency: 5%Sentiment: -0.40/1003 sources
Impact
5
onboarding1 issue

Is AeroSpace hard to set up?

There is no settings GUI: everything is a TOML file plus a CLI, and users must learn many hotkeys. Reviewers coming from automatic tilers note that layout is manual and opening a window doesn't rearrange the others the way they expected.

Frequency: 6%Sentiment: -0.30/1003 sources
Impact
5
support1 issue

AeroSpace support depends on one volunteer maintainer

The author builds it in his free time and asks for GitHub Sponsors. Issues can't be opened directly (a Discussion comes first), performance threads were locked and redirected, and some reports get 'doesn't ring a bell' with no fix.

Frequency: 4%Sentiment: -0.30/1002 sources
Impact
4
customization1 issue

AeroSpace has no drag-to-split or ricing

Unlike i3/sway you can't drag a window onto another to create a split; it's keyboard-only restacking. Visual customization is a stated low priority (gaps and bar callbacks only), so borders and bars need JankyBorders or SketchyBar.

Frequency: 4%Sentiment: -0.30/1002 sources
Impact
3

Regret Patterns

Common reasons users regret choosing AeroSpace.

Lag shows up once a heavy IDE is open

Setup feels instant, then workspace switches start stalling for seconds while a JetBrains IDE indexes or the CPU is busy.

Frequency: 6%First week of real work

Windows vanish after a crash

AeroSpace crashes or gets killed and windows stay parked in the screen corner, looking lost until dragged back.

Frequency: 4%First crash

An update breaks the config

A beta release changes command syntax or rejects rules, and bindings or scripts stop working until the config is fixed.

Frequency: 4%After a minor version update

Multi-monitor setup fights macOS settings

Users discover they need to turn off 'Displays have separate Spaces' and rearrange monitors, which changes how the menu bar and fullscreen apps work.

Frequency: 5%When connecting a second display

Too much config for the payoff

People who only wanted snapping realize full tiling plus a TOML file and dozens of hotkeys is more than they need and go back to Rectangle.

Frequency: 5%First few days

Popups and tabs get tiled

Small dialogs and native tabs are tiled as full windows, forcing a list of per-app floating rules.

Frequency: 5%First week

When AeroSpace Breaks Down

Specific scenarios where AeroSpace fails or underperforms.

Heavy CPU load or a blocked app

If an app's UI thread hangs, AeroSpace's Accessibility calls queue up and focus/workspace commands can take seconds.

Monitors arranged with no free bottom corner

Hidden windows from other workspaces peek out onto neighbouring displays.

'Displays have separate Spaces' left on

Wrong window gets focus, focus snaps back and moving windows between monitors misbehaves.

Apps with native macOS tabs

Ghostty, Alacritty and similar apps get each tab tiled as a separate window.

Other global hotkey tools running

skhd, Karabiner-Elements or Raycast grab the same keys and AeroSpace bindings silently stop.

Using Mission Control or native Spaces

Thumbnails shrink and macOS desktop switching confuses AeroSpace's emulated workspaces.