All windows always go to a single monitor, the Mac monitor. Rift does not respect the isolation of spaces.

[dagrlx]

Hello, I use two monitors, the Mac monitor and an external monitor. Since the penultimate update, I haven't been able to use Rift again. All the windows go to the Mac monitor, and it's hell trying to move them to the external monitor by dragging and dropping. Sometimes I have to close the app, focus on the external monitor, and reopen the app there. But as soon as I switch to another workspace, all the windows move back to the Mac monitor.
Rift is not respecting the space isolation. I have deleted and reinstalled Rift several times, activated it via rift services start, and used brew services start acsandmann/tap/rift.

I have used the default configuration default_disable = true, but when I press Alt+Z, both monitors are activated regardless of which monitor I have selected at the time of activation. I would like to take this opportunity to ask: does toggle_space_activated only activate Rift in the selected space, or should it also deactivate it if it is active? Because once I activate it, I cannot deactivate it using Alt+Z and I have to stop the service.

I disabled Sketchybar thinking it might be the cause of the problem, but it wasn't. I use DisplayLink for the external monitor, but I disabled it anyway and connected the external monitor directly to the Mac, but Rift's bad behavior is the same.

Before version 0.2.0, I didn't have this problem, and I don't know what else to check. I've used the default settings from the wiki, but everything is the same.

I had removed Aerospace and Hyperspace because I wanted to give this beautiful project a chance. I know it's very new, but something happened in the code. Thank you very much for your efforts to move Rift forward.
I don't want to go back to Hyperspace or Aerospace, so today I worked without using a tiling manager.

rift-cli query displays
[
  {
    "frame": {
      "origin": {
        "x": 0.0,
        "y": 0.0
      },
      "size": {
        "height": 1080.0,
        "width": 1920.0
      }
    },
    "name": "LG FHD",
    "screen_id": 3,
    "space": 1,
    "uuid": "CB1BEAEC-22F3-49BE-C90B-A2661D91F570"
  },
  {
    "frame": {
      "origin": {
        "x": 1920.0,
        "y": 180.0
      },
      "size": {
        "height": 900.0,
        "width": 1440.0
      }
    },
    "name": "Built-in Retina Display",
    "screen_id": 1,
    "space": 28,
    "uuid": "37D8832A-2D66-02CA-B9F7-8F30A301B230"
  }
]

rift-cli query workspaces
[
  {
    "id": "VirtualWorkspaceId(9v1)",
    "index": 0,
    "name": "A",
    "is_active": false,
    "window_count": 1,
    "windows": [
      {
        "id": {
          "pid": 34786,
          "idx": 3660
        },
        "title": "Elementos de inicio y extensiones",
        "frame": {
          "origin": {
            "x": 3358.0,
            "y": 1028.0
          },
          "size": {
            "width": 835.0,
            "height": 900.0
          }
        },
        "is_floating": true,
        "is_focused": false,
        "bundle_id": "Configuración del Sistema",
        "window_server_id": 3660
      }
    ]
  },
  {
    "id": "VirtualWorkspaceId(10v1)",
    "index": 1,
    "name": "B",
    "is_active": true,
    "window_count": 1,
    "windows": [
      {
        "id": {
          "pid": 33848,
          "idx": 3653
        },
        "title": "~",
        "frame": {
          "origin": {
            "x": 1925.0,
            "y": 185.0
          },
          "size": {
            "width": 1430.0,
            "height": 890.0
          }
        },
        "is_floating": false,
        "is_focused": true,
        "bundle_id": "Ghostty",
        "window_server_id": 3653
      }
    ]
  },
  {
    "id": "VirtualWorkspaceId(11v1)",
    "index": 2,
    "name": "C",
    "is_active": false,
    "window_count": 0,
    "windows": []
  },
  {
    "id": "VirtualWorkspaceId(12v1)",
    "index": 3,
    "name": "D",
    "is_active": false,
    "window_count": 1,
    "windows": [
      {
        "id": {
          "pid": 33655,
          "idx": 3640
        },
        "title": "New Issue - Vivaldi",
        "frame": {
          "origin": {
            "x": 1925.0,
            "y": 185.0
          },
          "size": {
            "width": 1430.0,
            "height": 890.0
          }
        },
        "is_floating": false,
        "is_focused": false,
        "bundle_id": "Vivaldi",
        "window_server_id": 3640
      }
    ]
  },
  {
    "id": "VirtualWorkspaceId(13v1)",
    "index": 4,
    "name": "E",
    "is_active": false,
    "window_count": 1,
    "windows": [
      {
        "id": {
          "pid": 39196,
          "idx": 3848
        },
        "title": ".config — config.toml",
        "frame": {
          "origin": {
            "x": 1925.0,
            "y": 185.0
          },
          "size": {
            "width": 1430.0,
            "height": 890.0
          }
        },
        "is_floating": false,
        "is_focused": false,
        "bundle_id": "Zed",
        "window_server_id": 3848
      }
    ]
  },
  {
    "id": "VirtualWorkspaceId(14v1)",
    "index": 5,
    "name": "F",
    "is_active": false,
    "window_count": 0,
    "windows": []
  },
  {
    "id": "VirtualWorkspaceId(15v1)",
    "index": 6,
    "name": "G",
    "is_active": false,
    "window_count": 0,
    "windows": []
  },
  {
    "id": "VirtualWorkspaceId(16v1)",
    "index": 7,
    "name": "H",
    "is_active": false,
    "window_count": 0,
    "windows": []
  }
]

