Repository navigation
Closed
Closed
Copy link
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.bugSomething isn't workingSomething isn't workingclawsweeper:current-main-reproClawSweeper found a high-confidence current-main issue reproduction.ClawSweeper found a high-confidence current-main issue reproduction.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.ClawSweeper 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.ClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.This issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🦀 challenger crabExceptional issue quality: high-confidence current-main reproduction and actionable evidence.Exceptional issue quality: high-confidence current-main reproduction and actionable evidence.
Description
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
Metadata
Metadata
Assignees
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.bugSomething isn't workingSomething isn't workingclawsweeper:current-main-reproClawSweeper found a high-confidence current-main issue reproduction.ClawSweeper found a high-confidence current-main issue reproduction.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.ClawSweeper 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.ClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.This issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🦀 challenger crabExceptional issue quality: high-confidence current-main reproduction and actionable evidence.Exceptional issue quality: high-confidence current-main reproduction and actionable evidence.
Type
Fields
Priority
None yet
Activity
clawsweeper commentedon Jun 10, 2026
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:
openclaw plugins install @openclaw/llama-cpp-provider. Public docs:docs/plugins/llama-cpp.md. (docs/plugins/llama-cpp.md:11, 37e3e895b020)@openclaw/llama-cpp-provider, plugin idllama-cpp, thelocalembedding provider contract, and npm install metadata. (scripts/lib/official-external-plugin-catalog.json:194, 37e3e895b020)@openclaw/llama-cpp-provider, withlatestset to2026.6.6andgitHeadset to8c802aa683510c7f7503597b54c3021733245e59.latestVersion2026.6.6,sourceTagv2026.6.6, andsourceCommit8c802aa683510c7f7503597b54c3021733245e59.2026.6.6and declares bothpublishToClawHubandpublishToNpmtrue. (extensions/llama-cpp/package.json:1, 8c802aa68351)extensions/llama-cpp/package.json:1, 31371101678d)Likely related people:
extensions/llama-cpp/package.json,docs/plugins/llama-cpp.md,scripts/lib/official-external-plugin-catalog.json)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.
nikosml commentedon Jun 11, 2026
It looks like too much time has passed, did the worker complete it's job?
nikosml commentedon Jun 11, 2026
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.