Plugin Setup

Installation

npm install @karmaniverous/jeeves-meta-openclaw
npx @karmaniverous/jeeves-meta-openclaw install
Copy

Prerequisites

The plugin requires the jeeves-meta service to be running. The plugin itself contains no synthesis logic — it delegates all operations via HTTP.

Configuration

The plugin resolves settings via a three-step fallback chain: plugin config → environment variable → default.

Plugin Config

In your OpenClaw configuration (openclaw.json or equivalent):

{
  "plugins": {
    "entries": {
      "jeeves-meta-openclaw": {
        "enabled": true,
        "config": {
          "apiUrl": "http://127.0.0.1:1938",
          "configRoot": "j:/config"
        }
      }
    }
  }
}
Copy

The configRoot tells @karmaniverous/jeeves core where to find the platform config directory. Core derives {configRoot}/jeeves-meta/ for component-specific configuration.

Lifecycle

On gateway startup:

1. Plugin calls init({ workspacePath, configRoot }) from @karmaniverous/jeeves
2. Registers 8 tools (meta_list, meta_detail, meta_trigger, meta_preview, meta_seed, meta_unlock, meta_config, meta_queue)
3. Creates a ComponentWriter via createComponentWriter() with a 73-second prime refresh interval
4. ComponentWriter manages TOOLS.md section writing (section ordering, version stamps, locking) and platform content maintenance (SOUL.md/AGENTS.md)

Each refresh cycle:

• Queries the meta service (GET /status and GET /metas) via MetaServiceClient
• Generates the ## Meta section content (entity stats, dependency health, tool listing)
• Core writes the section to TOOLS.md with managed markers and ordering

The plugin does not register virtual rules — that is the service's responsibility via the RuleRegistrar.