How to Install vorssaint-utils After Building: Complete macOS Guide

Run ./build.sh --install to compile vorssaint-utils from source and automatically copy the signed app bundle into /Applications.

Vorssaint-utils is a Swift-based macOS utility that requires local compilation before installation. Building from source gives you immediate access to the latest commits and development features not yet available in the release DMG. This guide explains exactly how to install vorssaint-utils after building it, referencing the actual implementation in the vorssaint/vorssaint-utils repository.

Prerequisites

Before building, ensure your system meets these requirements:

• macOS with Xcode Command Line Tools installed
• Git to clone the repository
• Administrator privileges to write to /Applications

Step 1: Clone the Repository

First, download the source code to your local machine:

git clone https://github.com/vorssaint/vorssaint-utils.git
cd vorssaint-utils

This creates a local copy of the repository, including the build.sh script that orchestrates the entire process.

Step 2: Build and Install Using build.sh

The build.sh script handles compilation, code signing, and optional installation. According to the source code in vorssaint/vorssaint-utils, the script behaves differently depending on the flags you provide.

Build Only (Default)

Running the script without flags compiles the app and places a signed bundle in the build/ directory:

./build.sh

This produces a runnable .app bundle inside ./build useful for testing changes without system-wide installation.

Build and Install to /Applications

To install vorssaint-utils after building it, append the --install flag:

./build.sh --install

According to the source code in build.sh (lines 31–38), the script parses the --install argument and triggers a specific installation flow. When this flag is present, the script:

1. Builds the release bundle
2. Copies the bundle to /Applications (lines 20–26)
3. Executes sign_installed_bundle to apply final code signing and verify the bundle integrity (lines 33–38)

This ensures the installed app passes macOS Gatekeeper checks despite being locally compiled.

Development Installation with --dev

If you want to install a development version that coexists with the official App Store release, add the --dev flag alongside --install:

./build.sh --dev --install

This modifies the bundle identifier and app name, preventing conflicts with the production version while allowing you to test bleeding-edge features.

Uninstalling vorssaint-utils

To completely remove the app and all associated data—including login items and stored preferences—run the provided uninstall script:

./Tools/uninstall.sh

This script safely deletes the app from /Applications and removes configuration files that a standard drag-to-trash operation would leave behind.

Summary

• Clone the repository with git clone https://github.com/vorssaint/vorssaint-utils.git
• Build and install by running ./build.sh --install, which copies the signed bundle to /Applications according to the logic in lines 20–28 of build.sh
• Develop alongside the stable release using ./build.sh --dev --install for isolated testing
• Uninstall completely using ./Tools/uninstall.sh to remove the app and all related data

Frequently Asked Questions

Where does vorssaint-utils install when I run build.sh?

Without the --install flag, vorssaint-utils builds to a build/ folder in your current working directory. When you run ./build.sh --install, the script copies the signed bundle directly into /Applications and verifies the installation using the sign_installed_bundle function defined in the build script.

Do I need to disable SIP or Gatekeeper to install a self-built vorssaint-utils?

No. The build.sh script automatically signs the bundle during the installation phase. The sign_installed_bundle function (lines 33–38 of build.sh) applies proper code signing to ensure the app passes Gatekeeper verification, allowing you to open it without security warnings.

Can I have both the App Store version and a self-built version installed?

Yes, but only if you build with the --dev flag. Running ./build.sh --dev --install creates a separately identifiable bundle that does not conflict with the production version. Building without --dev overwrites any existing vorssaint-utils installation in /Applications.

How do I completely remove vorssaint-utils and its data?

Use the dedicated uninstall script located at Tools/uninstall.sh. Unlike manually dragging the app to trash, this script removes the application bundle from /Applications plus all associated login items and preference files, ensuring a clean removal.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}