vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-03-12 07:20:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: context engine

Browse Source
This commit is contained in:
Vincent Koc
2026-03-06 08:55:58 -05:00
parent 5470337b1c
commit 151f26070b
3 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/concepts/context.md
View File

@@ -153,6 +153,12 @@ What persists across messages depends on the mechanism:
Docs: [Session](/concepts/session), [Compaction](/concepts/compaction), [Session pruning](/concepts/session-pruning). Docs: [Session](/concepts/session), [Compaction](/concepts/compaction), [Session pruning](/concepts/session-pruning).
By default, OpenClaw uses the built-in `legacy` context engine for assembly and
compaction. If you install a plugin that provides `kind: "context-engine"` and
select it with `plugins.slots.contextEngine`, OpenClaw delegates context
assembly, `/compact`, and related subagent context lifecycle hooks to that
engine instead.
## What `/context` actually reports ## What `/context` actually reports
`/context` prefers the latest **run-built** system prompt report when available: `/context` prefers the latest **run-built** system prompt report when available:

4
docs/plugins/manifest.md
View File

@@ -66,6 +66,10 @@ Optional keys:
- The manifest is **required for all plugins**, including local filesystem loads. - The manifest is **required for all plugins**, including local filesystem loads.
- Runtime still loads the plugin module separately; the manifest is only for - Runtime still loads the plugin module separately; the manifest is only for
discovery + validation. discovery + validation.
- Exclusive plugin kinds are selected through `plugins.slots.*`.
- `kind: "memory"` is selected by `plugins.slots.memory`.
- `kind: "context-engine"` is selected by `plugins.slots.contextEngine`
(default: built-in `legacy`).
- If your plugin depends on native modules, document the build steps and any - If your plugin depends on native modules, document the build steps and any
package-manager allowlist requirements (for example, pnpm `allow-build-scripts` package-manager allowlist requirements (for example, pnpm `allow-build-scripts`
- `pnpm rebuild <package>`). - `pnpm rebuild <package>`).

2
docs/tools/plugin.md
View File

@@ -66,6 +66,7 @@ Plugins can register:
- Agent tools - Agent tools
- CLI commands - CLI commands
- Background services - Background services
- Context engines
- Optional config validation - Optional config validation
- **Skills** (by listing `skills` directories in the plugin manifest) - **Skills** (by listing `skills` directories in the plugin manifest)
- **Auto-reply commands** (execute without invoking the AI agent) - **Auto-reply commands** (execute without invoking the AI agent)
@@ -370,6 +371,7 @@ Fields:
- `allow`: allowlist (optional) - `allow`: allowlist (optional)
- `deny`: denylist (optional; deny wins) - `deny`: denylist (optional; deny wins)
- `load.paths`: extra plugin files/dirs - `load.paths`: extra plugin files/dirs
- `slots`: exclusive slot selectors such as `memory` and `contextEngine`
- `entries.<id>`: per‑plugin toggles + config - `entries.<id>`: per‑plugin toggles + config
Config changes **require a gateway restart**. Config changes **require a gateway restart**.