conversation-state-db
Skill0 starsChanged 6 months agoMITView on GitHub
Persists conversation history to a database (SQLite/Postgres) via a custom ConversationStore implementation. Use when conversation history must survive process restarts, implementing a production database-backed store, or replacing InMemoryConversationStore with durable storage.
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
- 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
- managing-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
2 rules. About 0 are common, 0 are distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 131
Always create the schema before first use.
- Very specific: line 139
Test the store directly without an agent — just call save and load:
≈ “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.
Conversation State Serialization to Database
Overview
InMemoryConversationStore is convenient for development but loses all history
on process restart. Replace it with a database-backed implementation that
satisfies the ConversationStore protocol.
SQLite implementation (aiosqlite)
import asyncio
import json
import time
import aiosqlite
from lauren_ai._memory import ConversationStore
class SQLiteConversationStore:
"""Persist conversation history to SQLite via aiosqlite."""
def __init__(self, db_path: str = ":memory:"):
self._db_path = db_path
self._initialized = False
async def _ensure_init(self) -> None:
if not self._initialized:
async with aiosqlite.connect(self._db_path) as db:
await db.execute("""
CREATE TABLE IF NOT EXISTS conversations (
id TEXT NOT NULL,
messages TEXT NOT NULL,
updated_at REAL NOT NULL
)
""")
await db.commit()
self._initialized = True
async def save(self, conversation_id: str, messages: list) -> None:
await self._ensure_init()
async with aiosqlite.connect(self._db_path) as db:
await db.execute(
"INSERT OR REPLACE INTO conversations (id, messages, updated_at) VALUES (?, ?, ?)",
(conversation_id, json.dumps(messages), time.time()),
)
await db.commit()
async def load(self, conversation_id: str) -> list:
await self._ensure_init()
async with aiosqlite.connect(self._db_path) as db:
async with db.execute(
"SELECT messages FROM conversations WHERE id = ?",
(conversation_id,),
) as cursor:
row = await cursor.fetchone()
return json.loads(row[0]) if row else []
async def delete(self, conversation_id: str) -> None:
await self._ensure_init()
async with aiosqlite.connect(self._db_path) as db:
await db.execute("DELETE FROM conversations WHERE id = ?", (conversation_id,))
await db.commit()Wiring with an agent
store = SQLiteConversationStore(db_path="/tmp/conversations.db")
@agent(model="claude-opus-4-6", conversation_store=store)
class SupportAgent: ...
resp = await runner.run(SupportAgent(), "Hello", conversation_id="user-42")Postgres implementation (asyncpg)
For production multi-worker deployments, replace SQLite with Postgres. The interface is identical — only the driver changes:
import asyncpg
import json
class PostgresConversationStore:
def __init__(self, dsn: str):
self._dsn = dsn
self._pool = None
async def _pool(self):
if self._pool is None:
self._pool = await asyncpg.create_pool(self._dsn)
return self._pool
async def save(self, conversation_id: str, messages: list) -> None:
pool = await self._get_pool()
async with pool.acquire() as conn:
await conn.execute(
"""
INSERT INTO conversations (id, messages, updated_at)
VALUES ($1, $2, NOW())
ON CONFLICT (id) DO UPDATE
SET messages = $2, updated_at = NOW()
""",
conversation_id,
json.dumps(messages),
)
# ... load/delete follow the same patternSchema migrations
Always create the schema before first use. The pattern above uses
CREATE TABLE IF NOT EXISTS as a simple idempotent migration. For production,
use a dedicated migration tool (Alembic, Flyway).
Testing
Test the store directly without an agent — just call save and load:
store = SQLiteConversationStore(db_path=":memory:")
messages = [{"role": "user", "content": "hello"}]
await store.save("s1", messages)
loaded = await store.load("s1")
assert loaded == messagesReference
lauren_ai._memory:ConversationStore(protocol)lauren_ai._memory._stores:InMemoryConversationStore(reference implementation)- Skills:
conversation-memory,managing-memory
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.

