Files
goodbuddy/docs
mesalogo f327341b00
Cross-platform packages / Validate source (push) Canceled after 0s
Cross-platform packages / Authorize desktop packaging (push) Canceled after 0s
Cross-platform packages / linux arm64 (push) Canceled after 0s
Cross-platform packages / macos arm64 (push) Canceled after 0s
Cross-platform packages / windows arm64 (push) Canceled after 0s
Cross-platform packages / linux x64 (push) Canceled after 0s
Cross-platform packages / macos x64 (push) Canceled after 0s
Cross-platform packages / windows x64 (push) Canceled after 0s
Cross-platform packages / Publish GitHub and OSS release (push) Canceled after 0s
GoodBuddy Agents / Validate Agent source (push) Canceled after 0s
GoodBuddy Agents / Build Linux arm64 Agent (push) Canceled after 0s
GoodBuddy Agents / Build Linux x64 Agent (push) Canceled after 0s
fix: prevent duplicate queue replay and use cached Agents
An interrupted dispatch could leave the same user input both in conversation
history and in the pending queue, causing it to be sent again after restart.
Persisted user messages now retain their queue identity, startup recovery drops
only matching materialized inputs, and conversation branches discard that
ownership marker.

Explicit GoodBuddy transfer now leases a verified local Agent package when the
catalog is unavailable or the local version is at least as new, while a known
newer online package still wins. Prepare both the desktop and Agent locks for
0.11.7; the experimental LoongArch preview remains excluded.

Release note: 修复对话中断后同一条排队输入可能重复发送的问题;GoodBuddy 传输现在可复用已验证的本地 Agent 包,同时不会阻止已知的线上新版。
2026-08-29 13:31:56 +08:00
..

GoodBuddy 文档导航

GoodBuddy 文档按“文档类型 → 功能域”组织。新增文档应先选择类型,再放入对应功能目录, 避免继续把所有设计平铺到单一 features 目录。

产品需求

功能域 入口
Task 与 Job Task 与 Job 总览
Smart Heartbeat 智能心跳 PRD
助手工作栏 通用助手工作栏与执行空间 PRD
会话监督 会话监督 PRD
记忆 分区记忆 PRD
并行实验 并行实验工作台 PRD
持续学习 持续学习与评估门 PRD
知识库 知识库检索与分块增强 PRD
文档处理 文档解析与本地 OCR
消息通道 微信 ClawBot 通道 PRD

Task 与 Job 文档

跨功能文档

目录规则

  1. PRD 放在 docs/prd/<功能域>/。
  2. 跨功能技术总纲放在 docs/architecture/。
  3. 产品级设计放在 docs/design/,路线图和实施状态分别放在 roadmap、status。
  4. 测试方法、评估协议和质量报告放在 docs/quality/。
  5. 开发环境、实验性构建和移植说明放在 docs/development/。
  6. 一个概念只能有一份权威定义;其他文档链接到它,不复制另一套术语。
  7. Task、Job、Run、Subagent 和 Conversation 的含义以 Task 与 Job 统一领域模型 为准。