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.
Field names stay snake_case in every binding and in plugins.toml, even when
language helper functions use language-native naming conventions.
For plugin file discovery, precedence, merge behavior, editor controls, and gateway conflict rules, see Plugin Configuration Files.
Component Shape
The top-level adaptive object contains:
The requested area pages cover Adaptive Cache Governor (ACG) and Adaptive Hints. 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
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
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 adaptive
components are still validated, which lets operators prepare a rollout before
setting enabled = true.
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.
Clear plugin configuration during shutdown or test cleanup. Clearing the plugin configuration deregisters 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.