Urgent assistance required — Missing Cursor Cloud Agent sessions and development workspace

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Urgent assistance required — Missing Cursor Cloud Agent sessions and development workspace

Ticket number is T-H67010 given by Sam Cursor’s AI Support Assistant on 17/10/2026

Hello Cursor Team,

I’m raising this publicly after contacting Cursor Support by email and not yet receiving a response.

I’ve been using Cursor extensively to develop PEIGIAN V2, a premium ecommerce website built using Next.js, React and TypeScript.

Unfortunately, two recent Cloud Agent sessions have disappeared from my Cursor history, and I have lost access to several weeks of development work, including locally committed Git changes, uncommitted source files and original product assets.

I’m particularly concerned that the original development environment may still be recoverable, but any retained environment data could potentially expire before the issue is investigated.

1. Timeline of events

September–16 October 2026 — Original development

Over several weeks, we developed and tested the website through multiple stages:

  • Phase 1: Visual foundation and design system
  • Phase 2: Shared header, navigation and footer
  • Phase 3: Homepage and Device Finder
  • Phase 4: CLARITY Privacy product page
  • Phase 5: LINK 240W product page
  • Phase 6: Screen Protection Collection
  • Phase 7: Device-aware cart improvements, CMS-ready content architecture and SHIELD Protective product page

We had completed six Git checkpoints and were working on further Phase 7 refinements.

The original application had passed its automated tests and production build, with 76 routes reported. We also reviewed the running website extensively on desktop and mobile.

17 October 2026 — Original development environment became inaccessible

Following a reconnection in Cursor, the original development branch and its local Git commits were no longer available.

The missing branch was:

cursor/peigian-v2-implementation

The last confirmed original Git commit was:

a807fe84b46de4793d03f8c9537c84f1622b339c

The previous Phase 5 checkpoint was:

b15f044ca86fed22a37392d996446affe1ec1cf6

These commits had been created inside the original Cursor Cloud Agent development environment, but had not yet been pushed to GitLab.

17 October 2026 — Replacement Agent attempted reconstruction

A replacement Agent reported that it could not find the original development branch.

It attempted to reconstruct the website using previous conversation transcripts.

Although it reported 296 passing tests, the reconstructed website differed substantially from the original and did not contain the original product photography.

17 October 2026 — Both recent Agent conversations disappeared

The original development session and the replacement reconstruction session subsequently disappeared from Cursor’s Agent history.

They had previously been visible in the Cursor desktop application.

I noticed the disappearance during interface navigation, but I cannot establish whether that navigation caused the issue.

Closing and reopening Cursor did not restore the sessions.

Older Agent conversations remain visible, but the two recent development sessions are missing.

2. What is inaccessible

The missing development environment contained:

  • The original Next.js application source.
  • Six locally committed development checkpoints.
  • Uncommitted Phase 7 changes.
  • Device-aware cart functionality and tests.
  • CMS-ready editorial content architecture.
  • The SHIELD Protective product page and responsive styling.
  • Original product photography and branded imagery.
  • Development and quality-assurance artefacts.

Particularly important were actual binary image files, including:

  • shield-protective-studio-01.webp
  • clarity-clear-studio-01.webp
  • clarity-privacy-studio-01.webp
  • clarity-ar-studio-01.webp
  • clarity-fingerprint-studio-01.webp

We have since independently recovered copies of several original images from separately saved design archives, but the actual October Cursor development workspace and its Git history remain inaccessible.

3. Forensic investigation already performed

I created a separate Cursor Cloud Agent specifically to carry out a read-only investigation.

The investigation established that:

  • The new Agent was running in a newly created Cloud environment.
  • It could enumerate only its own Cloud Agent session through the available tools.
  • It could not access the original or replacement development environments.
  • Neither of the missing Git commits was present in the new environment.
  • The development branch was not present among the available GitLab remote branches.
  • A separate Windows laptop checkout contained an older version of the project.
  • The original Phase 7 uncommitted files were not found in any accessible working tree.

The investigation did not identify any recoverable original Git objects or workspace snapshots within its available environment.

Importantly, it could not inspect Cursor’s backend retention systems or the original environments. Therefore, it could not establish whether the missing files had been permanently deleted.

I have a complete forensic report, including the investigation Agent ID, environment ID and executed commands, which I can provide privately.

4. Cursor Support already contacted

