Context Optimizer
Advanced context management with auto-compaction and dynamic context optimization for DeepSeek's 64k context window. Features intelligent compaction (merging, summarizing, extractiβ¦
ad2546
@ad2546
What This Skill Does
Manages DeepSeek's 64k context window by auto-compacting messages through merging, summarizing, and extracting key information, with query-aware relevance scoring and a hierarchical memory archive for retrieval.
Replaces manual context trimming and token counting by automatically preserving high-value information while preventing context overflow.
When to Use It
- Prevent context overflow during long conversations with DeepSeek
- Retrieve relevant past conversation snippets from the archive for current queries
- Automatically compact chat history by merging similar or redundant messages
- Summarize older conversation segments to free up token space
- Filter out low-relevance messages based on current query similarity
- Monitor context health and token usage in real-time during a session
Install
$ openclaw skills install @ad2546/context-optimizerContext Pruner
Advanced context management optimized for DeepSeek's 64k context window. Provides intelligent pruning, compression, and token optimization to prevent context overflow while preserving important information.
Key Features
- DeepSeek-optimized: Specifically tuned for 64k context window
- Adaptive pruning: Multiple strategies based on context usage
- Semantic deduplication: Removes redundant information
- Priority-aware: Preserves high-value messages
- Token-efficient: Minimizes token overhead
- Real-time monitoring: Continuous context health tracking
Quick Start
Auto-compaction with dynamic context:
import { createContextPruner } from './lib/index.js';
const pruner = createContextPruner({
contextLimit: 64000, // DeepSeek's limit
autoCompact: true, // Enable automatic compaction
dynamicContext: true, // Enable dynamic relevance-based context
strategies: ['semantic', 'temporal', 'extractive', 'adaptive'],
queryAwareCompaction: true, // Compact based on current query relevance
});
await pruner.initialize();
// Process messages with auto-compaction and dynamic context
const processed = await pruner.processMessages(messages, currentQuery);
// Get context health status
const status = pruner.getStatus();
console.log(`Context health: ${status.health}, Relevance scores: ${status.relevanceScores}`);
// Manual compaction when needed
const compacted = await pruner.autoCompact(messages, currentQuery);
Archive Retrieval (Hierarchical Memory):
// When something isn't in current context, search archive
const archiveResult = await pruner.retrieveFromArchive('query about previous conversation', {
maxContextTokens: 1000,
minRelevance: 0.4,
});
if (archiveResult.found) {
// Add relevant snippets to current context
const archiveContext = archiveResult.snippets.join('\n\n');
// Use archiveContext in your prompt
console.log(`Found ${archiveResult.sources.length} relevant sources`);
console.log(`Retrieved ${archiveResult.totalTokens} tokens from archive`);
}
Auto-Compaction Strategies
- Semantic Compaction: Merges similar messages instead of removing them
- Temporal Compaction: Summarizes older conversations by time windows
- Extractive Compaction: Extracts key information from verbose messages
- Adaptive Compaction: Chooses best strategy based on message characteristics
- Dynamic Context: Filters messages based on relevance to current query
Dynamic Context Management
- Query-aware Relevance: Scores messages based on similarity to current query
- Relevance Decay: Relevance scores decay over time for older conversations
- Adaptive Filtering: Automatically filters low-relevance messages
- Priority Integration: Combines message priority with semantic relevance
Hierarchical Memory System
The context archive provides a RAM vs Storage approach:
- Current Context (RAM): Limited (64k tokens), fast access, auto-compacted
- Archive (Storage): Larger (100MB), slower but searchable
- Smart Retrieval: When information isn't in current context, efficiently search archive
- Selective Loading: Extract only relevant snippets, not entire documents
- Automatic Storage: Compacted content automatically stored in archive
Configuration
{
contextLimit: 64000, // DeepSeek's context window
autoCompact: true, // Enable automatic compaction
compactThreshold: 0.75, // Start compacting at 75% usage
aggressiveCompactThreshold: 0.9, // Aggressive compaction at 90%
dynamicContext: true, // Enable dynamic context management
relevanceDecay: 0.95, // Relevance decays 5% per time step
minRelevanceScore: 0.3, // Minimum relevance to keep
queryAwareCompaction: true, // Compact based on current query relevance
strategies: ['semantic', 'temporal', 'extractive', 'adaptive'],
preserveRecent: 10, // Always keep last N messages
preserveSystem: true, // Always keep system messages
minSimilarity: 0.85, // Semantic similarity threshold
// Archive settings
enableArchive: true, // Enable hierarchical memory system
archivePath: './context-archive',
archiveSearchLimit: 10,
archiveMaxSize: 100 * 1024 * 1024, // 100MB
archiveIndexing: true,
// Chat logging
logToChat: true, // Log optimization events to chat
chatLogLevel: 'brief', // 'brief', 'detailed', or 'none'
chatLogFormat: 'π {action}: {details}', // Format for chat messages
// Performance
batchSize: 5, // Messages to process in batch
maxCompactionRatio: 0.5, // Maximum 50% compaction in one pass
}
Chat Logging
The context optimizer can log events directly to chat:
// Example chat log messages:
// π Context optimized: Compacted 15 messages β 8 (47% reduction)
// π Archive search: Found 3 relevant snippets (42% similarity)
// π Dynamic context: Filtered 12 low-relevance messages
// Configure logging:
const pruner = createContextPruner({
logToChat: true,
chatLogLevel: 'brief', // Options: 'brief', 'detailed', 'none'
chatLogFormat: 'π {action}: {details}',
// Custom log handler (optional)
onLog: (level, message, data) => {
if (level === 'info' && data.action === 'compaction') {
// Send to chat
console.log(`π§ Context optimized: ${message}`);
}
}
});
Integration with Clawdbot
Add to your Clawdbot config:
skills:
context-pruner:
enabled: true
config:
contextLimit: 64000
autoPrune: true
The pruner will automatically monitor context usage and apply appropriate pruning strategies to stay within DeepSeek's 64k limit.
Related skills
Cognitive Memory
@icemilo414Intelligent multi-store memory system with human-like encoding, consolidation, decay, and recall. Use when setting up agent memory, configuring remember/forget triggers, enabling sleep-time reflection, building knowledge graphs, or adding audit trails. Replaces basic flat-file memory with a cognitive architecture featuring episodic, semantic, procedural, and core memory stores. Supports multi-agent systems with shared read, gated write access model. Includes philosophical meta-reflection that deepens understanding over time. Covers MEMORY.md, episode logging, entity graphs, decay scoring, reflection cycles, evolution tracking, and system-wide audit.
OpenClaw Memory
@weareallsatoshinManage, optimize, and troubleshoot the OpenClaw memory system β MEMORY.md curation, daily logs (memory/YYYY-MM-DD.md), memory_search tuning, compaction survi...
Memory System V2
@kellyclaudeaiFast semantic memory system with JSON indexing, auto-consolidation, and <20ms search. Capture learnings, decisions, insights, events. Use when you need persistent memory across sessions or want to recall prior work/decisions.
Git-Based Knowledge Graph Memory System for Claude Code
@mourad-ghafiriGit-Notes-Based knowledge graph memory system. Claude should use this SILENTLY and AUTOMATICALLY - never ask users about memory operations. Branch-aware persistent memory using git notes. Handles context, decisions, tasks, and learnings across sessions.
Triple Memory
@ktpriyathamComplete memory system combining LanceDB auto-recall, Git-Notes structured memory, and file-based workspace search. Use when setting up comprehensive agent memory, when you need persistent context across sessions, or when managing decisions/preferences/tasks with multiple memory backends working together.
Triple Memory
@ktpriyathamComplete memory system combining LanceDB auto-recall, Git-Notes structured memory, and file-based workspace search. Use when setting up comprehensive agent memory, when you need persistent context across sessions, or when managing decisions/preferences/tasks with multiple memory backends working together.