Skip to main content

Agent context SDK — persistent memory and structured retrieval for any AI application. Powered by Redis.

Project description

agentmem

Agent context SDK for Python. Give any AI app persistent memory and structured retrieval.

Inspired by Redis Agent Memory Server and Redis Context Surfaces.

Quick Start

pip install agentmem

Add to your .env:

AGENTMEM_REDIS_URL=redis://default:password@host:port
OPENAI_API_KEY=sk-...
AGENTMEM_APP_ID=my-app

Use it:

import agentmem

agentmem.init()

# Store something the app learned
agentmem.remember("User prefers numbered lists over bullets", scope="user-42")

# Later, before generating a response
corrections = agentmem.recall("formatting preferences", scope="user-42")
# ["User prefers numbered lists over bullets"]

That's it. Three env vars, three lines of code. Memory persists in Redis Cloud with semantic vector search.

What This Is

agentmem is a package your agent app imports. It is not an agent. It does not run prompts, call models, or orchestrate tools.

It does two things:

  1. Memory — store things the app learned (remember), search them by meaning later (recall)
  2. Retrieval — query the app's own data through adapters (register_source, retrieve)

Memory is what the app learned. Retrieval is what the app can look up. They're separate capabilities. Your app composes them however it wants.

How Memory Works

When you call remember("User prefers numbered lists"):

  1. agentmem sends the text to OpenAI to generate an embedding (a list of numbers that captures the meaning)
  2. The embedding + text are stored in your Redis Cloud database

When you call recall("formatting preferences"):

  1. agentmem generates an embedding for the query
  2. Redis finds the stored memories with the most similar meaning
  3. Returns them ranked by relevance

That's why "formatting preferences" finds "User prefers numbered lists" — they mean similar things even though the words are different.

Why do I need an OpenAI key? Redis stores and searches vectors but doesn't generate them. Something has to convert text into numbers. OpenAI does that. If you use the AMS backend instead (see below), AMS handles the OpenAI key internally and your app doesn't need one.

Memory Backends

Direct Redis Cloud (recommended)

Connects straight to Redis Cloud. Your app generates embeddings via OpenAI and stores them in Redis. No middleware, no server to deploy.

from agentmem import AgentMem

mem = AgentMem(
    redis_url="redis://default:password@host:port",
    app_id="my-app",
    openai_api_key="sk-...",
)

Requires:

  • Redis Cloud account with search module (free tier works)
  • OpenAI API key (for embeddings)

Via Redis Agent Memory Server (AMS)

Connects to AMS, which handles embeddings and Redis for you. Your app does NOT need an OpenAI key — AMS has its own.

mem = AgentMem(
    base_url="http://localhost:8000",
    app_id="my-app",
)

Requires AMS running (Docker or hosted).

Local in-memory (for development)

No server, no credentials. Memories live in process memory and disappear on restart.

mem = AgentMem(app_id="my-app")

Retrieval

Retrieval lets the app query its own data at runtime. Register a data source with an adapter, then call retrieve().

ContextSurfacesAdapter

Query data through Redis Context Surfaces. Context Surfaces reads your Redis data model and auto-generates search tools — search_product_by_text, filter_order_by_status, get_customer_by_id, etc. No OpenAI key needed — Context Surfaces handles everything.

from agentmem.adapters.context_surfaces import ContextSurfacesAdapter

mem.register_source("products", ContextSurfacesAdapter(
    agent_key="cs_agent_...",
    tool_name="search_product_by_text",
))

results = mem.retrieve("wireless headphones", source="products")
# [{"name": "Wireless Headphones Pro", "price": 79.99, ...}]

Requires a Context Surface connected to your Redis Cloud. See Context Surfaces Setup below.

SupabaseAdapter

Query a Supabase table with text search and scope filtering. For apps that keep data in Supabase.

from agentmem.adapters.supabase import SupabaseAdapter

