Repository navigation
[Bug] Support Copilot CLI 1.0.34 session-state DB schema (session-store.db no longer present) #3
Description
Describe the bug
auto-memory appears incompatible with the current Copilot CLI storage format on my machine. session-recall expects a database at ~/.copilot/session-store.db, but that file is not created. A newer Copilot DB exists under ~/.copilot/session-state/.../session.db, but it does not contain the tables auto-memory expects.
To reproduce
Steps to reproduce:
- Install auto-memory 0.1.0 (uv tool install --force --editable . from repo root).
- Run session-recall health.
- Run session-recall schema-check.
- Observe missing database error for ~/.copilot/session-store.db.
- (Optional) Point SESSION_RECALL_DB to ~/.copilot/session-state//session.db and run session-recall schema-check.
- Observe schema drift/missing expected tables.
Expected behavior
session-recall should find the active Copilot session database and return valid health/schema results, or document and handle the current Copilot CLI DB layout.
Actual behavior
session-recall health and session-recall schema-check fail against default path with:
error: database not found: /Users/username/.copilot/session-store.db
When SESSION_RECALL_DB is set to the discovered Copilot DB path, schema-check reports missing tables:
sessions, turns, session_files, session_refs, checkpoints
Environment
- OS: macOS 15.7.3 (24G419)
- Python version: 3.10.10
- auto-memory version: 0.1.0
- Copilot CLI version: 1.0.34
session-recall health output
error: database not found: /Users/username/.copilot/session-store.db
error: database not found: /Users/username/.copilot/session-store.db
EXIT:4
Additional context
Found Copilot DB at: /Users/username/.copilot/session-state//session.db
Running health with SESSION_RECALL_DB set to that path exits 0 but reports RED schema integrity and no such table: sessions.
sqlite tables in that DB are only: todo_deps, todos.
This suggests a Copilot CLI schema/storage change that auto-memory may not yet support.
Activity
dezgit2025 commentedon Apr 22, 2026
I think there selection mode where the db is stored when you start. i think you need to pick global user location like ~/.copilot/session-store.db.. the only way i think it might reprompt you i don't see ms docs. is if you close copilot cli and temporailry move the current db. it should recreate a new one. This is just suggestions since there no official docs i can find on ms docs about chaning session db locations.
dezgit2025 commentedon Apr 22, 2026
what os are you running windows?
mpowelltech commentedon Apr 22, 2026
Running macOS.
I ran the pip install command and it showed success, then ran the session-recall health which immediately failed saying the db didn’t exist. Pointed copilot at the deploy/install.md file too with no success.
There was no selection mode option when installing this or copilot cli. They both just installed with no further setup prompt.
BrttClne22 commentedon Apr 22, 2026
I'm having the same issue on Windows 11 pro I believe the CLI version is 1.0.34. I can check when I get home
hmawla commentedon Apr 23, 2026
I think you should run
/experimental onin copilot to enable the use and creation of session-store.db file.This enables experimental features, including:
SESSION_STORE - Enable SQLite-based session store for cross-session history, file tracking, and searchsc-rsayad commentedon Apr 23, 2026
Why isn't this mentioned at all in the README , Thanks this may work.
lab34 commentedon Apr 23, 2026
Perfect !
This solve my problem of "error: database not found: /home/username/.copilot/session-store.db" on W11 + WSL2 + CLI 1.0.34
jshessen commentedon Apr 23, 2026
I think the use of
/experimentalis certainly useful.One of the challenges I was trying to address with #5 was the proliferation of where sessions can be stored across Copilot CLI (both methods JSONL and DB), VSCode etc. Depending upon where I initiate my session (CLI, IDE, Cloud), the storage container differs, but trying to pull it all back together in a useful way was the intent.
dezgit2025 commentedon Apr 23, 2026
[hmawla] thanks added to README...
dezgit2025 commentedon Apr 23, 2026
[jshessen].
The only issue i see is i would have to store the session in the Azure cloud. How many folks would do use Azure? it certainly not hard to do it Azure since copilot cli is understand Azure pretty well, let me create a poll in disucssion to gauge the interest... fair?
dezgit2025 commentedon Apr 23, 2026
[jshessen]. are you running this muliple laptops? or in the cloud too? Trying to understand the use case.
dezgit2025 commentedon Apr 23, 2026
i will follow up with MS Copilot CLI Team about this. /experimental flag issue db work around.
jshessen commentedon Apr 23, 2026
this is a local machine -- where most engagements are made through a VS Code IDE ... in the default VS Code session scenario, these are written to
~/.config/Code/User/workspaceStorage/**/chatSessions/*.jsonlIf I modify the selection away from a VS Code (aka Local) to say Copilot CLI the sessions are now being written to
~/.copilot/session-state/*/events.jsonlVS Code has been updated to read from both of these locations and show both session files in the Sessions sidebar
Even if executed native with the Copilot CLI
`[jshessen@Unity ~] $ copilot version
GitHub Copilot CLI 1.0.34
You are running the latest version.
[jshessen@Unity ~] $ cd .copilot
[jshessen@Unity .copilot] $ ls
agents command-history-state.json.bak copilot-instructions.md logs scripts skills
command-history-state.json config.json ide restart session-state
[jshessen@Unity .copilot] $ cd session-state/
[jshessen@Unity session-state] $ ls -la
total 0
drwx------. 1 jshessen jshessen 1368 Apr 22 14:11 .
drwx------. 1 jshessen jshessen 272 Apr 22 16:21 ..
drwx------. 1 jshessen jshessen 76 Apr 22 11:47 f22892c1-f9c1-4dee-8388-87d557ff8f04
drwx------. 1 jshessen jshessen 140 Apr 14 14:27 f57bc62f-c52c-4d4b-aed2-bc2947a50618
[jshessen@Unity session-state] $ `
jshessen commentedon Apr 23, 2026
here is a set of calls using this code base pulling from both interaction sets
Step 1 — Schema check (all providers)
✅ Schema checks passed for active provider(s) - cli: OK (session-state-or-sqlite) - vscode: OK (file)Step 2 — Health check (provider-fallback mode)
{ "overall_score": 10.0, "dims": [ { "name": "SQLite Health Core", "zone": "CALIBRATING", "score": null, "detail": "session-store.db unavailable; running provider compatibility health", "hint": "Set SESSION_RECALL_DB if SQLite storage exists on this machine." }, { "name": "Provider:cli", "zone": "GREEN", "score": 10.0, "detail": "13 recent sessions detected", "hint": "" }, { "name": "Provider:vscode", "zone": "GREEN", "score": 10.0, "detail": "20 recent sessions detected", "hint": "" } ], "providers": ["cli", "vscode"], "storage_mode": "provider-fallback", "top_hints": [ "Set SESSION_RECALL_DB if SQLite storage exists on this machine." ] }Step 3 — Repository/workspace discovery
Step 4 — Include local (non-GitHub) workspaces
Step 5 — List sessions (all providers, last 14 days)
Step 6 — List (VS Code provider only)
Step 7 — List (CLI provider only)
Step 8 — Cross-provider search term frequency
Find terms with hits in both providers to use for the comparison in steps 9–11.
Step 9 — Search: VS Code provider
{ "query": "repo", "repo": "jshessen/auto-memory", "count": 5, "results": [ { "provider": "vscode", "session_id": "vscode:5", "session_id_full": "vscode:5564...ea04", "source_type": "turn", "summary": "I'm experiencing this issue based upon where memory lives depending upon the way AI is being called:", "repository": "unknown", "date": "2026-04-23", "content": "..." }, { "provider": "vscode", "session_id": "vscode:5", "source_type": "turn", "summary": "I'm experiencing this issue based upon where memory lives depending upon the way AI is being called:", "repository": "unknown", "date": "2026-04-23", "content": "2 would be useful ... as ideally we should be able to say show found session repositories like\n\nshared-memory repos\n" }, { "provider": "vscode", "session_id": "vscode:5", "source_type": "turn", "date": "2026-04-23", "content": "so if i list repos ... i get a list, and if i\n" }, { "provider": "vscode", "session_id": "vscode:5", "source_type": "turn", "date": "2026-04-23", "content": "so if i list repos ... i get a list, and if i ask for a list, i would have expected more in the list to align with the repos in structure and in counts\n\n(.venv) [jshessen@unity auto-memory] $ session-recall repos --include-local\n..." }, { "provider": "vscode", "session_id": "vscode:5", "source_type": "turn", "date": "2026-04-23", "content": "can you please process to understand the intended benefits ... and ensure our code is not just \"finding\" session history, but using it correctly within the context of the intent of this repo?\n" } ] }Step 10 — Search: CLI provider
{ "query": "repo", "repo": "all", "count": 5, "results": [ { "provider": "cli", "session_id": "b43bfb6b", "source_type": "turn", "summary": "can you fix the broken skills?", "repository": "local:/home/<user>/.config/squad", "date": "2026-04-22", "content": "I've likely been fixing the wrong layer: `/skills` is probably reading the global skill store under `~/.copilot/skills`, not just this repo's `.squad/skills`. I'm checking that store for the same corruption now." }, { "provider": "cli", "session_id": "b15c112d", "source_type": "turn", "summary": "from the ~/squad-export.json file", "repository": "local:/home/<user>/.config/squad", "date": "2026-04-22", "content": "<skill-context name=\"init-mode\">\nBase directory for this skill: ~/.copilot/skills/init-mode\n..." }, { "provider": "cli", "session_id": "10efd10e", "source_type": "turn", "summary": "pwd", "repository": "local:/home/<user>", "date": "2026-04-22", "content": "<skill-context name=\"init-mode\">..." }, { "provider": "cli", "session_id": "babd24ea", "source_type": "turn", "summary": "import ~/squad-export.json", "repository": "local:/home/<user>", "date": "2026-04-22", "content": "<skill-context name=\"init-mode\">..." }, { "provider": "cli", "session_id": "3e3c38ce", "source_type": "turn", "summary": "init --global", "repository": "local:/home/<user>", "date": "2026-04-22", "content": "<skill-context name=\"init-mode\">..." } ] }Step 11 — Search: all providers combined
{ "query": "repo", "repo": "all", "count": 10, "results": [ { "provider": "vscode", "session_id": "vscode:5", "date": "2026-04-23", "summary": "I'm experiencing this issue based upon where memory lives depending upon the way AI is being called:" }, { "provider": "vscode", "session_id": "vscode:5", "date": "2026-04-23", "content": "2 would be useful ... shared-memory repos" }, { "provider": "vscode", "session_id": "vscode:5", "date": "2026-04-23", "content": "so if i list repos ..." }, { "provider": "vscode", "session_id": "vscode:5", "date": "2026-04-23", "content": "so if i list repos ... i would have expected more in the list ..." }, { "provider": "vscode", "session_id": "vscode:5", "date": "2026-04-23", "content": "can you please process to understand the intended benefits ..." }, { "provider": "cli", "session_id": "b43bfb6b", "date": "2026-04-22", "repository": "local:/home/<user>/.config/squad", "summary": "can you fix the broken skills?" }, { "provider": "cli", "session_id": "b15c112d", "date": "2026-04-22", "repository": "local:/home/<user>/.config/squad", "summary": "from the ~/squad-export.json file" }, { "provider": "cli", "session_id": "10efd10e", "date": "2026-04-22", "repository": "local:/home/<user>", "summary": "pwd" }, { "provider": "cli", "session_id": "babd24ea", "date": "2026-04-22", "repository": "local:/home/<user>", "summary": "import ~/squad-export.json" }, { "provider": "cli", "session_id": "3e3c38ce", "date": "2026-04-22", "repository": "local:/home/<user>", "summary": "init --global" } ] }feat: v0.2.0 — multi-storage recall, security hardening, token budgets (
feat: v0.2.0 — multi-storage recall, security hardening, token budgets (