Migration

Trying a scrolling layout after AeroSpace

An AeroSpace configuration can encode years of small decisions about focus, window placement, and monitor use. Before trying another layout, describe those decisions in plain language. For example: editor on the main screen, logs on the second, reference material one workspace away. That description is a better migration checklist than copying key combinations without their original context.

Bring your workspace map, not the configuration file

The AeroSpace Guide, checked on 22 October 2026, documents a tree-based tiling model, tiles and accordion layouts, configurable bindings, and its own virtual workspaces. Its workspace-to-monitor behavior is an explicit part of that model. Those concepts should be compared deliberately; similar labels in another app do not establish equivalent behavior.

Test the layout before rebuilding workspaces

Begin with one display and three ordinary windows: editor, terminal, and browser. Quit AeroSpace for this trial so both managers cannot rearrange the same windows. In SlidePane, place the windows on a horizontal strip and choose readable widths. Practice moving focus, moving a window along the strip, and changing width as three separate actions.

Now add a second terminal. Does extending the strip help you retain the editor’s size, or would a split tree communicate the relationship more clearly? There is no need to force one model into the other. The experiment is useful when it reveals which relationships need simultaneous visibility and which can be reached by navigation.

Check workspace boundaries explicitly

SlidePane has nine of its own workspaces inside the macOS Space in use. They are not a conversion of an AeroSpace configuration or a promise to reproduce AeroSpace monitor assignments. Native macOS full-screen windows stay outside the regular managed strip.

Write a small test list before expanding the trial: switch workspace (Control-Option-Command and a digit), take the focused window along (add Shift), transfer a window to another display (Control-Option-N), then disconnect that display. Check the actual result at each step. Preserve your original configuration independently; no AeroSpace configuration import is promised.

Evaluate the automation you depend on

If your existing desk depends on scripts, callbacks, or external status tools, list those dependencies separately from layout. Verify each required integration against the current SlidePane documentation. A familiar CLI name or shortcut cannot prove that an automation contract transfers unchanged.

Keep Pause and restore windows (Control-Option-Q by default) available throughout the experiment. This article makes no claim that SlidePane reproduces every AeroSpace capability; there is no tree layout or configuration-file import. If you mostly used AeroSpace's tiles layout to keep a few windows visible at once, also try SlidePane's Grid or Columns mode, which keeps one to four windows in fixed slots and holds the rest as tabs. Use the displays and Spaces guide to understand the boundary and the profiles and undo guide for reversible layout changes.

Cite or share this page

Dapols. "Trying a scrolling layout after AeroSpace." SlidePane, November 18, 2026. https://slidepane.com/en/blog/from-aerospace

The link is stable. The citation uses the page's “Last updated” date.