Setup: BTT 6.183, macOS 26.3.1 (Tahoe), 3 displays with separate spaces.
Bug
"Move Left/Right a Space (Without Animation)" (actions 527/528) has a split behavior on multi-monitor setups:
- The actual space switch correctly targets the display where the cursor is positioned
- The boundary check ("reached end" in logs) evaluates against the keyboard-focused display instead
If the keyboard-focused display is at its last space in a given direction, BTT logs "reached end" and aborts — even though the cursor-positioned display has spaces available in that direction.
Reproduction
- Have 2+ displays with separate spaces
- Place cursor on Display A (which has multiple spaces to the right)
- Keep keyboard focus on Display B (which is at its rightmost space)
- Press trigger for "Move Right a Space (Without Animation)"
- BTT logs
reached endand does nothing, even though Display A has spaces to the right
From the BTT log:
triggering action Move Right a Space (Without Animation) - 0A68291E...
reached end
Pressing "Move Left" first succeeds (Display B has room left), then "Move Right" also succeeds — confirming the boundary check targets the keyboard-focused display while the actual switch targets the cursor display.
Expected
Boundary check should evaluate against the same display that the space switch targets (the cursor-positioned display).
Workaround
Adding "Bring Window Under Cursor to Front" (action 204) as the trigger-level action before the space switch in the action sequence shifts keyboard focus to the cursor display, making the boundary check evaluate correctly.
Note
This worked correctly pre-Tahoe (macOS 15). Tahoe likely changed how display keyboard focus relates to cursor position, exposing a latent inconsistency in the boundary check logic.