managing-memory
Skill0 starsChanged 6 months agoMITView on GitHub
Manages memory tiers in lauren-ai agents — short-term rolling window, conversation history, user memory facts with @remember, and vector store for RAG. Use when adding persistent memory to an agent, implementing @remember() for long-term facts, using ConversationStore across sessions, or building RAG with InMemoryVectorStore.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- myusernameiskey/Claude_skillstheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- myusernameiskey/Claude_skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository65 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/building-agents/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms-full.txtllms.txt
- llms.txtllms.txt
- adding-guardrailsSkill
- agent-health-timeoutSkill
- agent-permission-scopingSkill
- agent-session-isolationSkill
- agent-step-loggingSkill
- agent-supervisor-routerSkill
- agent-telemetrySkill
- async-agent-backgroundSkill
- building-agentsSkill
- building-teamsSkill
- building-toolsSkill
- calendar-scheduling-toolSkill
- callback-tracing-handlerSkill
- chain-of-thought-promptingSkill
- chat-model-configurationSkill
- code-execution-sandboxSkill
- common-agent-patternsSkill
- context-window-managementSkill
- conversation-memorySkill
- conversation-state-dbSkill
- database-query-toolSkill
- document-loadersSkill
- document-rerankingSkill
- email-notification-toolSkill
- embedding-model-ingestionSkill
- fallback-model-chainSkill
- few-shot-injectionSkill
- filesystem-toolSkill
- human-in-the-loopSkill
- hybrid-searchSkill
- inspecting-streamsSkill
- integrating-with-laurenSkill
- json-schema-enforcementSkill
- llm-provider-connectionSkill
- llm-rate-limitingSkill
- long-term-vector-memorySkill
- migrating-to-lauren-aiSkill
- multi-agent-delegationSkill
- multi-tool-orchestrationSkill
- multi-turn-tool-stateSkill
- output-guardrailsSkill
- plan-and-execute-agentSkill
- prompt-injection-defenseSkill
- prompt-versioningSkill
- rag-pipelineSkill
- react-agent-loopSkill
- response-validation-retrySkill
- rest-api-toolSkill
- securing-agentsSkill
- semantic-cacheSkill
- streaming-response-handlerSkill
- structured-output-parsingSkill
- sub-agent-spawningSkill
- system-prompt-templatingSkill
- testing-agentsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 75
Use ConversationStore to persist full message history across multiple agent runs within a session.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Use
codemap find "SymbolName"to locate any symbol before reading — it gives exact file + line range and is faster than grep across the whole repo.
Managing Memory in Agents
Memory tier overview
| Tier | Class | Scope | Persistence | Managed by |
| 1. Short-term | ShortTermMemory | Single agent run | None — resets each run | AgentRunner (automatic) |
| 2. Conversation | ConversationStore / InMemoryConversationStore | Session (conversation ID) | In-memory or custom backend | Application |
| 3. User memory | UserMemoryStore / InMemoryUserMemoryStore + @remember | Per user (user ID) | In-memory or custom backend | @remember decorator |
| 4. Vector | InMemoryVectorStore | Application-wide | In-memory | Application |
Quick start: @remember for long-term user facts
from lauren_ai import (
agent, remember, use_guardrails, use_tools,
InMemoryUserMemoryStore, PromptInjectionFilter,
)
_memory = InMemoryUserMemoryStore()
@agent(model="claude-opus-4-6", system="You are a personal assistant.")
@remember(store=_memory, extract=True, inject=True, top_k=5)
@use_guardrails(input=[PromptInjectionFilter()])
@use_tools(my_tool)
class PersonalAssistant: ...How it works:
- Inject (
inject=True): Before each LLM call,top_krelevant facts are retrieved from the store and prepended to the system prompt as:## What I remember about you: - User prefers dark mode (confidence: high) - User works on Python projects (confidence: medium) - Extract (
extract=True): After each conversation turn, the LLM extracts new facts from the exchange and stores them.
Decorator order (mandatory)
@remember() must sit between @agent() and @use_guardrails():
@agent(model="claude-opus-4-6") # outermost — applied last
@remember(store=_memory, ...) # reads/sets REMEMBER_META
@use_guardrails(input=[...]) # optional
@use_tools(my_tool) # innermost — applied first
class MyAgent: ...Python applies decorators bottom-up. Wrong ordering causes the decorator that reads metadata to run before the decorator that writes it, silently dropping tools, guardrails, or memory configuration.
Tier 2: Conversation history across runs
Use ConversationStore to persist full message history across multiple agent
runs within a session. Declare it on the agent (or override it per call):
from lauren_ai import agent, InMemoryConversationStore
store = InMemoryConversationStore()
@agent(model="claude-opus-4-6", conversation_store=store)
class MyAgent: ...Then pass a conversation_id on each run() call — the runner loads prior
history before the new message and saves afterward:
# Turn 1
result1 = await runner.run(agent, "My name is Alice.", conversation_id="sess-1")
# Turn 2 — agent sees the full prior exchange
result2 = await runner.run(agent, "What is my name?", conversation_id="sess-1")
# result2.content → "Your name is Alice."Without conversation_store, conversation_id is accepted but ignored.
Tier 4: Vector store for RAG
from lauren_ai import InMemoryVectorStore
store = InMemoryVectorStore()
# Index documents (requires EmbedService)
await store.add(
texts=["Python is a programming language.", "FastAPI is an async web framework."],
embed_service=embed_service,
)
# Query
results = await store.search(
query="web development with Python",
embed_service=embed_service,
top_k=3,
)
for doc, score in results:
print(f"{score:.3f} — {doc}")Reference
See memory.md for:
- Full
ShortTermMemoryAPI (includingctx.memoryaccess from lifecycle hooks) ConversationStoreprotocol and implementing a custom persistent backend@rememberparameters (store,extract,inject,top_k,store_token)- Manual
store.add()/store.search()usage withMemoryFact - Implementing a custom
UserMemoryStore(e.g. Postgres-backed) InMemoryVectorStorefull APITeamMemoryshared state for multi-agent teams
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

