Skip to main content

​
On Bugs and Privacy

Monarch takes a strong stance on user privacy so it does not contain any kind of software that does tracking, telemetry, analytics or automated bug reporting. While this stance may make it more difficult to track down tricky bugs, I hold that it is well worth it because you can be confident that when you are using Monarch you have absolute ownership and absolute privacy.

​
Get help with user interface bugs

If you are having issues with something in the user interface, such as Superlinks not working properly or a keypress not registering, please let me know rmdashrfv(at)hey(dot)com. It is better if you send along screenshots showing your issue, but the best thing is to send a video of you replicating the issue in real time, along with a short paragraph of what’s happening.

​
Where to post bugs & How to get help

If you are having any issues with bugs or need help with Monarch in general, it’s really easy to get help! You can post an issue in either the subreddit or the Bugs channel on Discord. If you decide to post a bug report, it makes it much easier for everyone involved if you include screenshots or a video and include detailed information (outlined in the pinned template at the top of the bugs channel on Discord). I’ll add it here to make it easier: 
**Title (\*)**  
Short summary of the issue (e.g., "App crashes when resizing window")  

**Description (\*)**  
What happened? Brief explanation of the bug.  

**Steps to Reproduce (\*)**  
1. Launch Monarch  
2. Do X  
3. Observe Y  

**Expected Behavior (\*)**  
What should have happened?  

**Actual Behavior (\*)**  
What happened instead?  

**Screenshots / Video (Preferred)**  
Attach images or videos if available.  

**System Info (\*)**  
- OS version:  
- Monarch version:  
- Hardware (e.g., MacBook Air M1, MacBook Pro Intel, external keyboard)

​
I don’t know where my question goes

No problem. Just post it in the Help channel on Discord.

​
What you should not do

Monarch is designed to be as self-contained as possible. If you are new to troubleshooting computer issues, or don’t feel confident in your troubleshooting skills, that’s perfectly fine. Here’s some things that will not help, and if you do them it will likely make it more difficult for myself or others in the Monarch community to help you. Avoid doing these things:
  • Do not completely remove your installation of Monarch.
  • Do not update your version of macOS, especially if a previous version of Monarch was already working.
  • Do not reinstall your operating system.
  • Do not edit your system configuration files.

​
What to do if Monarch crashes

NOTE: If you don’t want to manually navigate to the crash folder, you can use the Monarch Crash Reports command to instantly open it.
In the event Monarch crashes, it generates a crash report located in /Users/<username>/Application Support/com.monarch.macos/crash. The crash log should look something like 2026-02-13_17-53-28.log. Send that file to the developer either via email at rmdashrfv(at)hey(dot)com, or DM it to thievingfour on the Monarch Discord server. I’ll get back to you as soon as I’m able to and as soon as I have something to say. Sometimes I may simply fix the issue depending on its scope. The file is named to make it easy to identify precisely when a crash occurred to help provide additional context.

​
Easily access Crash Reports

To make it easier to access crash reports and share them with the developer, Monarch comes with a built-in command, Monarch Crash Reports, which can be run at any time from the main search bar. You can also type “mcr” to access it even more quickly.