Skip to content

Releases

v7.3.5

Choose a tag to compare

@Christian-SC26 Christian-SC26 released this 19 Nov 21:15

Fixed

  • Silent shadow failures. window --toggle shadow and config window_shadow exited 0 and printed nothing when the scripting addition was not loaded in the Dock, so the shadow stayed as it was with no hint why. This happens after --load-sa updates an outdated payload: it installs the new files and restarts the Dock, and the payload is only injected by the next --load-sa, usually from the dock_did_restart signal. Both commands now fail with the same scripting addition error as --sub-layer and --opacity. window_shadow still keeps the chosen mode and applies it once the scripting addition is loaded. Found while checking #12.
  • Focus fight after leaving Mission Control. After a Mission Control exit that counts as a cancellation, yabai could restore the top window of the previous space while also forcing the previous application back in front of a space where it had no window. Each round reordered windows across spaces, and a child window could be left over another application's native fullscreen animation. yabai now picks only eligible windows as the top window of a space, never a child or system window above its parent, and lets the front switch through when the activating application owns that window.

Added

  • Debug reports for lost windows. With debug_output on, yabai logs every window an application lists but yabai does not track, checked on startup, space change, front switch and window destroy, and every window drawn on screen while none of its spaces is visible, checked on every space change. Each window is logged once, so the log marks when the problem starts.

The scripting addition is unchanged (2.1.39), so no --load-sa is needed when upgrading from 7.3.4.

Signed with Developer ID and notarized by Apple.

v7.3.4

Choose a tag to compare

@Christian-SC26 Christian-SC26 released this 16 Nov 08:01

Fixed

  • Moving windows to hidden spaces on macOS 27. window --space exited 0 but left the window where it was when the target space was not visible, and moving it back to the visible space failed the same way. yabai used the bridged WindowServer operation whenever macOS offered it, and on macOS 27.2 that operation does nothing for hidden spaces. With the scripting addition loaded, yabai now asks the Dock to move the window first, on macOS 15 and later and on recent 12 to 14 point releases, and falls back to the previous ways when the scripting addition is not loaded, so nothing changes with SIP enabled. Reported and fixed by @aiguofer in #10 and #11.
  • Short messages to the Dock. The scripting addition read the fields of its fixed-size messages (spaces, window moves, opacity, layer, sticky, shadow, focus, scale, order and moving to a space) without checking how many bytes arrived. A short message made it act on bytes left over from an earlier one. Such messages are now dropped. The scripting addition is now 2.1.39, so run sudo yabai --load-sa once after upgrading.
  • Installing the service without ~/Library/LaunchAgents. --install-service and --start-service created only the last directory of the plist path, and failed when a parent directory was missing. They now create every missing directory.

Signed with Developer ID and notarized by Apple.

v7.3.3

Choose a tag to compare

@Christian-SC26 Christian-SC26 released this 11 Nov 18:46

