Proactive session capacity monitoring and management for OpenClaw. Prevents context window lockups by warning at configurable thresholds (75%, 85%, 90%, 95%), automatically backing up sessions before resets, and managing session resumption prompts. Use when working on long-running projects, managing multiple conversation channels (Discord, Telegram, webchat), or preventing lost work from full context windows. Includes CLI tools for capacity checks, cross-session dashboards, archive management, and session resumption. Supports any model or provider.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
tide-watch
description
Proactive session capacity monitoring and management for OpenClaw. Prevents context window lockups by warning at configurable thresholds (75%, 85%, 90%, 95%), automatically backing up sessions before resets, and managing session resumption prompts. Use when working on long-running projects, managing multiple conversation channels (Discord, Telegram, webchat), or preventing lost work from full context windows. Includes CLI tools for capacity checks, cross-session dashboards, archive management, and session resumption. Supports any model or provider.
{"openclaw":{"emoji":"🌊","version":"1.0.3","disable-model-invocation":false,"capabilities":["session-monitoring","capacity-warnings","session-backup","session-restoration","file-operations-local"],"requires":{"bins":["node","npm"],"config":["~/.openclaw/agents/main/sessions/"],"engines":{"node":">=14.0.0"}},"install":[{"type":"directives","description":"AGENTS.md/HEARTBEAT.md directives for automatic monitoring (recommended)","requires":[],"code-execution":false,"command":null,"files-modified":["~/clawd/AGENTS.md","~/clawd/HEARTBEAT.md"]},{"type":"npm","description":"Optional Node.js CLI for manual capacity checks and management","directory":".","command":"npm link","requires":["node>=14.0.0","npm"],"code-execution":true,"dependencies":{"dev":["jest@^30.2.0"],"runtime":[]},"binaries":[{"name":"tide-watch","path":"./bin/tide-watch"}],"files-installed":["bin/tide-watch","lib/capacity.js","lib/resumption.js"]}],"credentials":{"required":false,"types":[],"notes":"No external credentials required. Operates on local OpenClaw session files only."}}}
Tide Watch 🌊
Proactive session capacity monitoring for OpenClaw.
⚠️ Security & Architecture Notice
Tide Watch is a HYBRID SKILL with two operational modes:
Mode 1: Directives-Only (Recommended for Most Users)
Description: AGENTS.md and HEARTBEAT.md directives only Code Execution:NONE - Pure instructions, no executable code File Access: Reads OpenClaw session files via agent's built-in tools Installation: Copy template directives to workspace config files Security: Lowest risk - no code installation required
What it does:
✅ Monitors session capacity via session_status tool
✅ Warns at thresholds (75%, 85%, 90%, 95%)
✅ Auto-loads resumption prompts on session reset
✅ All operations through OpenClaw's native tools
Mode 2: CLI Tools (Optional)
Description: Node.js command-line tools for manual management Code Execution:YES - Executable JavaScript code File Access: Direct read/write to ~/.openclaw/agents/main/sessions/ Installation:git clone + npm link (requires Node.js) Security: Moderate risk - requires code inspection before install
What it does:
CLI commands: tide-watch status, tide-watch dashboard, etc.
Manual capacity checks
Session archive management
Resumption prompt editing (⚠️ see CVE-2026-001 below)
🚨 CRITICAL SECURITY NOTICE: CVE-2026-001
Vulnerability: Shell injection in editResumePrompt function Affected Version: v1.0.0 ONLY Current Version: v1.0.1 (PATCHED) Severity: HIGH (CVSS 7.8) Status: ✅ FIXED
Summary: v1.0.0 contained a shell injection vulnerability in the CLI's resume-prompt edit command. An attacker who could control the --session parameter could execute arbitrary commands. This has been fixed in v1.0.1 by replacing with .
execSync
spawnSync
If you installed v1.0.0:Update immediately to v1.0.1.
Network Activity:NONE - All operations are local filesystem only.
Runtime Requirements
Mode 1 (Directives-Only):
Node.js: Not required
npm: Not required
Dependencies: None
Binary: None
Installation: Copy templates to workspace config files
Mode 2 (CLI Tools - Optional):
Node.js: v14.0.0 or later required
npm: Any recent version
Dependencies:
Development: jest@^30.2.0 (for testing only)
Runtime: None (zero production dependencies)
Binary:tide-watch (installed globally via npm link)
Installation:git clone + npm link
Why zero runtime dependencies?
Uses only Node.js built-in modules (fs, path, child_process)
No external API clients
No network libraries
Minimal attack surface
Recommendation
Most users should use Directives-Only Mode. This provides automatic capacity monitoring without installing any code. Only install CLI tools if you specifically need manual capacity management features.
What It Does
Monitors your OpenClaw session context windows and warns you before they overflow:
🟡 75% — Heads up, consider wrapping up soon
🟠 85% — Recommend finishing current task and resetting
🔴 90% — Session will lock soon, ready to reset
🚨 95% — Critical! Save to memory NOW
Installation
Step 1: Add Monitoring Directive to AGENTS.md
Copy the directive template from AGENTS.md.template and add it to your workspace AGENTS.md file:
# From your workspace root (~/clawd or similar)cat skills/tide-watch/AGENTS.md.template >> AGENTS.md
Or manually add the monitoring section from the template.
This tells me (your agent) what to look for and when to warn you.
Step 2: Add Heartbeat Task to HEARTBEAT.md
Copy the heartbeat template from HEARTBEAT.md.template and add it to your workspace HEARTBEAT.md file:
# From your workspace root (~/clawd or similar)cat skills/tide-watch/HEARTBEAT.md.template >> HEARTBEAT.md
Or manually add the Tide Watch heartbeat section from the template.
This tells me to check capacity automatically on a schedule.
Step 3: Configure Settings (Optional)
Default settings work for most users, but you can customize in your AGENTS.md:
