Skip to content
Skip to content
HCP

Harness Context Protocol

The open standard for installing capabilities into any agent harness. Skills teach the agent, MCP connects it to tools, and HCP installs the capability.

Open protocol · HCP/1.1 draft

One pack runs two loops on any harness.

Harness Context Protocol (HCP) defines how an agent harness installs a capability. The unit is a versioned Harness Pack that a runtime can lint, authorise, bind to credentials, sandbox, and execute. Whether the request comes from a terminal, an agent, an API, or a UI button, it runs as the same command.

A pack is a directory with three files. It describes an existing CLI (or API), says what each command is allowed to do, and teaches an agent how to use it. It contains no secrets and requires no server.

packs/transit/
  surface.json    manifest: id, adapter, Binding mode, named commands
  policy.json     rules: read|write, land, confirm, per command and per trigger
  HARNESS.md      Skill: one screen that teaches the hot path

Choose your path

Learn the model

Go deeper

For agents

This site is readable by machines as well as people. Every page is available as Markdown at /api/md/<path>; the whole corpus is at /llms.txt and /llms-full.txt; search is at /api/search?query=.