OpenClaw
Overview
Section titled “Overview”Pulse installs an OpenClaw hook package that forwards OpenClaw events to pulse emit.
All spans are tagged with source: "openclaw".
Quick start
Section titled “Quick start”Requires a running Pulse trace service and a configured Pulse CLI.
- Configure Pulse.
pulse setup --local# or: pulse connect --api-url https://pulse.example.com --api-key pulse_sk_... --project-id my-project- Start the local server if you are using local mode.
pulse up- Connect OpenClaw hooks.
# If already connected to a server:pulse install-hooks
# If not yet connected:pulse connectIf prompted to choose an integration, select OpenClaw.
- Confirm integration health.
pulse statusIntegration behavior
Section titled “Integration behavior”Detection path: ~/.openclaw/
Installed hook path: ~/.openclaw/hooks/pulse-hook/
Pulse installs:
HOOK.md(hook metadata)handler.ts(event handler)
pulse connect only modifies Pulse’s hook directory and does not alter other OpenClaw hooks.
Commands
Section titled “Commands”| Command | Description |
|---|---|
pulse setup --local | Bootstrap a managed local Pulse instance |
pulse up | Start the managed local Pulse server |
pulse connect | Install or refresh OpenClaw hooks, or configure a remote Pulse target when flags are provided |
pulse install-hooks | Install or refresh OpenClaw hooks without changing config |
pulse disconnect | Remove the Pulse-managed OpenClaw hook package |
pulse status | Show config, connectivity, and hook status |
Events captured
Section titled “Events captured”| OpenClaw event | Pulse event | Notes |
|---|---|---|
command:new | session_start | New session created |
command:stop | stop | Session stopped |
command:reset | session_end | reason="reset" |
message:received | user_prompt_submit | Captures prompt text |
message:sent | notification | Agent notification/message |
Span fields
Section titled “Span fields”| Field | Description |
|---|---|
span_id | UUID v4 span identifier |
session_id | OpenClaw session identifier |
timestamp | Event timestamp (ISO 8601) |
source | openclaw |
kind | Event category |
event_type | Concrete event name |
status | success or error |
tool_name | Tool name when applicable |
tool_input | Tool input payload |
tool_response | Tool output payload |
error | Error object for failed events |
metadata | Integration and environment metadata |
Debugging
Section titled “Debugging”For setup validation:
export PULSE_DEBUG=1After running OpenClaw, inspect status and logs:
pulse statusFor CLI-wide troubleshooting, see CLI Reference.