Claude Code

Buggazi + Claude Code

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

Claude Code Cursor Cline Windsurf Aider Codex Copilot Claude Web Raycast

Step 1: Install + signup

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

API key saved to .bgz/config.json. The key is LIVE immediately with full access for 48h. Start filing right away, no card or email needed up front. Before the window closes, your human opens the trial link ($0 card-auth) to start the free 7-day trial; the same key keeps working, no re-signup.

Already have a key? bgz login --local --key YOUR_KEY. No --url needed.

Referred by a Buggazi user? Add --ref BGZ-REF-XXXX to signup: 14-day trial instead of 7.

Add .bgz/ to your .gitignore.

Step 2: Setup your agent

bgz init

Detects your agent (CLAUDE.md), outputs the config snippet to paste and MCP setup. The snippet points Claude Code to bgz init --agent-schema — the authoritative list of every command and valid flag. Everything you need, right in the terminal.

Step 3 (recommended): Install the schema gate hooks

bgz init --claude-hooks

Claude Code only. Writes two hook scripts into .claude/ and wires them into .claude/settings.json (your existing hooks are preserved; Claude Code asks you to approve project hooks on first run):

SessionStart refreshes the live agent-schema and reminds the agent this project tracks work in Buggazi. PreToolUse validates every bgz command against that schema before it runs: an invented verb or subcommand is blocked with an error that names the correct command, so the agent self-corrects in the same turn instead of burning a failed run. Raw curl writes against the Buggazi API get redirected to the CLI or the remote MCP.

Fail-open by design: if bgz or the schema file is unavailable, everything passes through and your session is never blocked. --print previews without writing, --force regenerates over your edited copies.

Commit .claude/ so every teammate's Claude Code picks the hooks up. Keep .bgz/ gitignored. Other agents (Cursor, Cline, Aider, web) keep using CLAUDE.md / AGENTS.md as before.

Step 4: Start using

Ask Claude Code to do anything — it discovers commands from bgz init --agent-schema and files bugs, features, and sprints automatically. Add --project KEY to group work by project (unknown keys auto-create it, unlimited on every plan).

Going further: dispatch to GitHub

Buggazi is the durable record; GitHub issues and PRs are disposable execution artifacts. You can dispatch a bgz bug as a GitHub issue that summons Claude Code in GitHub Actions: the agent opens a PR, you poll the PR state back onto the bgz item, verify locally, merge, then resolve in bgz. Only backend/logic/api items go headless; visual work stays with human eyes. The full pattern (routing, polling, workflow caps, subscription auth) is in llms.txt under "GitHub Bridge".