RLM-native ContextEngine plugin for OpenClaw
Stop compacting. Start querying.
Conversation history doesn't belong in the context window. recursive-claw keeps it external in SQLite and gives the model tools to query what it needs, when it needs it. No compaction. No summarization. Nothing is ever lost.
Based on MIT's Recursive Language Models paradigm.
| Legacy / lossless-claw | recursive-claw | |
|---|---|---|
| History in context | Summaries + tail (grows with conversation) | Tail only (constant) |
| Information loss | Compaction discards detail at every depth | Zero. Ever. |
| Token cost per turn | Scales with history length | Flat (~2K tokens) |
| 50K-token history | ~50K tokens per turn | ~2K + sub-query on demand |
| Cross-session | Lost or degraded | Fully queryable |
openclaw plugins install recursive-clawThat's it. Zero config needed. SQLite auto-created, Haiku sub-queries, $0.10/turn budget cap.
Every message is stored in SQLite with FTS5 full-text search. assemble() returns only the system prompt, a fresh tail (last 20 messages), and a context manifest. The model queries history on demand.
┌──────────────────────────────────────┐
│ OpenClaw Agent Turn │
│ │
│ System prompt │
│ + Fresh tail (last 20 messages) │
│ + Manifest: "847 messages stored" │
│ + 6 retrieval tools │
│ │
│ History stays in SQLite ──────────►│──── rc_grep("auth decision")
│ Model queries on demand │◄─── "JWT with RS256, 15-min access tokens"
└──────────────────────────────────────┘
| Tool | What it does |
|---|---|
rc_peek |
View messages at a position in history |
rc_grep |
Full-text search or regex across all stored messages |
rc_slice |
Extract a contiguous range by message index |
rc_query |
Ask a question — dispatches to cheap sub-agent for focused answer |
rc_timeline |
Structural overview: time periods, message counts, index ranges |
rc_repl |
Run JavaScript in a sandboxed REPL with all retrieval functions |
rc_query is where the cost savings live. It greps for relevant messages, feeds them to a cheap model (Haiku at $1/$5 per 1M tokens), and returns a focused answer. The main model never sees the raw history.
Works with zero config. Customize when you need to:
| Option | Default | Description |
|---|---|---|
mode |
"tools" |
"tools" or "repl" |
freshTailCount |
20 |
Messages kept in context window |
databasePath |
auto | SQLite database path |
subQuery.defaultProvider |
"anthropic" |
anthropic, openai, google, openrouter |
subQuery.defaultModel |
"claude-haiku-4-5" |
Model for retrieval sub-queries |
subQuery.maxBudgetPerQuery |
0.05 |
USD cap per sub-query |
subQuery.maxBudgetPerTurn |
0.10 |
USD cap per turn |
Environment variables (RC_MODE, RC_PROVIDER, RC_MODEL, RC_BUDGET_PER_TURN, etc.) override config for quick testing.
What's tested and working:
- Tools mode (rc_peek, rc_grep, rc_slice, rc_query, rc_timeline, rc_repl) — verified E2E against OpenClaw 2026.3.13
- Anthropic provider (Haiku) for sub-queries — live tested
- SQLite storage with FTS5 — cross-session persistence verified
- 147 automated tests (unit, integration, E2E with planted-fact retrieval)
What's configured but not yet live-tested:
- OpenAI, Google, and OpenRouter providers — routing logic tested with mocks, not yet verified with real API calls
- REPL mode code block interception — currently works via
rc_repltool call, nativereplblock execution planned
Coming next:
- Block-level storage — group messages into conversational blocks for better retrieval context
- Workspace context externalization — move SOUL.md, AGENTS.md, and other workspace files out of the system prompt and into queryable storage
- Formal benchmarks — token usage, cost, retrieval accuracy, and latency comparisons against legacy and lossless-claw
- Research paper formalizing the results
Contributions and feedback welcome — open an issue.
recursive-claw implements the paradigm from Recursive Language Models (Zhang, Kraska, Khattab — MIT CSAIL, 2025). Context stays external. The model programs its way to what it needs.
Built by David Kogan