Request : CMD installation for Windows user #13

Activity

1. dezgit2025 commented on Apr 30, 2026

   

   dezgit2025

   on Apr 30, 2026

   Owner

   More actions

   saurabhssgaikwad
   i put case in with github copilot cli team. can you also open an issue (helps to amplify). you can use copilot cli to do it for you just prompt it to open an issue on https://github.com/features/copilot/cli. missing session.db issue not resolved by /experimenta. 2. also try to use a more powerful model use gpt5.4 /experimental. use /model to change to stronger reasoning model.. then use /experimental...
2. dezgit2025 commented on Apr 30, 2026

   

   dezgit2025

   on Apr 30, 2026

   Owner

   More actions

   @saurabhssgaikwad — Heads up on some changes in v0.3.0 that may help your situation:

   What changed

   1. Copilot CLI is no longer listed as a hard prerequisite. The install guide (deploy/install.md) now shows two paths:

      • Option A: Copilot CLI (richest data, SQLite backend)
      • Option B: VS Code / JetBrains / Neovim (file-backed JSONL sessions)

      If you have VS Code with Copilot extension on Windows, the VS Code backend reads chat sessions directly — no /experimental flag needed, no .db file required.

   2. New agent-runnable setup guide: deploy/install-other-backends.md walks through enabling VS Code sessions step-by-step (detection, env var setup, verification).

   3. Per-provider health check: session-recall health --provider vscode now shows 4 diagnostic dimensions so you can verify each backend independently.

   What's still missing for your case

   Windows native (non-WSL) CMD support is not yet implemented — the file-backend auto-detection paths are Linux/macOS/WSL only. If you're running VS Code on native Windows, the auto-detect paths won't match. You'd need to set SESSION_RECALL_VSCODE_STORAGE manually to your VS Code workspace storage path (usually %APPDATA%\Code\User\workspaceStorage):

   # In WSL or Git Bash:
   export SESSION_RECALL_VSCODE_STORAGE="/mnt/c/Users/YourName/AppData/Roaming/Code/User/workspaceStorage"
   export SESSION_RECALL_ENABLE_FILE_BACKENDS=1
   session-recall health --provider vscode

   I've noted Windows native path detection as a future enhancement. Would the WSL + VS Code backend workaround help your use case in the meantime?
3. dezgit2025 commented on May 1, 2026

   

   dezgit2025

   on May 1, 2026

   Owner

   More actions

   please use try using a stronger reasoning model like gpt5.4 and try /experimental again.
4. dezgit2025

   closed this as completedon May 1, 2026