CHAP 解决了多智能体协作中人类监督信号丢失的痛点，做 AI 部署和智能体系统的团队可以直接参考其协议和开源实现，避免重复造轮子。
随着基础模型从生成回复转向执行操作任务，多人类、多智能体的协作场景日益普遍，但当前缺乏统一协议来记录人类判断、任务交接和审核决策。CHAP（Collaborative Human-Agent Protocol）协议应运而生，它定义了一个共享工作空间，通过核心组件（工作区、参与者、任务、工件和仅追加的证据日志）以及可组合的配置文件（如审核、路由、交接、签名等），将原本散落在聊天记录和代码中的关键信号（如人类编辑、审批、交接）转化为结构化、可追溯的事件。该协议旨在解决当前多智能体部署中人类监督信号丢失、责任归属不清的问题，为跨团队、跨时区的协作提供标准化基础。
Collaborative Human-Agent Protocol (CHAP)
Foundation models are moving from response generation into operational roles. They plan across steps, call tools, request human input, coordinate with other agents, and increasingly carry responsibility for work that affects customers, claims, code, contracts, and clinical decisions. Production deployments are no longer one human supervising one model. They are multi-human, multi-agent collaborations that cross teams, time zones, and trust boundaries. The technical surface for this collaboration remains weakly specified. When an agent drafts a response and a human edits it before it ships, the moment of human judgement is the most valuable signal in the system. In current practice it is recorded, if at all, in application code, chat threads, ticket comments, and tribal memory. Two protocol standards address adjacent concerns: MCP standardises agent access to tools and data, and A2A standardises agent-to-agent interoperability. Neither defines the shared workspace in which humans and agents perform accountable work together. This paper presents CHAP, the Collaborative Human-Agent Protocol. Under CHAP, the override that used to vanish into a chat thread becomes a structured event carrying a diff, a rationale, and a content hash. The handoff between shifts becomes a portable envelope rather than a pinned message. The human approval of an agent's draft becomes a non-repudiable signed decision that can be replayed years later. The protocol achieves this through a small Core (workspaces, participants, tasks, artefacts, and an append-only evidence log) together with composable profiles that add review, modes, routing, deliberation, handoff, identity, signatures, and transparency-backed audit as deployments require them. Specification, reference implementation, conformance suite, and worked examples are available at: https://github.com/BrightbeamAI/chap