Guides & Articles
Drop-in persistent memory for AI agents. Framework guides and integration patterns.
- Short-Term vs Long-Term Memory for AI Agents
Designer deciding memory architecture — what goes in-context, what goes in KV, what goes in vector DB.
- BotWire Memory vs Pinecone: When to Use Which
Dev comparing options, confused about when vector DBs are overkill for simple state.
- Agent Observability: Audit Logs + Memory Snapshots
DevOps-minded dev wanting to understand what their agent did, why, and replay its state.
- AgentOps + BotWire: Observability + Durable State
AgentOps user who needs persistent state separate from session traces.
- Persistent Memory for Agno (formerly Phidata) Agents
Agno/Phidata user needing memory that survives across agent runs.
- Cutting AI Agent Costs with Persistent Memory
Cost-conscious dev whose agent re-asks the same questions every run, burning tokens.
- Evaluating AI Agents Over Time: Memory as Ground Truth
ML engineer trying to benchmark agent quality across versions using persisted state.
- AI Agent Memory: BotWire vs Redis vs Vector DBs
Dev evaluating options, currently considering Redis/Pinecone. Needs decision framework.
- Scheduled AI Agent Tasks (Cron) with Persistent State
Dev running AI agents on cron that need to pick up where they left off last run.
- Managing AI Agent Session State in FastAPI
Backend dev shipping an AI agent via FastAPI who needs per-user session state.
- Testing AI Agents: Memory Fixtures and Replay
Engineer who wants deterministic tests for agents that depend on accumulated state.
- How to Store Per-User Preferences for AI Agents
Product builder who wants their agent to remember each user's preferences across sessions.
- Arize Phoenix + Agent Memory: Tracing Stateful Agents
Arize Phoenix user tracing agent behavior across sessions.
- Adding Memory to AutoGen Agents
AutoGen user whose agents lose conversation across restarts. Wants a one-class fix.
- BotWire vs LangMem: When Simplicity Wins
LangChain user comparing their new LangMem to simpler external KV backends.
- BotWire vs Mem0: Picking the Right AI Memory Tool
Dev evaluating Mem0 vs simpler KV alternatives. Wants honest trade-offs.
- BotWire vs Zep: Comparing AI Agent Memory Backends
Dev who tried Zep but finds it overkill for simple use cases.
- Braintrust Evals for Agents with Persistent State
Braintrust user evaluating agents whose output depends on accumulated memory.
- Browserbase Agents With Persistent Memory
Browserbase/Stagehand user whose browser-automation agents lose state between runs.
- Giving Claude Agents Persistent Memory Between Sessions
Anthropic SDK user building agents with Claude whose context vanishes each script run.
- BotWire Memory Cookbook - 20 Recipes
Copy-paste recipes for persistent memory patterns.
- Persistent Memory for CrewAI Agents (Cross-Session State)
CrewAI developer whose crew forgets everything between kickoff() calls. Needs memory that survives.
- Building a Discord Bot With AI Memory (Per User, Per Channel)
Discord bot dev whose AI responses forget user context every restart.
- E2B Code Interpreter Agents + Persistent Memory
E2B user building code-interpreter agents that reset between sandboxed runs.
- BotWire FAQ: Memory, Pricing, Self-Hosting, Privacy
Anyone evaluating BotWire who has objections before adopting.
- Persistent Memory for Haystack Agents
Haystack user running agent pipelines that lose state between runs.
- Helicone + Memory: Tracking LLM Costs per Agent Namespace
Helicone user wanting to group LLM call costs by persistent agent namespace.
- Humanloop + Persistent Memory for Prompt Iteration
Humanloop user iterating prompts whose agents need persistent state.
- Stateful AI Workflows with Inngest + BotWire
Dev using Inngest for durable AI workflows that need long-term agent memory.
- How to Add Persistent Memory to LangChain Agents
Developer using LangChain whose agent loses all state when the script exits. Wants a drop-in solution.
- Langfuse + BotWire: Observability Meets Persistent Memory
Langfuse user who wants persistent state alongside LLM traces.
- LangGraph Persistent State Across Runs
LangGraph user whose stateful graph loses progress between process restarts.
- Persistent Memory for LlamaIndex Agents
LlamaIndex user whose QueryEngine/Agent loses context across calls. Wants drop-in persistence.
- Adding Persistent Memory to Mastra Agents
Mastra (TypeScript agent framework) user whose agent loses context between runs.
- Adding Persistent Memory to MCP Servers
Dev building MCP servers who needs state that survives server restarts.
- Modal.com AI Agents with Persistent Memory
Modal user building agents on their serverless GPU platform who needs cross-run state.
- Sharing Memory Between Multiple AI Agents
Builder with multiple agents who need a common memory pool. Think research-team or trading-team patterns.
- Multi-Tenant AI Agent Memory Patterns
SaaS dev building per-customer agents who needs clean tenant isolation.
- Adding External Memory to the OpenAI Assistants API
OpenAI Assistants API user who wants memory outside the thread — cross-thread, cross-user, searchable.
- Portkey Gateway + BotWire Memory: Gateway + State
Dev using Portkey as LLM gateway who also needs cross-invocation memory.
- Adding Persistent Memory to Pydantic AI Agents
Pydantic AI user who wants state between Agent.run() calls.
- Pydantic Graph Agents + Persistent State
Pydantic Graph user whose nodes need to share and persist state across executions.
- Simple Key-Value Store for Python AI Agents
Python dev who rejected Redis/Postgres as overkill and wants the simplest possible state.
- Give Claude Persistent Memory in 2 Minutes
Claude API user who wants a working persistent chat example in 2 minutes.
- BotWire + CrewAI Quickstart (2 Minutes)
CrewAI dev who wants literal copy-paste integration.
- BotWire + LangChain Quickstart (2 Minutes)
LangChain dev who wants a literal copy-paste 2-minute setup.
- BotWire Memory from Node.js (via fetch)
Node/TypeScript dev who wants to use BotWire before the official JS SDK ships.
- RAG + Memory: When to Use Each (and Both)
AI engineer confused about when a vector DB beats a KV store and when you need both.
- Giving Replit Agents Persistent Memory
Replit dev building agents that restart from scratch every time the Repl wakes up.
- Persistent Memory for Semantic Kernel Agents
Semantic Kernel user who needs memory that survives restarts across C#/Python kernels.
- State for Serverless AI Agents (Lambda, Cloud Run, Vercel)
Dev running agents on ephemeral serverless compute that resets every invocation.
- Slack Bot With AI Memory (Per User, Per Channel)
Slack bot dev whose AI answers forget channel context every deploy.
- Streaming LLM Chats With Persistent Memory
Dev building a streaming chat UI (SSE/WebSocket) who needs memory that survives the stream.
- Telegram AI Bot With Persistent Memory Across Sessions
Telegram bot dev whose AI agent forgets chat history when the server restarts.
- Long-Running AI Agents with Temporal + Memory
Backend engineer running Temporal workflows for AI agents that span hours or days.
- Vercel AI SDK: Persistent Memory Across Sessions
Next.js dev using Vercel AI SDK whose chat state vanishes with every deployment.
- Persistent Memory for Voice AI Agents (ElevenLabs, Vapi, Retell)
Voice agent builder whose AI phone agent forgets every call.
- WhatsApp AI Assistant With Persistent Memory
Dev building a WhatsApp AI via Twilio/Meta whose chat history vanishes on restart.
- Why AI Agents Forget Everything (And How to Fix It)
Dev searching for explanation + solution. Educational but actionable.