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
{{ message }}
Repository navigation
[Bug] database not found. Copilot changed storage format from session-store.db to session-state folder #19
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:
Thanks for the detailed report, @ductaiii. The session-state fallback shipped in v0.2.0 — after the 0.1.0 you were running — so upgrading with pip install -U auto-memory (0.5.1 on PyPI) should resolve the "database not found" error.
#29 adds a regression test for exactly this case and improves handling of WSL-style session paths on Windows, and CI now runs on Windows too. Closing — please reopen if you still see it on the latest version.
Activity
erSpell commentedon Sep 8, 2026
I’m working on this and have a local fix under test for the session-state fallback case.
dezgit2025 commentedon Sep 30, 2026
Thanks for the detailed report, @ductaiii. The
session-statefallback shipped in v0.2.0 — after the 0.1.0 you were running — so upgrading withpip install -U auto-memory(0.5.1 on PyPI) should resolve the "database not found" error.#29 adds a regression test for exactly this case and improves handling of WSL-style session paths on Windows, and CI now runs on Windows too. Closing — please reopen if you still see it on the latest version.