Multi-Space switching causes Quitty to incorrectly quit apps with open windows on other Spaces

[patel-priyank]

When using multiple Spaces on macOS, switching away from a Space causes Quitty to think that the apps left open on the previous Space have no windows, and it quits them. The windows are still open, just on a Space that is not currently active.

Steps to reproduce

1. Open an app (for example, Xcode or VS Code) with at least one window on Space 1.
2. Switch to Space 2 using Mission Control, a trackpad gesture, or a keyboard shortcut.
3. Observe that Quitty quits the app that was left open on Space 1.

Expected behavior

Quitty should not quit an app just because its windows are not visible on the currently active Space. A window on a different Space is still open, not closed.

Actual behavior

Quitty appears to treat "not visible on the current Space" the same as "zero windows", and terminates the app.

Suspected cause

Based on the README's description of the detection logic (raw AXObserver on AXWindowClosed, followed by a check of the app's current window list), the window count check via the Accessibility API may only be returning windows on the active Space, rather than all open windows across every Space. This would make the "zero windows" check produce a false positive whenever the last window on the active Space belongs to an app whose other windows live on a different Space.

Environment

macOS version: 27.0 (but I noticed the same behaviour on 26.5 as well)
Quitty version: 1.1.17
Number of Spaces in use: 2

[chentao1006]

Thanks for the report — you've correctly diagnosed it. macOS's Accessibility API only reliably reports windows on the currently active Space for background apps; Quitty's cross-check via CGWindowListCopyWindowInfo is meant to catch cross-Space windows but isn't 100% reliable on newer macOS builds (26/27 have known regressions here).

Two workarounds for now:

1. Open Quitty's menu → recent terminations → mark the wrongly-quit app as "False Quit." This makes Quitty much more conservative about that app going forward.
2. Add apps you keep open across Spaces (e.g. Xcode, VS Code) to the exclude list in Settings — guaranteed fix for that app.

Based on testing, the manual feedback mechanism (marking it as a "False Quit") is largely effective at preventing recurrence for that app. A fully reliable fix likely needs undocumented, private Spaces APIs (the kind AltTab uses to solve this exact problem) — no official Apple API supports it. I'm holding off because private APIs can change or break without notice on any macOS update, and reverse-engineering + maintaining that across OS versions is a bigger commitment than a quick patch. Keeping this open as a known limitation for now.