AUVY
DEBook a walkthrough

Protocol started by AUVY building

HCP

An open format for installing agent capabilities. Each capability is a pack of three files that say what it can do, what it may do and how to run it, and one command runs it in any agent.

In one line
“Every capability installs with its rules.”

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" }
  }
}
The format

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 pack is three plain files: what the capability can do, what it's allowed to do, and how to run it. Hosts embed a runtime that reads them, the way they embed a tool client today, and coding agents load one plugin with a single command. AUVY installs every capability this way.

For
Anyone building agents or agent hosts who wants capabilities to install cleanly.
Where it stands
In private preview: specification, SDK, runtime, command line and agent plugin. AUVY and ImTakt run on it.

What runs today

  • hcp lint checks any pack against the three files
  • hcp adopt sets it up in Cursor and other coding agents
  • ImTakt ships its agent commands as an HCP pack
  • AUVY installs its connections and tools as packs

The company

Stage
Private preview
Legal
Inside AUVY GmbH until it becomes its own company
Run by
AUVY, until it has its own team
Infrastructure
Its own fenced part of AUVY's servers in Helsinki, until it moves to its own EU server
Runs on
Agent runtime · Sign-in and secrets

What happens next

  1. 1

    Publish the specification and the docs

  2. 2

    Open the packages beyond the preview

  3. 3

    A second host beside AUVY

More built by AUVY