When installing this project using OpenClaw, I encountered these two issues with OpenClaw:

[awecsfgvs]

Issue 1: The Guard plugin TypeScript cannot be executed by Node.js
Only .ts files are provided, with no build step and no corresponding .js files.
OpenClaw fails silently on load (no logs, no errors).
It requires compilation via tsc or direct provision of .js files.

Issue 2: The README configuration example does not match configSchema
The README specifies "path": "...",
but the path field does not exist in the plugin schema at all; the defined field is safeclawUrl.
Configuration following the README will not take effect.

[Kirito14IT]

Thanks for the detailed report — both points are helpful.

Re: TypeScript / Node
The extension ships with index.ts as the entry (package.json → "main": "index.ts") and no precompiled JavaScript or documented build step. Without a TypeScript loader in the host, plain Node won’t run that as-is; we’ll address this in an upcoming release (e.g. by shipping built .js, adding a build step, and/or clarifying supported OpenClaw versions and loader behavior). If failures are still silent on load, we’ll also try to surface clearer errors where we control the packaging or docs.

Re: README vs configSchema
configSchema in openclaw.plugin.json is meant for plugin options passed into config (e.g. safeclawUrl, failOpenOnGuardError). A host-level field like path wouldn’t belong in that schema. That said, our manual README snippet is out of sync with the shape our setup flow writes (enabled + config), so we’ll align the README with the manifest and our recommended openclaw.json layout in the same release.

We’ll track fixes in the next version. Thanks again.😄😄😄

[Kirito14IT]

Both issues have been fixed in commit 4cc7a73:

Issue 1 — TypeScript / Node.js:

• Compiled index.ts → index.js so OpenClaw's plain Node.js loader can execute the plugin directly without a TypeScript loader.
• Added tsconfig.json (targeting ES2020 modules) and an npm build script.
• Updated package.json "main" from "index.ts" to "index.js".

Issue 2 — README vs configSchema:

• Updated the openclaw.json snippet in both README.md and README_zh.md to include the enabled flag and a config block with safeclawUrl and failOpenOnGuardError, matching the fields defined in openclaw.plugin.json's configSchema.

The corrected snippet now looks like:

{
  "plugins": {
    "entries": {
      "safeclaw-guard": {
        "path": "~/.openclaw/extensions/safeclaw-guard",
        "enabled": true,
        "config": {
          "safeclawUrl": "http://localhost:6874",
          "failOpenOnGuardError": false
        }
      }
    }
  }
}

Thanks again for the detailed report — it was very helpful!