Skip to main content
Install the PraisonAI Mac desktop app, understand the two Gatekeeper messages you may see, and open the app on first launch.
Do not download v4.7.2. That build shipped with an invalid signature and cannot be opened on any Mac. v4.7.3 and later are ad-hoc signed and open with right-click → Open.

​
Download

Pick the build that matches your Mac. Open → About This Mac: “Chip” means Apple silicon, “Processor” means Intel. There is no universal build. A wrong-arch download fails when you launch it, not when you install it.

​
Quick Start

1

First launch (ad-hoc signed, v4.7.3+)

Gatekeeper refuses an app it cannot verify. The app carries an ad-hoc signature, which makes the signature valid but not trusted — so macOS says it cannot check for malicious software, or that the developer is unidentified.
  1. Drag PraisonAI to Applications.
  2. Right-click it → Open → Open.
  3. macOS remembers your choice; after that, double-click works.
2

Fallback if Gatekeeper still refuses

Clear the quarantine attribute your browser added when it downloaded the file, then reopen the app:

​
If you see “PraisonAI is damaged and can’t be opened”

That message means something different, and right-click → Open will not get past it: macOS says “damaged” when a signature is present but invalid, not when one is merely untrusted.v4.7.2 shipped in exactly that state. The bundle was never signed, so the only signature on it was the one the Rust linker leaves on the executable, and that signature declares a resource seal an unsigned bundle does not have. Every Mac rejected it. Use v4.7.3 or later; the release build now refuses to attach a macOS bundle whose signature does not verify.

​
Two Gatekeeper messages

The message you see tells you which fix applies.

​
First run

The app needs a Python environment to run its engine and offers to build one: it fetches uv, installs a pinned CPython, creates a virtual environment, and installs praisonaiagents into it. Roughly 500 MB, once. Nothing is installed system-wide. The environment and your conversations live together in ~/Library/Application Support/PraisonAI. To remove the app completely, uninstall it and delete that folder.

​
Questions a fresh user asks

The build is ad-hoc signed, not signed with a Developer ID. Gatekeeper trusts only Developer ID signatures, so it shows the “unidentified developer” warning. Right-click → Open bypasses it once.
Right-click the app → Open → Open. macOS remembers your choice; after that, double-click works.
No. “Damaged” means the signature is invalid (v4.7.2 only). “Unidentified developer” is the normal first-launch warning. Only the second is bypassable with right-click → Open. If you see “damaged”, upgrade to v4.7.3 or later.
Your browser attached a quarantine attribute. Clear it, then reopen:

​
Signing status

The Mac build is ad-hoc signed, which makes the signature valid but not trusted — Gatekeeper still shows the “unidentified developer” warning that right-click → Open bypasses. The release workflow verifies the signature before publishing, so a build that fails verification is never shipped. Full Developer ID signing (which removes the warning entirely) requires an Apple certificate in repository secrets; when that lands, the right-click step goes away.

Quick Install

Install the PraisonAI CLI with one command

Build Your First Agent

Create an AI agent in 3 lines of code