Mail drafts work on any desktop, and stay in front.
Version 1.36.1 ·
A draft works with Mail full screen or on another desktop, and stays open in front for you to read. A Desktop press that times out asks for a read, not a retry that could press twice.
Share this release
Mail drafts work on any desktop, and stay in front. A draft works with Mail full screen or on another desktop, and stays open in front for you to read. A Desktop press that times out asks for a read, not a retry that could press twice. https://cupertino.mgcrea.io/changelog/1.36.1/
Fixed
Mail drafts work with Mail in full screen or on another desktop. Accessibility lists only the windows on the desktop shown, so with Mail full screen every draft failed after 8 seconds with "no such window was readable", and
apple_mail_list_open_draftssaid no draft was open while one was. The app now finds Mail's windows on other desktops and reads them where they are, listed withonAnotherDesktop: true. Editing one brings Mail forward on that desktop first, and a composer that cannot be brought forward is refused before anything is touched. A compose that reads no Mail window at all no longer says "this is not a permission".A Mail draft stays in front for you to read. Once a draft was written or edited, Cupertino brought back the app you had been in, straight after the save and again 45 seconds later, so the draft disappeared under it while you were reading. Mail now stays in front with the draft open. To get the old behaviour, turn on Return to the previous app after a draft in Mail's settings in Cupertino, or
APPLE_MAIL_HAND_BACK_AFTER_DRAFToutside the app. A send, a refusal or a failure still brings back your app as before.A Desktop press or write that times out says it may have landed. An app answers a press only when the action returns, and an action that opens a modal alert returns when the alert closes, so a press that worked still answered "did not answer in time … retry", and the retry pressed a second time. A press or write with no answer within 2 s now says it may already have happened and asks for a read of the window before repeating it. A read that times out still says busy.
The Activity log shows a watch update that no one was listening for. When matching mail or a message arrived and the host had not subscribed to the watch, the update went nowhere and the Activity log showed nothing, so a push never sent and a push nobody took looked the same. Mail and Messages now log
push dropped (no listener): cupertino://mail/watch/…with the reason: no opensubscriptions/listennames the watch (2026-07-28 protocol), or it was not subscribed withresources/subscribe(2025). In Claude Code every watch update is such a line, since it never subscribes to a watch; its agents read the watch instead.