Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Self-improving AI memory system with intelligent context injection and adaptive learning
Self-improving AI memory system with intelligent context injection and adaptive learning
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.
Rune gives your OpenClaw agent persistent, intelligent memory that gets better over time. No more burning tokens on static context files or forgetting important information between sessions.
Dynamic Context Injection: AI selects only relevant facts for each conversation Access Pattern Learning: Frequently used facts get prioritized Forgetting Curves: Unused facts naturally fade like human memory Memory Consolidation: Similar facts get merged, verbose ones compressed
Interaction Style Detection: Learns if you prefer brainstorm vs deep-work vs debug modes Behavioral Pattern Analysis: Tracks your work patterns and preferences over time Proactive Memory: Volunteers relevant context unprompted ("last time you worked on this...")
Smart Task Recommendations: "What should I work on next?" with priority scoring Blocker Detection: Identifies stuck projects that need intervention Project Health Scoring: 0.0-1.0 health scores based on activity and progress
Priority Classification: Critical/High/Medium/Low/FYI with context analysis Smart Timing: Respects quiet hours, batches low-priority updates Channel Routing: DM for urgent, Discord for projects, digest for FYI
Pattern Detection: "Forgot to use X skill 3 times" β automatic escalation Performance Tracking: Measurable improvement over time Skill Usage Analysis: Which skills you use vs neglect
Rune is the OpenClaw skill name. rune is the CLI tool name. Think of Rune as the "skill package" and rune as the "command-line interface" - like how the git skill package provides the git CLI. Skill name: rune (what you install via ClawHub) CLI command: rune (what you run in terminal) Repository: https://github.com/TheBobLoblaw/rune
β οΈ What This Installation Does: The Rune skill installation will: Create directories: ~/.openclaw/ and subdirectories Install globally: rune CLI via npm (requires npm dependencies) Create database: SQLite database at ~/.openclaw/memory.db Modify files: Appends integration lines to existing ~/.openclaw/workspace/HEARTBEAT.md Add session hooks: Automatic memory integration for OpenClaw sessions Before installing: Back up HEARTBEAT.md if it contains important data Review package.json dependencies if security is critical Consider using local models (Ollama) instead of cloud APIs for privacy
# Via ClawHub (recommended) clawhub install rune # Manual installation git clone https://github.com/TheBobLoblaw/rune cd rune npm install --production npm install -g .
# Initialize memory system rune stats # Add your first fact rune add person cory.name "Cory - my human user" # Generate context for a conversation rune context "Let's work on the website" # Get task recommendations rune next-task # Weekly self-review rune self-review --days 7
rune add <category> <key> <value> - Store a fact rune search <query> - Find facts rune recall <topic> - Smart multi-source recall rune inject - Generate context file for agent
rune context <message> - Dynamic context for message rune score <message> - Relevance scoring rune proactive <message> - Volunteer relevant context rune session-style <message> - Detect interaction style
rune project-state <name> - Track project phases/blockers rune next-task - Smart task picker rune stuck-projects - Find blocked work
rune temporal "last Tuesday" - Time-based queries rune consolidate - Memory optimization rune forget - Apply forgetting curves rune pattern-analysis - Detect behavioral patterns
Add to your HEARTBEAT.md: # Memory maintenance rune expire && rune inject --output ~/.openclaw/workspace/FACTS.md # Proactive work selection NEXT_TASK=$(rune next-task --json) if [[ "$NEXT_TASK" != "null" ]]; then # Work on the recommended task fi
The skill automatically provides secure session hooks via OpenClaw integrations. For manual usage, use the secure session handler: # Secure session hooks (input sanitized automatically) ./rune-session-handler.sh start # Loads dynamic context safely ./rune-session-handler.sh end # Tracks session style safely # Direct usage (SECURE - input is sanitized): SAFE_MESSAGE=$(echo "$MESSAGE" | head -c 200 | tr -d '`$(){}[]|;&<>' | sed 's/[^a-zA-Z0-9 ._-]//g') rune recall "$SAFE_MESSAGE" --limit 10 β οΈ Security Note: Never pass unsanitized user input directly to shell commands. Always use the provided session handler or sanitize input manually.
SQLite Database: All memory stored in ~/.openclaw/memory.db Local LLM Integration: Ollama for relevance scoring and extraction Cloud API Support: Anthropic, OpenAI for advanced reasoning Local-First Design: Works completely offline with Ollama (cloud APIs optional for advanced features)
person: Information about people (names, roles, preferences) project: Project status, phases, decisions tool: How to use tools and their quirks lesson: Mistakes to avoid, best practices decision: Why certain choices were made preference: User likes/dislikes, settings environment: System configs, non-sensitive settings (β οΈ NEVER store credentials!)
What Rune Stores: Facts you explicitly add via rune add Session interaction patterns for learning (conversation style, not content) Project states and task recommendations What Rune Does NOT Store (by default): Full conversation transcripts (unless you run extract manually) API keys or credentials (use environment variables instead) Sensitive personal information (unless you explicitly add it)
NPM Dependencies: Installation fetches dependencies from npm registry at install time Review package.json for dependencies if security is critical Global npm install runs lifecycle scripts (standard npm behavior) Consider installing in isolated environment (container/VM) for high-security use Session Security: Fixed CVE-2026-0001: Input sanitization prevents shell injection All user input sanitized before shell execution Session handler validates and limits input length
Optional: Rune can use OpenAI/Anthropic APIs for fact extraction and scoring Local-first: Works completely offline with Ollama (recommended for privacy) Your choice: Configure which engines to use in your setup
Use local models (Ollama) for maximum privacy Avoid cloud APIs if processing sensitive information Review stored facts periodically with rune search Never store credentials in memory - use environment variables Privacy Best Practices: Never run rune add with sensitive data (passwords, API keys, personal info) Use rune extract carefully - review files before extracting facts Configure Ollama for local-only operation if you want zero cloud usage Review your ~/.openclaw/workspace/FACTS.md periodically Installation Changes: Adds memory maintenance commands to HEARTBEAT.md (if present) Creates ~/.openclaw/memory.db database file Session hooks may process conversation metadata (not full content) for learning
With Rune, your agent will: β Remember context between sessions without burning tokens β Pick relevant facts dynamically vs dumping everything β Get measurably better at avoiding repeated mistakes β Work autonomously on projects between check-ins β Learn your interaction patterns and adapt responses
# Tune relevance scoring rune score "your query" --threshold 0.6 --model llama3.1:8b # Configure forgetting curves rune forget --decay-rate 0.03 --grace-days 45 # Cross-session pattern analysis rune cross-session --days 90 --min-sessions 5
Rune performs best with regular maintenance. Here are automation strategies:
Daily Maintenance (3 AM) # Expire working memory and regenerate context 0 3 * * * /usr/local/bin/rune expire && /usr/local/bin/rune inject --output ~/.openclaw/workspace/FACTS.md Weekly Optimization (Sunday 2 AM) # Consolidate memory and run self-review 0 2 * * 0 /usr/local/bin/rune consolidate --auto-prioritize && /usr/local/bin/rune self-review --days 7 Monthly Deep Clean (1st of month, 1 AM) # Pattern analysis and database optimization 0 1 1 * * /usr/local/bin/rune pattern-analysis --days 30 && sqlite3 ~/.openclaw/memory.db "VACUUM; ANALYZE;"
# Daily backup at 4 AM 0 4 * * * cp ~/.openclaw/memory.db ~/.openclaw/memory.db.backup.$(date +\%Y\%m\%d) # Keep last 7 days 5 4 * * * find ~/.openclaw -name "memory.db.backup.*" -mtime +7 -delete
π§Ή Memory stays lean: Auto-removes expired facts β‘ Faster queries: Regular consolidation prevents bloat π Self-improvement: Pattern detection catches recurring issues π Current context: FACTS.md regenerated with latest data πΎ Data protection: Automated backups prevent loss
# Check database size and fact count rune stats # Review recent patterns rune pattern-analysis --days 7 # Check consolidation opportunities rune consolidate --dry-run
Memory growing too large? Run rune consolidate to merge similar facts Use rune forget to apply forgetting curves Check rune stats for database size Relevance scoring not working? Ensure Ollama is running: systemctl status ollama Test model: rune score "test" --engine ollama Fall back to anthropic/openai engines Context injection too verbose? Lower relevance threshold: --threshold 0.6 Use token budgeting: rune budget "query" --tokens 300
Rune is open source. Contributions welcome: Memory Science: Better consolidation algorithms, forgetting curves LLM Integration: New scoring engines, extraction methods UI/UX: Better command interfaces, visualization tools Performance: Speed optimizations, memory efficiency
MIT License - Use freely, modify as needed. Rune: Because your AI should remember like you do.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.