ClawHub

Ollama Memory Embeddings

v1.0.4

Configure OpenClaw memory search to use Ollama as the embeddings server (OpenAI-compatible /v1/embeddings) instead of the built-in node-llama-cpp local GGUF loading. Includes interactive model selection and optional import of an existing local embedding GGUF into Ollama.

⭐ 5· 1.6k·6 current·7 all-time
by@vidarbrekke
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
ℹ
Purpose & Capability
The scripts and SKILL.md are coherent with the stated purpose (switch OpenClaw memory embeddings to Ollama). They read/write the OpenClaw config, verify Ollama on localhost, optionally import local GGUFs, and offer restart/watchdog behavior. One inconsistency: the registry metadata reports "required binaries: none" / "instruction-only", but the packaged scripts clearly require node, curl, and the ollama CLI (and optionally openclaw, launchctl/systemctl). This is likely a metadata omission rather than malicious behavior, but you should expect those tools to be present.
✓
Instruction Scope
Runtime instructions and scripts stay within the stated scope: they read/write ~/.openclaw/openclaw.json (and backups), scan a small set of local cache directories for GGUFs, call the local Ollama HTTP endpoint (127.0.0.1:11434), and may run 'ollama create' to import a model. The default behavior is conservative (no GGUF import unless opted-in, no gateway restart unless requested). Nothing in SKILL.md or the scripts instructs reading or transmitting unrelated secrets or contacting external network hosts.
✓
Install Mechanism
There is no network-based installer: the repository includes install, verify, enforce, watchdog, audit, and uninstall scripts plus Node helper. No downloads from external URLs or package registry pulls are performed by the scripts. They assume required local tools are installed. This is low-risk compared to fetching and executing arbitrary remote archives.
✓
Credentials
The skill requests no environment variables or credentials from the registry. The code sets the OpenClaw memorySearch.remote.apiKey to a non-secret sentinel value (default 'ollama') as required by the client, and the enforcement tools treat apiKey presence (non-empty) as sufficient. No sensitive system credentials or unrelated tokens are requested or transmitted. The scripts do read local config and model cache directories, which is appropriate for the task.
✓
Persistence & Privilege
The skill does not request always:true and is not force-included. Persistence is optional and explicit: watchdog.sh can install a user-level LaunchAgents plist on macOS (or you can run the watchdog via cron/systemd on Linux). The installer writes files under the user's home (~/.openclaw and ~/Library/LaunchAgents) and creates logs there; it does not modify other skills or system-wide settings beyond user-level launchd/systemd guidance. Restarting the OpenClaw gateway is optional and requires either the openclaw CLI (if present) or manual action.
Assessment
This package looks coherent with its description, but a few practical things to check before installing: - Prerequisites: ensure node, curl, and the ollama CLI are installed and trusted on your machine (the repository metadata incorrectly lists no required binaries). openclaw is optional but needed if you want automatic gateway restart. - Review & dry-run: run install.sh --dry-run to preview changes; verify.sh to test the local embeddings endpoint. - Files touched: the installer will read/write ~/.openclaw/openclaw.json (backups are made before writes) and may create ~/Library/LaunchAgents/*.plist and logs under ~/.openclaw/logs if you opt into the watchdog—these are user-level files. - GGUF import: scanning and importing local GGUFs is opt-in. Do not use --import-local-gguf yes unless you trust the GGUF files on disk. - Persistence: watchdog installation is explicit; uninstall.sh and watchdog.sh --uninstall-launchd provide ways to revert. - Safety: do not run these scripts as root. Inspect install.sh, enforce.sh, and watchdog.sh yourself (they are included). If you want extra assurance, run them in a controlled environment or container first. If you want, I can point out the exact commands the scripts will run in a dry-run or summarize the lines that write your OpenClaw config and the launchd plist.

Like a lobster shell, security has layers — review code before you run it.

latestvk978kjffya29gry7ppz0s9wx0d81326x

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments