# Make Project Chats and Context Portable (Store Them with the Project)

**URL:** <https://forum.cursor.com/t/make-project-chats-and-context-portable-store-them-with-the-project/167255>\
**Category:** Feature Requests\
**Tags:** context, chat\
**Created:** [August 2, 2026, 12:22pm UTC](https://forum.cursor.com/t/make-project-chats-and-context-portable-store-them-with-the-project/167255 "2026-08-02T12:22:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![svda](https://avatars.discourse-cdn.com/v4/letter/s/43a26b/32.png) [@svda](https://forum.cursor.com/u/svda)\
**Post date:** [August 2, 2026, 12:22pm UTC](https://forum.cursor.com/t/make-project-chats-and-context-portable-store-them-with-the-project/167255/1 "2026-08-02T12:22:03Z")

</div>

### Feature request for product/service

Cursor IDE

### Describe the request

# Feature Request: Make Project Chats and Context Portable (Store Them with the Project)

Currently, Cursor stores project-specific chats, context, and other metadata in the user profile and associates them with the project’s absolute filesystem path.

This causes a significant usability issue.

## Problem

If the project is moved to another location—for example:

- cloned into a different directory,
- moved to another drive,
- opened from a different workspace,
- synchronized between multiple computers,

Cursor treats it as a completely new project.

As a result:

- chat history is lost;
- project context is lost;
- previous AI conversations are no longer available;
- the project effectively starts from scratch.

The project identity should not depend solely on its absolute filesystem path.

## Proposed Solution

Store project-specific data inside the project itself (for example, in a dedicated `.cursor/` directory) instead of tying it to the user’s profile and the project’s location.

This would make the project portable:

- moving the project would preserve its chat history;
- AI context would remain available regardless of where the project is located;
- sharing or synchronizing a project between machines would preserve the full development context.

Alternatively, Cursor could use a persistent project identifier stored inside the project directory while keeping metadata elsewhere. The important part is that project identity should survive path changes.

## Benefits

- Portable project history.
- Consistent AI context after moving projects.
- Better collaboration between multiple machines.
- Easier backups and project synchronization.
- No accidental loss of chat history when a project directory changes.

A project’s identity should be based on the project itself, not on the absolute path where it happens to be stored.

---

<div class="post-metadata">

**Author:** ![kevinn](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kevinn/32/101206_2.png) [@kevinn](https://forum.cursor.com/u/kevinn)\
**Post date:** [September 2, 2026, 5:14pm UTC](https://forum.cursor.com/t/make-project-chats-and-context-portable-store-them-with-the-project/167255/8 "2026-09-02T17:14:56Z")

</div>

Thanks for writing this up. Local chats stay on the machine and are tied to the workspace path, so a move, clone, or another computer looks like a new project. The older chats are still on disk; they just no longer attach to the new location. We’ve let the team know, and I’ll post here when there’s an update. If you only moved the folder on the same machine, opening it from the original path should bring the history back.