从 v0.3.0 到 v0.5.23解读 Buzz 版本演进、关键里程碑与 Agent 协作基础设施【免费下载链接】buzzA hive mind communication platform项目地址: https://gitcode.com/GitHub_Trending/buzz14/buzz本篇指南以开源仓库 CHANGELOG.md 为主体系统梳理 Buzz一个基于 Nostr 协议的人机协作通信平台从 v0.3.0 到 v0.5.23 的完整版本脉络解读桌面端、relay、数据库、认证与 Agent 协议各条线的演进逻辑。读完本文你将掌握 Buzz 的版本组织方式、各里程碑阶段的核心能力ACP 会话模型、NIP-FI 联邦身份、NIP-AM 用量度量、评测体系等并能对照仓库源码快速定位每个关键机制的实际实现。一、版本体系概览三段式演进与双线记录结构CHANGELOG.md 是理解 Buzz 仓库演化最快的入口。整个文件以版本号为骨架覆盖 v0.3.0Initial release on the automated pipeline. Unifies OSS and internal version numbering above both v0.0.21 (OSS) and v0.2.38 (internal)即自动化流水线发布的首个统一版本到最新的 v0.5.23可以粗分为三个阶段v0.3.xSprout → Buzz 更名期完成产品从 Sprout 到 Buzz 的品牌与代码更名如 v0.3.17 的 Rename desktop app to Buzz同时落地 relayer 性能优化、mesh 共享计算、NIP 系列规范。v0.4.x社区与项目管理期大规模重做 onboarding、社区community管理、Projects v3、agent 配置体系AgentDefinition/AgentInstance/AgentRecord 三层重构。v0.5.xAgent 协议深化期ACP 会话模型、NIP-FI 联邦身份、NIP-AM 用量度量、Bestie/Pi 预设、推送通知 MVP 与基准评测体系buzz-dataset。从 v0.5.20 起每个版本内部按两个分区组织Desktop and shared changes桌面端Tauri React见 desktop/以及与 Web 共享的改动Other repository changesrelay、数据库、CLI、移动端、CI、文档等其余部分的改动。每个版本段末尾是Compare desktop-vX...desktop-vY形式的版本对比链接标注该版本对应的 desktop 分支标签例如 v0.5.23 对比desktop-v0.5.22...desktop-v0.5.23。这说明 Buzz 的桌面端遵循独立的desktop-v*标签体系relay 则另有自己的版本线见 v0.3.33 的 release Buzz Relay version 0.1.1、v0.5.9 的 release Buzz Relay version 0.2.1 条目。二、最新版本 v0.5.23打包修复、ACP 提示词与远程提及授权以当前最新的 v0.5.23 为例可以看清一个小版本典型承载的内容打包与资产fix(desktop): keep packaged frontendDist relative so Windows embeds assets—— 保持打包后的frontendDist相对路径确保 Windows 平台正确嵌入前端资源。这与 desktop/src-tauri/tauri.conf.json 的构建配置直接相关。侧边栏fix(sidebar): simplify unread indicators and emphasize priority activity—— 简化未读指示器突出优先级活动。ACPAgent Client Protocolfeat(buzz-acp): update base prompt; add buzz context and skills to Pi agents—— 更新基础提示词fix(acp): rename system tag to agent-instructions—— 将系统标签重命名为agent-instructions。这条改动的落点在 crates/buzz-acp/src/base_prompt.md该文件是 agent 的行为总纲包含 Buzz CLI 用法、项目协作、沟通模式mention 规则、回调 mention 等章节。仓库中还存在 crates/buzz-acp/src/session_model_channel.md 与 crates/buzz-acp/src/session_model_thread.md分别对应 每个频道一个 agent 会话 与 每个线程一个 agent 会话 两种会话模型v0.5.22 的feat(buzz-acp): give each channel thread its own agent session。提及Mention机制fix(desktop): restore mention chip identity iconsfix(desktop): authorize remote mentions at publication—— 发布时授权远程提及fix(desktop): bind duplicate mention selections to exact recipientsfeat(desktop): preserve mentions across copy and paste。mention 是 Buzz 人机协作的核心原语。base_prompt 中明确要求通知性mention必须使用与 Buzz 中显示完全一致的名字禁止加粗/斜体/反引号格式化会破坏通知投递并在同一命令中用--mention hex-or-npub显式传递身份。评测体系甚至专门为提及不唤醒不相关 agent设计了 narrative-agent-names 回归任务。其他Persist video playback speed preference持久化视频播放速度、feat(desktop): invite owned agents from standalone forums从独立论坛邀请自有 agent、Collapse contiguous join messages折叠连续入群消息。三、v0.5.22 / v0.5.21Bestie、Pi 预设、Databricks OAuth 与语音v0.5.22 与 v0.5.21 的记录几乎完全重合后者是前者合并前的分支快照集中体现了 Agent 能力与多模态扩展Bestie 持久体验feat(desktop): add persistent Bestie experience与feat(desktop): add protected-build Bestie experiment并配套test(desktop): await Bestie drag and profile hover endpoints的 E2E 测试加固说明 Bestie 是一个需要与 UI 严格同步的受保护实验特性。Pi Agent 预设feat(desktop): add Pi agent preset并在 v0.5.23 中为 Pi agents 注入 buzz context 与 skills。Databricks 生态feat(buzz-agent): add DatabricksAuthCoordinator single-flight OAuth—— 单飞single-flightOAuth避免并发认证风暴feat: add databricks fable 5.1 model capabilities、feat(agent): discover Databricks Unity Catalog models、feat(model-capabilities): humanize databricks goose model names相关测试位于 crates/buzz-agent/tests/databricks_auth_coordinator.rs 与 crates/buzz-agent/tests/databricks_oauth.rs。语音与推送桌面端加入语音便签Add voice notes to desktop messages移动端完成推送通知 MVPfeat(mobile): push notifications MVP配套 crates/buzz-push-gateway 与 deploy/charts/buzz-push-gateway 部署图表并prepare buzz-push-gateway for deployment。团队目录Team Catalogfeat(desktop): implement 30178 team catalog backend—— 实现 kind 30178 团队目录后端relay 侧对应 v0.5.3 的 gate kind 30178 team-catalog reads behind the shared tag。身份与密钥fix(desktop): preserve keyring identity during recovery、feat(desktop): recover desktop identity from a signed-in phonev0.5.6—— 桌面端与移动端通过配对恢复身份。四、v0.5.x 主线ACP 会话模型、权限边界与认证基础设施进入 v0.5.x 后变更日志反复出现一组主线技术主题它们共同构成了 Buzz 的 Agent 运行时底座4.1 ACP 会话模型与提示词上下文feat(buzz-acp): give each channel thread its own agent session#6732—— 每个频道线程独立 agent 会话feat(desktop): add thread-scoped ACP session experiment#6909—— 线程级 ACP 会话实验Deduplicate ACP thread prompt context#6706、Reduce repeated ACP session context#5423、fix(acp): preserve truncated thread context#3340Use paired tags for standing per-turn context#6701—— 用成对标签区分常驻上下文与单轮上下文。从源码结构看crates/buzz-acp/src/base_prompt.md 定义了 agent 的完整行为边界CLI 退出码 0/1/2/3/4 分别表示成功/用户错误/网络/auth/其他而 crates/buzz-acp/src/config.rs、scope.rs、prompt_framing.rs 等模块可以推断负责把上下文频道描述、项目信息、会话历史装配进提示词。4.2 权限边界与安全加固feat(buzz-agent): gate LLM tool calls on session/request_permission#5712—— LLM 工具调用需经权限门控Enforce NIP-OA authorization time bounds#7004—— 强制 NIP-OA 授权时间边界fix(acp): reject unattended permission requests#4609后被 #5323 回滚、guard against unrequested public relay skills#6394fix(relay): reject a frame on its own acknowledgement channel#6961—— 拒绝在自己的确认通道上的帧权限边界测试见 crates/buzz-agent/tests/permission_boundary.rs。4.3 NIP-FI联邦身份与授权v0.5.x 在认证侧投入巨大全部围绕NIP-FI联邦身份feat(buzz-auth): add production NIP-FI federated assertion runtime#7109feat(db): add NIP-FI identity and final-admission schema foundation#6994docs(nip-fi): rewrite NIP-FI as stateless OSS Buzz spec v2#7214docs(nip-fi): adopt deny-until-TTL and extend enforcement to HTTP ingress#7254docs(nip-fi): document Git smart-HTTP credential exemption#7268、add Blossom kind-24242 media possession-proof exception#7278chore(db): drop Phase-A NIP-FI relay-side authority ledger#7221。实现集中在 crates/buzz-auth/src/nip_fi/11 个 Rust 模块数据库侧有 migrations/0041_nip_fi_identity_foundation.sql、migrations/0042_nip_fi_authorization_foundation.sql 与 migrations/0044_drop_nip_fi_ledger.sql对应废弃 Phase-A ledger。规范文档见 docs/nips/NIP-FI.md 与 docs/formal/nip-pl。4.4 NIP-AMAgent 用量度量feat(nips,relay,acp): NIP-AM durable encrypted agent turn metrics (kind 44200)#1441v0.3.44 起feat(acp,buzz-agent): thread model name through NIP-AM kind 44200 emit path#1564fix(buzz-acp): thread cache-read tokens into NIP-AM kind:44200 events#3999fix: report agent usage per provider round, not once per turn#4545docs(nip-am): normative amendment — cache SHOULD/MUST pricingIdentity consumer cost guidance#4632feat(archive): add agent turn-metric (kind 44200) local archive#1555。NIP-AM 让 agent 每次模型调用都以 kind 44200 事件形式产出可审计、可计量的加密用量记录与 v0.5.9 的 NIP-AM agent-usage backend — P2 emission/transport/archive P4a aggregation/D6 形成完整的发布—传输—归档—聚合链路。五、v0.4.x 阶段Projects、社区管理与 Agent 配置革命v0.4.x 记录了产品形态与配置模型的大规模重构Projects v3Projects v3: unify sharing, discussions, and issue ownership#5792feat(desktop): refine repository-aware project workspacesfeat(git): make project branch workflows reliable。项目对象以 kind 30621 事件表达feat(cli): add buzz projects CLI commands (NIP-MP kind:30621)relay 侧feat(relay): accept kind:30621 multi-repo projects at ingest规范见 docs/nips/NIP-MP.md。Agent 配置三层重构v0.4.0 起 unified AgentRecord groundwork — record-first resolution runtime materialization (Phase 1A.1) → fold personas.json into the unified agent store (Phase 1A.2) → single-home the definition form as AgentDefinitionDialog (Phase 1B.3a) → re-host instance edit as AgentInstanceEditDialog → converge the three definition→instance mappings (Phase 1B.3.5)最终统一到 AgentDialog 单一入口。make agent definition authoritative for model/provider/prompt#1968确立了定义即事实来源的原则。社区管理Community moderation Phase 1: reports, bans/timeouts, audit, tombstones, relay-DM notices#1616fix(git): revoke access for banned relay members#4608Add owned community onboardingGraduate community rail。身份安全feat(desktop): store nsec private keys in the OS keyring#1172feat(desktop): locally stored NIP-49 encrypted key backup#2937feat(desktop): add password-protected backups in settings#3701feat(desktop): gate sign-out behind key backup typed confirmation#2424。六、v0.3.x 阶段更名、relay 性能与 mesh 共享计算v0.3.x 是从内部代号 Sprout走向Buzz的过渡期也是基础设施密集建设期更名refactor: rename sprout backend to buzz#958→Rename desktop app to Buzz#960→Rename web app to Buzz#959→Rename mobile app to Buzz#955以及环境变量SPROUT_*→BUZZ_*#971、代码库known_acp_provider_exact → known_acp_runtime_exact#900、ACP provider→runtime 全库更名#783。relay 性能perf(relay): bounded-concurrency multi-filter query execution (S2)#1457perf(relay): defer post-commit dispatch and avoid verify clone#1453Serialize fan-out EVENT frames once#1459perf(relay): batch outbound websocket data frames#1464E1E3: reduce relay ingest/fan-out DB round trips#1454。数据库迁移migrations/从 0001 到 0044同步承载了 channel-id 索引0027、replica heartbeat0026/0034、push lease0012-0015等结构演进。Mesh 共享计算feat(mesh): upgrade embedded mesh to v0.74 and harden shared compute#3741Mesh-LLM v1: relay-gated direct-iroh inference between users (WAN)#822Relay mesh: cross-pod tunnel huddle transport (buzz-relay-mesh)#1670。实现见 crates/buzz-relay-mesh 与文档 docs/buzz-shared-compute-dev.md。NIP 基础设施NIP-30 自定义 emoji#816、NIP-ER 提醒kind:30300relay 调度器 #957 桌面 UI #963、NIP-34 git PR/issue CLI#1073/#1279、NIP-DV 隐藏 DM 可见性快照#857、NIP-38 用户状态buzz users set-status#3253。七、评测体系以变更日志为索引的 Buzz 行为基准v0.5.22 的Add Buzz benchmark evaluation layers#6823与 v0.5.18 的Add Buzz-native collaboration benchmarks#6264引入了专门的评测体系这在 benchmarks/buzz-dataset/README.md 中有完整说明每个任务评测的是Buzz 产品行为而非单纯的任务正确性——where the reply lands, who it notifies, what it was willing to read。评测分两层Regressionk1产品契约回归与Workflowk3多步协作例如任务层被测行为reply-to-threadRegression回复落在用户所在线程而非新顶层消息user-mentionRegression以事件级p-tag 提及请求者交还回合read-named-path-outside-workspaceRegression读取用户显式命名的路径而非拒绝create-channel-invite-usersWorkflow创建精确形状、TTL 与成员关系的频道ambiguous-user-mentionWorkflow解析重名显示名并只通知目标 pubkey运行命令仓库根目录执行为just benchmark \ --path benchmarks/buzz-dataset/reply-to-thread \ --manifest benchmarks/harbor-buzz-orchestra/manifests/buzz-native-solo-luna.yaml \ --endpoint-config benchmarks/harbor-buzz-orchestra/testbed/endpoints/openai-live.json \ --n-concurrent 1评测通过 benchmarks/harbor-buzz-orchestra 的BuzzOrchestraAgent适配器在 Harbor 任务容器内启动真实的buzz-acp → buzz-agent → buzz-dev-mcp进程树与桌面应用启动的进程树一致agent 停止后把 relay 公共状态快照导出为/logs/artifacts/buzz-evidence.json供 verifier 评分。值得注意的设计判断写在数据集 README 中for reply-to-thread and user-mention the graded behavior is deliberately absent from instruction.md — it has to come from buzz-acps production base prompt即被测行为刻意不出现在任务指令里必须来自生产 base prompt——这正是 v0.5.23 中update base prompt、rename system tag to agent-instructions等提示词改动如此重要的原因。八、工程实践测试、CI 与发布纪律CHANGELOG 还能读出 Buzz 的工程质量纪律文件体积门禁ci: make file-size policy a first-class gate#6187、ci: relax file-size ceilings by surface#6485、chore(desktop): bring ChannelScreen back under the size gate#1520—— 对应 desktop/scripts/file-size-policy.mjs 等检查脚本依赖安全大量 RUSTSEC 修复#6222 h2、#5659 webbrowser、#4392 nostr、#4139 nostr-relay-pool、#3135 NIP-44 remote DoS、#1563 crossbeam-epoch、#1004 等并有Enforce a three-day dependency cooldown#6426限制依赖更新节奏E2E 稳定化ci(desktop): surface flaky E2E tests instead of retry-masking them#1838、test: add deterministic desktop release smoke#5699发布不可变feat(release): make desktop releases immutable#3568、fix(release): require exact-head approval for desktop tags#3973、chore(release): release Buzz Desktop version ...与回滚记录v0.5.5 的三次 release/revert表明发布走的是 tag 审核 自动更新清单manifest流水线。九、如何继续深入如果某个版本条目引起了你的兴趣可以按如下路径在仓库中展开Agent 行为读 crates/buzz-acp/src/base_prompt.md当前生产提示词150 行配合 crates/buzz-acp/src/session_model_channel.md / session_model_thread.md 理解会话模型认证与授权读 crates/buzz-auth/src/nip_fi 与 docs/nips/NIP-FI.md结合 migrations/0041_nip_fi_identity_foundation.sql 理解 schema 落地Agent 运行时读 crates/buzz-agent/srcagent.rs、permission.rs、mcp.rs、handoff.rs与 crates/buzz-agent/tests 的权限边界、回归、golden transcript 测试relay 与多租户读 crates/buzz-relay/src83 个模块与 docs/multi-tenant-relay.md、docs/formal/MultiTenantRelay.tlaTLA 形式化证明评测读 benchmarks/buzz-dataset/README.md 与 benchmarks/harbor-buzz-orchestra/README.md每个任务的task.toml声明metadata.evaluation_layerverifier 测试在 benchmarks/harbor-buzz-orchestra/tests。最后提醒一点CHANGELOG 中 v0.5.23 与 v0.5.22、v0.5.21 的 Desktop 条目存在大面积重复同一条 commit 被计入多个版本段这是 release 分支合并节奏造成的正常现象阅读时以最新版本v0.5.23为准避免重复计数。【免费下载链接】buzzA hive mind communication platform项目地址: https://gitcode.com/GitHub_Trending/buzz14/buzz创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考