INSTALLATION

Download Mercury for macOS

The first version of Mercury Device Commander for Macs with Apple Silicon. This version is not signed with an Apple-issued Developer ID certificate and is not notarized by Apple, so macOS may display a warning when you first open it; below are instructions for different macOS versions.

Requirements
  • MacApple Silicon (M1 or later)
  • SystemmacOS 13 or later
  • FileMercury-Device-Commander-1.0.0-arm64.dmg, 151 MB
  • Version1.0.0
Signing and notarization: this version is not signed with an Apple Developer ID certificate and is not notarized; we plan to release a signed and notarized version once the Apple procedures are complete. Until then macOS may display a warning when you first open the app.
Questions: office@merlin-partners.com
SHA-256 checksum

4fc766a0ef5902d052a5eaa0f946442c631f4210d0801f3d19223e57242c3dae

Check in Terminal:

shasum -a 256 "$HOME/Downloads/Mercury-Device-Commander-1.0.0-arm64.dmg"

The first 64 characters of the result must match the checksum above; if they do not, do not open the file and write to us. The button file is stored in the public Mercury release repository on GitHub: release history.

After installation

When you first use a feature, macOS may ask for permissions. Accessibility: so Mercury can click and type for you. Screen Recording: so it can see what is on the screen. Automation: so it can control other apps. Grant only the permissions your tasks need; do not confirm an unexpected request. You can revoke a permission in System Settings, Privacy & Security. Each Mac has its own access key: it is created on your computer at first launch, there is no shared key. For step-by-step instructions on connecting an AI assistant to Mercury, write to office@merlin-partners.com.

How to open an app not signed by Apple: three steps

Continue only if you downloaded Mercury with the button on this page or from the Mercury release history on GitHub and the checksum matched. Do not open a file from any other source. Then open the .dmg file and drag Mercury to the Applications folder. Open Mercury from Applications by double-clicking it. The steps below are for macOS 15 and later; on macOS 13 and 14 it is simpler: right-click Mercury in Applications, choose Open and confirm; if that does not work, follow the steps below.

  1. “Mercury” Not Opened Apple could not verify “Mercury” is free of malware. Move to Trash Done

    1. Click “Done”

    macOS may show a window titled “Mercury” Not Opened. This warning is expected for this version of Mercury if its checksum matches. Click “Done”, not “Move to Trash”.

  2. Privacy& Security Security “Mercury” was blockedto protect your Mac. Open Anyway

    2. Allow it in Settings

    Open the Apple menu, then System Settings and Privacy & Security. Scroll to the Security section: if Mercury is blocked, you will see a message that “Mercury” was blocked to protect your Mac. Click “Open Anyway” and confirm with your password or Touch ID. If there is no message, open Mercury from Applications again and come back to this section.

  3. “Mercury” Confirm that you want to open the app. Open Anyway

    3. Confirm opening

    If a confirmation window appears, click “Open” or “Open Anyway” in it (the label depends on the macOS version). If no window appears and Mercury has not started, open it from the Applications folder again. You normally won’t need to repeat these steps for this version of the app.

The diagrams are simplified. The look of the windows and the order of confirmations may differ between macOS versions.

Limitations of the first version

  • This version is not signed with a Developer ID certificate and is not notarized: how to open it depends on the macOS version; see the instructions above. We plan to release a signed and notarized version once the Apple procedures are complete.
  • Mercury creates the first access key itself at first launch; after that, keys can be created and revoked only with Terminal commands: there is no key management screen in the app window yet. Do not send a key to anyone or publish it.
  • Mercury does not ask for confirmation before actions: it works within the assigned permission profile.
  • Phones: Android is controlled through adb (the Android debugging tool); iPhone and iPad are only shown in the device list for now.
  • The action log is kept on your Mac; its entries are not yet protected against later changes.
  • Information in the Permissions section inside Mercury appears after you set up fingerprint sign-in (Touch ID). macOS system permissions are set separately, in System Settings.
  • macOS on Apple Silicon only. A Windows version is not currently available.

How protection works: Security. Prices and terms: Pricing.