Install

One command, or the DMG. What it puts where, and how to check the build is really ours.

macOS 14+Universal — Apple Silicon and IntelSigned and notarised

Meshvy drives the claude CLI rather than the API, so install Claude Code first and sign in. There is nothing else to set up and nothing to sign in to for Meshvy itself.

Installing

curl -fsSL https://raw.githubusercontent.com/gowth6m/meshvy/main/scripts/install.sh | bash

It downloads the latest release, checks it against the published SHA-256, installs to /Applications and clears the quarantine flag. Run it again to update, or set a prefix to put it somewhere else:

PREFIX=~/Applications curl -fsSL …/install.sh | bash

Verifying the build

Releases are signed with a Developer ID and notarised by Apple, so a download opens without a warning. The release workflow gates on proving it rather than trusting that the signing secrets were set, and the script it gates on ships with the source, so you can run the same check yourself:

./scripts/verify-release.sh /Applications/Meshvy.app

First run

Meshvy opens empty — there is no sample project and nothing is created until you make a workspace. Claude Code asks you to trust a folder it has not seen, so the first orchestrator in a new workspace shows its trust prompt. Press Enter.

Meshvy will not answer that prompt for you

Pre-answering it means writing to ~/.claude.json, which every running Claude Code also writes. A read-modify-write there could clobber their changes.

Installing

Verifying the build

First run

Troubleshooting

“Apple could not verify Meshvy is free of malware”

An agent starts and immediately stops

Building it yourself