The no-tickets release ships two binaries — no-tickets (the CLI) and
no-tickets-mcp (the MCP server). Every install channel installs both
together; you don’t have to pick.
macOS and Linux — shell installer
Installs both binaries to ~/.local/bin/. Add that to your PATH if it
isn’t already:
The shorthand resolves to
https://github.com/magic-ingredients/no-tickets/releases/latest/download/no-tickets-installer.sh
— useful for environments where get.no-tickets.com is blocked.
macOS and Linux — Homebrew
brew tap magic-ingredients/tap is implicit on the first install.
Windows — PowerShell installer
Installs both binaries to %USERPROFILE%\.local\bin\ and prepends that
directory to the user PATH. Restart the shell after install.
Verify the install
no-tickets status works without authentication. The next step is
Your first push.
Updating
How no-tickets updates depends on the install channel.
no-tickets update detects which channel placed the binary and prints
the right command for that channel rather than running an in-place
swap that would conflict with the package manager.
If you’re on v0.1.2 and ran self-update, the bundled updater
shipped a broken archive format and left a non-executable file at
~/.local/bin/no-tickets. Recover by re-running the shell
installer (it overwrites the corrupt file with a working binary).
From v0.1.3 on the subcommand is renamed from self-update to
just update.
Advanced install paths
For air-gapped environments, restricted runners, build-from-source,
direct tarball downloads with sha256 verification, and the (coming
soon) cargo install channel, see the canonical install reference
in the binary repo:
magic-ingredients/no-tickets/docs/install.md.
Using no-tickets in CI
Most CI runners install fresh on every job. The shell installer fits
that model — see GitHub Actions,
Generic CI, and the other recipes
under Integration guides for
per-provider templates. 
