Home / Use cases / Offline issue tracking
Offline issue tracking
Because grite keeps issues inside the repository and needs nothing but git, every operation works offline. Open issues on a plane or an air-gapped machine, and let them sync when you next reach a remote.
The problem
- ▸Hosted trackers require connectivity — you cannot triage or update issues without a network.
- ▸Context switching to a browser to file a quick note breaks flow when you are deep in the terminal.
- ▸Notes taken offline in a scratch file rarely make it back into the real tracker.
How grite solves it
- ▸grite stores issues in refs/grite/wal inside your repo, so creating, editing, and closing all work with zero connectivity.
- ▸It is CLI-first — file an issue without leaving the terminal, with structured output for scripting.
- ▸When you reconnect, git push carries your offline changes upstream and git fetch merges everyone else's deterministically.
File issues with no network
# offline, mid-flight $ grite issue create --title "Edge case in retry loop" issue 3d70 · created # back online $ git push # syncs the issue upstream
Questions
+ What happens to offline edits when I reconnect?
They are appended to your local WAL as normal. git push shares them, and git fetch merges any changes made elsewhere via CRDT — no conflicts, no lost edits.
+ Do I need the daemon for offline use?
No. The CLI works standalone. The optional grite-daemon only speeds up queries; it is never required.
Try it in your repo
One install, one grite init, and the task graph lives with your code.