openviking backend submits sessions to OpenViking, which extracts user-related entities, events, and preferences for retrieval in later sessions. It includes both user messages and agent responses so OpenViking can derive memory from the complete conversation.
Prerequisites
- A reachable OpenViking HTTP service;
- A service owner API key issued by that service;
- VeADK 1.0.4 already includes the required
openviking-sdkdependency.
Configure long-term memory
user_id can retrieve memories committed by earlier sessions. app_name scopes the application, and the default peer identifier is the user_id itself.
Parameters
LongTermMemory parameters
OpenViking backend parameters
Explicit configuration example:
api_key through environment variables or a secret manager.
Customize user mapping
By default, the OpenViking peer identifier equals the VeADKuser_id. A multitenant application can provide peer_id_resolver to combine tenant and user values into one safe identifier:
@, and hyphens, and cannot be . or ...