Context engine

A context engine controls how OpenClaw builds model context for each run: which messages to include, how to summarize older history, and how to manage context across subagent boundaries.

OpenClaw ships with a built-in legacy engine and uses it by default. Install and select a plugin engine only when you want different assembly, compaction, or cross-session recall behavior.

Quick start

openclaw doctor# or inspect config directly:cat ~/.openclaw/openclaw.json | jq '.plugins.slots.contextEngine'

openclaw plugins install @martian-engineering/lossless-claw

openclaw plugins install -l ./my-context-engine

// openclaw.json{  plugins: {    slots: {      contextEngine: "lossless-claw", // must match the plugin's registered engine id    },    entries: {      "lossless-claw": {        enabled: true,        // Plugin-specific config goes here (see the plugin's docs)      },    },  },}

How it works

Every time OpenClaw runs a model prompt, the context engine participates at four lifecycle points:

Engines can also implement an optional maintain() method for transcript maintenance (safe rewrites via runtimeContext.rewriteTranscriptEntries()) after bootstrap, a successful turn, or compaction. Set info.turnMaintenanceMode: "background" to run it as deferred work instead of blocking the reply.

When queued budget compaction accepts background maintenance, it keeps the prepared runtime alive through maintenance, coalesced reruns, and engine disposal. Acceptance does not mean cleanup has finished. Return asynchronous work from engine methods and dispose() so the host can join it before releasing their resources.

A logical turn also retains its managed supplying registry through engine disposal. When that registry copied a runtime engine from another inspection, its recorded donor dependency can keep the engine usable after the donor inspection retires. Retiring the supplying registry still refuses new logical turns; existing engine work keeps its physical resources until cleanup finishes. Raw registrations keep their caller-owned lifetime.

For the bundled non-ACP Codex harness, OpenClaw applies the same lifecycle by projecting assembled context into Codex developer instructions and the current turn prompt. Codex still owns its native thread history and native compactor.

Subagent lifecycle (optional)

OpenClaw calls two optional subagent lifecycle hooks:

System prompt addition

The assemble method can return a systemPromptAddition string. OpenClaw prepends this to the system prompt for the run. This lets engines inject dynamic recall guidance, retrieval instructions, or context-aware hints without requiring static workspace files.

The legacy engine

The built-in legacy engine preserves OpenClaw's original behavior:

• Ingest: no-op (the session manager handles message persistence directly).
• Assemble: pass-through (the existing sanitize → validate → limit pipeline in the runtime handles context assembly).
• Compact: delegates to the built-in summarization compaction, which creates a single summary of older messages and keeps recent messages intact.
• After turn: no-op.

The legacy engine does not register tools or provide a systemPromptAddition.

