deep-agents-memory

Pluggable memory and file backends for Deep Agents with ephemeral, persistent, and hybrid routing options. Four backend types: StateBackend (thread-scoped, ephemeral), StoreBackend (cross-session persistent), FilesystemBackend (real disk access for local dev), and CompositeBackend (route different paths to different backends) FilesystemMiddleware provides six file operation tools: ls , read_file , write_file , edit_file , glob , grep CompositeBackend uses longest-prefix matching to route...

npx skills add https://github.com/langchain-ai/langchain-skills --skill deep-agents-memory
Deep Agents use pluggable backends for file operations and memory:

Short-term (StateBackend): Persists within a single thread, lost when thread ends Long-term (StoreBackend): Persists across threads and sessions Hybrid (CompositeBackend): Route different paths to different backends

FilesystemMiddleware provides tools: ls, read_file, write_file, edit_file, glob, grep

Use CaseBackendWhy
Temporary working filesStateBackendDefault, no setup
Local development CLIFilesystemBackendDirect disk access
Cross-session memoryStoreBackendPersists across threads
Hybrid storageCompositeBackendMix ephemeral + persistent
Default StateBackend stores files ephemerally within a thread.
from deepagents import create_deep_agent

agent = create_deep_agent()  # Default: StateBackend
result = agent.invoke({
    "messages": [{"role": "user", "content": "Write notes to /draft.txt"}]
}, config={"configurable": {"thread_id": "thread-1"}})
# /draft.txt is lost when thread ends
Default StateBackend stores files ephemerally within a thread.
import { createDeepAgent } from "deepagents";

const agent = await createDeepAgent();  // Default: StateBackend
const result = await agent.invoke({
  messages: [{ role: "user", content: "Write notes to /draft.txt" }]
}, { configurable: { thread_id: "thread-1" } });
// /draft.txt is lost when thread ends
Configure CompositeBackend to route paths to different storage backends.
from deepagents import create_deep_agent
from deepagents.backends import CompositeBackend, StateBackend, StoreBackend
from langgraph.store.memory import InMemoryStore

store = InMemoryStore()

composite_backend = lambda rt: CompositeBackend(
    default=StateBackend(rt),
    routes={"/memories/": StoreBackend(rt)}
)

agent = create_deep_agent(backend=composite_backend, store=store)

# /draft.txt -> ephemeral (StateBackend)
# /memories/user-prefs.txt -> persistent (StoreBackend)
Configure CompositeBackend to route paths to different storage backends.
import { createDeepAgent, CompositeBackend, StateBackend, StoreBackend } from "deepagents";
import { InMemoryStore } from "@langchain/langgraph";

const store = new InMemoryStore();

const agent = await createDeepAgent({
  backend: (config) => new CompositeBackend(
    new StateBackend(config),
    { "/memories/": new StoreBackend(config) }
  ),
  store
});

// /draft.txt -> ephemeral (StateBackend)
// /memories/user-prefs.txt -> persistent (StoreBackend)
Files in /memories/ persist across threads via StoreBackend routing.
# Using CompositeBackend from previous example
config1 = {"configurable": {"thread_id": "thread-1"}}
agent.invoke({"messages": [{"role": "user", "content": "Save to /memories/style.txt"}]}, config=config1)

config2 = {"configurable": {"thread_id": "thread-2"}}
agent.invoke({"messages": [{"role": "user", "content": "Read /memories/style.txt"}]}, config=config2)
# Thread 2 can read file saved by Thread 1
Files in /memories/ persist across threads via StoreBackend routing.
// Using CompositeBackend from previous example
const config1 = { configurable: { thread_id: "thread-1" } };
await agent.invoke({ messages: [{ role: "user", content: "Save to /memories/style.txt" }] }, config1);

const config2 = { configurable: { thread_id: "thread-2" } };
await agent.invoke({ messages: [{ role: "user", content: "Read /memories/style.txt" }] }, config2);
// Thread 2 can read file saved by Thread 1
Use FilesystemBackend for local development with real disk access and human-in-the-loop.
from deepagents import create_deep_agent
from deepagents.backends import FilesystemBackend
from langgraph.checkpoint.memory import MemorySaver

agent = create_deep_agent(
    backend=FilesystemBackend(root_dir=".", virtual_mode=True),  # Restrict access
    interrupt_on={"write_file": True, "edit_file": True},
    checkpointer=MemorySaver()
)

# Agent can read/write actual files on disk
Use FilesystemBackend for local development with real disk access and human-in-the-loop.
import { createDeepAgent, FilesystemBackend } from "deepagents";
import { MemorySaver } from "@langchain/langgraph";

const agent = await createDeepAgent({
  backend: new FilesystemBackend({ rootDir: ".", virtualMode: true }),
  interruptOn: { write_file: true, edit_file: true },
  checkpointer: new MemorySaver()
});

Security: Never use FilesystemBackend in web servers - use StateBackend or sandbox instead.

Access the store directly in custom tools for long-term memory operations.
from langchain.tools import tool, ToolRuntime
from langchain.agents import create_agent
from langgraph.store.memory import InMemoryStore

@tool
def get_user_preference(key: str, runtime: ToolRuntime) -> str:
    """Get a user preference from long-term storage."""
    store = runtime.store
    result = store.get(("user_prefs",), key)
    return str(result.value) if result else "Not found"

@tool
def save_user_preference(key: str, value: str, runtime: ToolRuntime) -> str:
    """Save a user preference to long-term storage."""
    store = runtime.store
    store.put(("user_prefs",), key, {"value": value})
    return f"Saved {key}={value}"

store = InMemoryStore()

agent = create_agent(
    model="gpt-4.1",
    tools=[get_user_preference, save_user_preference],
    store=store
)
### What Agents CAN Configure
  • Backend type and configuration
  • Routing rules for CompositeBackend
  • Root directory for FilesystemBackend
  • Human-in-the-loop for file operations

What Agents CANNOT Configure

  • Tool names (ls, read_file, write_file, edit_file, glob, grep)
  • Access files outside virtual_mode restrictions
  • Cross-thread file access without proper backend setup
StoreBackend requires a store instance.
# WRONG
agent = create_deep_agent(backend=lambda rt: StoreBackend(rt))

# CORRECT
agent = create_deep_agent(backend=lambda rt: StoreBackend(rt), store=InMemoryStore())
StoreBackend requires a store instance.
// WRONG
const agent = await createDeepAgent({ backend: (c) => new StoreBackend(c) });

// CORRECT
const agent = await createDeepAgent({ backend: (c) => new StoreBackend(c), store: new InMemoryStore() });
StateBackend files are thread-scoped - use same thread_id or StoreBackend for cross-thread access.
# WRONG: thread-2 can't read file from thread-1
agent.invoke({"messages": [...]}, config={"configurable": {"thread_id": "thread-1"}})  # Write
agent.invoke({"messages": [...]}, config={"configurable": {"thread_id": "thread-2"}})  # File not found!
StateBackend files are thread-scoped - use same thread_id or StoreBackend for cross-thread access.
// WRONG: thread-2 can't read file from thread-1
await agent.invoke({ messages: [...] }, { configurable: { thread_id: "thread-1" } });  // Write
await agent.invoke({ messages: [...] }, { configurable: { thread_id: "thread-2" } });  // File not found!
Path must match CompositeBackend route prefix for persistence.
# With routes={"/memories/": StoreBackend(rt)}:
agent.invoke(...)  # /prefs.txt -> ephemeral (no match)
agent.invoke(...)  # /memories/prefs.txt -> persistent (matches route)
Path must match CompositeBackend route prefix for persistence.
// With routes: { "/memories/": StoreBackend }:
await agent.invoke(...);  // /prefs.txt -> ephemeral (no match)
await agent.invoke(...);  // /memories/prefs.txt -> persistent (matches route)
Use PostgresStore for production (InMemoryStore lost on restart).
# WRONG                              # CORRECT
store = InMemoryStore()              store = PostgresStore(connection_string="postgresql://...")
Use PostgresStore for production (InMemoryStore lost on restart).
// WRONG                                    // CORRECT
const store = new InMemoryStore();          const store = new PostgresStore({ connectionString: "..." });
Enable virtual_mode=True to restrict path access (prevents ../ and ~/ escapes).
backend = FilesystemBackend(root_dir="/project", virtual_mode=True)  # Secure
CompositeBackend matches longest prefix first.
routes = {"/mem/": StoreBackend(rt), "/mem/temp/": StateBackend(rt)}
# /mem/file.txt -> StoreBackend, /mem/temp/file.txt -> StateBackend (longer match)