Logs
rift_dgarciar.err.log

[dagrlx]

Sorry, I forgot to paste my configuration.

Sorry, I forgot to paste my configuration. I would also like to mention that sometimes the window does not open in floating mode even though it is set to do so.
I use MacOS 15.7.2 Sequoia on a MacBook Air M1.

[settings]
animate = true
animation_duration = 0.3
animation_fps = 100.0
animation_easing = "ease_in_out"

default_disable = true

focus_follows_mouse = true
mouse_follows_focus = false
mouse_hides_on_focus = true

auto_focus_blacklist = ["com.apple.ScreenContinuity"]

run_on_start = [
  "rift-cli subscribe cli --event workspace_changed --command sh --args -c --args 'sketchybar --trigger rift_workspace_changed RIFT_WORKSPACE_NAME=\"$RIFT_WORKSPACE_NAME\" RIFT_WORKSPACE_ID=\"$RIFT_WORKSPACE_ID\"'",
  "rift-cli subscribe cli --event windows_changed --command sh --args -c --args 'sketchybar --trigger rift_windows_changed RIFT_WORKSPACE_NAME=\"$RIFT_WORKSPACE_NAME\" RIFT_WINDOW_COUNT=\"$RIFT_WINDOW_COUNT\"'",

  "borders style=round hidpi=off active_color=0xc0e2e2e3 inactive_color=0xc02c2e34 background_color=0x302c2e34 width=6.0",
]

# Hot Reloading
hot_reload = true

[settings.layout]
mode = "traditional"

[settings.layout.stack]
stack_offset = 10.0

default_orientation = "perpendicular"

[settings.layout.gaps]

[settings.layout.gaps.outer]
top = 38
left = 5
bottom = 5
right = 5

[settings.layout.gaps.inner]
horizontal = 5
vertical = 5

[settings.ui.menu_bar]
enabled = true
show_empty = false

[settings.ui.stack_line]
# experimental stack line indicator (defaults to off)
enabled = false
# in a horizontal stack where the line will be (top/bottom)
horiz_placement = "top"
# in a vertical stack where the line will be (left/right)
vert_placement = "left"
# how thick the line indicator will be (in px) -- default 0 when disabled
thickness = 0.6
# spacing between the stack line and window edges (in px)
spacing = 0.0

# experimental mission control
[settings.ui.mission_control]
enabled = false
# enable fade animation when entering/exiting mission control
fade_enabled = false
# native macos mission control fade is about 180ms
fade_duration_ms = 180.0

# Trackpad gestures
[settings.gestures]
# Enable horizontal swipes to switch virtual workspaces
enabled = false
# Invert horizontal direction (swap next/prev)
invert_horizontal_swipe = false
# Maximum vertical travel allowed for the horizontal swipe to register.
# Accepts normalized fraction (0..1) or percent (0..100). Example: 0.4 or 40.0
swipe_vertical_tolerance = 0.4
# Skip empty workspaces when swiping
skip_empty = true
# Number of fingers required for swipe
fingers = 3
# Normalized horizontal distance (0..1) to trigger swipe for NSTouch-based detection
distance_pct = 0.08
# Haptic feedback on commit (generic | alignment | level_change)
haptics_enabled = true
haptic_pattern = "level_change"

