Terminal-First Bug Tracking for Developers

Developers already live in the terminal and the editor. Every context switch out to a web ticketing UI is friction: a new tab, a login, a search, a status dropdown. A terminal-first bug workflow keeps the whole loop — see the queue, pick a bug, fix it, open the PR, update the status — in the place the work already happens.

The loop

In a terminal-first setup, a single command pulls the current bug queue into your shell, already triaged:

$ buhg:start
  Fetching open bugs...
  Found 3 open bugs.

  #4  Submit button unresponsive on mobile   high      open
  #5  Image upload 500 error                 critical  open
  #3  Nav dropdown not closing               medium    open

From there your coding agent reads the full context of a bug, follows your team's conventions from a BUHG.md file, creates a branch, writes the fix, runs your tests, opens a pull request, and updates the bug status — without you leaving the terminal.

Conventions as configuration

The reason a terminal-first agent workflow is safe to run is that your rules are explicit. A BUHG.md file in your repository defines your branch naming format, your PR target branch, and your team conventions. The agent follows them exactly, so its output looks like your team wrote it — because it is following the same rules your team does.

# BUHG.md
Branch format:  fix/bug-{number}-{slug}
PR target:      main
Rules:          run tests before PR; keep changes scoped to the bug

Multi-repo awareness

Real products span more than one repository. A terminal-first workflow that understands a workspace map can route a bug to the right codebase automatically, so a report about the billing service does not land a branch in the marketing site.

The dashboard still matters

Terminal-first does not mean terminal-only. A realtime dashboard is still the right surface for a shared view of everything open, for non-developers to watch progress, and for reviewing what shipped. The point is that the fixing happens in the terminal and the dashboard reflects it instantly — not that you give the dashboard up.

If you want to try the workflow end to end, the getting-started guide walks through installing the CLI and connecting your first project.