Skip to main content

1claw OpenClaw Plugin

The @1claw/openclaw-plugin is an official OpenClaw gateway plugin that adds native 1claw support inside your OpenClaw instance: agent tools, secret redaction, optional secret injection, Shroud TEE routing, key-rotation monitoring, and slash commands. It runs in-process with the gateway (no separate MCP process required for the tools it provides).

Repository: github.com/1clawAI/1claw-openclaw-plugin
npm: @1claw/openclaw-plugin

For a lighter setup that only teaches your agent how to use 1claw (e.g. via an external MCP server), see Using 1claw with OpenClaw (skill-only path).

What the plugin provides​

FeatureDefaultDescription
Native agent toolsOn13 tools: secrets, vaults, policies, sharing, EVM simulate/submit. Prefix: oneclaw_*.
Secret redactionOnScans outbound messages and redacts leaked secret values before they leave the gateway.
Secret injectionOffReplaces {{1claw:path/to/secret}} placeholders with real values at prompt time.
Shroud routingOffWhen the agent has shroud_enabled, routes LLM traffic through Shroud.
Key rotation monitorOffBackground service that warns when secrets expire within 7 days.
Slash commandsOn/oneclaw, /oneclaw-list, /oneclaw-rotate.
Gateway RPC—1claw.status for programmatic health/status.
Bundled skill—1claw skill (skills/1claw/SKILL.md) is auto-discovered by OpenClaw.

All of these are configurable via plugins.entries.1claw.config.features.

Install​

From your OpenClaw environment:

openclaw plugins install @1claw/openclaw-plugin

Restart the OpenClaw Gateway after install. The plugin is enabled by default; configure it under plugins.entries.1claw.config (see Config below).

To install from a local path (e.g. the 1claw submodule or a clone of the plugin repo):

openclaw plugins install -l ./path/to/1claw-openclaw-plugin

Config​

Minimal config: set the agent API key (from enrollment or the dashboard) in the plugin config or via environment variables.

Config file​

In your OpenClaw config (e.g. config.json5 or the file your gateway loads):

{
  plugins: {
    entries: {
      "1claw": {
        enabled: true,
        config: {
          apiKey: "ocv_..."
          // Optional: agentId, vaultId, baseUrl, shroudUrl
          // Optional: features: { tools: true, secretRedaction: true, slashCommands: true, ... }
          // Optional: securityMode: "block" | "surgical" | "log_only"
        }
      }
    }
  }
}

Environment variables​

You can rely on env vars instead of (or as fallback for) the config file:

VariableDescription
ONECLAW_AGENT_API_KEYAgent API key (ocv_...). Required.
ONECLAW_AGENT_IDAgent UUID. Optional; resolved from the key if omitted.
ONECLAW_VAULT_IDDefault vault UUID. Optional; auto-discovered from the token response or first vault.
ONECLAW_BASE_URL1claw API base URL. Default: https://api.1claw.xyz.
ONECLAW_SHROUD_URLShroud proxy URL. Default: https://shroud.1claw.xyz.
ONECLAW_MCP_SANITIZATION_MODESecurity mode for tool input inspection: block, surgical, or log_only. Default: block.

Config file values take precedence over env vars.

Enabling tools for your agent​

When the plugin’s tools feature is on, it registers tools with an oneclaw_ prefix (e.g. oneclaw_list_secrets, oneclaw_get_secret, oneclaw_put_secret). To allow your OpenClaw agent to call them, add the plugin or specific tool names to the agent’s tool allowlist in your config, for example:

agents: {
  list: [{
    id: "main",
    tools: {
      allow: ["1claw"]   // all 1claw plugin tools
      // or list specific tools: ["oneclaw_list_secrets", "oneclaw_get_secret", ...]
    }
  }
}

See OpenClaw plugin docs for the full tool-allowlist syntax.

Slash commands​

When slash commands are enabled, the plugin registers:

CommandDescription
/oneclawConnection status, vault info, token TTL, and which features are on.
/oneclaw-listList secret paths in the vault (metadata only). Optional argument: path prefix.
/oneclaw-rotate <path> <new-value>Rotate a secret at path to a new value.

These run without invoking the AI agent. Require auth by default.

Gateway RPC​

The plugin registers a single RPC method for programmatic checks:

  • 1claw.status — Returns authentication state, agent ID, vault ID, token TTL, vault count, enabled features, and security mode. Useful for health checks or admin tooling.

See OpenClaw Gateway RPC for how to call it from your stack.

Feature toggles​

To turn features on or off, set plugins.entries.1claw.config.features:

{
  plugins: {
    entries: {
      "1claw": {
        enabled: true,
        config: {
          apiKey: "ocv_...",
          features: {
            tools: true,
            secretRedaction: true,
            secretInjection: false,
            shroudRouting: false,
            keyRotationMonitor: false,
            slashCommands: true
          }
        }
      }
    }
  }
}
  • Secret injection and Shroud routing modify prompt or provider behavior; they can also be restricted by the operator via plugins.entries.1claw.hooks.allowPromptInjection: false if needed.
  • Key rotation monitor runs a background job that lists secrets and logs warnings for any expiring within 7 days.

Security and tool input inspection​

The plugin runs the same threat checks as the 1claw MCP server on tool inputs (command injection, encoding obfuscation, social-engineering patterns, etc.). The mode is controlled by plugins.entries.1claw.config.securityMode or ONECLAW_MCP_SANITIZATION_MODE:

  • block (default) — Reject tool calls when high/critical threats are detected.
  • surgical — Normalize Unicode and confusables where possible; still block on critical.
  • log_only — Log threats but do not block.

Plugin vs skill-only​

Plugin (@1claw/openclaw-plugin)Skill only (e.g. clawhub install 1claw)
Installopenclaw plugins install @1claw/openclaw-pluginclawhub install 1claw (or add skill manually)
ToolsNative gateway tools (oneclaw_*) in-processUses 1claw MCP server (stdio or hosted); agent calls MCP tools
Redaction / injectionBuilt-in hooksNot provided by the skill
Shroud routingBuilt-in when agent has shroud_enabledConfigure separately if needed
Slash commands/oneclaw, /oneclaw-list, /oneclaw-rotateNone
Best forFull 1claw integration inside OpenClawSimple “agent knows how to use 1claw” with minimal gateway changes

You can use the plugin and still point the agent at an external MCP server for other tools; the plugin simply adds native 1claw capabilities and optional safety (redaction, Shroud) inside the gateway.

Next steps​