Composer Chat History Lost After Restart — No Way to Restore Context

Bug Reports
1

Hi Cursor team,

There’s a serious issue with Composer chat windows losing all context after simply closing and reopening Cursor — not just after a full computer shutdown.

:bug: Bug Description

Whether I shut down my system or just quit and relaunch Cursor, the same issue occurs:

  1. I work in a Composer chat window for several prompts (e.g., building a module or automation).

  2. I save and close Cursor (or shut down my machine).

  3. Upon reopening Cursor:

    • A fresh, empty chat opens automatically

    • There is no reference to my previous Composer session

    • Attempts to access Composer history result in:

      • A loading spinner
      • Then I’m dropped into a new, blank chat

  4. I can’t even @ the old Composer to pull it back into the conversation — the thread is effectively gone.

:collision: Impact

  • Critical loss of context for mid-session development work
  • Can’t resume tasks where I left off
  • Forced to manually reconstruct context and restart conversations
  • Undermines trust in Cursor as a persistent dev workspace

:test_tube: Expected Behavior

  • Composer chat should persist across app restarts, not just within a single runtime session
  • Users should be able to open previous Composer chats from history
  • At minimum, @-mentioning a prior Composer should reconnect to their memory or allow context rehydration

:clipboard: Notes

  • Issue persists across several recent Cursor versions
  • Occurs on both macOS and Windows
  • Easy to reproduce: close Cursor → reopen → Composer gone

This bug makes Composer almost unusable for multi-session workflows. Let me know if you need logs or a screen recording — I can trigger this 100% of the time.

Thanks!

1 Like
2

@danperks