From zero to first issue in minutes
grite installs from every package manager you already use, needs nothing but a recent git, and stores its issues inside the repo. No account, no server, no config.
1 · Install
Pick whichever channel fits your stack. All ship the same grite CLI and optional grite-daemon.
Homebrew
$ brew install neul-labs/tap/grite Cargo
$ cargo install grite npm
$ npm install -g grite-cli pip
$ pip install grite-cli gem
$ gem install grite-cli Chocolatey
$ choco install grite Only runtime dependency: git 2.38 or later.
2 · Initialise, create, sync
$ grite init → created refs/grite/wal $ grite issue create --title "Fix WAL race" --label bug issue 0c3a · created $ grite list 0c3a bug Fix WAL race open $ grite issue close 0c3a issue 0c3a · closed $ git push # your issues travel with the code
3 · Optional daemon
The CLI works standalone. For teams and multi-agent workloads, grite-daemon keeps the projected issue state warm and serialises concurrent calls — a performance optimisation, never a requirement.
4 · Wire in an AI agent
Because grite is built for AI coding agents, point your agent at the grite CLI and let it open, update, and close issues as durable, shared memory. Merges are conflict-free, so several agents can work the same task graph in parallel. See AI coding agents for the full pattern.
That's the whole loop
Install, init, create, push. The full reference lives in the documentation; the design rationale is on how it works.