mem.register_source("orders", SupabaseAdapter(
    url="https://xxx.supabase.co",
    key="sb_secret_...",
    table="orders",
    search_columns=["description", "notes"],
    return_columns=["id", "status", "total"],
    scope_column="user_id",
))

results = mem.retrieve("shipping delay", source="orders", scope="user-42")

CallbackAdapter

Wrap any function as a retrieval source. For custom data access logic.

from agentmem.adapters.callback import CallbackAdapter

def search_tickets(query, scope, limit):
    return my_db.search(query, user_id=scope, limit=limit)

mem.register_source("tickets", CallbackAdapter(fn=search_tickets))

Custom adapters

Any class that implements BaseAdapter:

from agentmem.adapters.base import BaseAdapter

class MyAdapter(BaseAdapter):
    def retrieve(self, query, scope=None, limit=5):
        return self.db.search(query, tenant=scope, max_results=limit)

Using Memory + Retrieval Together

import agentmem
from agentmem.adapters.callback import CallbackAdapter

agentmem.init()  # reads AGENTMEM_REDIS_URL + OPENAI_API_KEY from env

agentmem.register_source("tickets", CallbackAdapter(fn=search_tickets))

# Before generating a response — gather context from both layers
memories = agentmem.recall("customer preferences", scope="user-42")
tickets = agentmem.retrieve("billing question", source="tickets", scope="user-42")

prompt = f"""
LEARNED ABOUT THIS USER:
{chr(10).join(f'- {m}' for m in memories)}

RECENT TICKETS:
{chr(10).join(str(t) for t in tickets)}

Now respond to their question: ...
"""

# After the interaction — store anything worth keeping
agentmem.remember("User is on the Pro plan and prefers email support", scope="user-42")

Environment Variables

# Direct Redis (recommended for production)
AGENTMEM_REDIS_URL=redis://default:password@host:port
OPENAI_API_KEY=sk-...          # only needed for direct Redis, not for AMS

# OR via AMS (alternative — no OpenAI key needed in your app)
AGENTMEM_BASE_URL=http://localhost:8000

# Common
AGENTMEM_APP_ID=my-app
AGENTMEM_TIMEOUT=5.0           # optional, default 5 seconds
import agentmem
agentmem.init()  # reads from env vars automatically

API

Core

Function Signature
init() init(base_url=None, app_id=None, redis_url=None, openai_api_key=None, timeout=None, on_error=None)
AgentMem() AgentMem(base_url=None, app_id="default", redis_url=None, openai_api_key=None, timeout=5.0, on_error=None)

Backend selection: redis_url → direct Redis. base_url → AMS. Neither → in-memory.

Memory

Function Signature Returns
remember() remember(text, scope=None, topics=None, metadata=None) bool
recall() recall(query, scope=None, limit=5) list[str]
  • scope — partition memories by tenant, user, project, workspace
  • topics — semantic tags stored with the memory (for future filtering)
  • metadata — structured context stored alongside (max 4KB, must be JSON-serializable)
  • recall() matches by meaning, not exact words

Retrieval

Function Signature Returns
register_source() register_source(name, adapter) None
retrieve() retrieve(query, source, scope=None, limit=5) list[dict]

Properties

Property Type Description
.last_error Exception or None Set on failure, cleared on success
.initialized bool False if init failed

Failure Behavior

agentmem never crashes the host app.

Runtime errors (Redis down, adapter timeout, network failure):

  • remember() returns False
  • recall() returns []
  • retrieve() returns []
  • Error stored in last_error and passed to on_error callback

Programmer errors (invalid arguments):

  • Non-JSON-serializable metadata → MemoryValidationError
  • Metadata over 4KB → MemoryValidationError
  • Missing adapter config → ConfigurationError
def on_err(method, exc):
    print(f"agentmem {method} failed: {exc}")

mem = AgentMem(app_id="my-app", on_error=on_err)

Context Surfaces Setup

To use the ContextSurfacesAdapter, you need a Context Surface connected to your Redis Cloud database. This is a one-time setup.