# Window snapping / drag-swap behavior
[settings.window_snapping]
drag_swap_fraction = 0.3

[virtual_workspaces]
enabled = true
default_workspace_count = 8
auto_assign_windows = true
preserve_focus_per_workspace = true
workspace_auto_back_and_forth = false

# Workspace names (indexed order). If fewer than default_workspace_count are provided,
# remaining workspaces are named "Workspace X".
# Do not provide more names than default_workspace_count.
workspace_names = ["A", "B", "C", "D", "E", "F", "G", "H"]

app_rules = [
  # Desarrollo - Workspace B
  { app_id = "com.mitchellh.ghostty", workspace = 1, floating = false },
  { app_id = "dev.zed.Zed", workspace = 1, floating = false },           # Editor de código

  # Navegación - Workspace D
  { app_id = "com.vivaldi.Vivaldi", workspace = 3, floating = false },
  { app_id = "org.mozilla.firefox", workspace = 3 },
  { app_id = "com.apple.Safari", workspace = 3 },

  # Comunicación - Workspace A y Workspace E
  { app_id = "net.whatsapp.WhatsApp", workspace = 0 },
  { app_id = "ru.keepcoder.Telegram", workspace = 0 }, # Telegram
  { app_id = "com.microsoft.teams2", workspace = 2 },  # Teams

  # Utilidades flotantes
  { app_id = "com.apple.iCal", floating = true },                           # Calendario
  { app_id = "com.apple.finder", floating = true },                         # Finder
  { app_id = "com.apple.systempreferences", floating = true },              # Preferencias del Sistema
  { app_id = "com.apple.SystemSettings", workspace = "", floating = true },
  { app_id = "com.apple.ActivityMonitor", floating = true },
  { app_id = "org.keepassxc.keepassxc", floating = true },
  { app_id = "com.microsoft.rdc.macos", floating = true },
  { app_id = "com.realvnc.vncviewer", floating = true },
  { app_id = "com.apple.SecurityAgent", floating = true },
  { app_id = "com.apple.Preview", floating = true },
  { app_id = "com.apple.QuickTimePlayerX", floating = true },
  { app_id = "com.raycast.macos", floating = true },
  { app_id = "com.apple.calculator", floating = true },
  { app_id = "com.linguee.DeepLCopyTranslator", floating = true },

  #   # Regla general para diálogos
  #   { ax_subrole = "AXDialog", floating = true },       # Todos los diálogos flotan
  #   { ax_subrole = "AXSystemDialog", floating = true }, # Diálogos del sistema
]

[modifier_combinations]
comb1 = "Alt + Shift"
comb2 = "Meta + Ctrl"

[keys]

"Alt + Z" = "toggle_space_activated"

"Alt + H" = { move_focus = "left" }
"Alt + J" = { move_focus = "down" }
"Alt + K" = { move_focus = "up" }
"Alt + L" = { move_focus = "right" }

"comb1 + H" = { move_node = "left" }
"comb1 + J" = { move_node = "down" }
"comb1 + K" = { move_node = "up" }
"comb1 + L" = { move_node = "right" }

"comb2 + 0" = { switch_to_workspace = 0 }
"comb2 + 1" = { switch_to_workspace = 1 }
"comb2 + 2" = { switch_to_workspace = 2 }
"comb2 + 3" = { switch_to_workspace = 3 }
"comb2 + 4" = { switch_to_workspace = 4 }
"comb2 + 5" = { switch_to_workspace = 5 }
"comb2 + 6" = { switch_to_workspace = 6 }
"comb2 + 7" = { switch_to_workspace = 7 }

"comb1 + 0" = { move_window_to_workspace = 0 }
"comb1 + 1" = { move_window_to_workspace = 1 }
"comb1 + 2" = { move_window_to_workspace = 2 }
"comb1 + 3" = { move_window_to_workspace = 3 }
"comb1 + 4" = { move_window_to_workspace = 4 }
"comb1 + 5" = { move_window_to_workspace = 5 }
"comb1 + 6" = { move_window_to_workspace = 6 }
"comb1 + 7" = { move_window_to_workspace = 7 }

"Alt + P" = "prev_workspace"
"Alt + N" = "next_workspace"

"Alt + Tab" = "switch_to_last_workspace"

