BotHub is not yet signed with an Apple Developer ID, so macOS may show one of these dialogs on first launch:
"BotHub.app" is damaged and can't be opened. You should move it to the Trash.
Or:
"BotHub.app" can't be opened because Apple cannot check it for malicious software.
The app is not actually damaged or malicious. This is just macOS Gatekeeper's default protection for unsigned apps. BotHub's source is open for inspection — it's safe to bypass with any of the methods below.
Works on macOS 13 Ventura and later.
BotHub.app once to trigger the "damaged" dialogBotHub.app again — it will open normallyAfter this, every future launch works without prompts.
If the "Open Anyway" button never shows up, or clicking it still fails, open Terminal.app and run:
sudo xattr -rd com.apple.quarantine /Applications/BotHub.app
sudo codesign --force --deep --sign - /Applications/BotHub.app
You'll need to enter your login password. Then launch BotHub normally.
If line 1 reports Operation not permitted, your terminal lacks Full Disk Access. Go to System Settings → Privacy & Security → Full Disk Access and add your terminal app, then restart it and retry.
If neither A nor B works, or if you regularly install unsigned apps, run:
sudo spctl --master-disable
Then go to System Settings → Privacy & Security → Allow applications downloaded from and pick the new Anywhere option.
All unsigned apps will now launch directly by double-click. This lowers your system's security posture — use only if you understand the trade-off. To re-enable:
sudo spctl --master-enable
We recommend dragging BotHub.app into Applications. Other locations work too, but Spotlight search and Dock pinning are easier from /Applications.
BotHub.app to TrashUser data lives at:
~/Library/Application Support/BotHub/
Remove this directory for a complete uninstall.
If all three methods fail, the download may be corrupted. Try:
.dmg from the official siteIf the problem persists, check the FAQ or open an issue.