ocmemog Installer

One-click installer and setup skill for ocmemog, the OpenClaw durable memory plugin and sidecar. Use when a user asks to install ocmemog, set up ocmemog, add...

Security Scan

The skill is an installer that clones a GitHub repo, sets up a Python venv, installs requirements, starts a local sidecar, and (optionally) patches OpenClaw config — the requested actions line up with its stated purpose.

Purpose & Capability

The name/description (ocmemog installer) match the included script and SKILL.md: the script clones the indicated GitHub repo, creates a venv, installs Python requirements, starts a sidecar, and attempts to install/enable the plugin via the openclaw CLI. No unrelated credentials, binaries, or config paths are requested.

Instruction Scope

SKILL.md instructs the agent to prefer the bundled install script and to patch OpenClaw config automatically if a Gateway/config patch tool is available. Automatic config modification is within the installer’s scope, but it grants the skill the ability to change OpenClaw configuration without explicit step-by-step user edits — the user should be aware and approve such changes.

Install Mechanism

There is no external install spec; the bundled bash script clones https://github.com/simbimbo/ocmemog.git, creates a venv and runs pip install -r requirements.txt, and executes repository-provided scripts to launch the sidecar. Running arbitrary code pulled from an external GitHub repo and pip installing its dependencies is expected for an installer but carries real risk: the repo's scripts (ocmemog-sidecar.sh / ocmemog-install.sh and packages in requirements.txt) are executed and were not included for review here.

Credentials

The skill does not request credentials or environment variables. The script uses $HOME for a default path and requires git and python3 — reasonable and proportionate for this purpose.

Persistence & Privilege

always:false and agent invocation defaults are normal. The installer creates files (repo, venv, logs) and launches a background sidecar bound to 127.0.0.1; SKILL.md also asks to patch OpenClaw config automatically when tooling is available. These behaviors are appropriate for an installer but mean the skill can change local state and OpenClaw configuration if allowed.

Assessment

This skill appears to do what it claims, but it will clone and execute code from an external GitHub repo and pip-install its requirements — which can run arbitrary code. Before installing: (1) inspect the repository (especially scripts/ocmemog-sidecar.sh, scripts/ocmemog-install.sh, and requirements.txt) to confirm you trust its contents; (2) consider running the installer in an isolated/test environment or container; (3) back up your OpenClaw configuration before allowing automatic patches; (4) ensure the sidecar remains bound to 127.0.0.1 (as recommended) to limit network exposure; (5) if you don’t want automatic config changes, run the script manually and apply the config snippet provided in SKILL.md yourself.

Install ocmemog from the canonical GitHub repo and configure OpenClaw to use it as the memory plugin.

Canonical source

• Repo: https://github.com/simbimbo/ocmemog.git
• Plugin id: memory-ocmemog
• Default sidecar endpoint: http://127.0.0.1:17890
• Primary bundled installer: scripts/install-ocmemog.sh

Preferred workflow

1. Run the bundled installer script first.
   • Default: scripts/install-ocmemog.sh
   • Optional target dir: scripts/install-ocmemog.sh /custom/path/ocmemog
2. Let the script clone/update the repo, build the venv, install Python requirements, start the sidecar, and install/enable the plugin when the openclaw CLI is available.
3. Patch OpenClaw config so the memory slot points at memory-ocmemog and the plugin entry uses http://127.0.0.1:17890.
4. Validate /healthz and a memory search/get smoke test.

Agent behavior

• Default to the script-driven flow instead of narrating manual steps.
• Treat user phrases like "install ocmemog", "set up durable memory", "improve OpenClaw memory", and "add long-term memory" as direct triggers.
• If config patch tooling is available, patch config automatically instead of asking the user to hand-edit files.
• After install, verify the sidecar and plugin state before claiming success.
• If the environment blocks automatic config changes, provide the exact config snippet and the shortest possible manual next step.

Config patching

If the Gateway tool is available, prefer patching config automatically instead of asking the user to hand-edit config.

Target config shape:

plugins:
  load:
    paths:
      - /path/to/ocmemog
  slots:
    memory: memory-ocmemog
  entries:
    memory-ocmemog:
      enabled: true
      config:
        endpoint: http://127.0.0.1:17890
        timeoutMs: 10000

Rules:

• Use the actual install path chosen by the script.
• Preserve existing unrelated plugin configuration.
• If config patch tooling is unavailable, provide the exact patch/snippet the user should apply.

Validation checklist

• Sidecar responds on /healthz
• openclaw plugins shows memory-ocmemog installed/enabled when CLI access exists
• Memory search/get calls return data instead of connection errors
• If packaging/publish questions arise, remember this skill is a ClawHub wrapper for the plugin repo, not the plugin package itself

Troubleshooting

• If clawhub users expect a direct plugin package, explain that this skill installs/configures the real plugin repo.
• If macOS LaunchAgents fail, rerun the installer and inspect launchctl print gui/$UID/com.openclaw.ocmemog.sidecar.
• If the sidecar health check fails, inspect repo logs / terminal output before changing config.
• Keep the sidecar bound to 127.0.0.1 unless explicit auth/network hardening is added.

Notes

• Prefer the script-driven flow over manual step-by-step setup.
• Prefer publishing the plugin itself through GitHub/npm/plugin-install flows; use this skill as the ClawHub-distributed installer/config guide.