When running Cursor on Linux, especially with the AppImage version, you might encounter a situation where you can’t log in. This usually happens because Cursor stores its session state locally, and sometimes that state gets corrupted.

In this article, we’ll walk through how to diagnose the issue and reset your session state without losing your extensions, settings, or local code.

---

1. Where Cursor Stores Data on Linux

Like VS Code, Cursor saves its user configuration and state inside your home directory:

~/.config/Cursor/

Inside this directory, you’ll find:

• User/ → User settings, keybindings.
• User/globalStorage/ → Session state, extension storage.
• IndexedDB/ → Internal database used by extensions.
• Local Storage/ → Session and chat data.

These files do not contain your cloned repositories or project files, so it is safe to remove them.

2. First Check: Does the Folder Exist?

Confirm that Cursor’s config folder exists:

ls -la ~/.config | grep Cursor

If you see something like:

drwx------ 23 j j 4096 Sep 11 15:41 Cursor

it means Cursor’s user profile is stored there.

3. Resetting Session State (Safe Method)

If the problem is just that you can’t log in, you don’t need to delete the entire folder.
You can simply clear the session-related files:

# 1. Close Cursor if it’s running
pkill -f cursor

# 2. Remove session state and cached login data
rm -rf ~/.config/Cursor/User/globalStorage/state.vscdb*
rm -rf ~/.config/Cursor/IndexedDB
rm -rf ~/.config/Cursor/Local\ Storage

Next time you run ./cursor.appimage, Cursor will ask you to sign in again — but your settings and extensions will remain intact.