Fixed

  • Switching to an application running under a debugger. An application launched from Xcode could not be reached with cmd + tab or the Dock while its windows were on another space. yabai ignores such processes so that one stopped at a breakpoint cannot block it, and their activations were dropped too. yabai now follows them to their space through WindowServer, still without sending them any accessibility request.

  • Stacks past 32 windows. yabai keeps the windows of a stack in one layout node with room for 32 of them. window --stack and dropping a window onto a stack with the mouse refused a window past that limit, but two other ways into a stack never checked it:.

    • a window that appeared on a space with layout stack (opened, deminimized, moved there from another space or unfloated). Such a space is a single node, so the limit is 32 windows per space.
    • a window opened after window --insert stack on a BSP space, when the stack it was meant for was already full.

    The 33rd window was written past the end of the node's window list, over the window order, the window count, the split ratio and the insert feedback state of that node. The layout went wrong from then on, and yabai could crash. Now a window past the limit of a stack layout stays out of the layout where it is, like a window on a space with layout float, and a window meant for a full stack on a BSP space gets a tile of its own next to the stack. Found by the new benchmarks in bench/, which crashed on a stack of 64 windows

  • Full stacks with window --stack and mouse drops. Both refused a window one place early, at 31 windows. And when the stack really was full, window --stack had already taken the window out of its tile, so it was left out of the layout. A stack now takes up to 32 windows, and a full one leaves the window where it was. A window yabai could not tile is no longer counted as managed either.

  • Insert feedback in stacks. The insert feedback of a stack was tied to the window that was in front when it was shown. Focusing, swapping or stacking another window in front, or removing the front one, left it ordered against the wrong window or pointing at a node that no longer existed, which could crash yabai. Ending a drag on an error path also left the drag feedback on screen. The feedback now follows the front window of its stack and is always cleaned up.

  • Rule order after removing a rule. rule --remove and expired one-shot rules moved the last rule into the gap. Rules are applied in the order they were added, so this could change which rule won. Removing a rule now keeps the order of the others.

  • Clients that stop talking to the daemon. A yabai -m client that connected and then stopped sending or reading held up all window management until it went away. Messages with a zero, negative or huge length were trusted too. The daemon now gives a client one second and refuses lengths outside 2 bytes to 1 MB.

  • Bursts of events. Under a long burst of events the event queue could wrap around and overwrite events that had not been handled yet. It now waits for room, and the mouse and event loop threads drop the event instead, since they cannot wait without deadlocking.

  • Layout of a display that comes back. When a display came back, the fresh empty view macOS triggered for one of its new spaces could take the place of the view that held the layout. The view with the layout now wins.

  • Long window lists sent to the Dock. Lists of window ids for animations, ordering and moving windows between spaces were packed into one fixed 4 KB message and ran past it with about a thousand windows. They are now sent in several messages, and the Dock reads a list only as far as the bytes it received. The scripting addition is now 2.1.38, so run sudo yabai --load-sa once after upgrading.

  • Previous and next space. space --focus prev and next now read space ids the same way as the rest of the macOS 27 code. An unknown space gives an error instead of jumping to the last space, and space --move to a missing space reports it.

  • Layout and session files with wrong value types. A string where a number was expected, or the other way round, raised an Objective-C exception and stopped the daemon. Such values are now skipped, and a tree that cannot be rebuilt puts its windows back the usual way.

  • Smaller crash fixes and leaks. yabai now handles a display without a uuid, short WindowServer notifications, a full signal buffer, two mouse buttons pressed while a click is held, more than 512 animated windows reported to JankyBorders, deep layout trees and stacks with many windows without crashing. Leaks of accessibility elements and of rule scratchpad names are fixed.

Signed with Developer ID and notarized by Apple.

v7.3.2

Choose a tag to compare

@Christian-SC26 Christian-SC26 released this 05 Nov 20:03

Fixed

  • Switching to an application with native tabs. With window_native_tabs on, activating an application from the Dock or with a hotkey could take several tries to reach its space. A hidden tab keeps reporting the space it was last shown on after its group moves to another space, so yabai thought the application already had a window on screen and stayed put. Hidden tabs no longer count when yabai decides where an application is.

Signed with Developer ID and notarized by Apple.

v7.3.1

Choose a tag to compare

@Christian-SC26 Christian-SC26 released this 03 Nov 23:37

