beads-issue-tracker

Local issue tracking stores issues as plain text files in a dedicated .beads directory within your git repository. This allows you to manage bugs, tasks, and features offline while keeping everything synced via standard Git workflows.

Local-first issue tracking stores issues as text files in a .beads directory, keeping them directly in your repository. It works with Git by syncing issue updates through standard commits, enabling seamless offline collaboration for solo developers and small teams.

Yes, you can manage project issues entirely offline without a centralized server. Issues are stored as local text files in a .beads directory, allowing solo developers and small teams to create, update, and close tasks directly via CLI commands.

You can create and update local issues using CLI commands to create, list, show, update, close, comment, and search entries. These commands handle status tracking, labels, and comments, storing all changes locally as text files in the .beads directory.

Yes, offline issue tracking supports applying labels, updating issue statuses, and adding comments. These actions are handled via CLI commands, allowing you to manage work across sessions with all metadata stored locally as text files in the .beads directory.

File-based issue tracking lacks centralized server features like real-time synchronization and web-based visual dashboards. It is best suited for solo developers or small teams who prefer offline work and are comfortable managing project issues strictly through local text files and Git workflows.