Answer: The caveats are that all sessions and users share one journal so one person's messages can surface in another's session; turning memory off keeps existing records; anyone who can message the agent writes to the journal, so keep the scaffolded rule against following instructions found in records; and records can be dropped or arrive late, so keep state your code depends on in ctx.host.kv or ctx.host.files. Status: Confirmed Entry: tool/cursor/memory-and-context/memory-caveats Revision: 1 Digest: sha256:6e2705eb579097e2 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:08:58Z Last changed: 2026-11-13T03:08:58Z Last verified: 2026-11-20T12:34:00Z Next check: 2026-11-21T12:34:00Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Shared journal | All sessions and users share one journal | [1] | 2026-11-20 Memory off behavior | Turning memory off keeps existing records | [1] | 2026-11-20 Journal write access | Anyone who can message the agent writes to the journal | [1] | 2026-11-20 Record reliability | Records can be dropped or arrive late | [1] | 2026-11-20 Recommended state storage | ctx.host.kv | [1] | 2026-11-20 Sources: [1] Anysphere. "cursor.com/docs/agent-sdk/reference/memory.md". https://cursor.com/docs/agent-sdk/reference/memory.md Role: primary. Accessed: 2026-11-20T12:34:00Z Quote: "All sessions and users share one journal, so one person's messages" (Supports: Shared journal) Quote: "Turning memory off keeps existing records." (Supports: Memory off behavior) Quote: "Anyone who can message the agent writes to the journal, so keep the" (Supports: Journal write access) Quote: "Records can be dropped or arrive late." (Supports: Record reliability) Quote: "on in `ctx.host.kv` or `ctx.host.files`." (Supports: Recommended state storage) Snapshot SHA-256: 0399fb970d1abc2f3b694f4326c31475ca335f833c289c12f75d7c9ad313b525 (captured 2026-11-13T03:08:56Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:08:58Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:34:00Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:34:00Z Last attempt: 2026-11-20T12:34:00Z Notes and limitations: Extracted automatically from a single official source (section "Caveats"). Related: https://latestn.com/tool/cursor/memory-and-context/read-memory How does Cursor Agent SDK read memory? https://latestn.com/tool/cursor/models/add-claude-haiku-5-5-to-model-picker How do I add Claude Haiku 5.5 to the model picker in Cursor? https://latestn.com/tool/cursor/models/add-sonnet-5-5-to-model-picker How do I add Claude Sonnet 5.5 to the model picker in Cursor? https://latestn.com/tool/cursor/integrations/when-to-use-sdk-bridge When should I use the Cursor SDK Bridge instead of the TypeScript or Python SDK? https://latestn.com/tool/cursor/integrations/xcode-cursor-prerequisites What are the prerequisites for using Xcode with Cursor? https://latestn.com/tool/cursor/memory-and-context/disable-memory How do I turn off memory in Cursor Agent SDK? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:08:58Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cursor/memory-and-context/memory-caveats/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cursor/memory-and-context/memory-caveats POST: https://latestn.com/dispute/tool/cursor/memory-and-context/memory-caveats with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/memory-and-context/memory-caveats?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What are the caveats of using memory in Cursor Agent SDK? Revision 1, last verified 2026-11-20T12:34:00Z. https://latestn.com/tool/cursor/memory-and-context/memory-caveats (accessed 2026-11-21T09:55:11Z). @misc{LatestN_tool_cursor_memory_and_context_memory_caveats_r1, title = {What are the caveats of using memory in Cursor Agent SDK?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/memory-and-context/memory-caveats}}, note = {Revision 1; digest sha256:6e2705eb579097e2; last verified 2026-11-20T12:34:00Z; accessed 2026-11-21T09:55:11Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cursor/memory-and-context/memory-caveats