I sent an urgent recovery and data-preservation request to:

Original support escalation:
Sent to Cursor’s official support email address,
with the Background Agent feedback team copied.

Initial escalation: 17 October 2026
Status as of 21 October 2026: No response or support reference received.

The email included the original Git commit identifiers, missing development history, the lost image files, forensic investigation results and a request for urgent preservation of any recoverable workspace data.

I have also attempted to contact several Cursor employees through LinkedIn to ask for help reaching the appropriate engineering or support team.

5. What I’m asking Cursor to investigate

Could someone from Cursor’s Cloud Agents engineering or support team please help with the following?

  1. Urgently preserve any existing data associated with the two missing Agent sessions before automated cleanup or retention processes could affect recovery.

  2. Locate the original Cloud Agent conversation and associated development environment using the account history and Git commit identifiers.

  3. Determine whether the original workspace, filesystem, Git object database, reflogs and uncommitted source files can be restored or exported.

  4. Investigate any retained copies of the original product-image and branding files, including untracked assets.

  5. Determine why the two conversations disappeared from Agent history while older conversations remain accessible.

  6. Locate the replacement reconstruction session as a secondary recovery option.

  7. Confirm whether a recoverable workspace snapshot or backup exists and how it could be restored.

6. Business impact and urgency

This represents several weeks of substantial development work for a business preparing to launch an ecommerce website.

I have been able to recover some visual reference packages, original images and older website code independently, but the actual October V2 application and locally committed Git history remain inaccessible.

Reconstructing the project from historical instructions would involve considerable additional development and testing and would not guarantee an exact restoration.

My immediate priority is preserving and recovering the original development environment, rather than rebuilding another approximation.

7. Assistance requested

Could a Cursor staff member please acknowledge this issue and help escalate it to the appropriate Cloud Agents engineering team?

I would particularly appreciate confirmation that the original environment data can be investigated and, if it still exists, preserved while the case is reviewed.

I can provide privately:

  • Cursor account details
  • GitLab repository details
  • Complete Git commit hashes
  • Investigation Agent URL and IDs
  • Forensic recovery report
  • Support email correspondence
  • Screenshots of the original working website
  • Details of the original image assets

Any assistance would be greatly appreciated. This has had a significant impact on our development project, and I’m concerned about the possibility of losing recoverable data through retention or cleanup.

Thank you.

Steps to Reproduce

  1. Open the Cursor desktop application on Windows 11, signed into the account used for PEIGIAN development.

  2. Access the PEIGIAN project and its existing Cloud Agent conversations. The original development session contained the branch cursor/peigian-v2-implementation, multiple locally committed checkpoints and uncommitted Phase 7 work.

  3. On 17 October 2026, following a reconnection, the original Cloud Agent development environment was no longer accessible. A replacement Agent could not locate the previously available branch or Git commits.

  4. A second Cloud Agent attempted to reconstruct the project using previous conversation transcripts.

  5. During subsequent navigation in Cursor Desktop, including use of Ctrl+E, both the original development conversation and reconstruction conversation disappeared from the Agent history. I cannot establish that the shortcut caused the disappearance.

  6. Close and reopen Cursor Desktop, return to the same repository and review the Cloud Agent history.

  7. The two development sessions remain missing. Older conversations and a newly created forensic investigation Agent are visible, but the original development environments and their Git data remain inaccessible.

Reproducibility: This is an observed incident, not a reliably reproducible sequence. The missing sessions have remained inaccessible since 17 October 2026.

Expected Behavior

Existing Cloud Agent conversations should remain accessible through Cursor Desktop or the web interface after reconnection, navigation, application restart or environment switching.

Previously created development workspaces should remain accessible according to Cursor’s applicable retention policies, including locally committed Git history and uncommitted project files.

If a development environment has expired or become unavailable, Cursor should clearly communicate its status and provide a way to identify the original session and investigate recovery.

In this case, I expect to be able to reopen the original PEIGIAN V2 development session and retrieve its source code, Git commits and associated assets, or receive confirmation from Cursor Support about whether the environment can be restored.

Operating System

Windows 10/11

Version Information

Version: 3.25.6 (user setup)
VS Code Extension API: 1.128.0
Commit: f0df777c412b670d09e3eaf214967d779e67c080
Date: 2026-10-14T22:46:28.448Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT arm64 10.0.26200

For AI issues: which model did you use?

