/` as `/memories/user` the same way as deploy. When you update the Managed Deep Agents SDK in your project, rebuild so `.mda/build/__runtime__` picks up the new runtime. The runtime is copied at compile time, so SDK changes do not take effect until you rebuild.
## Disable managed memory
Use `disableMemory` for stateless agents or when you manage persistence externally. Set `disableMemory` / `disable_memory` on the agent definition to skip hot injection and the `/memories/user` memory wiring. Identity `scoping.memory: "none"` also disables the mount.
```python agent.py theme={null}
from managed_deepagents import define_deep_agent
agent = define_deep_agent(
name="stateless-agent",
model="openai:gpt-5.5",
disable_memory=True,
)
```
```ts agent.ts theme={null}
import { defineDeepAgent } from "managed-deepagents";
export const agent = defineDeepAgent({
name: "stateless-agent",
model: "openai:gpt-5.5",
disableMemory: true,
});
```
## Deploy and Context Hub
On `mda deploy`, Managed Deep Agents syncs deploy-owned `instructions.md` and `skills/**` into the Context Hub agent repo and seeds agent memory when needed. Existing `memories/**` content is preserved. The sync and seeding behavior mirrors [local development](#local-development). For the deploy lifecycle, see [How Managed Deep Agents work](/langsmith/managed-deep-agents-how-it-works#context-hub) and the [CLI memory note](/langsmith/managed-deep-agents-cli#memory).
## Test and deploy
Test the project locally with [`mda dev`](/langsmith/managed-deep-agents-cli#develop-locally), then deploy it with [`mda deploy`](/langsmith/managed-deep-agents-deploy). Open deployment traces in LangSmith to inspect model calls, tool calls, errors, and latency.
## Troubleshooting
If the agent claims to remember something but the fact is missing in a new thread, check the agent's traces for `edit_file` or `write_file` tool calls on `/memories/user/AGENTS.md`. Confirm the call succeeded and that the target path is under `/memories/user/`. Verify that identity scoping is configured correctly. Writes outside the remounted slice are denied.
If hot memory at `/memories/user/AGENTS.md` grows too large, it consumes tokens from every request's system prompt. Move detailed content to cold files under `/memories/user/archive/` and keep only preferences and pointers in hot memory.
This is a misconfiguration, not a platform issue. Verify that `scoping.memory` is set to `actor` or `tenant` (not `agent`). Check that the identity declaration is present and that the ingress mode correctly resolves the caller. Inspect `runtime.identity` in traces to confirm the resolved actor and tenant ids. For more information, see [Identity](/langsmith/managed-deep-agents-identity).
The runtime creates `/memories/user/AGENTS.md` from the seed template only when the file does not already exist. If a user reports overwritten content, the file was likely absent when the slice was first accessed, so the runtime seeded a fresh copy. Deploy never overwrites existing `memories/**` files.
## Next steps
Partition memory per actor or tenant with `scoping.memory`.
See how Context Hub, threads, and deploy sync fit together.
Look up project files, `disableMemory`, and deploy behavior.
Read `runtime.identity` when tools need the caller id.
***
[Connect these docs](/use-these-docs) to Claude, VSCode, and more via MCP for real-time answers.
[Edit this page on GitHub](https://github.com/langchain-ai/docs/edit/main/src/langsmith/managed-deep-agents-memory.mdx) or [file an issue](https://github.com/langchain-ai/docs/issues/new/choose).