Adaptive Configuration
Use this page when you want to configure the built-in Adaptive plugin component
as a whole. The component kind is adaptive.
Adaptive plugin configuration uses the generic NeMo Relay plugin document
shape. Canonical plugin documents and plugins.toml use snake_case.
Binding helpers can use language-native names and serialize them to canonical
keys.
For plugin file discovery, precedence, merge behavior, editor controls, and gateway conflict rules, refer to Plugin Configuration Files.
Component Shape
The top-level adaptive object contains:
Dedicated pages cover Adaptive Cache Governor (ACG), Adaptive Hints, and Response Cache. State, telemetry, tool parallelism, and policy remain whole-plugin settings:
- Use
state.backend.kind = "in_memory"for local experiments. - Use Redis state when learned state must survive restarts or be shared across workers.
- Enable
telemetrywhen adaptive learners should consume runtime events. - Keep
tool_parallelism.mode = "observe_only"until scheduling behavior has been validated. - Keep
policy.unsupported_value = "error"for rollout safety.
plugins.toml Example
Add the following whole-plugin Adaptive configuration to plugins.toml:
This configuration activates adaptive telemetry, keeps tool parallelism
observational, injects adaptive hints, and leaves ACG in passthrough mode so
requests can be observed without provider-specific cache translation.
Per-Language Plugin Configuration
The following examples configure and activate the Adaptive component through a language binding:
validate() resolves the same configuration layers as initialize() without
loading plugin code or acquiring the activation lease. Use Python/Rust
validate_exact(), Node.js validateExact(), or Go ValidateExact() when only
the supplied static configuration should be checked. For complete
layering rules, refer to Plugin Configuration Files.
Python
Node.js
Rust
Manual API
Use the manual runtime API when an integration needs to own adaptive lifecycle directly instead of activating the top-level plugin component.
Python
Node.js
Rust
Validation and Teardown
Validate plugin configuration before initialization. Disabled components are excluded from the effective host; validate their component-local configuration before enabling them when preparing a rollout.
Common validation failures include:
- Unknown adaptive fields when policy treats unknown fields as errors.
- Unsupported backend kinds, tool-parallelism modes, or ACG providers.
- Unsupported schema versions.
- Backend-specific fields that do not match the selected backend.
Close the activation during shutdown or test cleanup. Closing the activation deregisters the adaptive subscribers and intercepts owned by the plugin runtime.
Rollout Guidance
Start by enabling state and telemetry in a development environment. Run representative instrumented workflows, inspect emitted events and adaptive reports, and then enable active behavior one area at a time. Keep rollback as a configuration change.