Knolo Exchange 0.1.0: Transfer a Verified Knowledge Image Between Agents
Knolo Exchange 0.1.0, core 6.2.2 and CLI 6.2.4 let one agent hand a verified V5 Knowledge Image to another, with signed offers, receipts and adopt off by default.
Knolo is the open-source, local-first Knowledge Image runtime and format: Apache-2.0, published on npm as @knolo/core. On 12 November 2026 Knolo shipped @knolo/exchange 0.1.0, together with @knolo/core 6.2.2 and @knolo/cli 6.2.4. With these releases, one agent can hand a verified V5 Knowledge Image straight to another agent, and Knolo Hub is not on that byte path.
This post walks through what the new knolo exchange commands do, and what they deliberately leave alone.
What Knolo Exchange 0.1.0 adds
The change landed in the Knolo core repository on GitHub as two merged pull requests: one that adds transfer of a verified V5 image between agents, and one that releases the packages.
@knolo/core6.2.2 carries the exchange and capsule helpers. Core verifies the signed offer and the V5 image.@knolo/exchange0.1.0 is the host transport. Its own description is short: "Core verifies the image. This package moves the bytes." It requires@knolo/core^6.2.2.@knolo/cli6.2.4 adds theknolo exchangecommands.
The wire contract is KIP-0028, the Exchange Offer V1 specification: a signed offer for one complete V5 Knowledge Image, addressed to one named recipient, followed by an accept or reject decision and a receipt.
Install the Knolo packages
npm install @knolo/core@6.2.2 @knolo/exchange@0.1.0
npm install -g @knolo/cli@6.2.4
If you are new to the CLI, the Knolo installation guide and the Knolo CLI reference cover setup.
Knolo exchange commands, step by step
knolo exchange serve --config exchange.json
knolo exchange offer ./knowledge.knolo --to agent-b --config exchange.json
knolo exchange pull <offer-id> --from agent-a --config exchange.json
knolo exchange export ./knowledge.knolo --to agent-b --out ./handoff --config exchange.json
knolo exchange import ./handoff --config exchange.json
knolo exchange adopt <receipt-id> --store <file> --home <dir> --config exchange.json
knolo exchange inspect <receipt-id> --home <dir> [--config exchange.json]
- serve binds the address in
listenand writesendpoint.jsonin the store directory. - offer copies the image into that store and registers the signed offer on the local server.
- pull downloads from the peer URL, checks the SHA-256 and the state root, then writes the image to
~/.knolo/cache/sha256/<sha256>.knoloand a receipt under~/.knolo/exchange/receipts/. - export and import do the same handoff through a directory (
offer.cborplus<sha256>.knolo). Neither command opens a socket, which suits air-gapped or file-based handoffs. - adopt reads the cached image named by a recipient receipt. It opens a new store, or fast-forwards a store that is directly behind that image. If the store is equal it stays unchanged; if it is ahead or has diverged, the file is left unchanged and the command fails.
- discover prints a publisher's public peer endpoints and does not download a pack.
Knolo receive policy: adopt stays off by default
Receive policy lives in exchange.json. An offer outside that policy is refused before the image bytes are kept. Shipped configs keep adopt at deny, and knolo exchange adopt only runs when that field is allow. Pull and import never adopt the image into a store, never write knolo.lock.json, and never call Knolo Hub.
Two practical details from the release:
- A partial transfer resumes across processes.
- A warm cache skips the blob download. A later pull of a different offer for a digest already in the cache still checks the signature, recipient, expiry and receive policy, then hashes the cached file before writing a receipt.
An Agent2Agent card can also name an offer, but the bytes still move through pull or import.
What a verified Knolo transfer means
Knolo verification is structural. A verified transfer means the bytes match the SHA-256, mount as a V5 image, and produce the stateRoot the signed offer declared. It does not mean the knowledge inside is true. The Knolo verification docs explain that narrow question in more detail, and the Knolo agents boundary page covers what the host still owns.
Where to go next
- Read the Knolo developer docs on knolo.dev to pack and pin your first image.
- Read the open specifications and KIPs on Knolo open technology at knolo.org.
- Browse the source, KIP-0028 and the exchange conformance cases in the Knolo core GitHub repo.
Knolo is built by Hive AI and released under the Apache-2.0 license.
knolo · exchange · release · cli · knowledge-image