Reference for theDocumentation Index
Fetch the complete documentation index at: https://docs.openclaw.ai/llms.txt
Use this file to discover all available pages before exploring further.
api.runtime object injected into every plugin during registration. Use these helpers instead of importing host internals directly.
Channel plugins
Step-by-step guide that uses these helpers in context for channel plugins.
Provider plugins
Step-by-step guide that uses these helpers in context for provider plugins.
Config loading and writes
Prefer config that was already passed into the active call path, for exampleapi.config during registration or a cfg argument on channel/provider callbacks. This keeps one process snapshot flowing through the work instead of reparsing config on hot paths.
Use api.runtime.config.current() only when a long-lived handler needs the current process snapshot and no config was passed to that function. The returned value is readonly; clone or use a mutation helper before editing.
Tool factories receive ctx.runtimeConfig plus ctx.getRuntimeConfig(). Use the getter inside a long-lived tool’s execute callback when config can change after the tool definition was created.
Persist changes with api.runtime.config.mutateConfigFile(...) or api.runtime.config.replaceConfigFile(...). Each write must choose an explicit afterWrite policy:
afterWrite: { mode: "auto" }lets the gateway reload planner decide.afterWrite: { mode: "restart", reason: "..." }forces a clean restart when the writer knows hot reload is unsafe.afterWrite: { mode: "none", reason: "..." }suppresses automatic reload/restart only when the caller owns the follow-up.
afterWrite plus a typed followUp summary so callers can log or test whether they requested a restart. The gateway still owns when that restart actually happens.
api.runtime.config.loadConfig() and api.runtime.config.writeConfigFile(...) are deprecated compatibility helpers under runtime-config-load-write. They warn once at runtime, and remain available for old external plugins during the migration window. Bundled plugins must not use them; the config boundary guards fail if plugin code calls them or imports those helpers from plugin SDK subpaths.
For direct SDK imports, use the focused config subpaths instead of the broad
openclaw/plugin-sdk/config-runtime compatibility barrel: config-types for
types, plugin-config-runtime for already-loaded config assertions and plugin
entry lookup, runtime-config-snapshot for current process snapshots, and
config-mutation for writes. Bundled plugin tests should mock these focused
subpaths directly instead of mocking the broad compatibility barrel.
Internal OpenClaw runtime code has the same direction: load config once at the CLI, gateway, or process boundary, then pass that value through. Successful mutation writes refresh the process runtime snapshot and advance its internal revision; long-lived caches should key off the runtime-owned cache key instead of serializing config locally. Long-lived runtime modules have a zero-tolerance scanner for ambient loadConfig() calls; use a passed cfg, a request context.getRuntimeConfig(), or getRuntimeConfig() at an explicit process boundary.
Provider and channel execution paths must use the active runtime config snapshot, not a file snapshot returned for config readback or editing. File snapshots preserve source values such as SecretRef markers for UI and writes; provider callbacks need the resolved runtime view. When a helper may be called with either the active source snapshot or the active runtime snapshot, route through selectApplicableRuntimeConfig() before reading credentials.
Runtime namespaces
api.runtime.agent
api.runtime.agent
Agent identity, directories, and session management.Prefer
runEmbeddedAgent(...) is the neutral helper for starting a normal OpenClaw agent turn from plugin code. It uses the same provider/model resolution and agent-harness selection as channel-triggered replies.runEmbeddedPiAgent(...) remains as a compatibility alias.resolveThinkingPolicy(...) returns the provider/model’s supported thinking levels and optional default. Provider plugins own the model-specific profile through their thinking hooks, so tool plugins should call this runtime helper instead of importing or duplicating provider lists.normalizeThinkingLevel(...) converts user text such as on, x-high, or extra high to the canonical stored level before checking it against the resolved policy.Session store helpers are under api.runtime.agent.session:updateSessionStore(...) or updateSessionStoreEntry(...) for runtime writes. They route through the Gateway-owned session-store writer, preserve concurrent updates, and reuse the hot cache. saveSessionStore(...) remains available for compatibility and offline maintenance-style rewrites.api.runtime.agent.defaults
api.runtime.agent.defaults
Default model and provider constants:
api.runtime.subagent
api.runtime.subagent
Launch and manage background subagent runs.
deleteSession(...) can delete sessions created by the same plugin through api.runtime.subagent.run(...). Deleting arbitrary user or operator sessions still requires an admin-scoped Gateway request.api.runtime.nodes
api.runtime.nodes
List connected nodes and invoke a node-host command from Gateway-loaded plugin code or from plugin CLI commands. Use this when a plugin owns local work on a paired device, for example a browser or audio bridge on another Mac.Inside the Gateway this runtime is in-process. In plugin CLI commands it calls the configured Gateway over RPC, so commands such as
openclaw googlemeet recover-tab can inspect paired nodes from the terminal. Node commands still go through normal Gateway node pairing, command allowlists, plugin node-invoke policies, and node-local command handling.Plugins that expose dangerous node-host commands should register a node-invoke policy with api.registerNodeInvokePolicy(...). The policy runs in the Gateway after command allowlist checks and before the command is forwarded to the node, so direct node.invoke calls and higher-level plugin tools share the same enforcement path.api.runtime.tasks.managedFlows
api.runtime.tasks.managedFlows
Bind a Task Flow runtime to an existing OpenClaw session key or trusted tool context, then create and manage Task Flows without passing an owner on every call.Use
bindSession({ sessionKey, requesterOrigin }) when you already have a trusted OpenClaw session key from your own binding layer. Do not bind from raw user input.api.runtime.tts
api.runtime.tts
Text-to-speech synthesis.Uses core
messages.tts configuration and provider selection. Returns PCM audio buffer + sample rate.api.runtime.mediaUnderstanding
api.runtime.mediaUnderstanding
Image, audio, and video analysis.Returns
{ text: undefined } when no output is produced (e.g. skipped input).api.runtime.stt.transcribeAudioFile(...) remains as a compatibility alias for api.runtime.mediaUnderstanding.transcribeAudioFile(...).api.runtime.imageGeneration
api.runtime.imageGeneration
Image generation.
api.runtime.webSearch
api.runtime.webSearch
Web search.
api.runtime.media
api.runtime.media
Low-level media utilities.
api.runtime.config
api.runtime.config
Current runtime config snapshot and transactional config writes. Prefer
config that was already passed into the active call path; use
current() only when the handler needs the process snapshot directly.mutateConfigFile(...) and replaceConfigFile(...) return a followUp
value, for example { mode: "restart", requiresRestart: true, reason },
which records the writer intent without taking restart control away from the
gateway.api.runtime.system
api.runtime.system
System-level utilities.
api.runtime.events
api.runtime.events
Event subscriptions.
api.runtime.logging
api.runtime.logging
Logging.
api.runtime.modelAuth
api.runtime.modelAuth
Model and provider auth resolution.
api.runtime.state
api.runtime.state
State directory resolution and SQLite-backed keyed storage.Keyed stores survive restarts and are isolated by the runtime-bound plugin id. Use
registerIfAbsent(...) for atomic dedupe claims: it returns true when the key was missing or expired and registered, or false when a live value already exists without overwriting its value, creation time, or TTL. Limits: maxEntries per namespace, 1,000 live rows per plugin, JSON values under 64KB, and optional TTL expiry.api.runtime.tools
api.runtime.tools
Memory tool factories and CLI.
api.runtime.channel
api.runtime.channel
Channel-specific runtime helpers (available when a channel plugin is loaded).Available mention helpers:
api.runtime.channel.mentions is the shared inbound mention-policy surface for bundled channel plugins that use runtime injection:buildMentionRegexesmatchesMentionPatternsmatchesMentionWithExplicitimplicitMentionKindWhenresolveInboundMentionDecision
api.runtime.channel.mentions intentionally does not expose the older resolveMentionGating* compatibility helpers. Prefer the normalized { facts, policy } path.Storing runtime references
UsecreatePluginRuntimeStore to store the runtime reference for use outside the register callback:
Prefer
pluginId for the runtime-store identity. The lower-level key form is for uncommon cases where one plugin intentionally needs more than one runtime slot.Other top-level api fields
Beyond api.runtime, the API object also provides:
Plugin id.
Plugin display name.
Current config snapshot (active in-memory runtime snapshot when available).
Plugin-specific config from
plugins.entries.<id>.config.Scoped logger (
debug, info, warn, error).Current load mode;
"setup-runtime" is the lightweight pre-full-entry startup/setup window.Resolve a path relative to the plugin root.
Related
- Plugin internals — capability model and registry
- SDK entry points —
definePluginEntryoptions - SDK overview — subpath reference