" });
// Schedule consolidation 30 minutes after the conversation
await client.runs.create(
thread.thread_id,
"consolidation_agent",
{
input: { messages: [{ role: "user", content: "Consolidate recent memories." }] },
afterSeconds: 1800,
},
);
// If the user sends another message, use rollback on the new run
// to delete the pending consolidation run before starting
const stream = client.runs.stream(
thread.thread_id,
"agent",
{
input: { messages: [{ role: "user", content: newMessage }] },
multitaskStrategy: "rollback",
},
);
```
See [double texting](/langsmith/double-texting) for details on how `multitask_strategy` controls the behavior of concurrent runs on the same thread.
For more on deploying agents with background processes, see [going to production](/oss/javascript/deepagents/going-to-production).
### Read-only vs writable memory
By default, the agent can both read and write memory files. For shared state like organization policies or compliance rules, you may want to make memory **read-only** so the agent can reference it but not modify it. This prevents prompt injection via shared memory and ensures that only your application code controls what's in the file.
| Permission | Use case | How it works |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Read-write** (default) | User preferences, agent self-improvement, learned [skills](/oss/javascript/deepagents/skills) | Agent updates files via `edit_file` tool |
| **Read-only** | Organization policies, compliance rules, shared knowledge bases, developer-defined [skills](/oss/javascript/deepagents/skills) | Populate via application code or the [Store API](/langsmith/custom-store). Use [policy hooks](/oss/javascript/deepagents/backends#add-policy-hooks) to block agent writes. |
**Security considerations:** If one user can write to memory that another user reads, a malicious user could inject instructions into shared state. To mitigate this:
* **Default to user scope** `(user_id)` unless you have a specific reason to share
* Use **read-only memory** for shared policies (populate via application code, not the agent)
* Add **human-in-the-loop** validation before the agent writes to shared memory. Use an [interrupt](/oss/javascript/langgraph/capabilities/human-in-the-loop) to require human approval for writes to sensitive paths.
To enforce read-only memory, use [policy hooks](/oss/javascript/deepagents/backends#add-policy-hooks) on the backend to reject write operations to specific paths.
### Concurrent writes
Multiple threads can write to memory in parallel, but concurrent writes to the **same file** can cause last-write-wins conflicts. For user-scoped memory this is rare since users typically have one active conversation at a time. For agent-scoped or organization-scoped memory, consider using [background consolidation](#background-consolidation) to serialize writes, or structure memory as separate files per topic to reduce contention.
In practice, if a write fails due to a conflict, the LLM is usually smart enough to retry or recover gracefully, so a single lost write is not catastrophic.
### Multiple agents in the same deployment
To give each agent its own memory in a shared deployment, add `assistant_id` to the namespace:
```typescript theme={null}
new StoreBackend({
namespace: (ctx) => {
const config = getConfig();
return [config.metadata.assistantId, ctx.runtime.context.userId];
},
})
```
Use `(assistant_id,)` alone if you only need per-agent isolation without per-user scoping.
Use [LangSmith tracing](/langsmith/tracing) to audit what your agent writes to memory. Every file write appears as a tool call in the trace.
***
[Edit this page on GitHub](https://github.com/langchain-ai/docs/edit/main/src/oss/deepagents/memory.mdx) or [file an issue](https://github.com/langchain-ai/docs/issues/new/choose).
[Connect these docs](/use-these-docs) to Claude, VSCode, and more via MCP for real-time answers.