When no plugins.slots.contextEngine is set (or it's set to "legacy"), this engine is used automatically.

Plugin engines

A plugin can register a context engine using the plugin API:

import { buildMemorySystemPromptAddition } from "openclaw/plugin-sdk/core"; // `buildContext`, `countTokens`, and `commitAcceptedTurn` below are your own// plugin's helpers to implement. They are not part of the plugin SDK.// `buildMemorySystemPromptAddition` is real SDK surface, imported above. export default function register(api) {  api.registerContextEngine("my-engine", (ctx) => ({    info: {      id: "my-engine",      name: "My Context Engine",      ownsCompaction: true,      acceptedHostParams: ["sessionKey", "runtimeContext"],      transcriptSemantics: {        currentTurnFence: "before-current-turn-entry-v1",        turnAdvancementIdempotency: "atomic-idempotent-v1",      },    },     async ingest({ sessionId, message, isHeartbeat }) {      // Store the message in your data store      return { ingested: true };    },     async assemble({      sessionId,      sessionKey,      messages,      tokenBudget,      availableTools,      citationsMode,    }) {      // Return messages that fit the budget      return {        messages: buildContext(messages, tokenBudget),        estimatedTokens: countTokens(messages),        systemPromptAddition: buildMemorySystemPromptAddition({          availableTools: availableTools ?? new Set(),          citationsMode,          agentSessionKey: sessionKey,        }),      };    },     async compact({ sessionId, force }) {      // Summarize older context      return { ok: true, compacted: true };    },     async commitTurn({ advancementKey, messages }) {      // Atomically store the accepted turn and advancementKey. Return      // "duplicate" when that exact key was committed by an earlier retry.      return await commitAcceptedTurn({        advancementKey,        messages,      });    },  }));}

The factory ctx includes optional config, agentDir, and workspaceDir values so plugins can initialize per-agent or per-workspace state before the first lifecycle call. Before a non-legacy assemble() call, the host completes registered async memory prompt preparation. The synchronous buildMemorySystemPromptAddition(...) helper reads that immutable run snapshot; pass the supplied tool, citation, agent, and session context through unchanged.

Then enable it in config:

{  plugins: {    slots: {      contextEngine: "my-engine",    },    entries: {      "my-engine": {        enabled: true,      },    },  },}

The ContextEngine interface

Required members:

Set info.acceptedHostParams to restrict the host-added lifecycle fields the engine receives. Current keys are sessionKey, prompt, runtimeSettings, sessionTarget, runtimeContext, and abortSignal. OpenClaw intersects the declaration with the fields available for each lifecycle method, so undeclared or unknown keys are never injected. abortSignal governs optional cooperative cancellation for maintain(); the existing compact-operation abort signal is always preserved. Engines without this declaration receive every current host field; declare an explicit list, including [], when the engine validates a narrower input shape.

For durable admitted turns, declare both transcript semantics:

• currentTurnFence: "before-current-turn-entry-v1"
• turnAdvancementIdempotency: "atomic-idempotent-v1"

and implement commitTurn(...) as one atomic, idempotent write keyed by advancementKey. Return { status: "committed" } for the first write and { status: "duplicate" } when a host retry presents an already-committed key. The messages payload contains only the inclusive range from the admitted user entry through the accepted terminal entry. Engines that need the earlier transcript during bootstrap or rebuild should read it through the transcript cursor API, readSessionTranscriptVisibleMessageDelta(...). Pre-turn transcript reads during bootstrap, maintenance, assembly, and retries then see the exact transcript prefix before the admitted user message. The host calls commitTurn only for the accepted successful turn; failed or aborted turns do not advance context-engine state.

For these admitted turns, embedded tool-loop assemble() receives the history before the current turn, with a token budget that reserves space for pending user and tool messages. The host appends those pending messages to the assembled history before the next model request, so they remain visible without entering the engine's store.

Without the full declaration and method, OpenClaw uses the legacy context path for the whole logical turn, including retries. The configured context-engine slot is not changed, and OpenClaw tries the configured engine again on the next logical turn. The same turn-local degradation applies if a declared fence cannot be honored because its exact admitted message is missing, rewritten, or already crossed by a transcript cursor.

assemble returns an AssembleResult with:

compact returns a CompactResult. When compaction changes the active session identity, result.sessionTarget (a typed ContextEngineSessionTarget carrying the session identity and store scope) identifies the successor session that the next retry or turn must use; result.sessionId mirrors the successor id.

Optional members:

Foreground engine disposal shares the agent cleanup deadline: 10 seconds by default, adjustable with OPENCLAW_AGENT_CLEANUP_TIMEOUT_MS. A stalled cleanup logs a warning and lets the completed reply return; it does not cancel the plugin's pending disposal. Cleanup failures and timeouts retain the existing one-shot CLI cleanup-failure outcome; they do not certify resource closure.

Runtime settings

Lifecycle hooks that run inside OpenClaw receive an optional runtimeSettings object. It is a versioned, read-only internal producer/consumer API surface: OpenClaw produces it for the selected context engine, and the context engine consumes it inside lifecycle hooks. It is not rendered directly to users and does not create a dedicated reporting surface.

• schemaVersion: currently 1
• runtime: OpenClaw host, runtime mode (normal, fallback, or degraded), and optional harness/runtime ids
• contextEngineSelection: selected context engine id and selection source
• executionHost: host id and label for the surface invoking the hook
• model: requested model, resolved model, provider, and optional model family
• limits: prompt token budget and max output tokens when known
• diagnostics: closed fallback and degraded reason codes when known

Fields that can be unknown are represented as null; discriminator fields such as runtime mode and selection source remain non-nullable. Engines that restrict host parameters and accept runtimeSettings must include it in info.acceptedHostParams.

Host requirements

Context engines can declare host capability requirements on info.hostRequirements. OpenClaw checks these requirements before starting the operation and fails closed with a descriptive error when the selected runtime cannot satisfy them.

For agent runs, declare assemble-before-prompt when the engine must control the actual model prompt through assemble():

info: {  id: "my-context-engine",  name: "My Context Engine",  hostRequirements: {    "agent-run": {      requiredCapabilities: ["assemble-before-prompt"],      unsupportedMessage:        "Use the native Codex or OpenClaw embedded runtime, or select the legacy context engine.",    },  },}

Native Codex and OpenClaw embedded agent runs satisfy assemble-before-prompt. Generic CLI backends do not, so engines that require it are rejected before the CLI process starts.

Failure isolation

OpenClaw isolates the selected plugin engine from the core reply path. If a non-legacy engine is missing, fails contract validation, throws during factory creation, or throws from a lifecycle method, OpenClaw quarantines that engine for the current Gateway process and downgrades context-engine work to the built-in legacy engine. The error is logged with the failed operation so the operator can repair, update, or disable the plugin without the agent going silent.

Host requirement failures are different: when an engine declares that a runtime lacks a required capability, OpenClaw fails closed before starting the run. That protects engines that would corrupt state if they ran in an unsupported host.

ownsCompaction

ownsCompaction controls whether OpenClaw runtime's built-in in-attempt auto-compaction stays enabled for the run:

That means there are two valid plugin patterns:

A no-op compact() is unsafe for an active non-owning engine because it disables the normal /compact and overflow-recovery compaction path for that engine slot.

Configuration reference

{  plugins: {    slots: {      // Select the active context engine. Default: "legacy".      // Set to a plugin id to use a plugin engine.      contextEngine: "legacy",    },  },}

Relationship to compaction and memory

Tips

• Use openclaw doctor to verify your engine is loading correctly.
• If switching engines, existing sessions continue with their current history. The new engine takes over for future runs.
• Engine errors are logged and the selected plugin engine is quarantined for the current Gateway process. OpenClaw falls back to legacy for user turns so replies can continue, but you should still repair, update, disable, or uninstall the broken plugin.
• For development, use openclaw plugins install -l ./my-engine to link a local plugin directory without copying.

Related

• Compaction - summarizing long conversations
• Context - how context is built for agent turns
• Honcho memory - a memory plugin a context engine can draw on
• Plugin Architecture - registering context engine plugins
• Plugin manifest - plugin manifest fields
• Plugins - plugin overview
• Session management deep dive - the session store, transcript events, and auto-compaction internals
• System prompt - what OpenClaw assembles into the system prompt for every agent run, and the layers it renders from