Please prioritize account-level sync for Agent/Chat history across devices.
My setup: I use the same Cursor account on multiple machines, and connect via Remote SSH to the same server. Code and environment follow me everywhere, but chat/agent history stays on the local UI machine. Switching laptops means losing context even though I am working on the same remote project.
Why this matters:
Remote SSH users already share code/server state; chat context is now equally important for continuity
Other AI tools (and even Codex in the same IDE) can continue conversations across machines via account/cloud
This is one of the most requested workflows for people who move between office/home laptops
Expected behavior:
Chat/Agent history tied to Cursor account + project (not only local disk)
Opening the same remote workspace on another machine shows the same conversation list
Optional: selective sync / privacy controls
I understand this is already “on your radar.” Even a simple opt-in cloud sync (or official export/import that preserves native chat UI) would help a lot until full sync ships.
Thanks for considering this — it would make Cursor much more usable for multi-device + SSH workflows.
I use Cursor from two different devices (a Windows desktop and a MacBook), both connecting to the same Linux development server via Remote SSH.
Currently, project-related configurations such as Skills, MCP configuration, and Rules can all live on the remote server, so both devices share the same development environment seamlessly.
However, Agent Chat sessions are still stored locally on each client. As a result, when I switch from one device to another, I lose all ongoing Agent conversations, even though I’m working on the exact same remote workspace.
Instead of cloud synchronization, I’d like to suggest an optional “Remote Session Storage” mode for Remote SSH development.
For example:
Local (current behavior)
Remote workspace (store Agent sessions on the remote server)
(Optional) Custom location
This would allow developers using multiple clients to continue the same Agent session simply by reconnecting to the same remote workspace.
From my perspective, Agent sessions are part of the project workspace, much like Skills, MCP configuration, and Rules. Keeping them alongside the remote workspace would make the Remote SSH experience much more seamless, especially for developers who regularly switch between desktop and laptop while connecting to the same development server.
This approach also has some advantages over cloud synchronization:
No need to upload chat history to Cursor’s servers.
Works well in enterprise environments where all development happens on remote machines.
Keeps all project-related state together with the remote workspace.
Hey, thanks for the detailed feature request, especially the specifics around Remote SSH.
Quick status update: chat and agent history is stored locally in per-workspace storage tied to the workspace path, including the SSH authority. So when you switch machines, the context doesn’t move over, even if your code and environment are on the same remote server. Cloud or cross-device sync is one of the most common requests and it’s on the team’s radar, but I can’t share a specific timeline yet.
Also, your idea of Remote Session Storage, keeping sessions next to the remote workspace without uploading to the cloud, is a great privacy-friendly option.
For now, as a temporary workaround, per-chat export to markdown is available. It won’t replace full sync, but it helps you save the context from important sessions.