mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-10-23 08:07:35 -06:00
[GH-ISSUE #1894] macOS 27: Siri interaction opens MonitorControl Settings #1306
Labels
No labels
Status: Abandoned
arm64
beta
beta
bug
done
duplicate
enhancement
feedback needed from reporter
in progress
information
invalid
investigating
known Issue
monitor Issue
pull-request
translation
unable to reproduce
unreleased
x86
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
github-starred/MonitorControl#1306
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @okleinschmidt on GitHub (Aug 20, 2026).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1894
Before opening the issue, have you...?
Describe the bug
Almost every interaction with the new dedicated Siri chat application in macOS 27 triggers the MonitorControls Settings window.
Steps to reproduce
Expected behavior
MonitorControl Settings shouldn't appear at interaction with other applications.
Anything else?
No response
Environment Information (please complete the following information)
@autoclave73 commented on GitHub (Aug 26, 2026):
came here to confirm this, sending a chat message in the siri app also brings up monitorcontrol
@waydabber commented on GitHub (Aug 31, 2026):
I am not able to reproduce this one (doesn't seem to happen on the latest macOS 27 beta and MonitorControl version on my setup). I don't see how the MonitorControl Settings window could interact with other apps. But it may be one of those weird macOS 27 beta issues that needs shorting out.
@easonwong-de commented on GitHub (Sep 4, 2026):
Happens on my mac. Both creating a new conversation and switching conversation open the settings window. Running macOS 27 beta.
@christophehad commented on GitHub (Sep 11, 2026):
Weird thing is that it also happened with BetterDisplay! At some point, it started switching to other open windows (like Slack, Chrome)
@waydabber commented on GitHub (Sep 11, 2026):
Some apps, including MonitorControl and BetterDisplay do open their Settings window when relaunched while already running. It may be that Siri somehow interacts with these apps this way for some reason (maybe it tries to discover app intents provided by the apps - although MonitorControl does not provide any). I wasn't able to reproduce the problem so far though.
It switching to other open windows (Slack, Chrome) may point to some general issue with the Siri app.
@waydabber commented on GitHub (Sep 11, 2026):
I was able to reproduce the issue with MonitorControl, but not with BetterDisplay.
Weird issue indeed.
@christophehad commented on GitHub (Sep 11, 2026):
Also to note, after quitting BetterDisplay and relaunching I'm not seeing this issue. Will let you know if I find more insights!
@thechriscrabb commented on GitHub (Sep 13, 2026):
Can confirm this behaviour also exists for me with MonitorControl on RC of macOS 27 Intermittently, using CMD + Space to launch Siri decides to launch MonitorControl's preferences/settings in the background.
@tacticalkeyboard commented on GitHub (Sep 14, 2026):
Confirming this bug on my MacBook M2 Pro.
@waydabber commented on GitHub (Sep 15, 2026):
Yes. The reason is that Siri app seems to call
applicationShouldHandleReopen()(anNSApplicationDelegatefunction) whenever anything happens. This is there to reopen Settings when an user relaunches the app. BetterDisplay does not have this issue, as since macOS 26 (where Shortcuts had a similar bug) it explicitly checks whether the reopen sender is the Finder (or some other legitimate source) or not.I'll fix this and provide an updated version.
Now that I am at it, I'll also restore the legacy OSD for macOS 26 and 27, so the app can shine in its former (although bit retro-looking) glory. :)
@waydabber commented on GitHub (Sep 15, 2026):
Published a v4.4.0 version that should fix this.
https://github.com/MonitorControl/MonitorControl/releases/tag/v4.4.0
Please let me know if this helps.
@billstanden commented on GitHub (Sep 15, 2026):
4.4.0 fixed it for me. Thanks for the update.
@waydabber commented on GitHub (Sep 15, 2026):
Nice! Thanks for the feedback @billstanden
@okleinschmidt commented on GitHub (Sep 16, 2026):
Thanks! Fixed it.