You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug Description
In the SpecStory extension for VSCode, inside the .specstory folder, there is a history folder where chat history from GitHub Copilot Chat prompts is saved as .md files. However, when opening a new chat via the plus button in GitHub Copilot Chat and entering new prompts, the extension creates a new .md file but replaces the old .md history file instead of preserving it. This means the previous chat history file is deleted or overwritten.
To Reproduce
Open VSCode with the SpecStory extension installed.
Use GitHub Copilot Chat and enter some prompts. The chat history gets saved as .md files inside .specstory/history.
Click the plus button in GitHub Copilot Chat to open a new chat.
Enter new prompts. A new .md file is created but the previous .md file is overwritten or replaced.
Expected behavior
Each chat session should create a unique .md history file. Opening a new chat or clearing chat history should not delete or replace existing .md history files. All previous chat histories should remain intact and accessible.
Additional context
This issue leads to data loss of previous chat histories, which is a critical problem for users relying on persistent session records for documentation or reference.
The text was updated successfully, but these errors were encountered:
Bug Description
In the SpecStory extension for VSCode, inside the .specstory folder, there is a history folder where chat history from GitHub Copilot Chat prompts is saved as .md files. However, when opening a new chat via the plus button in GitHub Copilot Chat and entering new prompts, the extension creates a new .md file but replaces the old .md history file instead of preserving it. This means the previous chat history file is deleted or overwritten.
To Reproduce
Open VSCode with the SpecStory extension installed.
Use GitHub Copilot Chat and enter some prompts. The chat history gets saved as .md files inside .specstory/history.
Click the plus button in GitHub Copilot Chat to open a new chat.
Enter new prompts. A new .md file is created but the previous .md file is overwritten or replaced.
Expected behavior
Each chat session should create a unique .md history file. Opening a new chat or clearing chat history should not delete or replace existing .md history files. All previous chat histories should remain intact and accessible.
System Information
SpecStory for GitHub Copilot (VSCode): Yes
Version: 1.100.2 (user setup)
Commit: 848b80aeb52026648a8ff9f7c45a9b0a80641e2e
Date: 2025-05-14T21:47:40.416Z
Electron: 34.5.1
ElectronBuildId: 11369351
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22631
Additional context
This issue leads to data loss of previous chat histories, which is a critical problem for users relying on persistent session records for documentation or reference.
The text was updated successfully, but these errors were encountered: