@limits/openclaw 0.0.1 → 0.0.2

package/README.md

@@ -23,6 +23,7 @@
 - [Security](#security-openclaw--limits)
 - [Development](#development)
 - [Migration from limits-enforcer](#migration-from-limits-enforcer)
+- [Troubleshooting](#troubleshooting)
 - [License](#license)
 
 ---
@@ -46,6 +47,7 @@ Then register the plugin with OpenClaw:
 ```bash
 openclaw plugins install ./node_modules/@limits/openclaw
 openclaw plugins enable "@limits/openclaw"
+openclaw gateway restart
 ```
 
 ---
@@ -59,6 +61,12 @@ openclaw plugins enable "@limits/openclaw"
 openclaw limits configure
 ```
 
+If you see **`error: unknown command 'limits'`**, the OpenClaw CLI may not load plugin commands in your environment. Run the configure script directly (from a directory where the package is installed):
+
+```bash
+node node_modules/@limits/openclaw/scripts/configure.js
+```
+
 Or set config manually:
 
 ```json
@@ -282,6 +290,34 @@ If you were using the plugin under the old name **limits-enforcer**, update your
 
 After renaming, reinstall the plugin and enable `"@limits/openclaw"`.
 
+---
+
+## Troubleshooting
+
+- **Config warning "plugin id mismatch (manifest uses '@limits/openclaw', entry hints 'openclaw')"**  
+  Some OpenClaw gateways install scoped packages under `extensions/openclaw` instead of `extensions/@limits/openclaw`. The gateway then infers the plugin id from the folder name (`openclaw`), which does not match the manifest id `@limits/openclaw`, so the plugin may not load and `openclaw limits configure` shows **unknown command 'limits'**.
+
+  **Workaround — install under the scoped path so the gateway matches the config entry:**
+  ```bash
+  # Create the scope directory and install the package there (adjust if you use npm -g or another path)
+  mkdir -p ~/.openclaw/extensions/@limits
+  cp -r ./node_modules/@limits/openclaw ~/.openclaw/extensions/@limits/
+
+  # Tell OpenClaw to load the plugin from that path
+  openclaw plugins install ~/.openclaw/extensions/@limits/openclaw
+  openclaw plugins enable "@limits/openclaw"
+  openclaw gateway restart
+  ```
+  Then run `openclaw limits configure`.
+
+- **`error: unknown command 'limits'`**  
+  The plugin did not load (often due to the id mismatch above). Use the workaround above, or run the configure wizard without the OpenClaw CLI:
+  ```bash
+  node node_modules/@limits/openclaw/scripts/configure.js
+  ```
+  Or from the plugin repo: `npm run configure`.
+
+
 ---
 
 ## License

package/package.json

@@ -1,12 +1,25 @@
 {
   "name": "@limits/openclaw",
-  "version": "0.0.1",
+  "version": "0.0.2",
   "description": "Delegates policy enforcement to the Limits platform before and after every tool call. Optional policy-generator tools for creating/updating policies from natural language.",
-  "keywords": ["openclaw", "limits", "policy", "enforcement", "agent", "guardrails", "ai-safety"],
+  "keywords": [
+    "openclaw",
+    "limits",
+    "policy",
+    "enforcement",
+    "agent",
+    "guardrails",
+    "ai-safety"
+  ],
   "author": "Limits",
   "license": "MIT",
-  "repository": { "type": "git", "url": "git+https://github.com/limitsdev/limits-openclaw.git" },
-  "bugs": { "url": "https://github.com/limitsdev/limits-openclaw/issues" },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/limitsdev/limits-openclaw.git"
+  },
+  "bugs": {
+    "url": "https://github.com/limitsdev/limits-openclaw/issues"
+  },
   "homepage": "https://github.com/limitsdev/limits-openclaw#readme",
   "type": "module",
   "main": "./src/index.ts",
@@ -19,13 +32,22 @@
     "node": ">=18.0.0"
   },
   "openclaw": {
-    "hooks": ["./"],
-    "extensions": ["./"],
-    "events": ["before_tool_call", "after_tool_call"]
+    "id": "@limits/openclaw",
+    "entry": "./src/index.ts",
+    "hooks": [
+      "./"
+    ],
+    "extensions": [
+      "./"
+    ],
+    "events": [
+      "before_tool_call",
+      "after_tool_call"
+    ]
   },
   "devDependencies": {
     "typescript": "^5.0.0",
     "@types/node": "^20.0.0",
     "vitest": "^2.0.0"
   }
-}
+}

package/scripts/configure.js

@@ -3,11 +3,16 @@
  * Interactive configure for @limits/openclaw plugin.
  * Writes to OpenClaw config via: openclaw config set plugins.entries["@limits/openclaw"].config.<key> <value>
  *
- * Run from plugin root: node scripts/configure.js
- * Or: npm run configure
+ * Use this script when "openclaw limits configure" fails with "unknown command 'limits'" or
+ * "plugin id mismatch (entry hints 'openclaw')". That usually means the plugin entry key in
+ * OpenClaw config is wrong — it must be exactly "@limits/openclaw". Fix with:
+ *   openclaw plugins enable "@limits/openclaw"
+ *   openclaw gateway restart
+ * Then "openclaw limits configure" should work. Until then, run this script from the plugin root.
  *
- * Prerequisite: openclaw plugins install <path> and openclaw plugins enable "@limits/openclaw"
+ * Run from plugin root: node scripts/configure.js  or  npm run configure
  * (so plugins.entries["@limits/openclaw"] exists).
+ * Prerequisite: openclaw plugins install <path> and openclaw plugins enable "@limits/openclaw"
  */
 
 import { createInterface } from "node:readline";
@@ -74,8 +79,8 @@ async function main() {
   const rl = createInterface({ input: process.stdin, output: process.stdout });
 
   console.log("\nConfigure @limits/openclaw plugin (writes to OpenClaw config via openclaw config set).");
-  console.log("Prerequisite: openclaw plugins install <path> (or -l to link).");
-  console.log("Tip: After linking, you can also run: openclaw limits configure\n");
+  console.log("Prerequisite: openclaw plugins install <path> and openclaw plugins enable \"@limits/openclaw\".");
+  console.log("If \"openclaw limits configure\" failed with \"unknown command 'limits'\", fix the plugin entry key then run: openclaw gateway restart\n");
 
   const apiToken = await ask(rl, "Organization API key (apiToken) — required for enforce and policy-generator tools", process.env.LIMITS_ENFORCER_API_TOKEN || "");
   const addSkillAnswer = await ask(rl, "Add limits-policy-generator skill to OpenClaw workspace?", "Y");