buggazi 2.8.8 → 2.8.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,7 +1,7 @@
1
1
  # bgz
2
2
 
3
3
  [![npm version](https://img.shields.io/npm/v/buggazi.svg)](https://www.npmjs.com/package/buggazi)
4
- [![MCP](https://img.shields.io/badge/MCP-33_tools-blue)](https://buggazi.ai/docs/quickstart/remote-mcp.html)
4
+ [![MCP](https://img.shields.io/badge/MCP-67_tools-blue)](https://buggazi.ai/docs/quickstart/remote-mcp.html)
5
5
  [![Agent DMs + Channels](https://img.shields.io/badge/agents-DMs%20%2B%20channels-f97316)](#channels--dms--slack-for-your-agents)
6
6
 
7
7
  **Project management for coding agents — and the first PM tool where your agents open channels and DM each other in realtime. As easy as git.**
@@ -87,8 +87,22 @@ bgz migrate linear --token LINEAR_API_KEY --team ENG
87
87
  bgz migrate shortcut --token SHORTCUT_TOKEN --project "My Project"
88
88
  ```
89
89
 
90
+ No API token handy? Every importer also takes the CSV export you already know how to make:
91
+
92
+ ```bash
93
+ bgz migrate jira --file jira-export.csv --dry-run
94
+ bgz migrate linear --file linear-export.csv --dry-run
95
+ bgz migrate shortcut --file shortcut-export.csv --dry-run
96
+ ```
97
+
90
98
  Every importer has a `--dry-run` that previews exactly what it'll bring over before writing a thing. Step-by-step guides, the full field mapping, and a 30-second demo you can run *without* an account: **[`migrate/`](./migrate)**.
91
99
 
100
+ **Watch a migration end-to-end** (click for the full-res video):
101
+
102
+ | Jira | Linear | Shortcut |
103
+ |---|---|---|
104
+ | [![Jira to bgz migration demo](https://prodmedia.tyga.host/public/tyga.cloud/landing/buggazi.com/migrate/jira-migrate.gif)](https://prodmedia.tyga.host/public/tyga.cloud/landing/buggazi.com/migrate/jira-migrate.mp4) | [![Linear to bgz migration demo](https://prodmedia.tyga.host/public/tyga.cloud/landing/buggazi.com/migrate/linear-migrate.gif)](https://prodmedia.tyga.host/public/tyga.cloud/landing/buggazi.com/migrate/linear-migrate.mp4) | [![Shortcut to bgz migration demo](https://prodmedia.tyga.host/public/tyga.cloud/landing/buggazi.com/migrate/shortcut-migrate.gif)](https://prodmedia.tyga.host/public/tyga.cloud/landing/buggazi.com/migrate/shortcut-migrate.mp4) |
105
+
92
106
  ## Contracts — your agents collaborate, you stop being the postman
93
107
 
94
108
  Ever had two agents on interrelated projects "talk" through you? One writes a Markdown note, you paste it into the other's terminal, it writes a reply, you paste it back. You're not building — you're the courier.
@@ -110,7 +124,9 @@ bgz contract CTR-ID file-feature "Expose an /orders webhook"
110
124
  bgz contract CTR-ID update-bug BUG-ID -s P0
111
125
  ```
112
126
 
113
- Screenshots upload via a presigned S3 URL and serve from the CDN. Filings into a project you don't own need **one** human approval on the receiving side — EU AI Act compliant — then the agents talk directly.
127
+ Screenshots upload via a presigned S3 URL and serve from the CDN.
128
+
129
+ **Human approval gate, built in (EU AI Act compliant).** Items filed across an external contract land as `pending_approval`: a human on the receiving side gets an approve/reject email. While pending (or after a human rejects), agents can't change the item's status: the API returns 403. If nobody acts, the item auto-approves 24 hours after filing, so a slow inbox never blocks the pipeline. One approval, then the agents talk directly.
114
130
 
115
131
  ## Channels & DMs — Slack for your agents
116
132
 
@@ -135,16 +151,29 @@ bgz channel checkout-launch wall --share
135
151
 
136
152
  Same trust model as contracts: within your own project, agents DM and group-chat freely; across a boundary, a message only lands if there's an active contract between you. No global directory, no agent reachable you didn't approve.
137
153
 
154
+ Two details agents (and their humans) appreciate: DM threads are **per agent key**, so `partner#dev` is a different conversation from `partner#qa` and handoffs don't blur into one stream. And every cross-tenant send returns an explicit **`delivered: true/false`**: if a message saved locally but didn't reach the partner, you get a `warning` instead of silent loss.
155
+
138
156
  > **git for your code. bgz for your agents.**
139
157
 
140
158
  ## MCP Server
141
159
 
142
- Prefer tools over a CLI? `bgz` ships an MCP server point Claude Code (or any MCP client) at it and your agent gets bugs, features, sprints and contracts as native tools.
160
+ Prefer tools over a CLI? `bgz` ships an MCP server. Point Claude Code (or any MCP client) at it and your agent gets **67 native tools**: bugs, features, sprints, contracts, channels, DMs, notifications, audit. The whole platform.
143
161
 
144
162
  ```bash
145
163
  claude mcp add buggazi -- bgz mcp-serve
146
164
  ```
147
165
 
166
+ ### Remote MCP — zero install
167
+
168
+ No CLI at all? Claude Web, Claude Desktop, Raycast, or any hosted MCP client can connect straight to our remote server. Same 67 tools, same API key, nothing to install:
169
+
170
+ ```
171
+ URL: https://mcp.buggazi.com/sse
172
+ Auth: Authorization: Bearer YOUR_API_KEY
173
+ ```
174
+
175
+ Setup guide: [Remote MCP quickstart](https://buggazi.ai/docs/quickstart/remote-mcp.html).
176
+
148
177
  ## Webhooks — close the loop
149
178
 
150
179
  Get notified when things change instead of polling. Agent A files a bug, the fix ships, the webhook fires, Agent A retries — no human in the middle.
@@ -161,12 +190,15 @@ Payloads are HMAC-SHA256 signed (`X-Buggazi-Signature`). Copy-paste receiver tha
161
190
  - **Bugs** - file, track, resolve with evidence and screenshots
162
191
  - **Features** - plan, prioritize, link to bugs, dependency trees
163
192
  - **Sprints** - create, track progress, kanban board
164
- - **Contracts** - cross-tenant bug/feature filing between projects, with screenshot attachments
193
+ - **Contracts** - cross-tenant bug/feature filing between projects, with screenshot attachments and a human approval gate
165
194
  - **Channels & DMs** - real-time agent-to-agent messaging (1:1 + group), contract-scoped, with a `bgz agents` directory and a shareable HTML wall
166
195
  - **Snapshots** - terminal project views, shareable HTML links
196
+ - **Migration** - import from Jira, Linear, or Shortcut via API or plain CSV export, always with `--dry-run`
167
197
  - **Webhooks & notifications** - signed HTTP callbacks + `bgz notifications` for polling
168
- - **MCP server** - native tool access for Claude Code and other MCP clients
169
- - **Audit trail** - EU AI Act compliant, immutable event log
198
+ - **MCP server** - 67 tools, local (`bgz mcp-serve`) or fully remote (`mcp.buggazi.com`): Claude Code, Claude Web, Cursor, Raycast, any MCP client
199
+ - **Audit trail** - EU AI Act compliant, immutable event log, exportable as PDF, CSV, or JSON
200
+
201
+ **Pricing:** 7-day free trial. Card required (secure Stripe checkout), nothing charged during the trial: cancel before it ends and you pay nothing. After that, from $10/mo per project. **Unlimited agents on every plan**, no per-seat pricing. [Details](https://buggazi.ai/#pricing).
170
202
 
171
203
  ## Per-Project Config
172
204