Updating
How Meshvy replaces itself, and how to take it off the machine without losing work.
Meshvy checks GitHub Releases on launch. When a newer version exists a pill appears in the toolbar; it shows the release notes and Install and restart, which downloads the zip, checks it against the published SHA-256, validates the bundle and swaps itself. Also Meshvy → Check for Updates…
The repository is public, so neither the listing nor the download needs a token. Development builds never offer updates.
If the swap fails
A running bundle cannot replace itself, so a detached helper waits for Meshvy to quit, swaps the two, clears the quarantine flag and relaunches. If that fails it puts the old bundle back — a failed update never leaves you with nothing installed.
Uninstalling
Meshvy → Uninstall Meshvy…, or run the script that ships inside the app:
/Applications/Meshvy.app/Contents/Resources/uninstall.sh --dry-run # look first /Applications/Meshvy.app/Contents/Resources/uninstall.sh
It removes the app, ~/Library/Application Support/Meshvy, the keychain entry, and the workspaces under ~/.meshvy.
| Flag | What it does |
|---|---|
| --dry-run | print the plan, change nothing |
| --keep-worktrees | remove the app but leave ~/.meshvy alone |
| --force | also remove checkouts with unsaved work |
| --yes | skip the confirmation |
rm would leave every source repository pointing at a checkout that no longer exists. The uninstaller hands each one back with git worktree remove and prunes the origin — and leaves alone any checkout holding uncommitted or unpushed work, telling you which and why. Nothing in your own repositories is touched.