ContextClaw Plugin Usage
ReviewAudited by ClawScan on May 1, 2026.
Overview
This is a coherent session-management helper, but it asks you to install an external plugin that can read and delete OpenClaw session history.
Before installing, make sure you trust the external ContextClaw plugin. Use dry-run mode first for prune and clean operations, review the listed files, and remember that session logs may include private conversation or task history.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Installing the plugin gives third-party code the ability to run locally and manage OpenClaw session files.
The skill relies on installing an external package/plugin whose code is not included in the artifact set. This is purpose-aligned but should be reviewed as third-party software.
npm install -g @rmruss2022/contextclaw openclaw plugins install @rmruss2022/contextclaw
Install only if you trust the npm package and repository; consider reviewing the plugin source and pinning a known version before use.
A live prune or orphan cleanup could remove session history or context that you may later want.
These documented commands can delete OpenClaw session files. The behavior is aligned with the skill purpose and the instructions emphasize dry runs and approval, but deletion is still a meaningful action.
openclaw contextclaw prune --days 30 --dryRun false openclaw contextclaw clean-orphaned --dryRun false
Run the dry-run commands first, review what would be deleted, and back up important sessions before approving live cleanup.
Session analysis or dashboard views may expose private conversation history or task context to anyone with access to the local machine or displayed output.
OpenClaw session files can contain prior prompts, outputs, tool activity, and other private agent context. Reading them is expected for session analysis, but it is sensitive local history.
Analysis: Parses all `.jsonl` files in `~/.openclaw/agents/main/sessions/`
Use this only on a trusted machine, avoid sharing dashboard/screenshots/output that include sensitive session details, and review the session directory contents if privacy matters.