Describe the bug
The auto-memory tool expects to find a single SQLite database file named session-store.db inside the .copilot directory. However, in recent versions of GitHub Copilot, this file no longer exists. The local storage structure has changed, and there is now a session-state folder instead of the .db file.
To reproduce
Steps to reproduce:
- Run
pip install auto-memory
- Run the command
session-recall health in the terminal
- See error indicating that the database cannot be found.
Expected behavior
The tool should successfully locate the new Copilot chat history storage (e.g., the session-state folder or related JSON files) and report a healthy status, allowing the extraction of memory.
Actual behavior
The tool throws an error because it is looking for a deprecated file path.
Error message: error: database not found: C:\Users\tainguyen\.copilot\session-store.db
Environment
- OS: Windows 11
- Python version: [3.11]
- auto-memory version: [0.1.0]
- Copilot CLI version: [e.g. 1.0.17]
session-recall health output
error: database not found: C:\Users\tainguyen\.copilot\session-store.db
error: database not found: C:\Users\tainguyen\.copilot\session-store.db
Additional context
Looking inside my C:\Users\tainguyen\.copilot\ directory, the session-store.db file is completely missing. Instead, I see the following structure:
- A folder named session-state
- A folder named ide
command-history-state.json
vscode.session.metadata.cache.json

Describe the bug
The
auto-memorytool expects to find a single SQLite database file namedsession-store.dbinside the.copilotdirectory. However, in recent versions of GitHub Copilot, this file no longer exists. The local storage structure has changed, and there is now asession-statefolder instead of the .db file.To reproduce
Steps to reproduce:
pip install auto-memorysession-recall healthin the terminalExpected behavior
The tool should successfully locate the new Copilot chat history storage (e.g., the
session-statefolder or related JSON files) and report a healthy status, allowing the extraction of memory.Actual behavior
The tool throws an error because it is looking for a deprecated file path.
Error message:
error: database not found: C:\Users\tainguyen\.copilot\session-store.dbEnvironment
session-recall health output
Additional context
Looking inside my
C:\Users\tainguyen\.copilot\directory, thesession-store.dbfile is completely missing. Instead, I see the following structure:command-history-state.jsonvscode.session.metadata.cache.json