"Alt + Meta + Left" = { join_window = "left" }
"Alt + Meta + Right" = { join_window = "right" }
"Alt + Meta + Up" = { join_window = "up" }
"Alt + Shift + Down" = { join_window = "down" }
"Alt + Comma" = "toggle_stack"
"Alt + Slash" = "toggle_orientation"
"Alt + Ctrl + E" = "unjoin_windows"

"Alt + Shift + Space" = "toggle_window_floating"
"Alt + F" = "toggle_fullscreen"
"Alt + Shift + F" = "toggle_fullscreen_within_gaps"
"Meta + Ctrl + Space" = "toggle_focus_floating"     # briefly bring focus to floating window

# smartly resize windowsdd
"Alt + Ctrl + 0" = "resize_window_grow"
"Alt + Ctrl + 9" = "resize_window_shrink"

# if mission control is enabled
# this will show an exploded view of the windows in the active workspace
"Alt + Ctrl + Shift + M" = "show_mission_control_current"
# this will show the mission control view shown in the readme
"Alt + Ctrl + M" = "show_mission_control_all"

"Alt + Shift + D" = "debug" # prints layout tree

"Alt + Ctrl + S" = "serialize"
"Alt + Ctrl + Q" = "save_and_exit"

[acsandmann]

looking into this. @brianwk i know you use a multi monitor setup, are you experiencing similar issues or not/are you doing something to work around this?

[brianwk]

@acsandmann Yes the windows will originally open on a seemingly arbitrary display in my experience. It will basically depend on what display the last window of the app was on I think. I have the UW set as the primary when it's connected, so everything will open up there. But it depends on what monitor I open it on.

I use a Hammerspoon script to move the windows to the external display until it's (hopefully) built into Rift. It will move the windows if they aren't already on the external display by UUID.

My HammerSpoon script is here: https://github.com/brianwk/dotfiles/blob/main/dot_hammerspoon/init.lua

There are functions to move windows to a specific Rift workspace, and also to move it to a specific display. I only typically have one external display connected. I had to do something similar for Aerospace and Sketchybar integration, so you will see some Sketchybar stuff in there that I'm no longer using and likely going to delete soon.

[acsandmann]

@brianwk does the latest commit help with isolating displays? i think some of the issues are macos specific (activating an app leading to space switches) so a workaround will take a bit of work..

[brianwk]

@acsandmann I will test tomorrow morning I am not plugged into a display as I'm out of the office. Also you may want to document that you should disable some settings in MacOS that will make automated window management unpredictable. For example the setting here to "switch to a space with open windows for the application"

[alexmohr]

Even with the settings shared by @brianwk new applications are always starting on the primary display.
Only floating applications are starting up on the currently active screen. (Using 3 displays in my office setup)

For multi monitor usage rift is lacking a bit as of now.
It seems like each monitor has it's own set of workspaces, but as they are numbered the same as on the other screens, there is no way to quickly jump to a workspace on a different screen.
What a lot of other WMs do is that the configured set of workspaces is shared among all screens.

In case you need testing or even have a dedicated task I could work on for multi monitor topics, let me know :)

[dagrlx]

Hello, I realized that the order in which windows are assigned and which monitor they go to depends on the VirtualWorkspaceId, and their values can change on the external monitor if, for example, you disconnect and reconnect the external monitor, the VirtualWorkspaceId are recreated with new numbers.

In my tests, I realized that when Rift assigns the first VirtualWorkspaceId to the external monitor by default, the applications open there, and Rift takes that monitor for all the applications you open.

In another test, Rift assigned the first VirtualWorkspaceId to the Mac monitor and all the apps go there, and if I select and manage to open an app on the external monitor, for example in workspace D, when I want to switch to workspace A, the app I had in workspace D moves to workspace D on the Mac monitor.

An important point that I realized last night is that it depends on how you have the screens arranged in the system settings. In my case, I had them arranged like this, and the top edge of the window I had on my external monitor was visible at the bottom of the Mac monitor.

Then I adjusted it like this and it was fixed. I also realized that this factor was affecting the problem of all the windows going to the Mac monitor.

[brianwk]

Even with the settings shared by @brianwk new applications are always starting on the primary display. Only floating applications are starting up on the currently active screen. (Using 3 displays in my office setup)

For multi monitor usage rift is lacking a bit as of now. It seems like each monitor has it's own set of workspaces, but as they are numbered the same as on the other screens, there is no way to quickly jump to a workspace on a different screen. What a lot of other WMs do is that the configured set of workspaces is shared among all screens.

