Git-bug is offering software teams a distributed issue tracker that travels with their Git repositories and remains usable without a network connection. The open-source tool treats bug data as collaborative material that can be pushed and pulled through Git remotes, giving developers a workflow that is closer to source-code version control than to a conventional centralized ticket service.
The project’s command-line workflow lets users create, inspect, comment on, close and reopen issues from a terminal. Teams can exchange those records with `git bug push` and `git bug pull`, allowing collaborators to synchronize through the same broad remote model they already use for code. Because the tracker is local, viewing or editing an issue does not depend on continuous access to a hosted platform.
Git-bug also provides two interfaces beyond its basic commands. An interactive terminal interface supports browsing and editing, while a browser-based interface adds searching, filtering, issue creation and changes to titles, labels and status. The web interface is bundled in the project’s Go binary and served by a local HTTP server. It includes a repository code browser with a file tree, syntax highlighting, commit history and diffs, and communicates with the backend through GraphQL.
The project is not limited to teams that want to leave established trackers. Bridges can import from and export to GitHub, GitLab, Jira and Launchpad, although support varies by service. That design makes it possible to use git-bug as a local interface while continuing to synchronize with an organization’s existing system.
Its distributed model is backed by a documented on-disk specification covering identities, bug entities and the directed acyclic graph used for records. The formal format is intended to let other software read git-bug data or build compatible implementations, rather than making the project’s own client the only route to stored issues.
Some planned use cases remain unfinished. The maintainers say public projects often need a portal where anyone can report or edit issues. The web interface is intended eventually to accept external OAuth authentication for that purpose, but that capability is not yet ready. The feature matrix also contains planned work and is not presented as exhaustive.
Git-bug is released under the GPLv3-or-later license. Its practical proposition is narrower than replacing every hosted project-management system: it gives developers ownership of a portable issue database, offline access and a path to interoperate with the services their teams may still require.