Cursor Cloud Agents, using the Auto model selection where applicable.

The exact model used in the original and replacement development sessions cannot currently be confirmed because both conversations have disappeared from the Agent history.

Additional Information

This is an ongoing data-recovery incident affecting two missing Cursor Cloud Agent sessions.

I have already emailed Cursor Support, including [email protected] and [email protected], requesting urgent preservation and recovery of the original development environment. As of 21 October 2026, I have not received a response or support reference.

The original development branch was cursor/peigian-v2-implementation.

Last confirmed Phase 6 commit:
a807fe84b46de4793d03f8c9537c84f1622b339c

Previous Phase 5 commit:
b15f044ca86fed22a37392d996446affe1ec1cf6

These commits were stored locally within the original Cloud Agent environment and had not been pushed to GitLab.

A separate forensic Cloud Agent investigation found that the original sessions, workspace and Git history were inaccessible from the newly created environment. It could not inspect Cursor’s backend storage or determine whether recoverable snapshots still exist.

Please urgently escalate this issue to the Cloud Agents engineering team and preserve any existing original workspace data, session records, Git objects, uncommitted source files and associated assets before automated cleanup or retention processes affect their recoverability.

I can provide the complete forensic investigation report and private account/session identifiers directly to authorised Cursor staff.

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey @Peigian,

The original development conversation hasn’t been deleted. It was archived, which hides it from the Agents sidebar. To bring it back, open the Agents Window, switch the sidebar filter to Archived, then right-click the conversation and choose Unarchive. (Ctrl+Shift+E is the shortcut that archives the selected agent, so it sits right next to Ctrl+E.)

The cloud machine behind it is a different story. A Cloud Agent’s machine is recycled automatically after the run has been idle for a while (see how Cloud Agent data is stored). By the time the conversation picked up again on 17 October, its original machine had already been recycled, so the follow-up started on a fresh machine with a fresh clone of your GitLab repo. The cursor/peigian-v2-implementation branch and its commits only ever existed on the original machine, which is why they weren’t there. The reconstruction attempt you saw ran inside that same conversation, on the new machine.

What is kept is the full conversation, including the file contents the agent wrote and edited along the way, so once it’s unarchived you can scroll back through it to recover text source files. Binary files such as the product photos aren’t stored in the conversation, so your design archives are the right source for those.

Going forward, ask the agent to push its branch to GitLab after each checkpoint. Work that hasn’t been pushed lives only on the agent’s machine.

8

Hi, Collin thanks for getting back to me and explaining what happened.

I’ve now managed to locate the original PEIGIAN V2 development conversation and can confirm that the historical messages and code changes are still accessible. This is reassuring, and I appreciate your help with that.

However, the main issue remains the loss of the original development workspace.

I’ve reconnected the original conversation and checked the Git repository. Unfortunately, the workspace is now running from the older commit 4fb065347e271799ca716b386b2c7af15ea76d77.

Our original development branch was cursor/peigian-v2-implementation, with the last completed Phase 6 checkpoint at:

a807fe84b46de4793d03f8c9537c84f1622b339c

I’ve confirmed that neither this commit nor the previous Phase 5 checkpoint is available in the reconnected workspace. The original Phase 7 source files are also missing.

Before we begin reconstructing several weeks of development work, could you please clarify whether Cursor can investigate any retained snapshots or backups of the original Cloud Agent environment?

Having reviewed Cursor’s documentation regarding Cloud Agent data storage, I understand that environment snapshots may be retained for a period after inactivity.

Would it be possible for your engineering team to check whether:

  1. Any snapshots or backups of the original development environment still exist.

  2. A previous workspace state containing our local Git commits and uncommitted source files can be restored.

  3. The original files could be exported into a separate environment, even if the original machine has been recycled.

  4. Any recoverable data can be preserved while this is investigated.

I understand that the conversation history has been retained and that the original machine was recycled, but I’d appreciate confirmation that the available recovery options have been checked before we accept that the development files are permanently lost.

We have recovered some original design assets from independent backups, but the actual October website source and Git history are still missing.

I’m happy to provide the original session details and any additional identifiers privately.

Thanks again for your assistance.

10

Hi @Peigian,

Glad the conversation is back, and thanks for confirming what the reconnected workspace looks like.

We don’t have a snapshot of that machine on record that we can access and restore, unfortunately.