Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Optimization suite for OpenClaw agents to prevent token leaks and context bloat. Use when an agent needs to implement background task isolation (Cron) or a Reset & Summarize workflow (RAG).
Optimization suite for OpenClaw agents to prevent token leaks and context bloat. Use when an agent needs to implement background task isolation (Cron) or a Reset & Summarize workflow (RAG).
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
This skill provides the procedural knowledge to keep your OpenClaw instance lean and efficient.
ProblemSolutionBackground tasks bloating contextCron isolation (sessionTarget: "isolated")Reading entire history every turnLocal RAG with memory_searchContext exceeds 100k tokensReset & Summarize protocolFinding old conversationsSession transcript indexing
To prevent background tasks from bloating your main conversation context, always isolate them.
Locate your openclaw.json config. In the cron.jobs array, set sessionTarget: "isolated" for any task that doesn't need to be part of the main chat history. Use the message tool within the task's payload if human intervention is required.
{ "cron": { "jobs": [ { "name": "Background Check", "schedule": { "kind": "every", "everyMs": 1800000 }, "sessionTarget": "isolated", "payload": { "kind": "agentTurn", "message": "Check for updates. If found, use message tool to notify user.", "deliver": true } } ] } }
sessionTarget: "isolated" runs the task in a separate, transient session Use deliver: true to send results back to the main channel Isolated sessions don't pollute your main context with heartbeat/check history
When your context usage (visible via π session_status) exceeds 100k tokens, perform a manual consolidation.
Check Context: Run π session_status to see current token usage Scan History: Review the current session for new facts, preferences, or project updates Update MEMORY.md: Append these new facts to your long-term memory file Daily Log: Ensure memory/YYYY-MM-DD.md is up to date with today's events Restart: Run openclaw gateway restart to clear the active history
Context > 100k tokens Session running for several days Noticeably slower responses User explicitly requests a "fresh start"
For efficient recall without token burn, configure local embeddings.
{ "memorySearch": { "embedding": { "provider": "local", "model": "hf:second-state/All-MiniLM-L6-v2-Embedding-GGUF" }, "store": "sqlite", "paths": ["memory/", "MEMORY.md"], "extraPaths": [] } }
Use memory_search to retrieve context from your logs instead of loading everything: memory_search(query="what did we decide about the API design") The tool returns relevant snippets with file paths and line numbers. Use memory_get to pull specific sections.
Index your session transcripts (.jsonl files) for searchable conversation history.
OpenClaw stores session transcripts in ~/.openclaw/sessions/. These can be indexed for semantic search, allowing you to find old conversations without loading them into context.
Add transcript paths to memorySearch.extraPaths: { "memorySearch": { "extraPaths": [ "~/.openclaw/sessions/*.jsonl" ] } }
Index selectively (recent sessions, important conversations) Use date-based filtering to limit search scope Archive old transcripts to cold storage after indexing
Combine semantic search with keyword matching for more accurate retrieval.
Search TypeStrengthsWeaknessesVector (semantic)Finds conceptually similar contentMay miss exact termsBM25 (keyword)Finds exact matchesMisses synonyms/paraphrasesHybridBest of both worldsSlightly more compute
When memory_search returns low-confidence results: Try the search with different phrasing (semantic variation) Search for exact keywords you remember (BM25 behavior) Combine results manually if needed
OpenClaw's RAG system may support native hybrid search in future versions. For now, run multiple queries when precision matters.
Check cron jobs: Are they isolated? Check heartbeat frequency: Too frequent = more tokens Are you loading large files unnecessarily?
Verify memorySearch is configured in openclaw.json Check that the embedding model is downloaded Ensure memory files exist and have content
The restart clears the session history, but: System prompt is always loaded Workspace files (MEMORY.md, etc.) are injected fresh This is by design for continuity
PΓ©pΓ¨re (shAde) β Original concept and documentation Zayan (ClΓ©ment) β Implementation and testing Built for the OpenClaw community. π¦¦πΈ
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.