Fixed

  • Native tab opacity (#9). With window_opacity on:
    • Switching tabs no longer flashes the selected tab at normal_window_opacity for a moment. The tab being hidden was dimmed while it was still on screen and came back dimmed when it was selected again.
    • A tab opened with cmd + t gets active_window_opacity right away instead of keeping normal_window_opacity although it has focus.
    • After window_opacity off, the other tabs of a group no longer come back dimmed when selected.

Signed with Developer ID and notarized by Apple.

v7.3.0

Choose a tag to compare

@Christian-SC26 Christian-SC26 released this 03 Nov 15:57

Added

  • Native macOS tabs in a single tile (#9). With yabai -m config window_native_tabs on, the tabs of Terminal, Finder, Ghostty and other apps with native tabs share one tile, so opening, switching and closing tabs no longer changes the layout. The setting is off by default.
    • Only the selected tab sits in the layout. yabai follows tab switches through WindowServer events and AXFocusedTabChanged instead of guessing from window frames, so holding cmd + t, Merge All Windows and dragging a tab between windows keep the layout intact.
    • A tab dragged out of the tab bar becomes its own tile, and the tabs that exist when the setting is enabled are picked up right away.
    • --warp, --swap, --stack and zoom-fullscreen act on the group, and a floating group stays floating when tabs are switched, opened or closed.
    • Based on the work of @jpatrolla in asmvik#68.

Fixed

  • Keyboard focus after leaving Mission Control. Leaving Mission Control any other way than with escape, such as with a gesture, left the application in front without a key window, so the keyboard reached nothing until the next click. The restored window is now made the key window.

Tested on macOS 27.2 with one display. Signed with Developer ID and notarized by Apple.

v7.2.1

Choose a tag to compare

@Christian-SC26 Christian-SC26 released this 02 Nov 14:19

Fixed

  • Tiled window staying resized after a mouse resize (#8). Releasing a mouse resize skipped the BSP adjustment if the cursor had stopped before the button came up. A window resized from an edge with no split stayed outside its tile, and with mouse_bsp_live_resize off the split was not updated. Both now apply on release, and a stationary click still changes nothing. The bug was introduced in v7.1.35.
  • Window stretching during a live resize. With mouse_bsp_live_resize on, a drag that had already moved a split could stretch the window along the axis with no split, for example when the cursor ended the drag moving straight down. The window stayed that way after release. Those steps are now ignored.

Signed with Developer ID and notarized by Apple.

v7.2.0

Choose a tag to compare

@Christian-SC26 Christian-SC26 released this 30 Oct 00:48

Added

  • Swipe down in Mission Control selects the window under the cursor (macOS 27). Leaving Mission Control with a swipe down now switches to the window under the cursor, on the current space or another one, like a click does. Escape, or a swipe with the cursor over empty space, still returns you to the window you opened Mission Control from. yabai finds the window through the accessibility elements that WindowManager exposes for each Mission Control thumbnail. A window on another space is only selected if you moved the cursor, so a space macOS showed by itself is never picked by accident.

Fixed

  • Mission Control jumping to another space when it opens (macOS 27.2). When Mission Control opens, macOS 27.2 activates an app on another space by itself, and Mission Control shows that space (#7). yabai now puts the app you opened Mission Control from back in front right away, so Mission Control stays on your space and cancelling no longer flashes the other one. The macOS bug itself is still there; please report it to Apple and add your FB number to #7.
  • Mission Control noticed late after a swipe. yabai checks for Mission Control right after a vertical swipe, instead of waiting for the next window or app event.

Signed with Developer ID and notarized by Apple.

v7.1.40

Choose a tag to compare

@Christian-SC26 Christian-SC26 released this 29 Oct 23:50

Fixed

  • App hotkeys ignored after cancelling Mission Control. On macOS 27 the Dock does not always report that Mission Control closed (for example when you cancel it with Escape). yabai kept treating app activations as happening inside Mission Control, so app hotkeys only moved menu bar focus for up to ~10 seconds, and the first one was overridden by the late return to the original space. yabai now notices the exit within ~0.3 s and returns you right away.
  • Clicking a window in Mission Control. Clicking a window on the current space no longer puts focus back on the previously focused window. After clicking a window on another space, cancelling the next Mission Control no longer bounces between two spaces.

Known issue (macOS, not yabai)

On macOS 27.2, opening Mission Control activates an app on another space and switches the preview to its space. This also happens with yabai stopped. yabai takes you back when Mission Control closes, so the other space shows briefly. If you can reproduce it, please report it to Apple and add your FB number to #7.

Signed with Developer ID and notarized by Apple.

v7.1.39

Choose a tag to compare

@Christian-SC26 Christian-SC26 released this 29 Oct 12:06

Added

  • space --move, --swap and --display work again on macOS 27.2. macOS 27.2 removed the Dock function the scripting addition used to move spaces. The scripting addition (2.1.37) now moves spaces through the WindowServer with SLSMoveManagedSpaceToDisplayIndex, the same call the Dock makes when it adds a space. The Dock keeps its space list in sync, so Mission Control shows the new order. Tested on one and two displays, including moving the active space.
  • Release check for the scripting-addition version. scripts/check-osax-version.sh fails when src/osax changed since the last tag but OSAX_VERSION did not. It runs in scripts/release.sh and in CI.

After upgrading, run sudo yabai --load-sa to install scripting addition 2.1.37.

Signed with Developer ID and notarized by Apple.