Skip to main content
The openviking long-term-memory backend submits session messages to OpenViking, which extracts and stores entities, events, and preferences for each user. VeADK keeps retrieval scoped to the current user and returns matching memory to the agent.

Prerequisites

Prepare a reachable OpenViking service and a service-owner API key. VeADK 1.0.3 includes openviking-sdk>=0.1.3 in its base dependencies.

Example

When a session is saved, the OpenViking backend receives text messages from both the user and the agent and forms long-term memory after committing the session. Retrieval is fixed to the current user’s viking://user/peers/{peer_id}/memories scope, keeping memories isolated between users.

Parameters

See the long-term memory overview for shared LongTermMemory parameters. Use backend_config to override these OpenViking backend parameters: By default, peer_id equals Runner.user_id. A custom function must return a non-empty identifier containing only letters, digits, periods, underscores, @, and hyphens; . and .. are not allowed.
peer_id_resolver defines the user-isolation boundary in OpenViking. Changing the mapping after deployment leaves existing memories under their old peer paths, so later searches may no longer find them.
Last modified on September 19, 2026