Back to directory

Collaborative Human-Agent Protocol (CHAP)

An open, MCP- and A2A-compatible protocol and runtime for auditable human-agent work, giving approvals, overrides, handoffs and escalations one shared, hash-chained shape that can be queried instead of grepped from logs.

Collaborative Human-Agent Protocol (CHAP)

CHAP is a runtime and protocol for recording accountable decisions between humans and AI agents. When an agent drafts something, such as a code review comment or a contract redline, and a human approves, edits or rejects it, CHAP stores that exchange as a structured artefact and override, with a diff, a rationale and tags, chained together by content hash so the whole history can be fetched with one call instead of reconstructed from chat threads and logs.

An optional signed profile adds an Ed25519 signature to every envelope, bindable to a real identity through an OpenID Connect profile, and another profile anchors the hash chain in an external transparency log that can be verified without trusting the operator's own servers. CHAP is designed to sit alongside the Model Context Protocol and the Agent2Agent protocol rather than replace them: MCP for tools, A2A for other agents, and CHAP for the shared record of human-agent work.

An embedded coordinator can persist to SQLite, and both TypeScript and Python surfaces are provided, including a typed facade in TypeScript.

More in Agent frameworks

See all 902
  • Recurse

    recurse.run

    A serverless harness that lets a coding agent design, test, and deploy its own specialist sub-agents as tools, MCP servers, or bots, defined by a schema-validated manifest.

  • ProofForge

    shulgin.is-a.dev

    An AI-agent pipeline that decomposes a mathematics problem, proves each piece, and formalizes the result in Lean 4 and Mathlib until the Lean kernel accepts it, with six of its proofs already merged into Google DeepMind's formal-conjectures repository.

  • local-coder

    github.com

    Builds a local coding-agent team on top of Ollama and OpenCode by detecting the machine's hardware, recommending models for seven specialist roles, and testing whether each assigned model can actually use tools, edit a repository and pass verification.