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.
Install
Section titled “Install”mise use -g --minimum-release-age 0 packslip:sweepies/count-patchulaEach 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.
Download the archive for your platform from the releases
page. It holds
bin/patchula, the man page under share/man, and bash, zsh and fish
completions under share/.
docker pull ghcr.io/sweepies/count-patchula:X.Y.ZThe image runs patchula serve with git included, for linux/amd64 and
linux/arm64, and installs mise into its volume on the first start. Each
release has a tag with its version, and latest. The server
guide covers the volume, health check,
settings and credentials.
cargo install --git https://github.com/sweepies/count-patchula --locked patchula-cliThis needs Rust 1.100 or newer and a C linker (cc). The repository’s own
build setup, which supplies a Zig linker through mise, is not used by
cargo install.
git clone https://github.com/sweepies/count-patchulacd count-patchulamise trust && mise installmise run build./target/debug/patchula --versionEvery tool version is pinned in mise.toml, including Rust and the Zig linker,
so a minimal image without system development packages can build it.
What the runner needs
Section titled “What the runner needs”miseon thePATH, or packslip, with whichpatchula serveandpatchula tools installinstall the Count’s own pinned mise; with only packslip, runpatchula tools installbefore 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/patchulaor~/.cache/patchulaon Linux, and~/Library/Caches/patchulaon macOS. Every checkout shares it, so lookups from one are reused in the next, and nothing is written into the repository. Pass--cache DIRto use another directory. It holdscache.sqlite(HTTP validators, catalogs and write receipts), the partial clones inworktrees/and the tool store intools/. A warm cache is most of the speed, so keep it between runs. With neitherHOMEnorXDG_CACHE_HOMEset, local commands stop and ask for--cache.
Some tools download slowly, so prewarm the store when you build an image:
patchula tools install --cache /var/lib/patchulapatchula tools prune --days 30 --cache /var/lib/patchulaShell completions and man page
Section titled “Shell completions and man page”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.
© 2026 Sweepy
