01
npm package
Install the AgentGuard runtime in the Node environment used for the OpenClaw deployment.
Connect AgentGuard To OpenClaw
Install the AgentGuard runtime through npm or install.sh, then bind it to OpenClaw through the current product-supported onboarding flow.
The public installation commands do not define the exact OpenClaw binding command. The production page must use the workflow confirmed by the product team.
OpenClawRuntime connection required
Local RuntimeIntegration method
AgentGuardSecurity service
ConnectReviewEvidence
Connectionnpm / install.sh
Service behaviorRuntime connection required
Delivery modelLocal AgentGuard runtime
Current statusBinding needs confirmation
01 / CONNECTION
How AgentGuard Connects
See which supported AgentGuard forms apply to this target and what connection work still remains.
02
install.sh
Bootstrap the local runtime and configuration on macOS or Linux with the current public installer.
03
Service binding
Connect OpenClaw to the installed AgentGuard service using the approved onboarding flow.
04
Coverage boundary
Separate successful runtime installation from verified OpenClaw requests and security outcomes.
02 / CONNECT
Connect, Configure, Verify
Commands match the current public setup paths. Production documentation should add approved versions, prerequisites, rollback steps, and source verification.
OpenClaw · current verified runtime commands
# Option 1: install through npm
npm install -g @goplus/agentguard
# Option 2: bootstrap on macOS / Linux
curl -fsSL https://agentguard.gopluslabs.io/install.sh | bash
# Verify the local runtime
agentguard status
agentguard doctor
# Exact OpenClaw binding command pending product confirmationInstall AgentGuard
Choose npm for package-managed setup or install.sh for the guided macOS and Linux bootstrap.
Complete OpenClaw binding
Use the exact OpenClaw activation or connection procedure approved by the product team.
Verify the workflow
Run a controlled OpenClaw security request and confirm the runtime result and evidence.
03 / SURFACE
Integration Surface
These labels separate installation, service access, workflow connection, and runtime behavior.
npm packageRuntime install
install.shRuntime bootstrap
OpenClaw bindingConfirmation required
SkillNot claimed here
MCP ServerNot claimed here
VerificationRun in OpenClaw
04 / EVIDENCE
Verify The Connection And Result
Check the connection, runtime, returned result, and coverage boundary before treating setup as verified.
The AgentGuard runtime and configuration are present in the OpenClaw environment.
OpenClaw reaches AgentGuard through the approved product onboarding path.
A controlled OpenClaw request produces the expected AgentGuard output.
Installed runtime without a verified OpenClaw connection is not an active integration.
05 / LIMITS
Known Limitations Stay Visible
These statements prevent a documented integration from being read as universal protection.
The final OpenClaw connection command is not established by the four public homepage setup commands.
npm and install.sh describe runtime delivery and should not be expanded into unverified OpenClaw hooks or plugins.
install.sh targets macOS and Linux; npm requires a supported Node environment.
Publish supported OpenClaw versions, activation state, and a controlled verification procedure.
06 / FAQ
Integration Questions
Keep answers aligned with current product behavior and the last verified integration version.
Which OpenClaw methods are shown?+
This prototype limits public commands to npm and install.sh for the AgentGuard runtime.
Why is the binding marked pending?+
The public setup commands do not specify the final OpenClaw connection step.
When is the integration verified?+
After OpenClaw reaches the installed AgentGuard runtime and a controlled request returns the expected evidence.
OpenClaw integration
Verify The Integration Before Production
Run the documented setup, confirm AgentGuard is reachable from OpenClaw, and test the behavior expected from this connection.