[FEATURE] Allow renaming or moving a project folder while persisting history for sessions

Resolved 💬 4 comments Opened May 3, 2026 by claell Closed Jun 3, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

This is a pretty important feature for UX. And also mirrored on other products, like Codex: https://github.com/openai/codex/issues/15347, or GitHub Copilot: https://github.com/microsoft/vscode/issues/313970, or OpenCode: https://github.com/anomalyco/opencode/issues/25625

Similar requests have been opened, but seem to got closed due to inactivity: #1516, #9084, #9306

Basically, as a user, I oftentimes don't already know where the folder I am working in will be finally staying. Sometimes, I might just create a folder on the Desktop, and then work from there. Later decide that it should live somewhere else. Sometimes, I might also want to do bigger restructuring of existing folders.

Currently, this seems to not keep the chat session history.

As a user, this is unwanted, and can prevent me from moving stuff around. Of course, one can probably somehow later have a script running that will point the existing session files to the new location as a workaround. But this is not nice.

Proposed Solution

So I hope that there can be a solution for this. For easy renaming/moving: Maybe have a context menu entry or general option for this, that does exactly such things automatically for me? Rename the folder and take care of everything?

For the future, one could also foresee something in addition, like (locally) fingerprinting a folder to easily find it again (maybe also storing some ID inside it), support for "orphaned" sessions, ...

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

_No response_

Additional Context

I don't know whether this tracker also is for the GUI application. Regardless, this would of course also be very useful to have in there.

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