Grite¶
A repo-local, git-backed issue/task system for AI coding agents and humans.
Grite keeps an append-only event log in git refs, builds a fast local materialized view, and never writes tracked state into the working tree. All state syncs via standard git fetch/push.
Features¶
- Git-native storage - Events stored in
refs/grite/wal, synced with standard git - CRDT-based merging - Deterministic conflict resolution, no manual merge needed
- Per-actor isolation - Each agent/device gets its own actor ID and local database
- Optional daemon - Auto-spawns for performance, not required for correctness
- Ed25519 signing - Optional cryptographic signatures on events
- Team coordination - Distributed locks for coordinated workflows
Quick Install¶
See Installation for other methods including Homebrew, Cargo, npm, pip, and gem.
Quick Start¶
# Initialize grite in a git repository
cd your-repo
grite init
# Create an issue
grite issue create --title "Fix login bug" --body "Users can't login"
# List issues
grite issue list
# Sync with remote
grite sync
See Quick Start for a complete walkthrough.
Who Is Grite For?¶
| Audience | Primary Use Cases |
|---|---|
| AI Coding Agents | Task decomposition, multi-agent coordination, persistent memory |
| Individual Developers | Offline issue tracking, personal task lists, technical debt |
| Development Teams | Distributed coordination, code review workflows, knowledge base |
| Security & Compliance | Private vulnerability tracking, incident response, audit trails |
| DevOps | CI/CD integration, release checklists, deployment tracking |
Architecture¶
Grite uses a three-layer architecture:
+------------------+ +-------------------+ +------------------+
| Git WAL | --> | Materialized View | <-- | CLI / Daemon |
| refs/grite/wal | | sled database | | grite / grite-daemon |
| (source of truth)| | (fast queries) | | (user interface) |
+------------------+ +-------------------+ +------------------+
Learn more in Architecture.
Design Principles¶
- Git is the source of truth - All state derivable from
refs/grite/* - No working tree pollution - Never writes tracked files (except AGENTS.md for agent discoverability)
- Daemon optional - CLI works standalone, daemon is performance optimization
- Deterministic merges - CRDT semantics, no manual conflict resolution
- Per-actor isolation - Multiple agents can work independently
Next Steps¶
- Installation - Get grite installed on your system
- Quick Start - Create your first issue
- Core Concepts - Understand how grite works
- CLI Reference - Full command documentation