Prerequisite

  1. Scoopika account. create one here.
  2. Scoopika access token. generate one here.
  3. Scoopika Pro plan. check pricing.

If you haven’t read about agents memory and how it works, refer to this page.

History stores are a powerful feature within Scoopika Pro that grants your agents long-term memory capabilities. By leveraging history stores, you can enable your agents to remember past interactions with users, fostering a more natural and engaging conversational experience.

All data is encrypted and never accessed by out team.

What are History Stores

Imagine a user interacting with your agent.. By default, Scoopika uses an in-memory store, meaning past conversations are forgotten. History stores offer a persistent solution, allowing you to record chat history and enable your agents to access and reference previous interactions. This empowers your agents to:

Maintain Context: Agents can remember past conversations and user preferences, leading to more meaningful and personalized interactions.

Improve Agent Performance: Over time, agents can learn from past interactions, allowing them to provide more relevant and accurate responses.

Create History Store

Scoopika Pro provides a user-friendly interface for creating history stores. Here’s how to get started:

  1. Go to the platform here.
  2. Assign a unique name to your store.
  3. Click on “Create” to establish a new history store.

This will create a managed Serverless data store for you that’s served edge-close to your users.

Connecting your Store

Once your history store is created, You just need to add its ID to your scoopika instance on the server-side setup:

import { Scoopika } from "@scoopika/scoopika";

const scoopika = new Scoopika({
	store: "STORE_ID"
});

By providing the history store ID during Scoopika instance initialization, you instruct Scoopika to utilize this persistent storage for managing chat sessions and conversation history.

With your history store connected, explore the comprehensive documentation to learn more about:

Server-side Session Management

Client-side Session Management

Was this page helpful?