In case you need testing or even have a dedicated task I could work on for multi monitor topics, let me know :)

In Aerospace the workspaces can be limited to specific screens. I think the issue is that in Rift all virtual workspaces are on every screen like you described. So if I have a app rule to send the window to space 3 or whatever, then it doesn't know what monitor to send it to, so it just keeps it in whatever display / space MacOS opens it in.

Using Hammerspoon I'm able to automate moving the windows to another display. I can modify the Hammerspoon script to be configurable and to be installable as a Spoon if it's helpful for your purposes.

Once the Hammerspoon script moves it the app rules kick in and move the window. Unless it's WezTerm, I had to implicitly move that window to the correct workspace.

Also what version of OS X are you using?

[alexmohr]

In Aerospace the workspaces can be limited to specific screens.

I know, but that's not what I'm personally using. I much rather have all workspaces share all monitors, then being able to freely move workspaces around the different displays.
This is the same behavior aerospace supports and other WMs like i3, sway and hyprland also default to.

I assume manually dragging a window to a different screen does the same thing as moving it manually?
For example if I'm moving a window from workspace 1 to another display, the new display also gets workspace 1 meaning workspace 1 now exists twice, which is an issue because now I cannot jump to the workspace via the keybinding before focusing the other display.

I'm using macOS 26.1

[brianwk]

In Aerospace the workspaces can be limited to specific screens.

I know, but that's not what I'm personally using. I much rather have all workspaces share all monitors, then being able to freely move workspaces around the different displays. This is the same behavior aerospace supports and other WMs like i3, sway and hyprland also default to.

I assume manually dragging a window to a different screen does the same thing as moving it manually? For example if I'm moving a window from workspace 1 to another display, the new display also gets workspace 1 meaning workspace 1 now exists twice, which is an issue because now I cannot jump to the workspace via the keybinding before focusing the other display.

I'm using macOS 26.1

Yes I have the same issue because the spaces are based on the active display. I was used to creating workarounds for Aerospace, so I already had this script created long before I used Rift. I will say that the Rift CLI responds a lot quicker than the Aerospace CLI, making workarounds like this a lot easier to do.

Obviously I don't think this workaround I'm using is ideal, and I hope it's not permanent.

Also when you say workspace are you referring to the virtual workspace or the native MacOS space? If the former, it's already on every display. AFAIK, for every MacOS space, it creates the same set of virtual workspaces in Rift.

Moving it is similar to clicking and dragging it but the main reason I use it to is to avoid using the mouse and clicking / dragging it.

Also I assume that "Automatically rearrange Spaces based on most recent use" is off? I don't know what other settings exist in Tahoe since I'm still on Sequoia myself. This setting will auto create MacOS spaces though.

[alexmohr]

I'm always refering to the virtual workspace. I never bothered to even try the MacOS spaces, since I've got this Mac I'm using aerospace.

it's already on every display.

I couldn't get this to work as expected then. Using pretty much the default configuration, nevertheless each 'display' is getting its unique sets of rift workspaces.

Automatically rearrange Spaces based on most recent use

Yes, there is no new setting in Tahoe regarding this. I had the same behavior with rift on Sequoia. Aerospace recommends this being off as well.

[brianwk]

I'm always refering to the virtual workspace. I never bothered to even try the MacOS spaces, since I've got this Mac I'm using aerospace.

it's already on every display.

I couldn't get this to work as expected then. Using pretty much the default configuration, nevertheless each 'display' is getting its unique sets of rift workspaces.

Automatically rearrange Spaces based on most recent use

Yes, there is no new setting in Tahoe regarding this. I had the same behavior with rift on Sequoia. Aerospace recommends this being off as well.

Also did you try this? (Copied and pasted instructions from Google)

Assign apps to specific spaces
You can also have apps always open in a specific space, which prevents them from creating new ones when you open them.
Open the app you want to assign.
Right-click (or Control-click) its icon in the Dock.
Go to Options.
Select This Desktop or All Desktops.
If you choose This Desktop, you'll need to manually assign it to a specific space, and if you make it full-screen, it will move to its own dedicated space.

This will change what MacOS space the app opens in. Which is a fundamental difference from Aerospace, where everything operates in the same MaOS space. Since MacOS is going to control what initial MacOS space it opens in.

