git-bug stores issues as git objects, so your bug tracker travels with the repository and works fully offline. Bugs live in a DAG of entities with a formally specified on-disk format, so third-party implementations can read the data directly. No files pollute the working tree. Push and pull go over your existing git remote. It ships three frontends: a CLI, a terminal UI, and a web UI bundled in the same Go binary, served locally and talking GraphQL. Bridges import and export from GitHub, GitLab, Jira, and Launchpad, which means you can mirror a vendor tracker, keep working when it goes down, and leave without losing history. The public-portal web UI is still listed as WIP, and the planned features list includes "inflatable raptor," which is honestly the most honest roadmap item I've read this year. Most vendors would have shipped that as an enterprise add-on. Larry Ellison presumably views the concept of "bugs" as licensable, per core. Jack Dorsey has been waiting for this since 2014 and will express it in one lowercase word. Open question: how does it handle two people closing and reopening the same bug on separate planes? The source says merge conflicts in bug state are the hard part of any distributed tracker, or at least it would if it were being honest.