Más skills de langchain-ai

langgraph-docs
langchain-ai
Accede a la documentación de LangGraph para construir agentes con estado y flujos de trabajo multiagente. Obtiene la documentación oficial de LangGraph en Python que cubre máquinas de estado, diseño de agentes basado en grafos y patrones de intervención humana. Prioriza la documentación relevante según el tipo de consulta: guías de implementación para preguntas de procedimiento, páginas conceptuales para teoría, tutoriales para ejemplos completos y referencias de API para detalles técnicos. Selecciona automáticamente de 2 a 4 URL de documentación más relevantes y recupera su contenido para responder...
official
langgraph-human-in-the-loop
langchain-ai
Pausar la ejecución del grafo para revisión, aprobación o validación humana, luego reanudar con su entrada. Requiere tres componentes: un checkpointer (InMemorySaver o PostgresSaver), un ID de hilo en la configuración y cargas de interrupción serializables en JSON. interrupt(value) pausa y expone datos; Command(resume=value) reanuda y devuelve ese valor al nodo pausado. Todo el código antes de interrupt() se re-ejecuta al reanudar, por lo que los efectos secundarios deben ser idempotentes (usar upsert, no insert). Soporta flujos de aprobación,...
official
web-research
langchain-ai
Usa esta habilidad para solicitudes relacionadas con investigación web; proporciona un enfoque estructurado para realizar investigaciones web exhaustivas.
official
langchain-oss-primer
langchain-ai
SIEMPRE EMPIEZA AQUÍ para cualquier proyecto de construcción de agentes LangChain, Deep Agents o LangGraph. Punto de partida requerido antes de elegir otras habilidades o escribir cualquier…
official
skill-creator
langchain-ai
Guía para crear habilidades efectivas que extiendan las capacidades del agente con conocimientos especializados, flujos de trabajo o integraciones de herramientas. Usa esta habilidad cuando el usuario…
official
social-media
langchain-ai
Redacta publicaciones para redes sociales específicas de cada plataforma, con contenido respaldado por investigación e imágenes complementarias generadas. Admite publicaciones de LinkedIn (1.300 caracteres con tono profesional) e hilos de Twitter/X (280 caracteres por tuit con formato 1/🧵). Requiere delegar la investigación a un subagente antes de redactar, y luego leer los hallazgos para garantizar precisión y relevancia. Genera automáticamente imágenes llamativas para redes sociales usando la herramienta generate_social_image con composiciones audaces y de alto contraste optimizadas para tamaños pequeños...
official
deep-agents-memory
langchain-ai
Backends de memoria y archivos conectables para Deep Agents con opciones de enrutamiento efímero, persistente e híbrido. Cuatro tipos de backend: StateBackend (efímero, con ámbito de hilo), StoreBackend (persistente entre sesiones), FilesystemBackend (acceso real a disco para desarrollo local) y CompositeBackend (enruta diferentes rutas a diferentes backends). FilesystemMiddleware proporciona seis herramientas de operación de archivos: ls, read_file, write_file, edit_file, glob, grep. CompositeBackend utiliza coincidencia de prefijo más largo para enrutar...
official
deep-agents-orchestration
langchain-ai
Orquestrar subagentes, planificar tareas de múltiples pasos y requerir aprobación humana para operaciones sensibles. Delegar trabajo a subagentes especializados mediante la herramienta de tareas; los subagentes personalizados admiten conjuntos de herramientas aislados y mensajes del sistema, mientras que el subagente "de propósito general" predeterminado hereda la configuración del agente principal. Planificar y rastrear flujos de trabajo complejos con write_todos, organizando tareas en estados pendientes, en curso y completados; requiere un thread_id para la persistencia entre invocaciones. Implementar...
official