It may be possible to automate the built in behavior of MacOS to take advantage of this setting for window management purposes. I will experiment with Hammerspoon when I get to the office.

(I use Lua / Hammerspoon because I'm currently in Grandpa mode when it comes to Rust, but I'm going through the Rust by practice site to pick it back up. Even then I'm still wildly unfamiliar with unsafe code...)

---

If you are using latest main branch of Rift you can query the workspaces by the MacOS space ID now:

❯ rift-cli query displays
[
  {
    "frame": {
      "origin": {
        "x": 0.0,
        "y": 32.0
      },
      "size": {
        "height": 1085.0,
        "width": 1728.0
      }
    },
    "is_active_context": true,
    "name": "Built-in Retina Display",
    "screen_id": 1,
    "space": 4, <--- MacOS Space ID
    "uuid": "37D8832A-2D66-02CA-B9F7-8F30A301B230"
  }
]

You can then query the workspaces belonging to that space ID:

❯ rift-cli query workspaces --space-id 4 | jq '.[] | .id'
"VirtualWorkspaceId(1v1)"
"VirtualWorkspaceId(2v1)"
"VirtualWorkspaceId(3v1)"
"VirtualWorkspaceId(4v1)"
"VirtualWorkspaceId(5v1)"
"VirtualWorkspaceId(6v1)"
"VirtualWorkspaceId(7v1)"
"VirtualWorkspaceId(8v1)"
"VirtualWorkspaceId(9v1)"
"VirtualWorkspaceId(10v1)"

You will notice that every MacOS space has 10 virtual workspaces assigned to it, meaning that when you do:

rift-cli execute workspace switch 1 for example, it will be in the context of the active display (or MacOS space.)

In latest main you can create a hotkey to switch to a specific monitor, and then you can use the hotkey to switch to the space. I do understand what you mean though, I used the same mechanism in Aerospace (separating the virtual spaces to different displays).

---

However since you can now use a command to move the focus to another display, you could in theory change the hotkey for example ALT+1 to do multiple commands. The first command of which to change the cursor to the display by UUID, and then the second command to switch to the workspace:

❯ rift-cli execute display move-mouse-to-uuid
error: the following required arguments were not provided:
  <UUID>

Usage: rift-cli execute display move-mouse-to-uuid <UUID>

For more information, try '--help'.
❯

Although I don't know if the hotkeys allow an array of commands. @acsandmann ?

[alexmohr]

You will notice that every MacOS space has 10 virtual workspaces assigned to it, meaning that when you do:

exactly and that's what I really don't like because it's such a different concept from everything else.

In latest main you can create a hotkey to switch to a specific monitor, and then you can use the hotkey to switch to the space

Sharing 10 workspaces along all displays would be a lot more convenient.
But I'm not even sure that works in the rift architecture, I might have to get used to a different workflow when using rift. (Which is kinda annoying because I'm still using linux and would have loved to get same behaviour everywhere)

What's still missing is a way to move the whole workspace to another monitor though (or much more all windows). If that's something that would in scope for rift and @acsandmann isn't implementing something like this already I'm probably able to cook something up.

The first command of which to change the cursor to the display by UUID, and then the second command to switch to the workspace:

Which also only works if you dedicate workspaces to screens or work with modifiers like + shift means display 2 or something like that.

[brianwk]

The first command of which to change the cursor to the display by UUID, and then the second command to switch to the workspace:

Which also only works if you dedicate workspaces to screens or work with modifiers like + shift means display 2 or something like that.

Sorry I do not understand. You can try it in your terminal:

$ rift-cli execute display move-mouse-to-uuid $DISPLAY_UUID && rift-cli execute workspace switch $WORKSPACE_ID

This should cause you to switch to $WORKSPACE_ID on $DISPLAY_UUID only.

Or you can set a hotkey that switches to the display using the move-mouse-to-uuid command and then you can just do ALT + 0 or whatever hotkey on the display.

I haven't tried this yet, so it's all in theory, but it should work based on latest changes in main branch.

Also I just realized I don't understand what is the desired outcome exactly. In my Aerospace setup when I did ALT+1 for example, it would move to that workspace on the specific display it was assigned to. So what is your desired setup here? -- The above is an example of this, although I'm not sure if you can execute two commands with a hotkey in Rift. You may have to use some other hotkey mapper in meantime.

Also I feel like we derailed this issue. As the topic is regarding the windows opening on the wrong MacOS space.