Skip to main content
The 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-sdk dependency.
When automatic saving is enabled, session content is sent to the configured OpenViking service. Confirm user consent, data scope, access controls, and retention policy before writing conversations.

Configure long-term memory

A new session with the same 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:
In production, inject api_key through environment variables or a secret manager.

Customize user mapping

By default, the OpenViking peer identifier equals the VeADK user_id. A multitenant application can provide peer_id_resolver to combine tenant and user values into one safe identifier:
The result cannot be empty. It may contain letters, digits, dots, underscores, @, and hyphens, and cannot be . or ...
Last modified on September 19, 2026