# grite

> grite is a repo-local, git-backed issue and task tracking system built for AI coding agents and humans. Issues are stored as an append-only event log inside git refs (refs/grite/wal), CBOR-encoded, optionally Ed25519-signed, and merged deterministically via CRDTs. No server, no database, no merge conflicts — just git. Built by Neul Labs. MIT licensed.

grite ships as a single CLI (`grite`) and an optional background daemon (`grite-daemon`). It is distributed via Cargo, npm (grite-cli), pip (grite-cli), gem (grite-cli), Homebrew, and Chocolatey. The only runtime dependency is git 2.38 or later.

## Docs

- [Home](https://grite.neullabs.com/): Overview, features, architecture sketch
- [Features](https://grite.neullabs.com/features/): Every feature by category — git-native storage, event log + CBOR, CRDT merge, Ed25519 signing, CLI + daemon, agent-first design
- [How it works](https://grite.neullabs.com/how-it-works/): The architecture in one page — CBOR events in refs/grite/wal, sync via git, deterministic CRDT merge
- [Quickstart](https://grite.neullabs.com/quickstart/): Install, grite init, create/list/close issues, sync via git push, wire in an agent
- [Use cases](https://grite.neullabs.com/use-cases/): AI coding agents, offline issue tracking, monorepo task tracking
- [FAQ](https://grite.neullabs.com/faq/): Server-less operation, conflict-free merge, what's stored in git, signing, agents, install, comparisons
- [Glossary](https://grite.neullabs.com/glossary/): CRDTs, event sourcing, git refs, CBOR, Ed25519, deterministic merge, and more
- [About](https://grite.neullabs.com/about/): Thesis — the tracker belongs in the repo
- [Field notes (blog)](https://grite.neullabs.com/blog/): Engineering writing from the grite team
- [Documentation](https://docs.neullabs.com/grite/): Full reference docs
- [GitHub](https://github.com/neul-labs/grite): Source

## Compare

- [All comparisons](https://grite.neullabs.com/compare/): Index of honest, fact-based comparisons against adjacent trackers
- [vs GitHub Issues](https://grite.neullabs.com/compare/github-issues/): grite vs GitHub Issues — internal task graph and offline-first work vs public inbound surface
- [vs Linear](https://grite.neullabs.com/compare/linear/): grite vs Linear — repo-local, account-free, git-synced storage vs a polished hosted tracker
- [vs Beads](https://grite.neullabs.com/compare/beads/): grite vs Beads — pure git refs with a CRDT log vs an embedded Dolt database

## Use cases

- [AI coding agents](https://grite.neullabs.com/use-cases/ai-coding-agents/): A durable, shared task graph for agents with conflict-free parallel edits and distributed locks
- [Offline issue tracking](https://grite.neullabs.com/use-cases/offline-issue-tracking/): Fully offline tracking from the terminal, sync on the next git push
- [Monorepo task tracking](https://grite.neullabs.com/use-cases/monorepo-task-tracking/): Issues that branch and merge with the code across a monorepo

## Field notes (blog)

- [Why your repo is a better issue store than your tracker SaaS](https://grite.neullabs.com/blog/your-repo-is-a-better-issue-store/): The architectural case for storing issues in git rather than a hosted tracker SaaS
- [Migration: 3,000 GitHub issues to grite in one afternoon](https://grite.neullabs.com/blog/migration-3000-github-issues-in-one-afternoon/): A practical walkthrough of moving a real backlog out of GitHub Issues and into grite
- [Issue tracking that doesn't pull devs out of the editor](https://grite.neullabs.com/blog/issue-tracking-without-leaving-the-editor/): Rebuilding issue tracking around the editor and terminal as the only surfaces engineers need
- [Designing for AI agents as first-class issue authors](https://grite.neullabs.com/blog/agents-as-first-class-issue-authors/): What changes when you assume agents, not humans, will be the majority of issue authors

## Optional

- [RSS](https://grite.neullabs.com/rss.xml): Field notes feed
- [llms-full.txt](https://grite.neullabs.com/llms-full.txt): Long-form summary