Install GitDocket

Install GitDocket 0.4.1 with Homebrew and Git:

brew install gitdocket/tap/gitdocket
docket --version
docket-mcp --version

One formula supplies both commands without separately installing Bun, Node or npm. Continue with Getting started, or use the npm alternative if you already have Node 22+.

Support and trust

The project-maintained tap is GitDocket/homebrew-tap; its formula is gitdocket. It is separate from Homebrew core and uses the same checked, versioned standalone archives as the other distribution channels. It does not use a cask. Linux qualification uses Ubuntu 24.04 on ARM64 and x64. Mac release checks run locally on Apple Silicon, including Intel compatibility through Rosetta; receipts record the actual macOS version and execution assistance. Rosetta does not establish testing on physical Intel hardware or an older macOS release. The formula requires macOS 15 or later and 64-bit ARM or Intel hardware; Linux must satisfy Homebrew's own supported-system requirements. Other Linux distributions and older OS releases have not been qualified. Windows is outside this release's scope.

Homebrew 6 and later require trust for third-party formulae. A fully qualified brew install gitdocket/tap/gitdocket grants trust to that formula, keeping installation to one command. It does not trust all future tap content. See Homebrew tap trust.

Updating and removing

Use brew update followed by brew upgrade gitdocket/tap/gitdocket. brew reinstall gitdocket/tap/gitdocket repairs the installed package; brew uninstall gitdocket/tap/gitdocket removes it. Homebrew manages its own executable files. These commands do not migrate or delete project bundles, authored Markdown, agent configurations or hooks.

Inside each project, review docket upgrade --dry-run --json, then run docket upgrade and resolve any reported instruction conflicts. Updating the executable does not imply that project instructions have been reconciled.

Moving from npm or Bun

Before switching channels, run type -a docket docket-mcp to see which executables your shell resolves. Inspect the existing installation with npm ls -g --depth=0 or bun pm ls -g, depending on the installer you used. Install the Homebrew package, then inspect its commands directly with $(brew --prefix gitdocket/tap/gitdocket)/bin/docket --version and the corresponding docket-mcp --version.

If Homebrew reports an existing link collision, review the named paths and uninstall only the prior GitDocket packages with their original package manager: npm uninstall -g @gitdocket/cli @gitdocket/mcp or bun remove -g @gitdocket/cli @gitdocket/mcp. Do not force-overwrite unknown executable paths. Then run brew link gitdocket/tap/gitdocket, refresh your shell's command cache or open a new terminal, and rerun type -a docket docket-mcp and both version commands. An earlier directory on PATH can still select another installation even when Homebrew linking succeeds.

Agent MCP configurations can contain an absolute path to the old executable. Review .mcp.json, .codex/config.toml and any host-level MCP configuration. Point intentional custom entries at the selected docket-mcp. Re-running docket init --agent claude --agent codex applies normal preservation rules and may leave an existing custom MCP entry untouched; inspect the result and restart the agent host. Removing a package does not remove project files or rewrite those entries for you.

npm alternative

GitDocket 0.4.1 supports npm as an alternative to Homebrew. Node 22 or later and npm are required. CLI/MCP commands use standalone binaries and need no separate Bun installation. Earlier 0.3.1 commands and the core/web library packages remain Bun-dependent.

With Node 22 or later and npm, the standalone release installs both commands through the existing package names:

npm install -g --include=optional @gitdocket/cli @gitdocket/mcp
docket --version
docket-mcp --version

The small launchers select exact-version @gitdocket/bin-<os>-<arch> dependencies. Those packages contain the same qualified binaries, build identity and licenses as the Homebrew archives. There is no install script, runtime download or source fallback. Keep optional dependencies enabled. This route supports macOS and glibc Linux on arm64 and x64; the native qualification matrix is shared with Homebrew. Musl/Alpine, Windows and 32-bit systems are unsupported.

For a temporary CLI invocation without a global installation, use:

npx --yes --package=@gitdocket/cli --package=@gitdocket/mcp docket --version
npx --yes --package=@gitdocket/cli --package=@gitdocket/mcp docket init --agent claude --agent codex

npm may ask before downloading packages when --yes is omitted. For a reproducible invocation, pin both package versions explicitly. npx makes the commands available only for that invocation. Generated MCP configuration names docket-mcp, which a later agent may not find; use a stable global installation for persistent MCP configuration, or configure the host explicitly to run npx --yes --package=@gitdocket/mcp@<version> docket-mcp. Restart the host after changing its MCP command.

Use npm update -g @gitdocket/cli @gitdocket/mcp to update both commands and npm uninstall -g @gitdocket/cli @gitdocket/mcp to remove them. Updates and removal preserve project bundles. Existing Bun-dependent npm packages upgrade under the same names. A separate Bun global installation uses a different package manager and must be reviewed separately. See the PATH and MCP migration procedure when switching channels or resolving command collisions. Project instruction reconciliation remains an explicit docket upgrade --dry-run --json, followed by a reviewed docket upgrade.