Cross-Account Memory and Repo Data Persist After Logout (Local Device)

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I sign out of Cursor with Account A and then sign in with Account B on the same device, Cursor still loads private data from Account A. This includes:
• Agent “memory”
• Repo insights and architectural notes
• Historical project context from months earlier
• Coding preferences and behavioural rules

All of this shows up inside Account B’s session, even though they are completely separate accounts and projects.

This means Cursor is storing memory/context at the device level and not clearing or re-keying it on logout, causing cross-account data leakage.

Steps to Reproduce

  1. Log in to Cursor with Account A.
    2. Open a repo and use the AI features so Cursor builds up agent memory and project context.
    3. Log out of Account A using the Cursor UI.
    4. Log in with Account B on the same device.
    5. Open a new repo or start a new chat.
    6. Ask Cursor a general question (e.g., “What do you remember?”) or inspect its suggestions.
    7. Observe that Cursor still shows agent memories, repo context, and architectural details that clearly belong to Account A.

Expected Behavior

When logging out of one Cursor account and logging into another:
• All data from the previous account should be fully isolated and inaccessible.
• Cursor should load only the new account’s own chat history, agent memory, repo context, and preferences.
• Any local caches, embeddings, or long-term memory tied to the previous account should be cleared, re-keyed, or sandboxed per account.
• The new session should behave as a clean, separate user environment, with no crossover from the previous account.

In other words, logging out should completely sever access to the prior user’s memory, context, and project data.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

ersion: 2.1.19 (Universal)
VSCode Version: 1.105.1
Commit: 39a966b4048ef6b8024b27d4812a50d88de29cc0
Date: 2025-11-21T22:59:02.376Z (1 wk ago)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

N/A

For AI issues: add Request ID with privacy disabled

N/A

Additional Information

N/A

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

Hey, thanks for the report. This isn’t a bug - Cursor stores all chats and settings locally on the device, not tied to the account.

When you switch accounts on the same device, local data stays in place - it doesn’t get cleared on logout, because it’s device/workspace level data, not cloud-based.

Solution - use separate profiles via --user-data-dir That way, you’ll have fully isolated sessions for each account (own chats, settings, extensions, logins).

More details: Seamless Account Switching in Cursor - #19 by danperks