agent-memory

Store and retrieve user memories across sessions using Databricks Lakebase.

Updated May 10, 2026
One-click install
npx skills add https://github.com/keqingli1129/agent-langgraph-one --skill agent-memory-keqingli1129
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-memory
Source: https://github.com/keqingli1129/agent-langgraph-one/tree/main/.claude/skills/agent-memory
Command: npx skills add https://github.com/keqingli1129/agent-langgraph-one --skill agent-memory-keqingli1129

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires databricks-langchain[memory], databricks-sdk, langchain-core, langgraph, mlflow.

What problem does it solve?

This Skill solves the problem of agents forgetting prior user context by enabling long-term and short-term memory so the assistant can remember preferences, facts, and conversation history across requests.

Core Features & Use Cases

  • Long-term memory with Lakebase: Store, search, and delete user memories that persist across sessions using Databricks Lakebase (via AsyncDatabricksStore).
  • Short-term memory with checkpointing: Maintain conversation/session continuity using AsyncCheckpointSaver keyed by thread_id.
  • Agent tool integration: Adds memory tools (get/save/delete) that the agent can call, with user_id extraction and safe JSON validation for saving.

Quick Start

Add the memory dependency and configure Lakebase environment variables, then wire memory_tools() into your agent server so the agent can save and retrieve memories for a provided custom_inputs.user_id.

Frequently Asked Questions about agent-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist user preferences and conversation state across LangGraph agent sessions?

You can persist user preferences and conversation state across LangGraph sessions by integrating memory tools with AsyncDatabricksStore for long-term Lakebase storage and AsyncCheckpointSaver for short-term thread_id-scoped state.

What is the difference between short-term checkpointing and long-term Lakebase storage for agent memory?

Short-term checkpointing maintains session continuity within a thread_id, while long-term Lakebase storage stores, searches, and deletes user memories that persist across sessions using AsyncDatabricksStore.

How do I configure Databricks Lakebase to save and retrieve agent memories?

To configure Databricks Lakebase for agent memory, add the databricks-langchain memory dependency, set Lakebase environment variables, and wire memory_tools into your agent server to handle user_id extraction and safe JSON validation.

Does LangGraph checkpointing work with Databricks LangChain for maintaining conversation history?

Yes, LangGraph checkpointing works with Databricks LangChain by using AsyncCheckpointSaver to maintain conversation history scoped by thread_id, while AsyncDatabricksStore handles long-term memory persistence across requests.

Do I need MLflow and databricks-sdk dependencies to implement long-term agent memory?

Yes, implementing long-term agent memory requires databricks-langchain memory, databricks-sdk, langchain-core, langgraph, and mlflow dependencies to enable storage, checkpointing, and tool integration functionality.

Why does my agent forget user-specific information between conversations using LangGraph?

Agents forget user-specific information between conversations when they lack persistent memory; integrating memory_tools with AsyncDatabricksStore enables storing and retrieving preferences, facts, and history across separate requests.