Skip to content

Installation

The Count is one binary, patchula. Releases have static builds for Linux (x86_64 and arm64) and macOS (Apple silicon). Intel Macs are not supported.

Terminal window
mise use -g --minimum-release-age 0 packslip:sweepies/count-patchula

Each release carries a packslip manifest signed by the release workflow, so mise checks every download against it. --minimum-release-age 0 skips mise’s 24-hour wait for new releases, so a release installs as soon as it is published. Pin a version with packslip:sweepies/count-patchula@0.9.0.

The manifest also ships a patchula skill for coding agents, from skills/patchula: how to configure, validate and run the Count, with links back to these docs.

  • mise on the PATH, or packslip, with which patchula serve and patchula tools install install the Count’s own pinned mise; with only packslip, run patchula tools install before other commands. Without mise, mise tools and lockfiles fail and everything else works. Tools go into the tool store; keep it on a persistent volume.
  • git, for the partial clones a lockfile tool works in.
  • A writable cache directory. By default it is patchula/ in your user cache directory: $XDG_CACHE_HOME/patchula or ~/.cache/patchula on Linux, and ~/Library/Caches/patchula on macOS. Every checkout shares it, so lookups from one are reused in the next, and nothing is written into the repository. Pass --cache DIR to use another directory. It holds cache.sqlite (HTTP validators, catalogs and write receipts), the partial clones in worktrees/ and the tool store in tools/. A warm cache is most of the speed, so keep it between runs. With neither HOME nor XDG_CACHE_HOME set, local commands stop and ask for --cache.

Some tools download slowly, so prewarm the store when you build an image:

Terminal window
patchula tools install --cache /var/lib/patchula
patchula tools prune --days 30 --cache /var/lib/patchula

mise run docs:cli in a checkout generates generated/patchula.1 and bash, zsh and fish completions under generated/completions, along with the CLI reference.