Knolo CLI 6.2.7: Publish and Install Private Hub Packs
Knolo CLI 6.2.7 adds knolo publish --private and signed-URL installs for owner-only Hub packs, still pinned by SHA-256. Plus what merged on main after.
Knolo is the open-source, local-first Knowledge Image runtime and format: Apache-2.0, published on npm as @knolo/core, with the source in the Knolo core repo on GitHub. On 15 Nov 2026 npm latest for the CLI moved to @knolo/cli@6.2.7. @knolo/core stays at 6.2.3. The new CLI release adds one thing: owner-only packs on Knolo Hub, through knolo publish --private and a matching install path in knolo add and knolo info.
This post covers what changed in Knolo CLI 6.2.7, how to use it, and what landed on main after the release.
What Knolo CLI 6.2.7 adds
Until 6.2.6, every pack the CLI published to Knolo Hub was public, and the CLI refused private Blob hosts. 6.2.7 (PR #179, stamped in #185) adds an opt-in flag:
knolo publish … --privatesendsvisibility: "private"with the upload request and accepts a private Blob host for that pack.- The success text and
--jsonoutput leave out the Blob URL. The CLI printsvisibility privateinstead. knolo infosends your stored token when it matches the registry, and hides a private Blob URL.knolo addasks Hub for a short-lived signed download URL, downloads from it, and pins the SHA-256 of what it received.
Packs published without --private behave exactly as before.
Publishing a private Knolo pack
Install or update the CLI (see installation and the Knolo CLI reference):
npm install -g @knolo/cli@6.2.7
Private packs need a Hub dashboard token. knolo login stores it locally. It does not mint one:
knolo login --token kno_…
knolo publish ./dist/knowledge.knolo \
--slug refund-policy --version 1.2.0 --license Apache-2.0 --private
Installing a private Knolo pack
The install command is the same one you use for public packs:
knolo info acme/refund-policy
knolo add acme/refund-policy@1.2.0
Without a stored token, installing a private pack stops with Private packs require a Hub token. Run knolo login. With one, the CLI calls the pack's download route with your token and expects a signed URL back. It refuses that URL if it is not HTTPS, if it points at a local or private-network host, or if it is just the stored private Blob URL with no signature. After the download, the usual checks run: size, SHA-256 against the manifest, then local Knowledge Image structure. The result is cached by SHA-256 and recorded in knolo.lock.json, so the private pack is pinned by digest like any other (see verification).
Queries still run locally against the mounted image in @knolo/core. Hub stores and lists packs. It does not answer questions.
On Knolo main after 6.2.7
Two more pull requests merged on 15 Nov. Neither bumps a version, so neither is in @knolo/cli@6.2.7 on npm yet:
- #187 adds
knolo research verify <image> [--json] [--cited <file>]... [--require-material]. It re-checks a received research pack with checks that already exist: V5 roots, the stored composition record, a stored Cortex trace when the cited image is supplied, and typed failure codes such asCOMPOSITION_ROOT_MISMATCH. - #188 adds
knolo_kite_evaluateandknolo_kite_verifyto@knolo/tools, registered by the MCP, AI SDK, Mastra and OpenAI Agents adapters. A mount opts in with an emptykiteobject. Mounts that do not opt in keep their current tool list and fail closed on a KITE call. See Knolo tools.
Both are read-only: no model call, no download, and no MCP write tool.
Where to go next with Knolo
Check Knolo versions for the current package matrix, and the Knolo docs on knolo.dev for everything else. For the specification side of moving images between agents, read Knolo open technology at knolo.org.
knolo · cli · release · hub · knowledge-image · npm