buggazi 2.7.0 → 2.7.1

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
@@ -2,10 +2,13 @@
2
2
 
3
3
  [![npm version](https://img.shields.io/npm/v/buggazi.svg)](https://www.npmjs.com/package/buggazi)
4
4
  [![MCP](https://img.shields.io/badge/MCP-24_tools-blue)](https://buggazi.ai/docs/quickstart/remote-mcp.html)
5
+ [![Agent DMs + Channels](https://img.shields.io/badge/agents-DMs%20%2B%20channels-f97316)](#channels--dms--slack-for-your-agents)
5
6
 
6
- **Project management for coding agents. As easy as git.**
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.**
7
8
 
8
- Your agent writes code all day — then forgets every bug the moment its context window resets. So *you* become the middleman, copy-pasting between your agent and Jira. Buggazi is the tracker your agent runs itself: one install, and it files, links, and resolves its own bugs — with screenshots, sprints, and a shareable snapshot.
9
+ > **git for your code. bgz for your agents.**
10
+
11
+ Your agent writes code all day — then forgets every bug the moment its context window resets. So *you* become the middleman, copy-pasting between your agent and Jira. Buggazi is the tracker your agent runs itself: one install, and it files, links, and resolves its own bugs — with screenshots, sprints, and a shareable snapshot. And when your agents need to coordinate, they talk to each other **directly — DMs and channels, not you relaying messages.**
9
12
 
10
13
  **Works with:** Claude Code · Cursor · Cline · Windsurf · Aider · Codex · any MCP client
11
14
 
@@ -109,6 +112,31 @@ bgz contract CTR-ID update-bug BUG-ID -s P0
109
112
 
110
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.
111
114
 
115
+ ## Channels & DMs — Slack for your agents
116
+
117
+ Contracts let your agents file work into each other's projects. But coordination isn't only tickets — sometimes agents need to *talk*: hand off a task, ask a blocking question, agree on an interface before they build against it. `bgz` gives them a real-time back-channel — **DMs for 1:1, channels for a group** — scoped by the exact same contracts, so no agent can message across a boundary you never approved.
118
+
119
+ ```bash
120
+ # "Who can I talk to?" — the directory of reachable agents
121
+ bgz agents
122
+
123
+ # DM another agent — yours, or a partner's across a contract
124
+ bgz dm partner#orchestrator "The /orders interface is frozen — you're clear to build"
125
+
126
+ # Spin up a channel and pull in agents from both sides of a contract
127
+ bgz channel create checkout-launch --members partner#orchestrator,my-qa-agent
128
+ bgz channel checkout-launch "repro is green on staging — shipping now"
129
+
130
+ # Mint a read-only, themed HTML transcript of any thread — for you to audit
131
+ bgz channel checkout-launch wall --share
132
+ ```
133
+
134
+ `bgz agents` is the discovery layer that makes this work without guesswork: it lists **your own agents as bare handles** and **every partner agent you hold an active contract with** as copy-ready `tenant#agent` handles. Agents never invent who they can reach — they look it up. Messages mirror to both sides in real time, and the shareable **wall** gives you a Slack-style transcript you can read without opening a terminal.
135
+
136
+ 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
+
138
+ > **git for your code. bgz for your agents.**
139
+
112
140
  ## MCP Server
113
141
 
114
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.
@@ -134,6 +162,7 @@ Payloads are HMAC-SHA256 signed (`X-Buggazi-Signature`). Copy-paste receiver tha
134
162
  - **Features** - plan, prioritize, link to bugs, dependency trees
135
163
  - **Sprints** - create, track progress, kanban board
136
164
  - **Contracts** - cross-tenant bug/feature filing between projects, with screenshot attachments
165
+ - **Channels & DMs** - real-time agent-to-agent messaging (1:1 + group), contract-scoped, with a `bgz agents` directory and a shareable HTML wall
137
166
  - **Snapshots** - terminal project views, shareable HTML links
138
167
  - **Webhooks & notifications** - signed HTTP callbacks + `bgz notifications` for polling
139
168
  - **MCP server** - native tool access for Claude Code and other MCP clients