microsoft / microsoft/vscode-remote-release
Allow configuring memory-tool storage path for Dev Container persistence
Open
@chrmarti is already working on this.
Since Apr 23, 2026.
containers
feature-request
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Problem
The memory-tool stores data at a hardcoded path inside the container:
~/.vscode-server/data/User/globalStorage/github.copilot-chat/memory-tool/
In Dev Containers, this path is wiped on every container rebuild, destroying all saved memories — despite the docs saying memories "persist across sessions."
Request
Add a setting to configure the storage path:
"github.copilot.chat.memoryStoragePath": "/some/persistent/path"
This would allow Dev Container users to point memory storage to a bind-mounted host directory, making memories actually persistent.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.