Using the CLI

pip install context-surfaces  # requires Python 3.11+

# Create a surface pointing at your Redis Cloud
ctxctl surface create \
  --name "my-surface" \
  --models ./models.py \
  --redis-addr "host:port" \
  --redis-password "$REDIS_PASSWORD" \
  --admin-key "$CTX_ADMIN_KEY"

# Create an agent key for querying
ctxctl agent create \
  --surface-id "$SURFACE_ID" \
  --name "my-agent" \
  --admin-key "$CTX_ADMIN_KEY"

# Verify — list auto-generated tools
ctxctl tools list --agent-key "$AGENT_KEY"

Using the ContextSurfaceManager (Python)

from agentmem.adapters.context_surfaces import ContextSurfaceManager

mgr = ContextSurfaceManager(admin_key="cs_admin_...")

surfaces = mgr.list_surfaces()
tools = mgr.list_tools(agent_key="cs_agent_...")

Getting credentials

  • CTX_ADMIN_KEY — found in Redis Cloud dashboard under Context Surfaces → Access Management → API Keys
  • AGENT_KEY — created when you run ctxctl agent create
  • REDIS_PASSWORD — found in Redis Cloud dashboard under your database → Security

Where Credentials Go

Credential Where When needed
AGENTMEM_REDIS_URL Your app .env Direct Redis memory
OPENAI_API_KEY Your app .env Direct Redis memory (not needed for AMS)
AGENTMEM_BASE_URL Your app .env AMS memory (alternative to direct Redis)
AGENTMEM_APP_ID Your app .env Always
CTX_ADMIN_KEY Setup only Creating Context Surfaces (one-time)
Agent key (cs_agent_...) Your app code or .env Querying Context Surfaces
Supabase URL/key Your app code or .env SupabaseAdapter

Install (development)

# From a local checkout
pip install -e /path/to/agentmem

# With Redis support
pip install -e /path/to/agentmem[redis]

# With Supabase support
pip install -e /path/to/agentmem[supabase]

# Everything
pip install -e /path/to/agentmem[all]

Testing

PYTHONPATH=src python3 -m unittest discover -s tests

What This Package Does Not Do

  • Run an LLM
  • Act as an autonomous agent
  • Manage tool orchestration
  • Automatically crawl or index your database
  • Merge memory and retrieval into one magic result

You own the application logic. agentmem gives you memory and retrieval primitives.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

agentmem_sdk-0.1.0.tar.gz (23.7 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

agentmem_sdk-0.1.0-py3-none-any.whl (19.2 kB view details)

Uploaded Python 3

File details

Details for the file agentmem_sdk-0.1.0.tar.gz.

File metadata

  • Download URL: agentmem_sdk-0.1.0.tar.gz
  • Upload date:
  • Size: 23.7 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.9.6

File hashes

Hashes for agentmem_sdk-0.1.0.tar.gz
Algorithm Hash digest
SHA256 3d422c96de56cb52501d90841b588dcc053d92f4b9455635046f3e0e43ccaebb
MD5 652728f7a7d967f95fea546e169dd927
BLAKE2b-256 cabe4fcfb3b82174feefd1f2ead7cf16f8ff80c42a05cebc74691255d8aa8d73

See more details on using hashes here.

File details

Details for the file agentmem_sdk-0.1.0-py3-none-any.whl.

File metadata

  • Download URL: agentmem_sdk-0.1.0-py3-none-any.whl
  • Upload date:
  • Size: 19.2 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.9.6

File hashes

Hashes for agentmem_sdk-0.1.0-py3-none-any.whl
Algorithm Hash digest
SHA256 6555a3499850d5aeda1cefb7ebc3d7dda34aca0f108d39c78d2610f9c4045a9d
MD5 16d7c857037da4d51b20823385cce89e
BLAKE2b-256 6215f1160de20782a132e1396cf342a890a28af44e744b0cca11689fc383d5c0

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page