Skip to content

[Bug]: @openclaw/llama-cpp-provider documented but not published to npm/ClawHub #91971

Closed

Description

@nikosml

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Tried to install package @openclaw/llama-cpp-provider but it cannot be found in npm or clawhub.

Steps to reproduce

Start on any new openclaw installation and run openclaw plugins install clawhub:@openclaw/llama-cpp-provider or openclaw plugins install @openclaw/llama-cpp-provider
The package is not found.

Expected behavior

Package should be found and installed.

Actual behavior

Package is not found in order to be installed:

$ openclaw plugins install @openclaw/llama-cpp-provider
│
◇  

OpenClaw 2026.6.5 (5181e4f) — Your config is valid, your assumptions are not.

Downloading @openclaw/llama-cpp-provider…
Package not found on npm: @openclaw/llama-cpp-provider. See https://docs.openclaw.ai/tools/plugin for installable plugins.
Also not a valid hook pack: Package not found on npm: @openclaw/llama-cpp-provider. See https://docs.openclaw.ai/tools/plugin for installable plugins.
$ openclaw plugins install clawhub:@openclaw/llama-cpp-provider
│
◇  

OpenClaw 2026.6.5 (5181e4f) — Pairing codes exist because even bots believe in consent—and good security hygiene.

Resolving clawhub:@openclaw/llama-cpp-provider…
Package not found on ClawHub.

OpenClaw version

2026.6.5

Operating system

Fedora Workstation 44

Install method

npm

Model

gpt-5.5

Provider / routing chain

OpenAI

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

Local memory embeddings cannot be used.

Additional information

No response

Activity

  1. clawsweeper commented on Jun 10, 2026

    @clawsweeper
    Contributor

    Thanks for the context here. I did a careful shell check against current main, and this is already implemented.

    Close as implemented: the documented llama.cpp provider package is present in current source, resolves from both npm and ClawHub, and first shipped with v2026.6.6 tied to release commit 8c802aa.

    So I’m closing this as already implemented rather than keeping a duplicate issue open.

    Review details

    Best possible solution:

    Keep the v2026.6.6 npm and ClawHub package path, and track broader local-embedding upgrade compatibility in #92808.

    Do we have a high-confidence way to reproduce the issue?

    No, current live registry checks no longer reproduce the reported package-not-found failure: npm and ClawHub both return HTTP 200 for the provider package.

    Is this the best way to solve the issue?

    Yes, publishing and indexing the official external plugin is the best solution for this issue because it keeps the native llama.cpp dependency outside the core OpenClaw package while preserving the documented install command.

    Security review:

    Security review: No PR patch is under review and this issue is not a security report.

    AGENTS.md: found and applied where relevant.

    What I checked:

    • Current docs advertise the installable package: Current main documents llama-cpp as the official external provider for local GGUF embeddings and shows openclaw plugins install @openclaw/llama-cpp-provider. Public docs: docs/plugins/llama-cpp.md. (docs/plugins/llama-cpp.md:11, 37e3e895b020)
    • Current official catalog maps the provider to npm: The official external plugin catalog lists @openclaw/llama-cpp-provider, plugin id llama-cpp, the local embedding provider contract, and npm install metadata. (scripts/lib/official-external-plugin-catalog.json:194, 37e3e895b020)
    • Live npm registry now resolves the package: The npm registry returned HTTP 200 for @openclaw/llama-cpp-provider, with latest set to 2026.6.6 and gitHead set to 8c802aa683510c7f7503597b54c3021733245e59.
    • Live ClawHub now resolves the package: The ClawHub package API returned HTTP 200, latestVersion 2026.6.6, sourceTag v2026.6.6, and sourceCommit 8c802aa683510c7f7503597b54c3021733245e59.
    • Release source package metadata publishes to both registries: At tag v2026.6.6, the provider package is version 2026.6.6 and declares both publishToClawHub and publishToNpm true. (extensions/llama-cpp/package.json:1, 8c802aa68351)
    • Fix provenance: provider extraction created the package path: Merged work in commit 3137110 created the llama-cpp plugin package, docs page, catalog entry, tests, and shrinkwrap. (extensions/llama-cpp/package.json:1, 31371101678d)

    Likely related people:

    • osolmaz: Authored and merged the provider-plugin extraction that created the official llama-cpp package path, docs, catalog entry, and runtime package. (role: feature author and merger; confidence: high; commits: 31371101678d, e825b67100f9; files: extensions/llama-cpp/package.json, docs/plugins/llama-cpp.md, scripts/lib/official-external-plugin-catalog.json)
    • vincentkoc: Authored the v2026.6.6 release commit used by the live npm and ClawHub package metadata, and merged release-gate work for plugin verification. (role: recent release and publish-path contributor; confidence: high; commits: 8c802aa68351, 6fb0c940fa5d, 37e3e895b020; files: extensions/llama-cpp/package.json, .github/workflows/plugin-clawhub-release.yml, .github/workflows/plugin-npm-release.yml)

    Codex review notes: model internal, reasoning high; reviewed against 37e3e895b020; fix evidence: release v2026.6.6, commit 8c802aa68351.

  2. nikosml commented on Jun 11, 2026

    @nikosml
    Author

    It looks like too much time has passed, did the worker complete it's job?

  3. nikosml commented on Jun 11, 2026

    @nikosml
    Author

    The shell commands and the related output at the actual behavior section provide all the info needed to verify or disprove the reported Issue. Can you fix the execution failiure and retry? Note that the steps to reproduce are already clearly described in the first post of the issue.

  4. added
    P2Normal backlog priority with limited blast radius.
    impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.
    issue-rating: 🦀 challenger crabExceptional issue quality: high-confidence current-main reproduction and actionable evidence.
    clawsweeper:current-main-reproClawSweeper found a high-confidence current-main issue reproduction.
    clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.
    clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.
    on Jun 11, 2026
  5. locked as resolved and limited conversation to collaborators on Jun 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.bugSomething isn't workingclawsweeper:current-main-reproClawSweeper found a high-confidence current-main issue reproduction.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🦀 challenger crabExceptional issue quality: high-confidence current-main reproduction and actionable evidence.

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions