// lezli01 / agentic tooling # vincent

durable local orchestration for agentic development

You are viewing docs for v0.8.0 — see the latest release.
// docs/platforms/macos.md docs online

vincent on macOS

Apple silicon and Intel are both released and both exercised in CI.

Install

brew install lezli01/tap/vincent

Or install vincent_*_darwin_universal.pkg from the release page — one universal installer for both architectures, putting the binary at /usr/local/bin/vincent. It is unsigned, so open it with right-click → Open rather than a double-click, which a double-click will not offer:

sudo installer -pkg vincent_*_darwin_universal.pkg -target /   # or from the terminal

Or unpack the release archive by hand:

tar -xzf vincent_*_darwin_arm64.tar.gz      # or _darwin_amd64 on Intel
sudo mv vincent /usr/local/bin/
vincent version

~/.local/bin works just as well if you would rather avoid sudo. Full detail, including signature verification: Installation.

Gatekeeper

The macOS artifacts are not Apple code signed. Developer ID signing and notarization require an Apple Developer Program membership — a ~$99/yr recurring purchase this project has not made — so a downloaded binary is quarantined by the browser and Gatekeeper refuses it: “vincent cannot be opened because the developer cannot be verified.”

Clear the attribute the browser set, once per download:

xattr -d com.apple.quarantine /usr/local/bin/vincent
vincent version

brew install needs none of this — the cask strips the attribute itself as part of the install. Neither does vincent update: it downloads the archive itself rather than through a browser, and clears the attribute from the binary it swaps in.

For the .pkg, the equivalent is opening it from the Finder’s context menu (right-click → Open → Open in the dialog), or installing it from the terminal with sudo installer -pkg … -target /, which does not consult Gatekeeper at all.

Stripping quarantine turns off the check that would otherwise flag a tampered file, so do it on a download you have verified. Both the archives and the .pkg carry proof of where they came from that does not depend on Apple:

cosign verify-blob checksums.txt \
  --certificate checksums.txt.pem --signature checksums.txt.sig \
  --certificate-identity-regexp 'https://github.com/lezli01/vincent/.*' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com
shasum -a 256 -c checksums.txt --ignore-missing
gh attestation verify vincent_*_darwin_universal.pkg --repo lezli01/vincent

The full verification story, including why the .pkg is outside checksums.txt, is in Installation.

com.apple.provenance is unrelated — macOS adds it to everything and it does not block execution.

Directories

macOS is the one platform where config and data are nested under the same root:

Purpose Location
Config ~/Library/Application Support/vincent/
Data ~/Library/Application Support/vincent/data/ 
~/Library/Application Support/vincent/config.yaml         # 0600, dir 0700
~/Library/Application Support/vincent/workflows/*.yaml
~/Library/Application Support/vincent/data/vincent.db
~/Library/Application Support/vincent/data/token          # 0600
~/Library/Application Support/vincent/data/daemon.json
~/Library/Application Support/vincent/data/logs/daemon.log
~/Library/Application Support/vincent/data/worktrees/{task_id}/
~/Library/Application Support/vincent/data/transcripts/{task_id}/

Note the space in the path when scripting — quote it, or use ~/Library/Application\ Support/vincent. Both directories are overridable with VINCENT_CONFIG_DIR and VINCENT_DATA_DIR; see Files and directories.

Running at login

vincent service install
vincent service status

That writes a LaunchAgent to ~/Library/LaunchAgents — a per-user agent, never a root LaunchDaemon, and no elevation is required. The OS user is vincent’s trust boundary: an agent gets your privileges, your agent-CLI logins and your git identity, and nothing more.

KeepAlive is conditional on a non-clean exit. A daemon that exits 0 was asked to stop, and relaunching it would make vincent daemon stop impossible.

The agent starts at login, which is the same promise the Linux and Windows backends make.

The PATH problem

This is the macOS-specific gotcha, and it is worth understanding rather than just working around.

launchd hands a service a minimal PATH — /usr/bin:/bin:/usr/sbin:/sbin. Every agent CLI installs outside it: Homebrew (/opt/homebrew/bin on Apple silicon, /usr/local/bin on Intel), an npm prefix, an nvm shim directory, ~/.local/bin.

Left alone, an installed service therefore resolves no agent CLI at all, while the same daemon started by hand finds every one — the daemon runs, the TUI lists every adapter as missing, and nothing in either says why.

So vincent service install captures the PATH of the shell that ran it, along with the config and data directories, and writes them into the plist. The shell you install from has, by construction, the PATH that works.

Two consequences:

  • It goes stale. Install an agent CLI somewhere new and run vincent service install again to recapture. That is the same “reinstall to recapture” contract the directories have.

  • It is not the only answer. agents.<name>.path in config.yaml is absolute and never consults PATH:

    agents:
  claude: { path: "/opt/homebrew/bin/claude" }

Verify with vincent daemon status or the TUI’s daemon view: if the adapter list is empty under a service that is running, this is why.

Terminal notes

  • Native text selection needs the TUI’s mouse handling off: press M, or hold ⇧ while dragging.
  • Cmd+V pastes; it arrives as a bracketed paste and lands in the focused field with no key involved.
  • $EDITOR is honored for edit-and-retry and description editing. Use something that runs in the terminal and blocks until you close it — vim, nano, or code --wait.
  • Everything on this platform behaves the same as Linux, including restricted permission mode for all three adapters.

See also