Issues with rapid keyboard shortcut usage causing all emails in all inboxes to be archived / very destructive bug

Description

All emails appeared to have been archived across multiple inboxes including GSuite, GMail, and O365 accounts without explicitly triggering this activity. I know that it was immediately following archiving via “E” an email that was opened, it appeared as if all the emails in the list in the inbox flashed and then disappeared. It also appeared that the “undo” feature did not seem to see this mass-archiving as on the stack of things to be possibly undone. I also confirmed the messages were all archived by finding specific emails I recalled not having been read yet in “All Mail” still (as opposed to deleted).

Note oddly for at least the O365 account the emails keep flickering in and out – like wait 30 seconds, they disappear, and in another 30 seconds they reappear.

To Reproduce…

I unfortunately do not know, otherwise, I’d likely not be reporting it here. I do know I am a heavy keyboard shortcut user, using navigation keys and “E” (gmail style shortcuts). My primary email workflow is inbox-zero style usage. I do know I was browsing emails in the “Inbox” view (e.g. all inboxes in one view). Also note I am coming from Superhuman daily usage where I’ve been trained to effectively use the keyboard for everything.

Expected Behavior

Mass archiving doesn’t happen. If it is possible to have happened accidentally, the action would be something that the “undo” feature could undo (or if for some reason this was a non-undoable action, a warning shows before archiving all emails). So I guess this is either one bug or the other depending on the expectations of the implementer.

Setup

Mac OSX 15.5 with Mailspring 1.15.1

Additional Context

Note, this is on day two of me test-driving Mailspring… so presumably my workflow is risky enough to cause this issue in a short timeframe (or I am just very unlucky).

As an aside, this was a pretty catastrophic bug for me. While I know my reproduction steps here are not well informed, the side effects of this bug were huge for me personally. I am more than happy to share any further debugging info I can gather after the fact.