Protocol started by AUVY building
HCP
An open format for installing agent capabilities together with their rules, tools and tests.
“Harness Context Protocol.”
harnesscontextprotocol.dev
my-capability/
├─ surface.json what it can do: verbs, inputs, transports
├─ policy.json what it may do: read, write, ask a person first
└─ HARNESS.md how to run it, for people and agents
{
"id": "my-capability",
"hcp": { "hcp": 1, "adapter_kind": "wrap", "transports": ["cli", "json_exec"] },
"verbs": {
"status": { "path": ["status"], "policy": "read", "help": "Health" },
"send": { "path": ["send"], "policy": "write", "help": "Asks a person first" }
}
}Why it exists
Agents get new abilities all the time, but every tool arrives in its own shape. Nobody can see at a glance what it may do, what needs a person, and how to run it.
An HCP is three plain files: what the capability can do, what it's allowed to do, and how to run it. Any agent host can read them. AUVY installs every capability this way.
- For
- Anyone building agents who wants them to install cleanly.
- Where it stands
- Opening to developers at harnesscontextprotocol.dev.
What happens next
- 1
Open the specification to developers
- 2
Publish the pack rules and a reference
- 3
Index it publicly once the legal details are complete
The company
- Stage
- building
- Legal
- Its own company
- Run by
- AUVY, until it has its own team
- Infrastructure
- Its own EU cluster
- Runs on
- Its own siteAgent runtime
- Site
- harnesscontextprotocol.dev
More built by AUVY
exploringakoloThe structured platform for search funds and ETA teams: map a market, source targets, screen deals and reach the investment decision in one workspace.Full page →