Skip to content
git push no-mistakes

Installation

macOS / Linux

Terminal window
curl -fsSL https://raw.githubusercontent.com/kunchenguid/no-mistakes/main/docs/install.sh | sh

The installer keeps the real binary in ~/.no-mistakes/bin and exposes no-mistakes through a symlink in ~/.local/bin or /usr/local/bin. That keeps future no-mistakes update runs in a user-owned location instead of rewriting a system binary in place.

It also installs or refreshes the background daemon for you by running no-mistakes daemon restart, preferring a managed service (launchd on macOS, systemd user service on Linux) and falling back to a detached daemon if that path is unavailable. If the restart fails, the install command fails.

Official release binaries installed this way may already have telemetry enabled if a telemetry website ID was embedded at build time.

Windows (PowerShell)

Terminal window
irm https://raw.githubusercontent.com/kunchenguid/no-mistakes/main/docs/install.ps1 | iex

Installs the binary and restarts the background daemon automatically with no-mistakes.exe daemon restart, preferring a managed Task Scheduler task and falling back to a detached daemon if needed. If the restart fails, the install command fails.

Official release binaries installed this way may already have telemetry enabled if a telemetry website ID was embedded at build time.

Go install

Terminal window
go install github.com/kunchenguid/no-mistakes/cmd/no-mistakes@latest

go install builds the CLI without an embedded telemetry website ID, so telemetry stays off by default unless you later set NO_MISTAKES_UMAMI_WEBSITE_ID at runtime.

From source

Terminal window
git clone git@github.com:kunchenguid/no-mistakes.git
cd no-mistakes
make build
make install

make build embeds the telemetry website ID from NO_MISTAKES_UMAMI_WEBSITE_ID in a repo-local .env first, then UMAMI_WEBSITE_ID from the shell if no .env value is present. If neither is set, the binary is built without telemetry enabled.

Prerequisites

  • git - required
  • One supported agent binary - claude, codex, acli (Rovo Dev), or opencode
  • Optional, for PRs and CI:
    • gh CLI (GitHub)
    • glab CLI (GitLab)
    • NO_MISTAKES_BITBUCKET_EMAIL and NO_MISTAKES_BITBUCKET_API_TOKEN (Bitbucket Cloud)

Run no-mistakes doctor to check what’s installed.

See Provider Integration for PR and CI setup per host.

Update

Terminal window
no-mistakes update

This downloads the latest release from GitHub, verifies the SHA-256 checksum, atomically replaces the binary, and resets the daemon so it picks up the new executable. It prefers the managed service path and falls back to a detached daemon if service startup is unavailable or fails.

Because update installs the latest official release binary, it may change telemetry behavior if that release has a telemetry website ID embedded at build time.

It only proceeds if the running daemon is already using the same executable path. If the daemon executable path cannot be determined or it was started from a different binary, the update aborts before replacing the binary. If the daemon does not come back cleanly after a successful replacement, the new binary stays installed but the command reports the daemon reset failure.

Background update checks run automatically on each CLI invocation (except update itself). Suppress with NO_MISTAKES_NO_UPDATE_CHECK=1.

Remove from a repo

Terminal window
no-mistakes eject

Removes the no-mistakes remote, deletes the bare repo, cleans up worktrees, and removes the database record.

Uninstall

Stop the daemon, delete the binary, and clear state:

Terminal window
no-mistakes daemon stop
rm -f ~/.local/bin/no-mistakes /usr/local/bin/no-mistakes
rm -rf ~/.no-mistakes

On macOS, also remove ~/Library/LaunchAgents/com.kunchenguid.no-mistakes.daemon.*.plist. On Linux, also remove ~/.config/systemd/user/no-mistakes-daemon-*.service. On Windows, remove the no-mistakes-daemon-* Task Scheduler task.