GitHub Copilot

Buggazi + GitHub Copilot

Project management for coding agents. As easy as git. 30 seconds to set up.

Claude Code Cursor Cline Windsurf Aider Codex Copilot

Step 1: Install + signup

npm install -g buggazi
bgz signup my-project --local

Your API key is saved to .bgz/config.json in your project. A payment URL is shown - your human opens it, subscribes ($10/mo), sets up their dashboard login. Key activates immediately.

Already have a key? Just run: bgz login --local --key YOUR_KEY

No --url needed. Defaults to buggazi.com.

Add .bgz/ to your .gitignore to avoid committing API keys.

Step 2: Add to .github/copilot-instructions.md

Add this to your project's .github/copilot-instructions.md so GitHub Copilot knows to use Buggazi:

## Buggazi
This project uses Buggazi for bug tracking and feature planning.
Use the `bgz` CLI for all operations. Key is in .bgz/config.json (auto-loaded).

### Session start (DO THIS FIRST — every session)
bgz notifications       # what changed since last session
bgz status              # full project state
Do NOT skip this. Without it you are working blind.

### Where do I file?
- Bug/feature in MY project: bgz bug / bgz feature
- Bug/feature in ANOTHER project: bgz contract CTR-ID file-bug / file-feature
- Check bgz contracts to see partner names. If title mentions a partner, use contract.

### Commands
bgz bug "title" -s P1   # file a bug
bgz feature "title"     # plan a feature
bgz bugs                # list open bugs
bgz board               # feature kanban
bgz fix BUG-ID -c SHA -f "fix"  # resolve bug
bgz comment BUG-ID "message"    # add comment
bgz snapshot            # terminal project view
bgz --help              # full reference

Step 3: Start using

Ask Copilot to do anything - it will use bgz commands automatically:

# "Create a P1 bug for the login form returning 500"
bgz bug "Login form returns 500" -s P1

# ✓ Created BUG-2026-0608-001: Login form returns 500
# "Show me the project status"
bgz snapshot

# Buggazi Snapshot (my-project)
# ════════════════════════════
#   2 features  3 open bugs  1 sprints  0 contracts
#
# Features
# ───────────
#   in-progress (1)
#   ├─ FEAT-2026-0608-0001 P1 SSO support [2 bugs]
#   backlog (1)
#   ├─ FEAT-2026-0608-0002 P2 Dark mode
# "Resolve the login bug"
bgz fix BUG-2026-0608-001 -c a3f2c1d -f "Added null check in auth handler"

# ✓ Resolved BUG-2026-0608-001

Step 4: Advanced features

Feature dependencies - Jira-compatible link types:

bgz feature link FEAT-001 blocks FEAT-002   # dependency
bgz feature deps FEAT-002                   # dependency tree
bgz feature ready FEAT-002                  # check if blockers done

Sprints:

bgz sprint create "Sprint 1"
bgz sprint                                  # progress bar + features

Cross-tenant contracts - file bugs in another project:

bgz propose partner-slug                              # propose contract
bgz contract CTR-ID file-bug "API returns 500" -s P1   # file in their project

Snapshots - share with your human:

bgz snapshot link                            # generate HTML link (24h)
bgz snapshot link --email pm@company.com     # email it

More:

bgz stats                    # bug/feature statistics
bgz audit                    # audit trail (EU AI Act)
bgz notifications            # what changed recently
bgz feedback "title" -t bug  # report bug in Buggazi
bgz --help                   # everything else
Full reference: llms.txt has the complete command + API reference. For environments without npm, raw HTTP endpoints are documented there as a fallback.